How to document a blocked access route for an HSE report

An access route doesn't need a forklift wedged across it to count as blocked. A pallet of blockwork creeping two metres past its laydown line, a skip left in the swing of the site gate, scaffold tube stacked against a fire route sign: all of it narrows the path below the width your RAMS says it needs to be. The job is the same either way. You need a record that stands up if someone asks about it six months later, and that gets the obstruction cleared this week, not logged and forgotten.

What actually needs to go in the report

Start with the route reference, not a description of where you were standing. If your site logistics plan numbers the routes (Route 3, Access B, whatever the drawing calls it), use that number. "Blocked near the canteen" means nothing to the next shift supervisor who wasn't there.

Then:

• Date and time the obstruction was found, not when you got round to writing it up.
• What's blocking it. Name the material or plant, not just "materials." A pallet of insulation board is a different corrective action than a parked telehandler.
• How much of the route width is left. If the plan specifies 3.6 m clear for plant and pedestrian segregation and you've got 1.2 m left, write 1.2 m. A vague "partially blocked" gets read differently by every person who reads it.
• Who's responsible for the area, if you know. Trade package, subcontractor, or "unknown, no delivery ticket visible."
• Photo evidence, timestamped, taken from a position that shows the obstruction against a fixed reference point: a gate, a hoarding panel, a marked line on the ground. A photo of a blockage with nothing in frame to judge scale against is close to useless in a dispute.
• Immediate action taken. Did you get it moved, put out cones and tape, or just flag it and walk on? Write down which.
• CAR number and close-out date, once it's raised.

That's the skeleton. The report reads as a record of fact, not a complaint, which matters if it ever ends up in front of a client's HSE rep or an HSE inspector asking why a fire route was obstructed on the day of an incident elsewhere on site.

Template language that holds up

Keep the wording factual and specific. A line like "Access Route 3, west elevation, obstructed by stacked scaffold tube (approx. 4 bundles) reducing clear width from 3.6 m to 1.1 m, observed 09:40, 14 Oct" does more work than a paragraph explaining how unsafe it felt. Avoid adjectives that aren't measurements: "seriously," "badly," "completely" don't tell the next reader anything the numbers don't already say.

If you're recording a near-recurring obstruction (same route, same subcontractor, third time this month), say that in the report rather than filing it as a one-off. That's the detail that turns a single CAR into a pattern worth raising at the next subcontractor coordination meeting.

Where the gap actually comes from

Most blocked-route write-ups start with a walk: a supervisor notices the obstruction, logs it, moves on to the next task. That only covers the routes that particular walk happened to cover. A site with six active laydown areas and four access routes doesn't get walked end to end every week, not by one person with the rest of the job to do. The violation sits there until it's in someone's way badly enough to force the issue, logged or not.

Site Logistics Audit is built around that gap: a weekly overhead pass that flags laydown encroachment, blocked routes and missing edge protection against your logistics plan, so you've got a list to work from before you've walked a metre of the site yourself. It doesn't replace the write-up above. It's the reason you know where to go write one.

If closing out access and edge-protection violations before they turn into an incident report sounds like the gap on your site, that's exactly what Site Logistics Audit is for.