Learning From Near Misses: 8 Example Reports and What Each Should Change

Good near miss examples from traffic control show the same pattern: a plain description of what happened, a cause that goes deeper than "careless driver", and a specific change to the plan, set-up, briefing or equipment. A report that changes nothing is just paperwork. The eight examples below show what each should lead to.

All eight are example scenarios written for this guide, not real incidents. They are typical of what crews see on Australian roads, and they are written the way a useful report should be written. For the reporting process itself, including notifiable incidents, see incident and near-miss reporting for traffic control companies. This is general guidance, not legal advice; check notification duties with your regulator.

What makes a near miss report useful

A useful report answers five questions:

1. What happened? Time, place, who, what, in order. Facts, not opinions.
2. What stopped it becoming an injury? Luck, a quick reaction, a barrier, a TMA. This tells you which control worked.
3. Why did it happen? Ask "why" until you reach something the company controls.
4. What should change? One or more specific actions, with an owner and a date.
5. Was the change made? Someone checks and closes it.

When choosing fixes, use the hierarchy of controls: eliminate the hazard (close the road, detour), separate (barriers, TMA), reduce speed, warn (signs, VMS), then procedures and PPE. Fixes higher up the list work better.

Weak report versus strong report

Most weak reports fail in the same few ways. Compare the two versions of the same event:

The strong version takes two more minutes to write and gives the operations manager something to act on. Supervisors can coach this by reading the first few reports from a new crew member and asking one follow-up question each time.

Examples 1–4: vehicles and the work zone

Example 1: Car enters the closed lane. Report: "10:40 am, eastbound lane closure. A sedan drove past the taper into the closed lane and stopped about 15 metres from a worker at the kerb. Driver said they didn't see the merge. Worker stepped onto the footpath." Why: The drive-through after the report found the first advance sign hidden by a parked truck that arrived after set-up. Change: Add parking checks to every inspection on this road; ask the client whether the TGS should include no-stopping at the sign positions. See work zone intrusions.

Example 2: Truck reverses towards a controller. Report: "7:15 am, site access. Tipper reversed out of the work area towards TC 2's station without a spotter. TC 2 moved away. No contact." Why: The site's reversing plan existed but the driver was a new subcontractor not inducted. Change: Induct every new driver at the gate; spotter assigned for all reversing; brief in the pre-start. See reversing plant and spotters.

Example 3: Vehicle fails to stop at stop/slow. Report: "3:20 pm, north end. Ute passed TC 1 showing STOP at about the speed limit. TC 1 used escape route. Vehicle slowed in the shuttle lane and passed oncoming traffic on the shoulder." Why: Queue had extended past the prepare-to-stop sign; drivers were arriving fast at a queue they didn't expect. Change: Queue length trigger set for the afternoon peak; extend end-of-queue warning as the TGS allows; review whether portable traffic lights suit the site.

Example 4: Work zone speed ignored. Report: "Throughout the shift, controllers reported vehicles passing the work area well above the temporary speed. No contact." Why: Long, straight approach with no visible work for most of the zone; drivers saw no reason to slow. Change: Raise with the TGS author whether the zone can be shortened to where work is happening, and whether speed awareness devices are suitable.

Examples 5–8: equipment, communication and people

Example 5: Sign blows into the traffic lane. Report: "1:50 pm, wind change. A sign blew over and slid into the left lane. A car swerved. TC 2 reported it, supervisor recovered it during a gap." Why: Sign stand weighted for the morning's conditions; nobody rechecked when the wind rose. Change: Add "re-weight all signs on wind change" to the site's weather triggers; carry extra weights.

Example 6: Both ends release at once. Report: "11:05 am, stop/slow. TC 1 released westbound while TC 2's last vehicle was still in the shuttle lane. Vehicles met head-on at low speed; one pulled onto the shoulder." Why: TC 2's radio call described the last vehicle as "white car"; there were two. Change: Brief full description calls (make, colour, type); release only after the described vehicle passes; refresh on the stop/slow bat technique.

Example 7: Pedestrian walks through the work area. Report: "8:35 am. Pedestrian walked past the footpath closure into the trench area. Works crew stopped excavator. Pedestrian redirected." Why: Detour sign was only at the closure itself, not at the earlier corner where people decide their route. Change: Add detour signs at decision points; assign a person at school times.

Example 8: Controller nearly faints in heat. Report: "2:10 pm, 36 degrees. TC 1 felt dizzy on the bat and sat down in the closed lane. Supervisor relieved TC 1, provided water and shade." Why: Rotation planned hourly but slipped because of crew shortage. Change: Roster an extra controller for hot days; supervisor tracks rotation times; see heat stress and traffic controllers.

Summary table: example, cause and change

The level column is a guide for discussion, not a strict classification; several fixes combine more than one level. Notice how few of these causes are "the driver". Even where a driver did something wrong, there is almost always something in the plan, set-up, briefing or roster that made it more likely.

Example scenario: from report to change in one week

Here is how this plays out on a typical job, using Example 6.

1. Monday 11:05 am. The near miss happens. Nobody is hurt. The supervisor stops both ends, checks everyone is OK and resumes once the crew is calm.
2. Monday 11:30 am. TC 1 and TC 2 write the report with the supervisor at the break, while details are fresh. They note the exact radio call made.
3. Monday afternoon. The operations manager reads it and asks why. The answer: the crew had drifted into short calls during a busy morning.
4. Tuesday pre-start. The supervisor briefs the full call format and practises it with both ends. The company adds the call format to its stop/slow briefing notes for every site.
5. Wednesday. The operations manager checks in at the site and listens to the radio. Calls are complete.
6. Friday toolbox talk. The example is shared, without names, with all crews.
7. Close-out. The report is marked closed with the action, date and who checked it.

Near miss report template

Some events must be notified to the regulator even if nobody is hurt. Check what counts with SafeWork NSW or Safe Work Australia, and preserve the site where required.

Getting crews to report

Reporting rates rise when reporting is quick, nobody is blamed and people see changes. Practical steps:

• Make the form short enough to fill in on a phone at the break.
• Thank people for reports, publicly.
• Share the change at the next toolbox talk.
• Never use a near miss report to discipline the reporter for an honest mistake.
• Look for patterns monthly: the same site, time of day, task or type of event turning up more than once.
• Report back to the reporter personally when their report led to a change, even if it was small.
• Treat a month with no reports as a warning sign, not a success. On busy roads, near misses happen; silence usually means they are not being written down.

Next steps

Pick one recent near miss and run it through the five questions with your crew. If you want reports, pre-starts and SWMS sign-on in one place, a platform like TrafWise keeps crew records together so the follow-up is easier to track.