Building a COSHH audit checklist your supervisors will actually use

A COSHH audit checklist has one job: catching the gap between what's written down and what's actually happening on site, before a client or the HSE finds it first. Most contractors have some version of one. Fewer have a version supervisors actually reach for on a routine site visit, rather than something dug out specifically ahead of a known audit.

Why the folder version doesn't get used

A long, thorough checklist — the kind that covers every substance, every regulation reference, every possible finding — is genuinely useful as a reference document and genuinely unlikely to be run through on a normal Tuesday between other tasks. Supervisors default to what's quick. If the honest choice is between a fifteen-minute form and getting to the next site on time, the form loses, and COSHH checking quietly becomes something that only happens ahead of a scheduled visit rather than as routine practice.

What a working version actually checks

A checklist that gets used tends to be short and specific: does the SDS on site match what's physically in the cupboard, is it accessible rather than locked in an office, are products stored separately according to the risk assessment rather than convenience, is anything decanted into an unlabelled container, and can the staff member on shift name the hazard of the product they're currently using. That last question does more work than most of the others — it tests understanding, not just the presence of a document.

• –SDS on site matches the product physically in the cupboard, not a discontinued or previous version
• –Products stored according to the risk assessment, with incompatible substances kept apart
• –No decanted or unlabelled containers in use
• –PPE specified in the assessment is present and actually being used, not just available
• –The staff member on shift can describe the hazard of the product they're using in their own words
• –Any recent product or supplier change reflected in the SDS and assessment on file

Making it something supervisors reach for

The practical fix is usually format rather than content — a checklist that fits on a phone screen and takes five minutes gets used far more consistently than a multi-page form that requires sitting down with a laptop. Whether that's a short paper form or something built into whatever quality audit tooling a contractor already uses on site, the length is the thing most worth cutting down, not the coverage.

Closing what it finds

A checklist that surfaces a gap and then goes nowhere isn't much better than not checking at all. Whatever it flags — a mismatched SDS, an unlabelled bottle, PPE that's gone missing — needs a clear path to actually getting fixed and confirmed closed, in the same way any other audit finding needs raising and closing properly rather than noted and left.

What a working checklist finds that a filed one does not

A supervisor running a genuine ten-minute check on a live site tends to surface the same handful of things, and none of them are visible from head office: a decanted bottle with no label, a dilution dispenser that has been broken long enough that people have stopped mentioning it, gloves in the wrong size so nobody wears them, a sheet on the wall for a product that was replaced in spring, and one member of staff who has never used the product she was handed on Monday.

That list is worth noticing because none of it appears in a records audit. All five would pass a folder inspection and all five are live risk. It is the argument for the checklist being something carried around a site rather than completed at a desk.

Common mistakes

• –Building the checklist around what is filed rather than what is in the cupboard
• –Making it long enough that supervisors complete it from memory at the end of the day
• –Recording findings without an owner and a date, so nothing closes
• –Running it only before a client audit, which is when the site is least representative
• –Never checking the same site twice, so nothing is ever confirmed fixed
• –Treating a clean checklist as proof, rather than asking why nothing was found