Why English? | Writing a Service Level Agreement Through Service Scope, Users, Availability, Performance, Support, Incidents, Measurement, Remedies and Review

ORIENTATION

What this guide covers

Current fact check

Checked on 8 November 2026, current GOV.UK digital guidance defined SLAs through a named service and expected performance, advised teams to choose indicators around user needs, and discussed availability, latency and throughput. The GOV.UK Service Manual also cautioned that credits for missed uptime or response targets may not offset the effect of downtime on users.

What this guide does not cover

This article owns the reader task of writing a service level agreement and its measurement logic. It does not own the full contract, procurement specification, service design, technical architecture, incident response plan, disaster recovery plan, pricing schedule, regulatory obligation or final commercial approval.

Worked example

Every chapter returns to a fictional learning platform used by students to reach course materials, submit practice and contact support during published service hours. It is fictional, low-stakes and educational; it does not report a real school, clinical decision or guaranteed outcome.

Warm up with eduKate’s guides to explaining scientific evidence and asking better questions in class.

CHAPTER 1 OF 15

1. State the Agreement's Purpose and Parties

Back to contents

Why this move matters

Name provider, users or customer, contract context, decision owners, effective date and hierarchy of documents.

Start with the user's service outcome

Name provider, users or customer, contract context, decision owners, effective date and hierarchy of documents. In the fictional service, The school contracts a platform provider while staff and learners use the service. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

An SLA cannot silently override higher contractual or legal terms. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “State the Agreement's Purpose and Parties”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 2 OF 15

2. Define the Service and User Outcome

Back to contents

Why this move matters

Describe the service, critical functions, users, channels, locations, data and outcome supported.

Start with the user's service outcome

Describe the service, critical functions, users, channels, locations, data and outcome supported. In the fictional service, Students must open materials, submit practice and see confirmation during stated hours. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

A component can be healthy while the user-facing service fails. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Define the Service and User Outcome”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 3 OF 15

3. Set Boundaries, Hours and Dependencies

Back to contents

Why this move matters

List included and excluded functions, support hours, maintenance, third parties, networks, identity services and customer duties.

Start with the user's service outcome

List included and excluded functions, support hours, maintenance, third parties, networks, identity services and customer duties. In the fictional service, The SLA distinguishes the learning platform from a student's home internet connection. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

Exclusions can make a target meaningless if they swallow normal failure. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Set Boundaries, Hours and Dependencies”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 4 OF 15

4. Classify Criticality and Service Tiers

Back to contents

Why this move matters

Define service tiers by user impact, timing, population, safety, regulatory or operational consequence.

Start with the user's service outcome

Define service tiers by user impact, timing, population, safety, regulatory or operational consequence. In the fictional service, Assessment submission has a stricter tier than a non-urgent profile update. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

Criticality can change during examinations or enrolment peaks. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Classify Criticality and Service Tiers”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 5 OF 15

5. Choose Service Level Indicators

Back to contents

Why this move matters

Select observable indicators for availability, latency, throughput, accuracy, queue, completion or user experience.

Start with the user's service outcome

Select observable indicators for availability, latency, throughput, accuracy, queue, completion or user experience. In the fictional service, The platform measures successful submission confirmation rather than server heartbeat alone. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

Many indicators create noise without clarifying outcomes. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Choose Service Level Indicators”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 6 OF 15

6. Write Availability and Downtime Rules

Back to contents

Why this move matters

Define available state, denominator, reporting period, planned maintenance, partial failure, failed requests and data source.

Start with the user's service outcome

Define available state, denominator, reporting period, planned maintenance, partial failure, failed requests and data source. In the fictional service, Availability counts successful access to core functions across the monthly service window. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

A monthly percentage can hide a long outage at the worst time. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Write Availability and Downtime Rules”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 7 OF 15

7. Set Performance, Capacity and Quality Targets

Back to contents

Why this move matters

Define latency percentiles, throughput, concurrency, accuracy, freshness, backlog, capacity headroom and test conditions.

Start with the user's service outcome

Define latency percentiles, throughput, concurrency, accuracy, freshness, backlog, capacity headroom and test conditions. In the fictional service, Submission acknowledgement is measured at a percentile under an agreed peak load. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

An average can conceal slow experiences for many users. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Set Performance, Capacity and Quality Targets”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 8 OF 15

8. Define Support Channels and Request Handling

Back to contents

Why this move matters

Specify authorised channels, service desk hours, acknowledgement, ownership, information required and handoff rules.

Start with the user's service outcome

Specify authorised channels, service desk hours, acknowledgement, ownership, information required and handoff rules. In the fictional service, Students use one support route and receive a case number and named next update. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

A response is not the same as a useful diagnosis or fix. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Define Support Channels and Request Handling”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 9 OF 15

9. Classify Incidents by Impact and Urgency

Back to contents

Why this move matters

Write severity criteria using functions, users, workaround, timing, data, safety and escalation thresholds.

Start with the user's service outcome

Write severity criteria using functions, users, workaround, timing, data, safety and escalation thresholds. In the fictional service, A widespread inability to submit before a deadline is classified above a cosmetic error. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

Provider labels should not ignore customer impact. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Classify Incidents by Impact and Urgency”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 10 OF 15

10. Separate Response, Update, Restoration and Resolution

Back to contents

Why this move matters

Define each clock, start and stop events, pause rules, targets, workarounds, recovery and root-cause completion.

Start with the user's service outcome

