What it addresses and what it does not
INSST’s NTP 324 presents checklists as tools for identifying deficiencies and risk factors. Estimating risk also requires consideration of exposure and consequences; counting negative answers is not equivalent to assessment.
A checklist can support an inspection, a pre-use check or document review. It does not by itself establish full compliance or replace technical knowledge, measurements or tests where necessary.
Define scope before writing questions
Specify the equipment, task, location and conditions to be reviewed, who can do so and which decisions the check supports. Applicable legislation, manufacturer instructions, risk assessment and incidents provide criteria.
Copying another site’s checklist can omit risks or require irrelevant checks. People familiar with the activity and technical requirements should participate. A short, specific list is often more useful than an extensive one unrelated to the task.
Write observable checks
Each question should address one specific condition and make clear how it is checked. “Is the workstation safe?” is ambiguous; checking that a route is unobstructed produces defined evidence.
Separate issues that may have different answers. “Not applicable” and “not checked” must be distinguished from a compliant result, and their use justified. Where a requirement is critical, the checklist should identify the expected response to a deficiency.
Record context and evidence
Date, equipment, location, operating condition and reviewer allow results to be interpreted. Observations describe the problem precisely; a photograph may help, but does not always demonstrate function or effectiveness.
There must also be space for anomalies not included in the list. A checklist directs attention and can make unasked-about issues invisible. Listening to those performing the activity and observing the surroundings prevents it becoming an automatic sequence of tick boxes.
Move from findings to action
A deficiency should trigger a decision proportionate to the risk: correction, an interim measure, technical review or stopping work where appropriate. Preventive planning assigns owners, resources, deadlines and follow-up.
Closure requires checking that the condition was corrected and the solution works. A high percentage of compliant boxes can conceal one critical deficiency; results must not offset each other as if all requirements had equal importance.
Maintain the checklist and its version
Changes in equipment, legislation, processes or assessment may require updates. It should be possible to identify the version used and withdraw obsolete forms from routine use.
Digitalisation facilitates records and follow-up but does not automatically improve questions. Review repetitions, fields nobody understands and problems never detected. If answers are always identical, check whether the system is observing reality or reproducing previous responses.
Hypothetical example: reviewing a warehouse
A checklist asks whether aisles and exits are clear. One review finds an obstruction that is removed immediately, but subsequent visits find it again.
Follow-up reveals insufficient space for material awaiting dispatch. The final action changes that organisation and checks the result. Repeatedly signing off removal of the obstruction would have closed boxes without eliminating why it appeared.
