What a supervisor should actually check on a site visit

A supervisor site visit can mean very different things depending on the supervisor and the day — anywhere between a genuinely useful structured check and a quick walk-through followed by a chat with whoever's on shift. The difference matters more than it might seem, because a site visit is one of the few points where problems that don't show up in a checklist or a distant audit score can actually get caught.

Why an unstructured visit misses things

Without a structure to work from, a site visit naturally drifts toward whatever's visually obvious and whatever the team on shift happens to mention — which tends to miss the quieter problems: a checklist being completed implausibly fast, a specification that's drifted from what's actually being delivered, or a compliance gap that isn't visually apparent at all, like an out-of-date safety data sheet sitting in the store cupboard.

What's actually worth checking

A genuinely useful visit combines a physical check of standard — is the site actually clean to the agreed specification — with a review of the records behind it: are checklist completions consistent with what a supervisor can see was actually done, are compliance documents current and matched to what's physically on site, and can the team on shift speak confidently to how the site is meant to be run rather than needing to check with someone else for basic answers.

• –Compare physical standard against the current specification, not against a general sense of whether the site looks clean
• –Spot-check recent checklist completions against what's plausible for the time actually taken
• –Check that COSHH documentation on site matches products physically in use, not a previous or discontinued version
• –Ask the team on shift open questions about how the site runs, rather than only questions with an obvious expected answer
• –Note anything raised previously and confirm it's actually stayed fixed, not just addressed in the moment it was last flagged

Timing visits deliberately, not just routinely

A visit that always happens at the same time, on the same day, tends to show the site at its most prepared rather than its ordinary state — staff often know roughly when to expect it, consciously or not. Varying the timing, and occasionally visiting a newly onboarded site inside its first couple of weeks specifically because that period carries the highest onboarding risk, gives a more accurate picture than a fixed, predictable schedule.

Turning what's found into something that sticks

A finding from a site visit needs the same discipline as any other audit finding — a specific description, an owner, and a follow-up to confirm it actually got fixed rather than just noted. A supervisor's own informal notes, if they never turn into a tracked action, tend to get lost between visits in exactly the way a formal client audit finding wouldn't be allowed to.

The visit that finds nothing

A supervisor who visits a site and reports nothing has either found a well-run site or run an unstructured visit. From head office these look identical, which is the argument for a visit having a shape — a handful of things checked every time, so that "nothing found" is a result rather than an absence of looking.

Timing matters as much as content. A visit always made at ten on a Tuesday inspects a site that knows a visit is always made at ten on a Tuesday. Varying the time, and occasionally arriving at the end of a shift rather than the middle, tends to produce a different picture of the same contract.

Common mistakes

• –Visiting without a consistent set of checks, so visits are not comparable
• –Always arriving at the same time on the same day
• –Checking the areas the client looks at and skipping the ones they do not
• –Speaking only to the supervisor and never to the staff doing the work
• –Recording findings in a notebook that never reaches anyone
• –Reporting nothing found without noting what was actually checked