Define each clock, start and stop events, pause rules, targets, workarounds, recovery and root-cause completion. In the fictional service, The provider acknowledges quickly, updates regularly, restores service, then completes analysis later. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

Combining the clocks makes performance impossible to interpret. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Separate Response, Update, Restoration and Resolution”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 11 OF 15

11. Plan Communication and Escalation

Back to contents

Why this move matters

Set contacts, audience, frequency, channels, templates, decision authority and major-incident routes.

Start with the user's service outcome

Set contacts, audience, frequency, channels, templates, decision authority and major-incident routes. In the fictional service, Learners receive plain-language status while technical teams exchange diagnostic detail. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

More messages do not help if they repeat uncertainty without a next update. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Plan Communication and Escalation”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 12 OF 15

12. Design Measurement, Evidence and Reporting

Back to contents

Why this move matters

Define telemetry, sampling, clocks, timezones, exclusions, validation, customer evidence, dashboards and retention.

Start with the user's service outcome

Define telemetry, sampling, clocks, timezones, exclusions, validation, customer evidence, dashboards and retention. In the fictional service, Both parties can reproduce the monthly submission-success result from named logs. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

The party operating the metric should not make opaque adjustments. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Design Measurement, Evidence and Reporting”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 13 OF 15

13. Specify Remedies and Service Improvement

Back to contents

Why this move matters

Define credits or other remedies, eligibility, caps, claims, repeated failure, improvement plans and non-financial responses.

Start with the user's service outcome

Define credits or other remedies, eligibility, caps, claims, repeated failure, improvement plans and non-financial responses. In the fictional service, Repeated missed targets trigger a joint improvement plan, not only a small credit. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

A remedy may not compensate students for lost opportunity. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Specify Remedies and Service Improvement”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 14 OF 15

14. Manage Disputes, Exceptions and Changes

Back to contents

Why this move matters

Set evidence exchange, escalation, temporary waivers, emergencies, planned changes, version control and approval.

Start with the user's service outcome

Set evidence exchange, escalation, temporary waivers, emergencies, planned changes, version control and approval. In the fictional service, A temporary maintenance exception has an owner, end date and affected-user plan. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

Informal exceptions can quietly become the normal service. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Manage Disputes, Exceptions and Changes”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

CHAPTER 15 OF 15

15. Review Targets Against User Needs

Back to contents

Why this move matters

Schedule reviews of performance, cost, incidents, demand, architecture, satisfaction, accessibility and changed priorities.

Start with the user's service outcome

Schedule reviews of performance, cost, incidents, demand, architecture, satisfaction, accessibility and changed priorities. In the fictional service, The school lowers a vanity target but strengthens submission completion during peak periods. Define the user, service boundary, dependency and business consequence before choosing a percentage or response time.

Turn expectations into measurable indicators

Specify the event, numerator, denominator, clock, exclusions, data source, sample, reporting period and timezone. A target is only usable when two readers can calculate it the same way.

Connect support, incidents and recovery

Define severity, support channels, response, update, workaround, restoration, escalation and post-incident learning. Keep response time separate from restoration or resolution time.

Review value, cost and behaviour

A target can be met while the service still fails users. Test whether targets improve outcomes or merely reward attractive reporting, then record changes, exceptions, disputes and exit routes.

Student, parent and career transfer

Make one evidence card for “Review Targets Against User Needs”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports technology, education administration, service management, procurement, operations, customer support, engineering, finance, contract management and leadership without promising a grade, admission, funding decision or job.

PRACTICE LAB

Build a service level agreement decision trail

Student route

1. Choose one original report inside this guide’s scope.
2. Copy its objective and underline actor, action, context, evidence and intended decision.
3. Draw the specific reasoning chain used in this article.
4. Mark each step reported, inferred, contested or unknown.
5. Rewrite the conclusion so it preserves the narrowest important limitation.

Parent or teacher route

Ask the learner to explain turn a promise of reliable service into measurable expectations, usable support routes, honest exclusions, fair remedies and a shared method for learning from performance twice: once to a classmate and once to a method specialist. Praise a precise correction and a well-stated unknown; both show disciplined attention to evidence.

Early-career route

Create a one-page service level agreement audit with source link, date checked, scope, method logic, decisive wording, contrary evidence, limit and next action. A colleague should be able to continue without guessing.

Continue with eduKate’s guides to reading course and career information and giving useful feedback in group projects.

USEFUL NEXT READING

Connect this narrow owner to its neighbour

Read the procurement-specification guide for a related but different reader job. Return here when the question is specifically how to turn a promise of reliable service into measurable expectations, usable support routes, honest exclusions, fair remedies and a shared method for learning from performance. Use each guide for the reader task named in its heading.

For English practice across research, school and career communication, visit the Singapore English Tuition Centre learning site.

FREQUENTLY ASKED QUESTIONS

Questions students and parents often ask

What is the difference between an SLI, SLO and SLA?

An indicator is the measurement, an objective is the target, and an SLA is the documented agreement that may include targets and consequences.

Does 99.9% availability mean almost no disruption?

Not by itself. Check the period, service window, exclusions, partial failures and when downtime occurs.

Is response time the same as resolution time?

No. Response acknowledges and engages; restoration or resolution concerns service recovery or completion.

Should planned maintenance be excluded?

It can be defined separately, but the user impact, notice and limits should remain visible.

Are service credits enough?

Not always. Credits may not offset user harm; improvement, escalation and exit rights can matter.

How often should an SLA be reviewed?

At agreed intervals and after major demand, service, supplier, incident, architecture or policy changes.