How to write a risk assessment that tradespeople will actually use

If you're reading this, you probably know how to write a risk assessment already. You can list the hazards, weigh up the risk, and come up with some controls. That's the easy part, and it's not what this article's about.

The real problem is what happens when that document actually reaches site. You hand it to the crew, and it goes in the van, or in a folder, or gets folded up in a hi-viz pocket. Nobody reads past the first line. The words you spent an evening writing sit there doing nothing, and you're left with a box you've ticked rather than a tool that keeps people safe.

This article's about fixing that. It's about writing controls a tradesperson will actually read, understand, and follow on a Monday morning. Because a risk assessment only works if the person holding the tools acts on it.

Why Risk Assessments Get Ignored

Most risk assessments fail for the same three reasons, and none of them are about the quality of the paperwork. They're about how the document is written and who it's written for.

The Box-Ticking Trap

A lot of risk assessments are written for the wrong audience. They're written to satisfy an auditor, a client, or a compliance officer, not to help the person doing the actual work. The result reads like it was produced to be filed away, not acted on.

When you write for the auditor, you write to cover yourself. When you write for the worker, you write to keep them safe. Those produce very different documents, and only one of them gets read on site.

Generic Controls Nobody Follows

The classic offender is the control that says "wear appropriate PPE" or "follow safe working practices". These sound sensible on paper, but to the person holding a grinder on a scaffold, they mean nothing. What's appropriate? Which practices? What's the actual thing you need to do differently?

Vague controls get ignored because they're uncheckable. Nobody can tell whether they did it or not, so nobody does it. Guidance should land as a specific instruction, not a general principle.

The One-Page Problem

There is also a layout problem, and it's the opposite of what most people expect. The danger isn't that documents are too short but that real hazards get buried. When a risk assessment runs to eight pages of near-identical rows, the one genuinely dangerous task, the one that could kill someone, sits in the middle looking just like everything else. Nobody finds it.

If you're still working out your hazards and getting through the mitigation hierarchy, the risk assessment step-by-step guide covers the mechanics so this article can stay focused on making the words work.

Write Controls People Will Actually Follow

Here's the shift that changes everything. Stop describing a hazard and start telling a specific person what to do about it. A good control is an instruction, not a description.

Name the Hazard and the Exact Action

A control should be specific enough that someone watching could tell you whether it happened. "Keep the work area clear" isn't that. "Move the cable and cut-offs behind the board before you climb the steps" is. Name the hazard, then name the exact action, then say when it starts and when it ends.

Observable instructions get followed because they can be checked, by you and by the person doing the job. If you can't tell whether a control was followed, rewrite it until you can.

Write for the Person Holding the Tools

Use plain language and the second person. Say "you" and "before you start", not "operatives shall" or "personnel must ensure". If a sentence would sound odd said out loud on a site, it won't survive a single read on one either.

Think about which control actually stops the work. If you want to know how far up the hierarchy a given measure sits, and what "reasonably practicable" means in practice, the hierarchy of controls guide breaks down elimination, substitution and engineering controls in plain English. That's a relevant read for how you word your own controls.

Common Risk Assessment Format Mistakes

You can tell a lot about how someone approaches writing a risk assessment from the layout alone. These are the mistakes that get in the way of a document being read.

How to Brief Your Team on the Risk Assessment

Writing a readable document is only half of it. The other half is making sure the people doing the work have actually taken it in. Briefing the team at the start of the job is good practice, and on a project with a principal contractor it lines up with the worker-consultation expectations under CDM 2015. It isn't a separate legal burden for every solo job, but it makes the document work.

Make It a Two-Minute Conversation

Talk through the controls before work starts, out loud, with the people who'll be doing the job, and ask what they would change. Keep it short, point at the specific things that will stop the work, and check the crew actually heard them. If someone spots a hazard you missed or a control that won't work in practice, update the document before work starts. Then note the date on the document so there's a record that the briefing happened.