When the cleaning specification and what's actually delivered drift apart
Every cleaning contract starts with a specification — the tasks, frequencies and standards agreed at the outset. Very few contracts, run long enough, still exactly match that document a year or two later. That's not usually the result of one decision to cut corners; it's the accumulated effect of small, individually reasonable adjustments, each of which made sense at the time and none of which was ever formally agreed against the original specification.
How drift actually happens
A task gets skipped once because a site was short-staffed, and becomes the informal norm because nobody flagged it as temporary. A client asks verbally for a change in priority that never gets written into the specification. A new supervisor inherits a site and works from what they observe happening rather than the original paper document, which they may never have actually read. None of these are dramatic failures — they're the ordinary way specifications quietly stop matching reality.
Why it matters even when nobody's complained yet
Drift can run for a long time without causing a visible problem, especially if the client is generally satisfied with the outcome even though the exact route to it has changed. The risk surfaces at specific moments: a client audit scoring against the original specification rather than current practice, a new facilities contact who reads the contract document literally and asks why it isn't being followed, or a renewal negotiation where the gap between paper and practice becomes a bargaining point the client raises.
- Periodically compare what's actually happening on site against the original written specification, not just against client satisfaction
- Formally document any agreed change rather than letting a verbal request become an informal, unrecorded new normal
- Brief new supervisors from the specification document itself, not purely from observing current practice on handover
- Flag drift internally as soon as it's noticed, rather than waiting for a client audit or complaint to surface it first
- Treat a specification review as a standing item at contract reviews, not something only revisited when a problem forces it
Fixing drift without alarming the client
Discovering and correcting drift doesn't need to be presented to the client as a confession of past failure — in most cases it's better framed as a routine tightening-up, particularly where the drift hasn't actually affected satisfaction. What matters is getting the specification and practice back in alignment, ideally with the client's awareness, rather than either reverting abruptly to the original document or leaving the informal version to keep drifting further.
Where a supervisor visit fits in
Regular supervisor site visits are one of the more reliable ways to catch drift early, precisely because they compare current practice against what should be happening rather than just checking general cleanliness. A supervisor working from the actual specification document, not institutional memory of "how this site's always been done," is far more likely to notice when the two have quietly separated.
Key takeaways
- Specification drift is usually the accumulated effect of small, reasonable adjustments, not one deliberate decision.
- It can run for a long time unnoticed if the client is broadly satisfied, then surface awkwardly at an audit or renewal.
- Document any agreed change formally rather than letting a verbal request become an unrecorded new normal.
- Brief new supervisors and staff from the actual specification, not just from observing current site practice.
- Regular supervisor visits, working from the specification rather than memory, are one of the more reliable ways to catch drift early.
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.