Cleaning Service Level Agreements: What to Measure and Specify

A commercial cleaning contract needs two documents that do different jobs. The specification states what is cleaned, where, how often, with what method and to what standard. The service level agreement states how anyone can tell whether that standard was met, who checks, how often, and what happens when the answer is no.

Contracts that end badly usually had a reasonable specification and no service level agreement at all. The client was unhappy, the contractor was working hard, and neither side could point at a document that defined the difference. This guide covers how to build measurable levels, how to pair them with response standards, and how to keep remedies proportionate so the agreement supports the contract instead of becoming the argument that ends it.

Key takeaways

• A service level agreement converts the specification into measures: what is inspected, how often, by whom, and what counts as a pass
• Measure by area group rather than the building as a whole, because a single site-wide score hides the failures that generate complaints
• Keep condition levels and response standards separate; a missed washroom round and a slow spill response are different failures with different remedies
• Keep remedies proportionate: rectification closes most issues, written pattern recognition follows repeat failures, and credits are reserved for persistent or critical failure
• State exclusions and client responsibilities in the same document, or every performance conversation becomes a scope argument
• Insist on dated, repeatable evidence, because a level that cannot be demonstrated is a level nobody will accept at renewal

The three documents clients confuse

Specification, service level agreement and key performance indicator are often used as if they mean the same thing. They do not, and blurring them is the fastest route to an unenforceable document.

• Specification. What is done, where, how often and to what method. The task and frequency schedule lives here.
• Service level agreement. The measurable level of performance the client can expect, how it is measured, and what follows if it is not met.
• Key performance indicators. The small set of numbers reported over time: scores by area group, rectification times, complaint counts, completion rates.

Write them in that order. A service level agreement assembled before the specification exists ends up measuring whatever is convenient rather than what the contract promises, and the client will notice at the first dispute. The structure of a workable specification is set out in cleaning specification writing.

Measure areas, not the building

One overall score for a building is comfortable and close to useless. A site can score well overall while the washrooms in a leased wing fail every week, because the average absorbs the failure.

Define levels by area group instead: entrances and lobbies, washrooms, office and workstation areas, corridors and stairwells, elevators, kitchens and break rooms, waste and recycling rooms, loading areas, and exterior hard surfaces. Each group gets its own expected level, its own check frequency and its own sample size.

Two further distinctions do most of the work:

• Condition levels describe how clean an area is at the moment of inspection, on a defined scale.
• Completion levels describe whether the scheduled work happened, which is a different question from whether the result looks right today.

A building can show high completion with poor condition, which usually means the time allowance or method is wrong, or good condition with poor completion, which usually means the schedule is not being followed. Reporting both is what makes the numbers actionable, and the measurement mechanics are covered in how to measure cleaning quality.

Routine quality: what a score should mean

Most commercial contracts grade appearance on a five-point scale. The best known is the APPA custodial scale, where level 1 is the highest standard and level 5 is the lowest. The scale matters less than the discipline around it:

• The same inspector, or inspectors trained against written descriptors, so a 3 means the same thing in March and in November
• Defined sample sizes, so a washroom inspection covers every fixture group rather than the nearest basin
• Weighted items, where high-traffic, high-visibility and hygiene-critical items count for more than a mark on a partition
• Critical items, a short list where any failure fails the inspection outright instead of shaving a point

A weighted structure matters because clients see entrances, lobbies and washrooms far more often than they see a store room floor. A scoring method that treats them equally will report a passing building while the client keeps finding fault. How the levels look when they are applied to real areas is set out in APPA cleaning standards and the five levels.

Response standards: the half most agreements miss

Quality levels describe a state. Response standards describe time. Both need a number in the document.

Two rules keep that table honest. First, response standards only apply during the hours the contractor is on site unless the contract funds standby time. Second, anything outside the contractor's trade, training or insurance is a report and escalate item rather than a response item. That includes electrical faults, plumbing repairs, machinery servicing, pest activity, confined space access and clinical or sharps waste. Writing that boundary into the agreement prevents the most common dispute in the whole document.

Remedies that stay proportionate

Remedies should escalate with the failure, not with the temperature of the relationship.

• First failure: rectify and record. A deficiency with a description, a location, an owner and a closure date resolves the large majority of issues.
• Repeated failure: document the pattern. The same finding at three consecutive inspections should trigger a written response from the contractor, naming a manager and proposing a change to method, time or product.
• Critical failure: notify and correct immediately, before the client discovers it. A restroom left without soap, towel or tissue is a hygiene failure, not a rounding error — critical
• Systemic failure: credits or a rate review. Credits work when they are small, capped and tied to defined measures. They damage the relationship when they are punitive, vague, or applied to one inspection instead of a trend.

