Solution · Service level management
Set service levels you can keep — and prove you kept them.
A service level agreement is a promise with a number in it: how available a service will be, and how fast the team responds when it is not. Without that number, every outage becomes an argument about what good was supposed to mean.
Targets agreed in writing, before the outage, not during it.
Uptime percentages translated into downtime anyone can picture.
A report that shows what was promised and what was delivered.
The problem
Why service levels break down
Service levels usually fail in one of two ways: the target was never written down, or it was written down and nobody measured it. Both end the same way — a difficult conversation with no numbers in it.
A percentage nobody can picture
99.9% uptime sounds strong until you learn it allows over forty minutes of downtime a month. Agreeing a number without translating it into minutes is agreeing to something nobody understands.
Targets set by hope
A target copied from a vendor brochure or a larger company rarely fits a small team’s staffing or budget. When the target is unreachable, the team stops taking it seriously — and so does everyone else.
No record of what was agreed
The agreement lives in someone’s inbox, or was never written at all. When a service fails, there is nothing to point to, and the discussion starts from scratch every single time.
Measured never, reported never
Nobody tracks whether the target was met, so nobody knows until a user complains. By then the evidence is gone, and the team can neither defend its work nor show where it needs help.
The process
Five steps, and the itserva page for each
Five steps, from the promise to the proof.
- 01
Agree what “good” looks like
Write down the services covered, the targets for each, and what is excluded. An agreement that names its limits is more useful than one that pretends there are none.
- 02
Turn targets into numbers
Convert each uptime percentage into allowed downtime per week, month and year. Minutes and hours are numbers the business can argue about honestly; percentages hide the real allowance.
- 03
Price the cost of missing
Work out what an hour of downtime costs in lost revenue, wages and recovery. The number decides how much it is worth spending to avoid the next outage — and what to tell the business.
- 04
Check availability in nines
Compare availability targets side by side in nines, so the jump from three nines to four is visible as hours, not as a decimal. Small differences in the percentage are large differences in the month.
- 05
Review and report
At the end of each period, compare what was promised with what happened, and say so plainly. A short, honest report builds more trust than a perfect month nobody believed.
What’s included
Tools, templates and guides for service level management
Tool
SLA Uptime Calculator
Turn an uptime percentage into allowed downtime per week, month and year.
Product
SLA Tracker
Track uptime against target for every service, and see the downtime budget that is left.
Measure it
The four numbers worth tracking
Four numbers show whether your service levels are honest, reachable and kept. Review them with the business, not only inside the IT team.
Uptime against target
Actual availability for each service, next to the target you agreed. The gap, in minutes, is the number the business understands — not the percentage.
Downtime cost
What the downtime in the period actually cost. It turns an abstract breach into a business case for the fix, the cover, or the extra pair of hands.
MTTR
How fast the team recovers when a service fails. Recovery speed is what stands between a missed target and a kept one, and it is the number you can improve fastest.
Breaches by service
How often each service misses its target, and why. One service breaching every month is a target problem, a capacity problem, or a problem nobody has owned yet.
Frequently asked questions
What is a good SLA uptime target?
One your team can actually meet with its current staffing and budget. Start from what the service has delivered in the last few months, not from a number in a brochure, and tighten the target only when the numbers support it.
What is the difference between an SLA and an SLO?
An SLA is the agreement with the people who use the service, often with consequences if it is missed. An SLO is the internal target the team aims for, usually set a little tighter so there is room to recover before the agreement is breached.
How much downtime does 99.9% allow?
About 43 minutes a month, or just over 8 hours a year. The exact figure depends on the period you measure over, which is why the calculator shows the allowance per week, month, quarter and year.
Who should sign off an SLA?
Someone who owns the service on the business side and someone who owns it in IT. A target agreed by one side only is a wish, and it will not survive the first serious outage.
Write the agreement before the next outage.
Run the uptime calculator on the service that matters most, then put the number into the SLA template. A free workspace saves both, so the next service review starts from a written promise.