Cleaning quality control checklist
This one is pointed at your own company rather than a building. Run it once a quarter and it will tell you which of your accounts is being managed and which is being hoped about.
Most cleaning companies that lose accounts are inspecting. That is what makes the loss confusing to the owner, who can produce a stack of completed inspections for the building that just cancelled.
The inspections were real. What was missing sat around them. No written standard, so two supervisors scored the same corridor differently and neither was wrong. No fixed cadence, so the site got visited when somebody had a spare afternoon. No assignment after a failure, so the finding went into a report and the corridor stayed the same. And no record the customer ever saw, so from their side of the desk none of it happened.
The list below scores those five things. It is deliberately uncomfortable in a few places. If you get through it with every line passing, you have a better system than most companies with ten times your headcount.
Standards and Scope
- A written scope of work exists for every site, not only for the sites that complained
- The scope names each area of the site and what is done in it
- Every line in the scope is checkable by a second person without asking the cleaner
- Subjective wording removed: no 'as needed', 'when required' or 'maintain appearance'
- Frequencies are stated per line, not as a single site-wide frequency
- The customer has seen and agreed the same document the inspector scores against
- Site-specific problem areas from the last 90 days are written into the scope
Inspection Cadence
- Every site has a stated inspection frequency written down, not held in a supervisor's head
- New sites are inspected weekly for the first 90 days regardless of size
- High-traffic and high-value sites are inspected more often than low-traffic ones
- Inspections are dated in advance, so a missed inspection is visible rather than silent
- At least one inspection per site per quarter falls outside the usual day and time
- Inspection load per supervisor is known and is achievable in their working week
- A missed inspection is recorded as missed, never backfilled from memory
Scoring Method
- One rating language is used across the whole company
- Pass, Fail or N/A per line, with no partial credit or middle option
- N/A requires a written reason so it cannot be used to avoid a fail
- Every fail carries a photo taken at the time, not a description written later
- Two supervisors scoring the same area would land within a few points of each other
- The score is calculated the same way at every site, so sites can be compared
- A passing threshold is agreed and known by the crew before they are measured against it
The Deficiency Loop
- Every fail becomes a tracked deficiency with an owner and a due date
- The cleaner who has to fix it receives it directly, not through a chain of forwarded messages
- Fix confirmation includes photo evidence of the corrected condition
- A supervisor reviews the fix before it is closed, and no fix closes itself
- Open deficiencies from the last inspection are verified at the start of the next one
- Repeat deficiencies at the same site are visible as repeats, not logged as new each time
- A deficiency that cannot be fixed by cleaning is escalated to the customer as a building issue
Communication and Escalation
- The customer knows who to contact and gets an acknowledgement the same business day
- A complaint triggers an inspection, not only a phone call and a promise
- Escalation steps are written: who is told, after how long, and what happens next
- The crew is told what failed and why, in their own language where needed
- Praise and passing results are shared with the crew, not only failures
- The account owner sees the site's results without having to ask for them
Records and Review
- Inspection records are retained and retrievable by site and by date
- Photo evidence is stored with the inspection, not in a supervisor's phone gallery
- Scores are trended over time per site, not read one inspection at a time
- The customer receives a summary on a regular cadence, before there is a problem
- A renewal file exists per customer: visits completed, scores, response times, fixes
- Results are reviewed with supervisors monthly and something changes as a result
- The program itself is reviewed at least twice a year against what is actually happening
General checks (site-wide)
- One person owns quality control company-wide and is named
- Every supervisor has been trained on the scoring standard, not just handed the form
- The same standard applies to the founder's accounts as to everyone else's
- The program survives a supervisor leaving without knowledge walking out with them
- Nothing in the program depends on a spreadsheet only one person can open
How often to inspect
| Per inspection | Score every line, photograph every fail, verify the previous inspection's open items |
| Weekly | Review open deficiencies, chase anything past its due date, check missed inspections |
| Monthly | Trend scores per site, review repeat deficiencies, send customer summaries |
| Quarterly | Review scope documents for drift, re-check inspection load per supervisor, audit N/A usage |
The lines people fail most
A written standard per site, not per company
Pass: each building has its own scope with frequencies, and the inspection list for that building is built from it. Fail: one generic company checklist used everywhere. A generic list scores a medical clinic and a warehouse the same way, which means it scores neither of them usefully. It also guarantees that the site-specific item, the awkward stairwell or the parkade elevator lobby, never appears on any form.
Two inspectors, one answer
Pass: send two people to the same building in the same week and the scores land within a few points. Fail: a twenty-point spread. Actually run this test rather than assuming the answer. Where it fails, the cause is almost always lines written as tasks instead of observable states, and the fix is rewriting the list rather than retraining the people.
Every failure has a name and a date on it
Pass: pick three failed items from last month at random and you can say who it was assigned to and when it was confirmed closed. Fail: you can find the finding but not the fix. This is the single most common gap in the trade and the most expensive one, because the customer experiences the gap directly.
Score the closing speed separately
One thing worth building into the review, because almost nobody tracks it: split time-to-close into the time the cleaner took to fix the item and the time the supervisor took to confirm it.
Operators who run that split for the first time are usually surprised by which half is slow. Crews often rectify things the same day. Sign-off can sit for a week, and the customer experiences the whole week. If you only track one combined number you will spend a year improving the half that was already working.
Where this fits
Use this page quarterly, on the company. Use the commercial cleaning inspection checklist weekly or monthly, on a building. If you do not yet have the written program this list is testing for, the janitorial quality control plan template is the document to fill in first, and the quality control guide explains the reasoning behind each part.
Common questions
What is a cleaning quality control checklist?
A checklist used to score your own quality program rather than a site. It asks whether a written standard exists for each building, whether inspections happen on the cadence you claim, whether scoring is consistent between inspectors, whether failed items get assigned and closed, and whether you could produce a year of records for a customer tomorrow. It is normally run by an owner or operations manager once a quarter.
How is this different from an inspection checklist?
An inspection checklist scores a building on a given day. This one scores whether the system that produces those inspections is real. A company can pass every site inspection it runs and still fail this list badly, usually because the inspections are being run by one person from memory and would not survive that person leaving.
Who should run the quality control review?
The owner, or an operations manager who does not personally supervise the sites being reviewed. Someone reviewing their own program will pass their own program. If you are small enough that there is no such person, trade the review with another operator you trust and score each other.
How often should you review your quality control program?
Quarterly, and again after any structural change: a new supervisor, a large new account, a change in how inspections are recorded. Quarterly is frequent enough to catch drift and infrequent enough that people take it seriously when it happens.
What is the most common quality control failure?
Inspections that produce a score and nothing else. Almost every company that has a problem here is inspecting. What is missing is the second half: the failed item becoming a job assigned to a named person with a date, and somebody other than that person confirming it was done. Without that, inspecting simply generates a record of decline.