Avoid writing remedies against a measure nobody can verify. A credit tied to general cleanliness is unenforceable. A credit tied to two consecutive inspections below the agreed level in a named area group is straightforward to apply and easy to defend in either direction.

Exclusions and client responsibilities

Every agreement should carry a short section stating what the contractor is not responsible for:

• Repairs, trade work, machinery servicing and any building system adjustment
• Pest treatment, and removal of the conditions that attract pests beyond cleaning
• Clinical, sharps and biohazardous waste handling beyond trained surface cleaning and immediate reporting
• Pool and spa water chemistry, and any confined space entry
• Damage caused by client equipment, occupant behaviour or a building defect
• Consumables the client has agreed to supply

Then state the client's own obligations: access and keys, water and power, secure chemical storage, a named contact who can approve additional work, and prompt action on reported defects. An agreement that lists only contractor duties will eventually be used to score the contractor on outcomes the client controls.

Reporting and evidence

A level that cannot be demonstrated is a level that will be argued about. Put the reporting mechanism in the agreement:

• Inspection records per area group, with date, inspector, item-level scores and photos for anything scored below the target
• Deficiency lists with owner, severity, date raised and closure date
• Completion records for scheduled work, showing what was done and when
• A fixed reporting cadence, monthly for most commercial contracts, sent whether or not the news is good

The record should be generated during the inspection rather than written up afterwards from memory. NeatScore runs inspections on an Android app or in the web portal, works offline and syncs later, scores each area on a defined scale with weighted and critical items, captures photos per item, and produces branded PDF reports per site. That gives a supervisor one dated evidence trail and gives the client a document they can forward instead of a summary email.

Where these agreements break down

The same drafting mistakes appear in contract after contract:

• Levels written as adjectives rather than numbers
• Measuring the whole building instead of named area groups
• Remedies with no defined verification method
• Different inspectors applying different standards
• No baseline, so the first report has nothing to compare against
• Client obligations left unwritten
• Levels set above what the funded hours can deliver

That last one is arithmetic rather than drafting. A level requiring more labour than the contract funds will be missed every month; the crew absorbs the shortfall for a while, then stops trying, and the record becomes a list of failures everyone has agreed to ignore. Set levels against the hours actually sold, or reprice and say why.

Levels that hold: review and reset

Treat the service level agreement as a living schedule rather than a signed appendix. Review it at a fixed point each year using evidence the monthly reports already produce: scores by area group, deficiency trends, rectification times and complaint counts.

Then decide one of three things. Leave the levels unchanged. Raise them with a matching change in hours, method or equipment. Or lower them where they were never realistic. A contract whose levels have not moved in three years is either perfectly scoped or not being measured, and the reports will usually tell you which.

Where performance has genuinely failed, the recovery path in reacting to a failed cleaning inspection and the tracking discipline in deficiency tracking do most of the work. Scope and price also have to move together, which is why the level structure should be reviewed alongside the cleaning contract pricing methods behind it. NeatScore keeps the level definitions, the inspection records and the deficiency history in one place, so the annual review starts from evidence instead of recollection. Try it free for 7 days, or see pricing.

Where this fits in the quality system

This sits under our how to win janitorial contracts, which sets out the standard these checks are measured against.

Frequently asked questions

What is the difference between a cleaning specification and a service level agreement?

The specification says what work is done, where, how often and to what method. The service level agreement says how performance against that work is measured, how often it is checked, what counts as a pass, and what happens when it does not. A contract needs both, and the specification should be written first.

How many KPIs should a cleaning service level agreement contain?

Keep it to a handful that somebody will actually use: an appearance score by area group, rectification time for deficiencies, completion of scheduled work, and complaint counts. Adding more measures spreads attention and makes the monthly report unreadable. Fewer measures used consistently beat a long list that nobody reviews.

Should a cleaning service level agreement include service credits?

Credits are useful for persistent or critical failure and are best kept small and capped. Tie each credit to a defined measure and a defined period, such as two consecutive inspections below target in a named area group. Avoid credits tied to vague wording, and avoid using them as the first response to a single finding, which only converts a rectification task into a financial argument.

How often should cleaning service levels be measured?

Routine condition inspections suit a weekly or fortnightly cycle for most commercial sites, with a monthly summary and immediate recording of critical failures. High-traffic or high-risk areas such as washrooms and entrances may need more frequent checks. The frequency belongs in the agreement so both sides know what the score is based on.

Can a contractor refuse a level the funded hours cannot deliver?

Yes, and it is better to raise it before signing than to absorb it for a year. Show the task hours the level requires, the hours the price funds, and the gap. Then offer the choice: reduce the level, reduce the frequency, or add hours at a rate that covers them. Documenting that conversation protects the contract at renewal.