Writing a Vendor SLA That Actually Gets Enforced

A vendor service level agreement gets enforced when every service level inside it is observable by someone other than the vendor, measured on a stated frequency, and attached to a stated consequence. Remove any one of those three and the clause is decoration. This is the enforcement layer of the wider property management vendor management lifecycle.

Most contracts in commercial buildings fail the first test. They promise "a high standard of cleanliness" and "prompt response to complaints" — feelings rather than measures. Nothing can be verified, so nothing can be enforced.

Key takeaways

• A service level needs three properties: it is observable by you, it has a number attached, and breaching it triggers a defined step.
• Split every obligation into an outcome (how clean), a response (how fast someone acknowledges), and a resolution (how fast it is fixed). They are different promises.
• Write frequencies as numbers. "Periodic" and "as required" cannot be verified and will not be performed.
• Grade the outcome on a shared scale so a 3 in March means the same thing as a 3 in November.
• Remedies should escalate: informal note, documented cure period, formal notice. Never jump straight to termination.
• Measure the same way every month. An SLA enforced only when someone complains is not an SLA.

Why most vendor SLAs are never enforced

They are written to be signed, not to be used. Three habits cause it.

Vague outcomes. "Maintained in a clean and sanitary condition" sounds serious and means nothing. When a dispute arises, the vendor points at the restroom and says it is clean. You point at the same restroom and say it is not. There is no third opinion available, so the invoice gets paid.

Unverifiable frequencies. "Common areas cleaned as required" and "high dusting performed periodically" describe intentions. Without a stated interval there is no gap between what was promised and what was done, because nothing was promised.

No consequence. A service level with no remedy is advice. If the only tool available for a breach is a stern email, the contract has told the vendor exactly how much the standard matters.

The three-part structure of a usable service level

Every obligation worth writing should split into three measurable promises.

A restroom that scores level 2 but took three days to fix a soap dispenser has met the outcome and failed the resolution. Under a properly structured SLA those are separate breaches with separate consequences. Under a vague contract they are a single amorphous complaint.

CCOHS recommends recording both what was examined and what was not, and assigning each finding a priority so the urgency of corrective action is explicit. Their workplace inspection guidance uses an A/B/C priority scheme — major requiring immediate action, serious requiring short-term action, minor requiring long-term action. That is a workable basis for resolution timeframes in a cleaning SLA.

Turning vague scope into a measurable vendor service level agreement

This is the core exercise. Take each line of your scope and force it into something a person with a clipboard or a tablet could confirm.

Two things make this table enforceable. First, every row can be checked by walking the building. Second, every row has a frequency or a threshold, so a miss is a fact rather than an opinion.

Note the 2-metre sightline in the floors row. It gives you a defensible observation standard instead of "looks dirty." Any observation standard needs to be stated in the contract or it will be argued.

Writing response and resolution times

Response and resolution get conflated constantly. A vendor "responds" by replying to your email. The dispenser stays empty for two days. Under a single "prompt response" clause, they have complied.

Separate them, and set them by severity:

• Critical — safety hazard, biohazard, loss of a restroom, water where it should not be. Response within 1 hour, resolution within 4 hours.
• Routine — an empty dispenser, a scuffed wall, a missed area. Response within 4 business hours, resolution within 24 hours.
• Scheduled — periodic work such as floor care or high dusting. Completion by the agreed date, with at least 30 days notice of the date.
• Cosmetic — minor items that affect appearance only. Resolution within 5 business days.

Critical items need a definition inside the contract, or every item becomes critical during an argument. Write the list explicitly and keep it short.

Scope note: items that are genuinely urgent — a live electrical fault, water ingress from a failed fitting, a suspected gas or chemical release — are not cleaning issues. Notify the responsible trade or utility immediately and document that you did. Do not ask a cleaning crew to resolve them.

What remedies should sit behind the service levels

Remedies do not have to be financial to work, but they must be real. Build the ladder before you need it and put it in the contract.

The important design point is that the ladder starts low. A manager who has only two settings — ignore it or terminate — will ignore everything until they terminate. A contract with six steps gives you somewhere to stand in month four.

Service credits work well because they are automatic. Set them as a small percentage of the monthly fee per missed service level, capped at a stated ceiling so the relationship does not become punitive. The credit rarely gets claimed. Its presence changes behaviour because it converts a complaint into a cost.

Making the SLA verifiable in practice

