Most engineers who apply for the DevOps & Reliability standard can define a service level objective. Far fewer can describe a time an error budget changed what their team did the following week. That second thing is what we now assess.
From definition to decision
Reliability targets have been one of the six capability areas since the standard launched, alongside delivery flow, automation, observability, on-call practice and incident review. The capability description has always said that SLOs and error budgets should be used as real decision tools. In practice, many portfolios stopped at the definition: a dashboard, a target, a percentage. The council has tightened the guidance so that evidence must show a budget being spent, protected or renegotiated.
Good evidence tends to look like one of these:
- A release freeze, or a deliberate slowing of change, triggered because the budget was exhausted, and what the team did instead.
- A decision to spend remaining budget on a risky migration or experiment, made knowingly.
- An SLO you revised because it did not reflect what users actually experienced.
- A conversation with product owners where the budget settled a disagreement about priorities.
An error budget nobody has ever acted on is just a number on a wall. We want to see the week it cost someone something.
How expectations rise through the levels
At BIPS Practitioner, where you maintain delivery and monitoring for a service under review, we look for understanding. Can you explain the SLO for your service and what happens when it is breached? At BIPS Professional, where you own a service’s reliability, the budget should visibly shape decisions you made.
At BIPS Specialist, leading a specialism such as SRE or release engineering, we expect you to have designed the policy others follow. At BIPS Expert, where you set reliability standards across an organisation, you should be able to show how targets were agreed with the business and not only with engineers.
In the professional discussion
Assessors will ask about the trade-offs, not the arithmetic. Why that target and not a stricter one? Who argued against it? What did the team give up to protect it? Candidates who have genuinely lived with an error budget tend to find these the easiest questions of the whole discussion, because the answers come from memory rather than from a textbook.
If your team uses SLOs informally, that still counts. What matters is that a real decision followed from them, and that you can explain your part in it.