Most cleaning contractors assume they lose accounts because the work slipped. Plenty of them lose accounts while the work is fine, because they could not produce evidence in the format the facility director needed to defend the contract to their own boss.
That is a documentation failure, not a cleaning failure. And it is the one failure you can fix without hiring a single additional cleaner.
To prove SLA compliance, convert each contract clause into a measurable metric with a defined data source, then report monthly: inspection scores by area type, corrective action response times against the contract clock, staffing hours delivered versus scheduled, and photo-documented closure of every logged deficiency. Evidence beats assertion.
Below are the four beliefs that keep otherwise well-run janitorial companies from ever getting credit for their work, and what to do instead of each one.
Myth: A 97% inspection average proves SLA compliance
An average is a summary of your opinion of your own work. A service level agreement is a set of individual promises, each with its own threshold.
The two are not the same thing, and a facility director who has been burned before knows it. If your SLA says restrooms are serviced twice per shift and inspected weekly at an acceptable appearance level, then a 97% building average tells them nothing about restrooms. It may be hiding the exact clause that generates every complaint they receive.
There is a second problem. Most self-inspection scoring is built so that a nearly perfect score is the normal outcome. When a report always says 96 to 99, the number stops carrying information, and the client starts reading it as marketing.
What to do instead: build a clause-to-metric map
Open the contract. Pull every sentence that contains a frequency, a standard, a response window, or a staffing commitment. Each one becomes a row.
| SLA clause language | Metric you report | Where the data comes from | Evidence artifact |
|---|---|---|---|
| "Restrooms serviced twice per shift" | Completed restroom service events per shift | Checklist completion timestamps | Signed checklist log, by date |
| "Maintained at APPA Level 2" | Weighted inspection score for that area type | Scored inspection with photos | Inspection report PDF |
| "Deficiencies corrected within one business day" | Percent closed inside the window | Deficiency log with open and close times | Corrective action register |
| "Minimum 130 labor hours per month on site" | Hours delivered vs. hours scheduled | Clock-in and clock-out records | Timekeeping export, by location |
| "Day porter on site 7:00 a.m. to 3:00 p.m." | Coverage compliance by day | Clock-in and clock-out records | Attendance exception list |
| "Quarterly carpet extraction, all traffic lanes" | Completion date vs. scheduled date | Work order closure | Before and after photos, work order number |
If a row has no data source, you cannot prove that clause today. That gap is your first project, not a reason to keep quoting a building average.
Weight the score so it reflects what the client actually cares about. In most office and medical accounts, restrooms, entrances, and any patient or food area carry more consequence than a stairwell. A simple weighting, restrooms 30 percent, entrances and lobby 20 percent, offices and workstations 20 percent, floors and common areas 20 percent, back of house 10 percent, produces a number that moves when something real goes wrong.
Myth: If we were out of compliance, the facility director would tell us
They will tell you about the complaint. They will not tell you about the record.
Facility directors work inside their own systems: a CMMS, a help desk, a ticket queue, sometimes a shared spreadsheet a receptionist maintains. Every occupant complaint about cleaning lands there with a timestamp, whether or not anyone forwards it to you. At renewal, that log is the document that gets pulled, and it will not match your version of events, because your version starts when someone called you.
A common pattern in commercial janitorial accounts: the contractor believes there were four complaints in the quarter, and the client's ticket log shows eleven. Seven of them were resolved by the day porter within the hour and never escalated. That gap is not dishonesty. It is two systems with two different clocks.
What to do instead: reconcile logs monthly and own the register
- Ask, in writing, for read access to the cleaning-related tickets or a monthly export. Frame it as wanting to measure your response time against their clock, not yours.
- Keep your own deficiency register with five fields minimum: date and time reported, source (client ticket, inspection, self-identified), location and area, corrective action, date and time closed.
- Reconcile the two lists on the same day each month. Anything on their list that is not on yours is a communication break in your own chain, usually a supervisor solving a problem without logging it.
- Report the reconciled count, including the items you found yourself. Self-identified deficiencies are the strongest trust signal you have, because nobody fabricates their own faults.
Measure response time from their timestamp. If a ticket opens at 8:12 a.m. and your day porter resolves it at 9:40 a.m., that is 88 minutes, not "same day." Precision is what makes the number credible.
Myth: GPS clock-in proves the work got done
Geofenced clock-in proves a person with a phone was inside a defined radius at a specific minute. That is genuinely valuable, and it is also not performance evidence.
Attendance data answers one question: did the labor arrive as scheduled. It cannot tell you whether the third-floor restroom got serviced twice, whether the entrance glass was done, or whether the vacuuming was detail or maintenance. Present attendance data as SLA proof and a sharp facility director will point out the obvious hole in about nine seconds.
Be careful with how you describe the capability, too. Location captured at clock-in and clock-out is a bracket around a shift, not a trail through the building. Overstating it once costs you more credibility than never mentioning it.
What to do instead: pair coverage with completion, then show the variance
Two numbers, side by side, every month. Coverage compliance answers whether the labor showed up. Task completion answers whether the scope was executed.
Here is the arithmetic on an illustrative account. Assume Meridian Office Park, 62,000 square feet, cleaned five nights a week, with a contracted minimum of 130 labor hours per month plus a day porter.
- Hours scheduled: 130.0
- Hours delivered (clock records): 126.5
- Coverage compliance: 126.5 / 130.0 = 97.3 percent
- Variance: 3.5 hours short, traced to two late arrivals and one shift cut for a fire alarm evacuation
Now report it before they find it. Three and a half hours, explained, with the make-up date for the deferred work, reads as control. The same three and a half hours discovered by the client during a renewal review reads as short-staffing.
Myth: Photos are proof
A clean-looking photo with no timestamp, no location code, and no before state proves that a clean surface existed somewhere at some point. It is not evidence. It is decoration.
Photo dumps are worse than useless in a compliance file. Forty-one thumbnails of empty hallways attached to a monthly report tell the facility director you are filling space, and they will stop opening the attachment by month three.
What to do instead: adopt a four-part photo standard
Every photo in a compliance file should carry four attributes, and photos that do not carry them should not be in the file at all.
- Location code: Building, floor, and room or area, using the client's own naming convention. "3rd floor women's restroom, B wing," not "restroom."
- Timestamp: Captured automatically at the moment of the inspection, not typed in afterward.
- Pairing: A before shot tied to a numbered deficiency and an after shot tied to its closure. A lone after photo cannot demonstrate a correction.
- Reference number: The deficiency or work order ID that ties the image to a line in the register, so anyone can trace image to record and back.
Ration them. For most monthly reports, six to ten photos that each map to a logged item beat fifty that map to nothing. Periodic project work, strip and seal, carpet extraction, high dusting, is the exception: those always get a paired before and after, because that is the work clients most often suspect was never performed.
What actually proves SLA compliance
Compliance is proven by a small, repeatable evidence pack that arrives on the same day every month, keyed to contract language, and readable in under five minutes.
The five-minute constraint is real. Facility directors manage HVAC, grounds, security, elevators, and life safety in addition to cleaning. A twenty-page report gets skimmed. A two-page report gets read, and gets forwarded up the chain with your numbers in it, which is exactly where you want them at budget time.
The monthly SLA evidence pack
- Page 1, top: weighted inspection score by area type, current month plus the previous three months, so the trend is visible
- Page 1, middle: coverage compliance (hours delivered vs. scheduled) with every variance explained in one line
- Page 1, bottom: response-time compliance, calculated as deficiencies closed inside the contract window divided by total deficiencies logged
- Page 2: the reconciled deficiency register, including self-identified items, with open and close timestamps
- Page 2, sidebar: periodic and project work completed this month with work order numbers, and what is scheduled next month
- Appendix, kept short: paired before and after photos, each tied to a register line
- One line naming the single thing you are fixing next month and by what date
The response-time math a facility director will check first
Response time is the metric clients trust most, because it is the one they can verify from their own ticket queue without asking you anything.
The formula is simple. Deficiencies closed within the contract window, divided by total deficiencies logged, times 100.
Continuing the Meridian Office Park example, with an SLA that requires correction within one business day and a compliance threshold of 95 percent:
- Deficiencies logged in the month: 34
- Closed within one business day: 30
- Closed in two business days: 3
- Open at month end: 1
- Response-time compliance: 30 / 34 = 88.2 percent
That account is out of compliance, and the trap is that its inspection average may still read 96. Two metrics, two different verdicts. Only one of them is in the contract as a threshold.
The recovery math is worth doing out loud in the report. At a similar volume of roughly 30 logged items, hitting 95 percent means missing the window no more than once. That reframes the fix from "try harder" to a specific operational change: a same-day escalation rule for anything logged after 2:00 p.m., or a standing 30-minute punch-list block at the start of each shift.
How to set this up on an account you are already six months into
You do not need to renegotiate anything. You need one afternoon and the executed contract.
- Extract the clauses. Every frequency, standard, response window, and staffing minimum becomes a row in the clause-to-metric map. Most commercial janitorial contracts yield somewhere between 8 and 20 measurable clauses.
- Flag the unprovable rows. Any clause with no data source gets fixed first, usually by adding a checklist item or a required photo at a specific frequency.
- Fix your inspection form. Score by area type, weight by consequence, and require a photo on any item scored below standard. A form where everything passes is not an inspection form.
- Set the deficiency clock. Decide who logs, who closes, and what the escalation trigger is. Unwritten, this collapses the first week a supervisor calls out.
- Send the first pack, and say what it is. One short note: "Starting this month, here is how we are measuring ourselves against the SLA. Tell me if the thresholds match how you are measuring us."
That last sentence does more work than the entire report. It invites the facility director to correct your definitions before a dispute exists, and it puts you in the small group of contractors who show up with numbers instead of reassurance.
Where CleanTrack360 fits
Every artifact described above can be produced with a clipboard, a camera, and a disciplined spreadsheet. The reason most operators stop after two months is assembly time, not intent. CleanTrack360 keeps the pieces in one place: quality inspections with custom checklists, photo evidence and automatic scoring; geofenced GPS clock-in and clock-out in the phone browser for coverage records (location captured at clock-in and clock-out, with a default 150 m radius you can configure per location); work orders for periodic and project tasks; and reports with CSV export when you want to build the numbers your own way.
There is also a browser-based client dashboard where the facility director can see schedules, inspection reports, and service requests without waiting for your monthly email, which changes the tone of the renewal conversation. Plans start at $99 per month for Starter (up to 5 team members), $199 for Pro (up to 20) and $249 for Business (up to 50), priced per plan rather than per user, with a 14-day free trial and no credit card required.