A service level you cannot measure is a service level you cannot enforce, so the verification method belongs in the contract too.

Specify:

1. The measurement method — scored inspection against an agreed checklist.
2. The scale — APPA cleanliness levels, or a defined 1–5 scale with written descriptors for each point.
3. The frequency — monthly full inspection, quarterly deep sample.
4. The sampling rule — how many restrooms, floors and stairwells get inspected each cycle.
5. The evidence standard — a photo per deficiency, dated.
6. The reporting deadline — report issued to the vendor within 3 business days of inspection.
7. The dispute window — vendor may contest a finding in writing within 5 business days, with evidence.

That last item matters more than it looks. A vendor who can contest a finding with counter-evidence will engage with the process. A vendor who has no route to contest it will disengage from the process entirely and treat inspections as attacks.

Set the sampling rule generously. Inspecting one restroom and declaring the site below standard is not defensible in a review meeting. Inspecting six of twenty restrooms and reporting the pattern is. The same logic underpins any vendor quality audit — sample size is what makes a finding survive a challenge.

Running the SLA month to month

An SLA is a routine, not a document. The routine looks like this:

• Weekly — visual pass on high-traffic areas, exceptions logged only.
• Monthly — full scored inspection, report issued to the vendor within three business days.
• Monthly — open deficiency list reviewed; anything past its resolution window is escalated one step on the ladder, with the manager and vendor contacts agreed up front under a written vendor communication protocol.
• Quarterly — performance review meeting with the evidence pack, including the score trend across the term.
• Annually — service levels and frequencies reviewed against how the building is actually used.

That review meeting is where most of the value gets realised, because it is the only venue where the numbers, the cost and the contract can be discussed together. Our guide to running a quarterly vendor performance review covers the agenda and the evidence pack.

Three things break the routine in practice. Inspections stop when the manager gets busy. The report goes out late, so the vendor's response window collapses. Open items get closed on the manager's word rather than on evidence. Any of the three turns the SLA back into decoration within a quarter.

Aligning the SLA with the rest of the contract

The SLA does not stand alone. Four other clauses have to line up with it or the service levels will not survive contact with a dispute.

• Scope — the SLA defines how well; the scope defines what. A service level about restroom scores is meaningless if the scope never listed the restrooms.
• Variations — any added area or task needs a corresponding service level. Adding a floor without adding hours is how contracts quietly fail.
• Payment — link payment terms to the reporting obligation, so an unreported month is an incomplete month.
• Termination — the cure periods in the remedy ladder must match the termination clause, which determines whether any of it matters.

Where NeatScore fits

Enforcement needs a record, and the record has to be consistent enough to survive a disagreement. NeatScore builds area-specific checklists with critical items flagged so they cannot be skipped, scores items on the APPA 1–5 scale, attaches photos to individual findings, and works offline in parkades and stairwells. Each inspection produces a dated, branded report you can issue to the vendor as the evidence pack.

Deficiency tracking keeps unresolved items on the list across months, which is what turns a single inspection into a trend and a trend into a defensible position at renewal.

Start a free 14-day trial or see pricing.

Frequently asked questions

What should a cleaning vendor SLA include?

Every service level should state an outcome with a threshold, a response time for complaints, a resolution time by severity, the measurement method, the inspection frequency, and the remedy for a breach. If a clause cannot be measured by walking the building with a checklist, rewrite it until it can.

How do I measure cleanliness objectively?

Score each area against a defined scale rather than a general impression. The APPA cleanliness levels give you five defined points, so a 3 means the same thing in every building and every month. Combine the score with photographic evidence per deficiency, and apply a consistent sampling rule so single rooms cannot skew a site result.

Are service credits worth including?

Yes, set low and capped. A small percentage of the monthly fee per missed service level changes behaviour because it converts a complaint into a cost the vendor's finance team sees. The credit is rarely claimed, which is the point — it exists to make the standard real rather than to generate revenue.

How long should a cure period be?

Match it to the severity. Critical items get hours, not days — often 4 hours to resolve. Routine findings usually get 5 business days for a documented cure period before a formal notice. Whatever you choose, the same period must appear in the termination clause or the ladder has no weight.

Can a vendor dispute an inspection finding?

They should be able to, in writing and within a set window such as 5 business days, with counter-evidence. A dispute route keeps the vendor engaged with the process instead of treating inspections as hostile. If a vendor stops contesting findings entirely, that is usually a sign they have stopped reading them.