You wrote the RAMS. You updated the COSHH sheet after the new floor cleaner arrived last month. You even sent the H&S policy round in the WhatsApp group with “please read, this is important” typed above it. None of that proves a single cleaner actually read it. If a client, an insurer, or an HSE inspector asks who signed off on the current version of your policy, and when, “I sent it in the group chat” isn’t an answer. It’s an admission that you don’t actually know.
That gap, between having a policy and being able to prove a named person read it, is exactly what staff policy sign-off software exists to close for a cleaning company. Not because the paperwork is satisfying to file, but because a policy nobody can prove was read carries almost the same risk as no policy at all the moment something goes wrong on site.
Why “we sent it in the group chat” isn’t proof
A message in a group chat proves you sent something. It doesn’t prove anyone opened it, understood it, or even still has the number that group was built around after two staff changes. Twelve people in a thread, a policy PDF attached, and zero way of knowing which of those twelve actually read past the first line. If a client or auditor later asks “can you show me that this specific cleaner acknowledged this specific version of the manual handling policy,” a screenshot of a WhatsApp message with no reply underneath it answers a different question than the one being asked.
What a client, insurer, or inspector actually wants to see
The bar isn’t “does a policy exist somewhere.” It’s a specific, attributable record, and it needs four things to hold up:
- Who signed, a named cleaner, not a department or a generic “all staff” entry.
- When they signed, a real timestamp, not an approximate date typed in from memory.
- Which version they signed, tied to the exact document, not just its title, so a later revision doesn’t retroactively look covered.
- Which site or role it applies to, because a COSHH acknowledgement for one site’s chemical set doesn’t automatically cover a different site using different products.
A policy nobody can prove was read is not a policy. It’s a document that exists, which is a different thing entirely.
Old sign-offs go stale the moment the policy changes
This is where a lot of otherwise well-run companies get caught out. The RAMS gets updated after a near-miss, or a new cleaning product comes in and the COSHH sheet changes with it, and the old signed version keeps sitting in the folder looking perfectly compliant. A stale sign-off is arguably worse than no sign-off, because it creates the appearance of coverage that isn’t actually there anymore. The same problem shows up right next to it in one missing COSHH sheet away from losing the contract, both are cases where the underlying work might be fine, but the paper trail meant to prove it is out of date, scattered, or simply doesn’t exist in a form anyone can hand over on request.
Commercial clients increasingly ask for this alongside vetting, not instead of it. The same procurement teams checking DBS status and right-to-work documents before signing off a contract are starting to ask whether your staff have actually acknowledged the site-specific RAMS they’ll be working to. A vetted cleaner with an unsigned or outdated policy still leaves the client exposed, and a sharp procurement team knows that.
None of this needs to be complicated to be effective. It needs to be attributable, current, and retrievable in minutes rather than days, because the moment someone has to go looking for proof, the honest answer is usually that it doesn’t exist in a usable form.