Read It Like They Will: A Ten-Minute Test for Frontline Risk Assessments
Photo: Roger Kidd, CC BY-SA 2.0, via Wikimedia Commons
A risk assessment can be signed, filed and reviewed on schedule yet still fail at the point of use. The document may satisfy a folder check while leaving a busy team member unable to find the row that applies to the job in front of them. For UK managers, the practical question is not simply whether an assessment exists. It is whether the people expected to follow it can use it under pressure.
This is a usability test, not a legal audit. It does not replace a suitable and sufficient assessment by a competent person. It does, however, expose the gap between paperwork and practice, and it can be done in ten minutes with two colleagues and the current controlled copy.
Why usability deserves a place on the checklist
The Management of Health and Safety at Work Regulations 1999 remain the baseline for UK employers, and the principles of sensible risk management have not changed. An assessment should identify the significant hazards, set out proportionate controls and be understandable to those who need it. A document that only its author can navigate is unlikely to shape behaviour on the floor.
Frontline staff rarely read a risk assessment from beginning to end. They arrive with a task in mind: changing a blade, moving a pallet, decanting a cleaning chemical, visiting a lone client. They need to locate that task quickly, recognise the hazard, understand the control and know who owns the next review. If those four items are buried, the assessment becomes an archive item rather than a working tool.
Set up a ten-minute read-through
Choose one task that carries a genuine risk and is performed regularly. Select two team members who do the task but did not write the assessment. Give them the current version and a simple scenario: they are about to carry out the task and have ten minutes to use the document. Ask them to show you the task, the main hazard, the control and the review date, then explain what they would do differently tomorrow.
Do not coach, prompt or point at the right page. Note where they look, how long they take and where they hesitate. Record the version date of the document. If two people reach for different copies, stop: version control is already part of the usability problem.
A five-question score
Use the same five questions for each person and score each answer from 0 to 2. A total of 10 is possible.
| Question | 0 | 1 | 2 |
|---|---|---|---|
| Can they locate the relevant task? | Cannot find it or needs help | Finds it after a long search | Finds it within a minute |
| Can they point to the main hazard? | Not stated or ambiguous | Buried in dense text | Clear and specific |
| Can they explain the control in their own words? | Cannot explain it | Repeats the wording without a practical example | Gives a practical example of what they would do |
| Can they find the review date and owner? | Neither is findable | Only one is findable | Both are clear |
| Can they name one thing they would do differently tomorrow? | No | Vague or generic | Specific to the task |
A score of 8 to 10 suggests the assessment is usable for that task. A score of 5 to 7 points to revision. A score of 0 to 4 means the document is not fit for frontline use in its current form, even if it is well intentioned.
What to listen for during the test
Jargon is a common barrier. Phrases such as 'ensure appropriate controls are implemented' may be technically correct but tell a busy operative very little. Passive sentences hide who does what. Cross-references to procedures stored elsewhere add friction. A review date printed only on the cover is easy to miss. A task listed under a hazard category rather than its common name forces the reader to translate before they can act.
Watch for the moment when a colleague asks a question such as 'Is this the old one?' or 'Where does it say who checks it?' Those questions are useful evidence. They show where the document expects the reader to carry knowledge that is not on the page.
One improvement to make before the next shift
Pick the lowest-scoring task and rewrite that single row or page. Use a task-first heading in plain language. Then set out the hazard, the control with a named role, and the review owner and date. Replace vague verbs with observable actions. For example, instead of 'appropriate PPE to be worn', state who wears which item and when. Instead of 'regular checks', state the frequency and the person responsible.
Do not attempt to rewrite the whole assessment overnight. Replace one task page, brief the team at the next handover and ask a different colleague to repeat the ten-minute test. Keep the original controlled copy, update the version and date, and record the change in the assessment register. That single improvement is realistic, traceable and more useful than a wholesale redesign that never reaches the floor.
Keep the test in proportion
A usability test does not prove that risks are adequately controlled. If the read-through reveals a missing hazard or an inadequate control, escalate it for proper assessment rather than treating it as a formatting issue. The test is a check on communication and access, not a substitute for competent review.
Used quarterly, or after a change in task, equipment or personnel, it gives managers a quick signal about whether the risk assessment is doing its job. The best document is not the longest or the most polished. It is the one a team member can pick up, understand and act on before the next shift begins.
