Staff compliance records: what a cleaning contractor needs to keep and for how long
A cleaning contractor's staff compliance file is usually a mix of a few different obligations sitting side by side: right to work evidence, COSHH training records, and depending on the client and site, things like DBS checks or site-specific inductions. None of these is individually complicated. Keeping all of them current for a workforce with real turnover, shift patterns and multi-site movement is where it gets genuinely difficult.
Why "we have the records" isn't the same as "they're current"
Most contractors, asked directly, would say their compliance records are in order. What that usually means in practice is that a record exists somewhere for most staff, most of the time — not that every current employee has every applicable check up to date on the day someone asks. The difference matters because a client audit or an inspection doesn't ask about the general state of the file; it asks about a specific person, on a specific date, and expects a specific answer.
What actually belongs in the file
The exact requirements vary by client contract and by role, but a reasonably complete staff compliance record for a cleaning operative typically covers evidence of right to work, COSHH training relevant to the products they use, any site-specific induction the client requires, and, where the contract or site calls for it, a DBS check. What matters as much as the list itself is that each item has a date attached and, where relevant, an expiry or review trigger — a record with no date is functionally unverifiable.
- Right to work evidence, dated, including for agency and subcontracted staff working under the contract
- COSHH training records specific to the substances a person actually uses, not a generic "completed COSHH training" flag
- Site-specific inductions where a client contract requires them
- DBS checks where the site or client specification calls for one, with renewal dates tracked
- A single, current status per person rather than a history that requires interpretation to work out what's actually valid today
Retention and access
How long records need to be kept, and in what format, depends on the specific requirement — right to work evidence has its own retention expectations under Home Office guidance, for instance, separate from how long a training certificate is useful to keep on file. What's consistent across all of them is that the record needs to be genuinely retrievable, not technically retained somewhere nobody can access quickly. A file that exists but takes two days to locate during a client audit doesn't function much differently to a missing one on the day it's actually needed.
Turnover is the real operational challenge
Cleaning has higher staff turnover than many sectors, and cover shifts and agency staff add a second layer of complexity on top of that. The practical answer isn't a stricter policy — most contractors already have a reasonable policy on paper. It's a system that makes it obvious, at a glance, which current staff have a gap, rather than relying on someone remembering to manually check every new starter and every renewal date across every site.
Turnover is the thing that actually breaks the file
A cleaning business with meaningful churn is not maintaining a static set of records; it is running a queue. Every leaver needs their file retaining correctly rather than deleted, every joiner needs a complete one before their first shift, and the people in between need their expiring items watched. At twenty per cent annual turnover across two hundred staff that is roughly one complete file built and one retired every week, indefinitely, on top of the day job.
Businesses rarely fail this because they do not care. They fail it because the work is continuous and invisible, and it is nobody's named responsibility until an audit makes it urgent.
Common mistakes
- Letting a joiner start before the file is complete, intending to catch up
- Deleting a leaver's records immediately rather than retaining them for the required period
- Holding records in a personal drive or inbox rather than somewhere the business owns
- Having no single person accountable for the file being current
- Tracking documents but not their expiry dates
- Discovering the backlog only when a client asks for a named individual's file
- A record existing somewhere isn't the same as it being current for a specific person on a specific date — that's the distinction an audit actually tests.
- Every compliance item needs a date and, where relevant, a renewal trigger — an undated record is effectively unverifiable.
- Retention and access requirements vary by check type, but all of them need to be genuinely quick to retrieve, not just technically kept.
- High turnover and agency cover are the real operational challenge, more than the individual compliance requirements themselves.
- The goal is visibility into current gaps at a glance, not a stricter policy nobody has time to manually enforce.
About this article
The CleanOptix team
Written by people who work daily with cleaning contractors on contract delivery, COSHH and the records that hold up under a inspection.
- Published
- 3 March 2026
- Last revised
- 27 September 2026
- Topic
- COSHH & Compliance
How this is researched, dated and corrected is set out in our editorial standards. If something here is wrong or out of date, email hello@cleanoptix.co.uk — corrections to a regulated detail are made as soon as we can confirm them, and the revision date above moves when they are.