Every school cleaning contract should explain what will be cleaned, where and how often. Far fewer make it clear what happens after the school reports that something has gone wrong.
A useful service level agreement turns words such as “quickly”, “promptly” and “as soon as possible” into shared, measurable expectations. It separates acknowledgement from action, action from resolution, and resolution from proper closure.
What a school cleaning SLA should actually do
A cleaning specification and a service level agreement do different jobs.
The cleaning specification explains
- Which buildings and areas are included
- Which tasks need to be completed
- How frequently each task should happen
- How many hours or operatives are expected
- Which periodic and deep-cleaning tasks are included
The SLA explains
- How a service issue should be reported
- How quickly it should be acknowledged
- What immediate action is expected
- When the issue should be resolved
- What happens if the target is missed
The SLA does not replace the cleaning specification. It gives the school and contractor a practical way to manage exceptions when the agreed service has not been delivered or an urgent issue appears during the day.
Without that structure, contractor conversations can become frustratingly vague. The school says the response was too slow. The contractor says someone replied on the same day. Both statements may be true because nobody agreed whether the relevant target was acknowledgement, attendance, temporary containment or full resolution.
“We will respond promptly” is reassuring language, but it is not a manageable service level.
A good SLA replaces broad wording with clear definitions, timings, owners and evidence.
The four service clocks schools should separate
One of the most important changes a school can make is to stop treating “response time” as one single measure. A useful SLA normally separates four different stages.
Acknowledgement
The contractor confirms that the issue has been received, records the priority and identifies who owns the next action.
Containment or attendance
The immediate impact is controlled, the area is made safe where necessary, or an operative attends to assess and begin work.
Resolution
The agreed cleaning or corrective action has been completed to the required standard, not merely discussed or assigned.
Verification and closure
The school or agreed owner confirms that the outcome is acceptable and any longer-term preventive action has been recorded.
Why the distinction matters
Imagine that a school reports an unusable washroom block at 9:00 am.
- The contractor replies at 9:08 am. That is a fast acknowledgement.
- A supervisor attends at 9:35 am. That is attendance.
- The immediate contamination is removed and the area is made safe at 10:05 am. That is containment.
- A blocked drain is found and passed to the school’s maintenance provider. The permanent cause is not resolved by the cleaning contractor.
If the SLA only says “respond within 15 minutes”, the contractor may technically meet the target while the washroom remains unusable for much longer. The service record needs to show each stage and identify where responsibility transfers to another party.
Acknowledgement is not resolution. An email saying “we will speak to the team” may meet an acknowledgement target, but it does not prove that the area has been corrected, checked and prevented from failing again.
The free school cleaning complaint log structure brings the issue, severity, action, contractor response, closure status and repeat-issue flag into one record.
Before choosing times, define the service you are actually buying
A target can only be fair and useful when it reflects the operating model behind the contract.
Before writing response and resolution times, agree the answers to these questions:
What are the covered hours?
State whether the SLA operates during cleaning shifts, school opening hours, evenings, weekends or a separate emergency support window.
Who is normally on site?
An on-site supervisor can act more quickly than a contract manager who must travel from another location.
Which areas are critical?
Washrooms, dining spaces, medical rooms, reception and high-use areas may need different targets from low-use offices.
How are issues reported?
Define the telephone number, email, helpdesk or portal that starts the SLA clock and the route used for urgent incidents.
What sits outside cleaning?
Identify maintenance defects, access failures, additional-service requests and specialist incidents that need another owner.
What emergency cover exists?
Do not promise a rapid out-of-hours response unless the contract includes people, communication and travel arrangements to deliver it.
Who can authorise extra work?
Some incidents require additional hours, specialist cleaning or replacement supplies. Agree who can approve that work and any cost.
Who verifies closure?
Name the school role or contractor role allowed to confirm that the issue has been resolved to the required standard.
Routine service failures and emergency incidents should not be forced into the same process. Where contamination, bodily fluids, sewage, flooding or an outbreak is involved, use a separate emergency route with its own responsibilities and response arrangements. Ever Brite’s Emergency Cleaning Response Checklist for Schools helps schools prepare that process.
An example school cleaning SLA priority matrix
The table below is an illustrative starting point, not a universal set of contract terms. The correct timings depend on the site, covered hours, staffing model, travel arrangements, risk and the services included in the contract.
Critical
Immediate hygiene, safety or operational impact. The area may need to be isolated or made safe before reuse.
Urgent
A significant failure in a high-use area that needs prompt action during the school day.
Standard
An isolated service failure that should be corrected quickly but does not create immediate operational risk.
Routine
A minor presentation concern, improvement request or planned adjustment that can be scheduled.
| Priority and examples | Acknowledgement | Containment or action | Resolution target | Update and escalation |
|---|---|---|---|---|
| P1: Critical Significant contamination, sewage, a critical washroom block unusable, a major missed clean affecting safe operation, or another immediate hygiene concern. | Within 15 minutes during covered hours, using the urgent reporting route. | Begin immediately where staff are on site. If an off-site or specialist response is contracted, dispatch should be confirmed without delay. | Make safe before the area is reused. Where the contract includes rapid specialist attendance, set the agreed attendance window clearly. If another provider owns the permanent cause, record the handover and interim control. | Updates at agreed short intervals, for example every 30 minutes. Escalate automatically if acknowledgement, dispatch or containment misses its target. |
| P2: Urgent A high-use area materially below standard, several rooms missed, a key washroom block without supplies, or a staffing shortfall affecting delivery. | Within 30 minutes during covered hours. | Confirm an action owner and practical recovery plan within one hour. | Normally within two to four hours, before the next high-use period, or within another site-specific target agreed in the contract. | Update at least hourly while the issue remains open. Escalate if action has not started or the resolution target is at risk. |
| P3: Standard An isolated missed task, an individual room below standard, or a routine cleaning complaint without immediate hygiene risk. | Within four working hours. | Assign the action and confirm when it will be completed. | By the next scheduled clean or within one working day, whichever is appropriate to the area and impact. | Update at closure. Escalate if overdue, reopened or identified as a repeat issue. |
| P4: Routine A minor presentation concern, non-urgent improvement request, planned frequency review or additional-service query. | Within one working day. | Provide a plan, decision or quotation within two working days where required. | Within three to five working days, at the next planned visit, or on another agreed date. | Escalate if the agreed date is missed or the issue starts to affect normal service delivery. |
Do not paste these times into a contract without testing them
A school with a permanent on-site cleaning supervisor may reasonably expect faster action than a small site supported remotely. A contract that only operates during evening cleaning hours cannot credibly promise the same daytime response as a service with daytime janitorial cover.
Use the matrix to structure the conversation, then adapt every target to the service being funded and delivered.
How to set targets that are useful, fair and measurable
Good service levels balance risk, practicality and value for money. A demanding target is only useful when the supplier has the staffing, communication route and authority required to meet it.
Step 1: start with the issues that matter most
Review recent complaints, audit failures, missed cleans and operational incidents. Identify the areas and failures where a delayed response creates the greatest impact.
The School Cleaning Control Kit provides the audit, complaint log and performance review templates needed to build that evidence.
Step 2: agree the priority definitions
Write short definitions and examples for each level. Everyone reporting issues should understand why a critical hygiene incident is P1 and why a minor presentation concern is not.
Step 3: set a target for each stage
Agree acknowledgement, containment or attendance, resolution, update frequency and closure requirements separately. Avoid a single response target that hides what happens after the first reply.
Step 4: define the clock rules
State exactly when the timer starts, which hours count, who may report an issue, how out-of-hours incidents are handled and when a clock can legitimately pause.
Step 5: agree ownership on both sides
The contractor may own cleaning action while the school owns access, maintenance, event information or approval for additional work. The SLA should make those dependencies visible.
Step 6: define the evidence for closure
Depending on the issue, closure may require a site recheck, photograph, completed rota change, supply confirmation, supervisor sign-off or follow-up audit.
Step 7: test the process before relying on it
Run the proposed matrix for four to six weeks. Look for targets that are routinely missed, priorities that are being misclassified and incidents where responsibility is unclear.
Step 8: review the targets after real use
An SLA should not change every month, but it should be reviewed when the school day, buildings, staffing model or service scope changes materially.
The small print that prevents avoidable disputes
Most SLA disagreements are not caused by the target itself. They are caused by missing definitions around how the clock works.
| Rule | What should be made clear |
|---|---|
| Start time | Does the clock begin when the issue occurs, when the school reports it, or when it enters the agreed helpdesk or telephone route? |
| Covered hours | Define working hours, cleaning-shift hours, school holidays, evenings, weekends and any separately funded emergency cover. |
| Reporting route | State which channel starts the SLA clock. An urgent issue sent to an individual’s inbox may not be seen as quickly as a call to the agreed emergency number. |
| Priority authority | Clarify who assigns the initial priority and who can change it if the impact is greater or lower than first reported. |
| Clock pauses | List valid reasons, such as denied access, waiting for school approval, a maintenance dependency or a specialist third party. A pause should be recorded, explained and time-stamped. |
| Temporary resolution | Define when containment is acceptable while a permanent fix is arranged, and who remains responsible for monitoring the interim control. |
| Reopened issues | Explain whether a problem that returns within an agreed period reopens the original incident, becomes a repeat complaint or starts a new SLA clock. |
| Closure | State who can close the issue and what evidence is required. Contractor acknowledgement alone should not close a recurring or significant failure. |
Build the evidence behind your service levels
The free School Cleaning Control Kit gives schools a practical way to record the information needed to monitor an SLA properly.
- Log the issue, severity, contractor response and closure status
- Identify repeated complaints rather than treating every report as new
- Track resolution performance and overdue actions
- Use audit findings and KPIs in contractor review meetings
- Recognise when ordinary improvement should become formal escalation
What is the difference between an SLA and a KPI?
The terms are often used together, but they are not interchangeable.
Service level agreement
An SLA sets the target for an individual event.
Example: P2 cleaning complaints will be acknowledged within 30 minutes during covered hours.
Key performance indicator
A KPI shows how consistently the contractor achieved that target over a reporting period.
Example: Percentage of P2 cleaning complaints acknowledged within the agreed 30-minute target during the month.
The target percentage used for the KPI should be agreed by the school and contractor. It should reflect the importance of the service level, the baseline and the consequences of failure. A critical containment target may reasonably require a different level of consistency and scrutiny from a routine request target.
Ever Brite’s guide to eight school cleaning KPIs explains how audit scores, complaints, missed cleans, staffing gaps and action completion can be read together.
Useful SLA performance measures
Acknowledged within target
The percentage of incidents where the contractor confirmed receipt, priority and ownership on time.
Contained within target
The percentage of urgent incidents where the immediate impact was controlled within the agreed time.
Resolved within target
The percentage of incidents where the required outcome was completed within the SLA.
Reopened or repeated
The number of issues that returned after closure or appeared again in the same area.
Updates provided on time
Whether the school received the agreed progress updates while significant issues remained open.
Escalations required
The number of incidents that moved beyond the normal owner because a target was missed or the impact increased.
Do not rely only on the average resolution time. Several very fast routine closures can make the average look strong while one important incident remains open for too long. Review performance by priority, target achievement, repeat rate and individual exceptions.
A practical school cleaning escalation process
Escalation should not begin only after a relationship has broken down. It should be a pre-agreed route that brings the right level of authority into the issue before it drifts.
Level 1: on-site cleaner or supervisor
Handles ordinary corrections, supply issues and local service failures within the agreed target. The issue is recorded and closed once the outcome has been checked.
Level 2: contract or account manager
Becomes involved when a P1 or P2 incident occurs, an SLA target is at risk, a complaint repeats, cover arrangements fail or the local team needs additional authority or resources.
Level 3: senior operations lead
Reviews material failures, repeated missed targets, cross-site problems, unresolved staffing concerns or issues that require a wider change to mobilisation, resourcing or management.
Level 4: formal performance review
The school and contractor agree a documented improvement plan with a baseline, corrective actions, owners, deadlines, measures and a final decision date.
Use the 30-day school cleaning contractor improvement plan when normal escalation has not produced a sustained recovery.
Level 5: contractual and procurement action
Where performance does not recover, the school or trust reviews the contract’s formal remedies, notice provisions and procurement route with the appropriate internal and professional advice.
If a change of provider is approved, the guide to Switching School Cleaning Contractors Without Chaos helps plan mobilisation, TUPE, safeguarding, equipment and day-one delivery.
Automatic escalation triggers to consider
- A P1 incident is reported
- An acknowledgement, containment or resolution target is missed
- An issue is reopened after being marked as resolved
- The same or substantially similar complaint reaches the agreed repeat threshold
- A staffing or cover failure affects several areas or more than one site
- A previous corrective action has not been completed by its deadline
- The contractor cannot provide a clear owner or recovery plan
- Service records appear inaccurate or incomplete
The school should not need to decide from scratch who to contact each time. Names, roles, telephone numbers and substitute contacts should be documented and kept current.
What should happen in the monthly contractor review?
Service levels become useful when they are reviewed consistently and lead to decisions.
A monthly SLA summary should show:
- The number of issues raised by priority
- The percentage acknowledged within target
- The percentage contained or attended within target
- The percentage resolved within target
- Open, overdue, repeated and reopened issues
- The main reasons for missed targets
- Actions, owners and deadlines agreed in response
- Any proposed change to staffing, supervision, rotas, access or service scope
Use the same definitions and layout each month so the school can see whether performance is improving rather than simply reading a new narrative report.
The guide to school cleaning review meetings provides a practical agenda covering standards, complaints, staffing, supervision and action follow-through.
Can schools introduce SLAs into an existing cleaning contract?
Often, schools can improve day-to-day performance management without waiting for the next retender. The right route depends on the current contract and the scale of the proposed change.
Start with existing obligations
Review the specification, reporting requirements, complaint process, KPIs, escalation clauses and any existing service levels before adding something new.
Agree an operating protocol
Where the contract allows, the school and contractor may document practical reporting routes, priority definitions, meeting routines and evidence requirements without changing the commercial scope.
Document genuine variations properly
If the proposal changes hours, staffing, risk transfer, out-of-hours cover, price or contractual remedies, follow the organisation’s variation and procurement process.
Test before formalising
A short pilot can show whether the proposed targets are measurable, affordable and operationally realistic before they become long-term expectations.
Contractual wording needs appropriate review
This article provides an operational framework, not legal or procurement advice. Any change to formal contract terms, service credits, deductions, termination rights or procurement obligations should be reviewed through the school or trust’s approved process.
Should missed cleaning SLAs trigger service credits or deductions?
Financial remedies can have a place in larger or more formal contracts, but they should not be the only performance-management tool.
A useful approach normally starts with:
- Immediate correction of the service failure
- Clear recording of the missed target
- Root-cause review where the failure is significant or repeated
- A corrective action with an owner and deadline
- Escalation where the same failure continues
Where service credits or deductions are included, they should be linked to clear, measurable obligations and drafted so that both parties understand when they apply. The remedy should encourage reliable performance rather than create arguments about ambiguous data.
For many schools, the first priority is not a more complicated penalty table. It is a complaint record, audit process and contractor review that can prove whether the service level was met in the first place.
Common school cleaning SLA mistakes
Using one target for every issue
A critical hygiene incident and a minor presentation concern should not compete for the same response route or deadline.
Measuring acknowledgement only
A quick reply can create a strong-looking statistic while the actual problem remains open.
Writing “promptly” without a time
Broad language creates different expectations and makes performance difficult to evidence.
Promising 24-hour cover without funding it
An SLA must match the people, communications, travel and authority included in the contract.
Ignoring school dependencies
Access, maintenance, event information and approval for additional work may affect resolution and should be recorded openly.
Closing issues after the first action
A temporary re-clean may correct the immediate symptom without preventing the same problem from returning.
Having no rule for repeat complaints
Several individually closed incidents can conceal an underlying failure in frequency, staffing, supervision or scope.
Collecting data without decisions
Every missed target or deteriorating trend should lead to a question, an owner, an action and a review date.
A simple SLA schedule schools can use
Whether the SLA sits inside the contract or in an agreed operating schedule, each issue type should be described in one consistent format.
| Field | What to include |
|---|---|
| Issue category | The service failure or incident covered by the row. |
| Priority | P1, P2, P3 or P4, with a definition that reflects impact and risk. |
| Reporting route | The phone number, email, portal or helpdesk that starts the clock. |
| Acknowledgement target | When the contractor must confirm receipt, priority and ownership. |
| Containment or attendance target | When immediate control, attendance or dispatch must begin. |
| Resolution target | When the agreed outcome should be completed. |
| Update frequency | How often the school should receive progress information while the issue remains open. |
| Closure evidence | The check, photograph, sign-off, record or follow-up required before closure. |
| Escalation trigger | The missed target, repeat threshold or impact change that moves the issue to the next level. |
| Named roles | The school and contractor roles responsible at each stage. |
Keep the schedule short enough to use. A school will gain more from four well-defined priority levels than from a large catalogue of targets that nobody can remember or report consistently.
What a good school cleaning SLA gives you
When service levels are clear and consistently used, the school should begin to see:
- Less disagreement about what “quickly” means
- Faster action on issues with the greatest operational impact
- Clearer ownership between the school, contractor and other service providers
- Fewer complaints being closed before the result has been checked
- Earlier escalation when performance starts to drift
- More useful monthly contractor reviews
- Better evidence for leadership, governors and trust teams
- A fairer basis for improvement, contractual action or retendering
The purpose is not to turn every small cleaning concern into a formal incident. It is to make sure the important issues receive the right response and that recurring failures do not disappear behind a series of quick acknowledgements.
Turn service expectations into a working management system
The School Cleaning Control Kit includes the practical tools needed to monitor whether agreed standards and response targets are being delivered:
- School Cleaning Standards Audit
- Cleaning Complaint Log
- Contractor Performance Review
- Simple Cleaning KPI Tracker
- Weekly, monthly and termly monitoring guidance
- Improve-or-escalate guidance
School cleaning SLA FAQs
What is a school cleaning SLA?
A school cleaning SLA is an agreed set of measurable service commitments covering how cleaning issues are reported, acknowledged, acted on, resolved, updated and escalated. It sits alongside the cleaning specification, which describes the routine tasks and frequencies included in the service.
What is the difference between response time and resolution time?
Response time normally measures how quickly the contractor acknowledges the issue and confirms ownership. Resolution time measures how quickly the required outcome is completed. A fast acknowledgement does not prove that the cleaning problem has been corrected.
How many priority levels should a school cleaning SLA have?
Four levels are usually enough to separate critical, urgent, standard and routine issues without making the process difficult to use. A smaller contract may use three levels, provided the definitions and examples remain clear.
What is a reasonable response time for an urgent school cleaning issue?
The right target depends on covered hours, whether staff are already on site, the location, the operational impact and the emergency support included in the contract. As an illustrative starting point, a school may consider a 15-minute acknowledgement for critical issues and 30 minutes for urgent issues during covered hours, with separate targets for containment, attendance and resolution.
Should different parts of the school have different SLA targets?
They can. A failure in a main pupil washroom, dining area, medical room or entrance may have a greater impact than the same issue in a low-use office. Priority should reflect risk, usage and operational effect rather than location alone.
What happens when the problem is caused by maintenance or access?
The cleaning contractor should record the finding, complete any reasonable temporary cleaning or containment action and hand the issue to the correct owner. The SLA should explain how the clock is handled when permanent resolution depends on school access, maintenance approval or another supplier.
How should out-of-hours cleaning incidents be handled?
Out-of-hours targets should match the service that has been contracted. If the school needs rapid support during evenings, weekends or holidays, the agreement should include the reporting route, on-call arrangements, attendance expectations and any additional cost.
When should a cleaning issue be escalated?
Escalation may be automatic for critical incidents. It should also occur when an SLA target is missed, an issue is reopened, the same complaint reaches the agreed repeat threshold, a staffing failure affects delivery or a corrective action remains overdue.
Should missed SLAs automatically lead to a financial deduction?
Not necessarily. The appropriate remedy depends on the contract and the seriousness and frequency of the failure. Correction, root-cause review, corrective action and escalation are often the first steps. Any service-credit or deduction mechanism should be clear, measurable, proportionate and reviewed through the school or trust’s approved contractual and procurement process.
Can a multi-academy trust use one SLA across all schools?
Yes, a trust can use common definitions, priority levels, reporting fields and escalation routes across its schools. Site-specific schedules may still be needed where buildings, opening hours, staffing models, service scope or emergency arrangements differ.
How often should school cleaning SLA performance be reviewed?
Open urgent issues should be monitored while they are active. A summary of target achievement, repeated issues and missed deadlines should normally form part of the monthly contractor review, with longer-term trends considered termly.
Do we need to be an Ever Brite customer to use the School Cleaning Control Kit?
No. The toolkit can be used with an existing cleaning contractor or an internally managed cleaning team.
About Ever Brite Cleaning
Ever Brite Cleaning supports schools, academies, colleges and multi-academy trusts with professionally managed cleaning services designed around reliable delivery, clear communication and consistent standards.
Our approach combines trained site teams, structured supervision, practical auditing, responsive contract management and clear reporting. The aim is to help education teams maintain clean, safe and well-presented environments without spending every day chasing the cleaning service.
Built for schools. Backed by strategy. Delivered without drama.