Traffic Management Risk Assessment: A Step-by-Step Method for Any Site

A traffic management risk assessment identifies what could hurt workers, drivers, cyclists and pedestrians at your site, judges how likely and serious each risk is, and chooses controls starting with the most effective. Work through the job stage by stage, apply the hierarchy of controls, record the result in the SWMS and plan, and review it when anything changes.

Most traffic management risk assessments fail in one of two ways. Either they are generic, copied from the last job with the address changed, or they are thorough on paper but never reach the people setting out the cones. This guide gives you a method you can use for anything from a driveway pour to a night lane closure, a filled-in example, and the review triggers that keep it current. It is general guidance only. It is not legal or engineering advice, and traffic guidance schemes (TGS) must be prepared by a suitably qualified person under your state's requirements. For the legal duties behind it, read WHS duties for road work.

Why the risk assessment comes before the plan

Work on or next to a road used by traffic is high-risk construction work under WHS laws, so a safe work method statement (SWMS) is required before work starts. The risk assessment is the reasoning that drives both the SWMS and the traffic arrangements.

Done properly, it answers questions that change the design: Can we avoid working next to live traffic at all? Should this be a full closure on a Sunday instead of a lane closure on a Tuesday? Do we need a barrier or a truck-mounted attenuator (TMA)? A plan drawn first and assessed afterwards tends to justify itself rather than test itself.

National guidance on managing risk is published by Safe Work Australia, and state regulators such as SafeWork NSW publish codes of practice. The Austroads Guide to Temporary Traffic Management (AGTTM) and each state's supplement set the traffic-specific requirements.

Step 1: Gather the site facts

You cannot assess a site you have not seen. Before anyone opens a template, collect:

• road type, speed limit and the speed traffic actually travels
• traffic volumes and peaks, including heavy vehicles and buses
• sight lines: crests, bends, trees, parked cars, sun angle at the work times
• pedestrians, cyclists, schools, shops, driveways and bus stops
• the work method, plant and vehicles, and where they need to move
• duration: minutes, hours, days or weeks, and day or night
• what is next to the work zone: drop-offs, excavations, overhead lines, rail crossings

A site visit at the same time of day as the work is worth more than an hour on a map. Take photos from the driver's position on each approach.

Step 2: Break the job into stages and list the hazards

Traffic hazards change through the shift. Assessing "the job" as one block misses the moments when people are most exposed.

Then add the people-related hazards: fatigue on long and night shifts, heat and UV, and verbal or physical abuse from the public. These are recurring hazards in traffic control, not rare events.

Step 3: Rate each risk consistently

For each hazard, ask who could be hurt, how badly, and how likely it is with no controls in place. Most companies use a likelihood and consequence matrix for this. Which matrix you use matters less than using the same one consistently, so a "high" means the same thing on every job.

Two rules keep scoring honest:

1. Rate the realistic worst outcome, not the most common one. A car entering the work zone at speed is a fatality risk, even though most intrusions end with a near miss.
2. Do not lower the score because the crew is experienced. Experience is part of competence, not a control that stops a vehicle.

Step 4: Choose controls from the top of the hierarchy

The hierarchy of controls applies to traffic management as it does to any hazard. Work from the top down and only move to the next level when the one above is not reasonably practicable.

Our guide on choosing between cones, barriers or a full closure walks through the separation decision with examples. Remember that specific dimensions such as taper lengths, sign spacings and buffers come from the TGS, AS 1742.3 and your state's manual for that road and speed, not from the risk assessment template.

Example scenario: a two-day water main repair near a school

Here is how this plays out on a typical job. A utility contractor needs to excavate and repair a water main in one lane of a two-lane 60 km/h collector road. A primary school entrance is 150 metres away. The work runs over two days, about 7 am to 4 pm, with an excavator, a tipper and a vacuum truck.

Site facts gathered. The supervisor visits at 8.15 am and 3 pm. Heavy school traffic, parents parking on both sides, a bus stop on the work side, and a slight bend limiting sight lines from the north.

Initial plan. Stop/slow with two controllers, working through the school peaks.

Assessment challenges the plan:

• End-of-queue risk from the north is high because of the bend and peak traffic.
• Children walking past the excavation on the footpath during peaks.
• The bus cannot stop at its usual stop.
• Reversing tipper movements inside a narrow work area.

Controls chosen, from the top:

1. Eliminate: the contractor asks whether excavation can pause and the site be plated and made safe during school drop-off and pick-up. The client agrees, subject to approval of the hours in the permit.
2. Separate: pedestrian barriers and a signed footpath diversion on the opposite side, with a temporary crossing point managed by a controller.
3. Reduce speed: portable traffic lights instead of manual stop/slow, if approved in the TGS, removing controllers from the live lane.
4. Warn: advance signs placed per the TGS on each approach, with extra warning from the north for the bend.
5. Administrative: a dedicated spotter for all reversing, a bus operator notified to relocate the stop, an inspection at start, during and end of each shift, and a briefing on escape routes.

What goes wrong on day one: at 2.50 pm the queue from the north extends past the PREPARE TO STOP sign because a parent drop-off zone was missed. The traffic control supervisor holds the lights longer for the north, asks a second controller to move the advance signs back as the TGS allows, and calls the designer, who confirms the arrangement for day two is updated.

What gets recorded: the revised TGS, the reason for the change, who approved it, the time it took effect, and a toolbox talk note before day two.

Step 5: Record it where the crew will use it

A risk assessment in a project folder protects nobody on the road. Make sure:

• the controls appear in the SWMS in plain language
• the TGS shows the physical controls and positions
• the pre-start briefing covers each high risk and its control
• every worker signs onto the SWMS before starting, including late arrivals

Our SWMS for traffic control guide lists what the document must include. A short daily briefing works better than a long one people tune out of.

A printable risk register template

Step 6: Review when anything changes

A risk assessment is a living document. Review it when:

• the work method, plant or work area changes
• traffic volumes or speeds are different from what was assumed
• a control is not working, such as queues past the warning signs
• the weather changes, such as fog, heavy rain or strong wind
• the crew changes or someone is new to the site
• there is an incident, intrusion or near miss
• the client, council or road authority requires a change

Record what changed, who decided, and when it took effect. Our guide to when a traffic management plan should be reviewed covers the formal triggers.

Next steps

Start your next assessment with a site visit at the same time as the works, break it into stages, and challenge the first plan with the hierarchy of controls. The free traffic control checklists can help structure your pre-start and inspection records. Check current requirements with your state regulator and the road authority before relying on any template.