TivloThe call comes in: your client is conducting a cleaning contractor audit in three weeks.
For a lot of cleaning company owners, that sentence produces a low-grade dread. Not because the operation is bad, but because proving it is not is a different skill set to running it.
Audits fail for a handful of predictable reasons. Not because the cleaning is poor, and not because the contractor is cutting corners. They fail because the paperwork is not in order, the records do not tell a consistent story, or the people on site cannot explain the processes that are supposed to be in place.
This guide covers what cleaning contractor audits actually involve, what auditors are most likely to find wrong, and how to prepare so that your first audit does not become your worst.
What a Cleaning Contractor Audit Is Actually Looking For
An audit is not an inspection of how clean the building is. That might surprise you, but it is true.
The auditor is there to assess whether your operation meets a defined standard systematically, not whether the floors were swept last Tuesday. They are looking for evidence of a system, not a snapshot.
Specifically, most cleaning contractor audits examine:
- •Health and safety compliance -- COSHH assessments, method statements, PPE provision and usage
- •Staff competency -- training records, induction documentation, BICSc or equivalent accreditations where required
- •Site-specific documentation -- risk assessments that name this specific building, not a generic template
- •Quality management -- how inspections are conducted, recorded, and followed up
- •Communication and reporting -- how issues are escalated, who is the point of contact, what the response time SLA is
- •Environmental and chemical management -- are COSHH substances correctly stored, labelled, and recorded?
The audit is a check of your management system. The building may be spotless, but if you cannot demonstrate the system that keeps it that way, you will not pass.
The Five Things That Cause Audits to Fail
1. Generic risk assessments
This is the most common failing. The contractor submits a COSHH risk assessment or method statement that was clearly written for a generic office environment and has not been adapted for the specific site.
An auditor at a school contract will look for risk assessments that reference areas children use, hours of operation, and COSHH substances appropriate to an educational setting. A generic document with the client's name pasted in the header is not adequate.
Fix: maintain site-specific versions of all core documents. They can share a common structure, but the specific site details must be accurate.
2. Outdated training records
Staff training records that are incomplete, out of date, or missing entirely are an immediate flag. If your long-serving operatives completed induction training four years ago and there is no record of refresher training since, that is a gap.
Many auditors will also check whether training is appropriate to the tasks being performed. COSHH training, manual handling, and any specialist training for the site in question (clinical environments, food preparation areas, etc.) should all be documented and current.
Fix: maintain a training record for each operative that includes date of training, trainer name, and next review date. Review annually as a minimum.
3. No inspection records
If you cannot demonstrate that you are monitoring the quality of your own service, the auditor will question whether quality is being managed at all.
A site visit is not the same as a documented inspection. The inspection record should show what was checked, what was found, any issues raised, and what action was taken. If you visited a site twelve times last year and cannot show a single inspection record, that is a problem.
Fix: introduce a structured inspection programme with a consistent record format. Even a simple checklist completed and signed monthly is better than nothing.
4. Communication that exists only in WhatsApp
This one is increasingly common as cleaning companies rely on messaging apps for day-to-day communication. The problem is that when an auditor asks you to demonstrate how you escalate issues or report near-misses, "we WhatsApp the supervisor" is not a system.
You need to be able to describe a process, show that it is documented, and ideally evidence it in practice.
Fix: define your escalation and communication process in writing. It does not need to be complex. A one-page document that says who reports what to whom, within what timeframe, and how it is recorded is enough.
5. Staff who cannot describe the procedures
An auditor may speak to operatives as well as managers. If your staff on site cannot explain what to do in the event of a COSHH spill, or what the reporting process is for an accident, that raises questions about whether your training programme is real.
This is not about expecting operatives to recite policy documents. It is about whether the systems you have on paper are the same ones being used in practice.
Fix: brief site supervisors before an audit. Make sure they know the key procedures and can talk confidently about the inspection and reporting process.
Preparing Effectively in the Three Weeks Before an Audit
Week 1: Document review
Pull together all compliance documentation for the specific site being audited: COSHH assessments, risk assessments, method statements, insurance certificates. Check the dates. Update anything that has expired or lapsed.
Make sure every document is specific to the site. Generic templates are not adequate. This is also the time to check that your insurance certificates cover the correct level for this contract.
Week 2: Records review
Compile your inspection records, incident records, and training records for the past twelve months. Identify any gaps. If inspections were skipped, be prepared to explain why. If training is overdue, schedule it now.
If you use a paper-based system, get it organised into a format you can present clearly. Folders stuffed with loose sheets do not create confidence.
Week 3: People preparation
Brief your site supervisor and any operatives likely to be present during the audit. Walk them through the key procedures, particularly COSHH handling, escalation, and reporting. Make sure they know what an inspection involves and who to contact if they are asked something they cannot answer.
On the Day
Arrive with your documentation pre-organised. An auditor who has to wait while you search through your laptop for a file has already formed an impression.
Be honest about gaps. If you identify a weakness in your documentation before the audit, it is better to acknowledge it upfront and explain the corrective action you are taking than to hope it is not noticed. Auditors are experienced. They notice.
After the audit, request the findings in writing even if the verbal outcome was positive. Knowing exactly what was assessed and how you performed gives you a baseline for continuous improvement and a record to reference at the next audit.
Building a System That Does Not Need Cramming
The cleaning companies that pass audits without stress are not the ones who work hardest in the three weeks before. They are the ones who maintain their documentation, inspection records, and training schedules consistently throughout the year.
That consistency does not happen by accident. It requires a system: a place where records are kept, a schedule for inspections, a process for updating compliance documents when they change.
Tivlo is a client portal built for cleaning companies that includes structured inspection reporting and document management. If you want to see how your current operation stacks up against what professional auditors are looking for, the Tivlo scorecard will give you a clear picture in five minutes.
Tivlo is a client portal built for cleaning companies. It helps you manage inspection records, share compliance documents with clients, and demonstrate a professional operation at every contract review.