Sites do not have traffic accidents, they have traffic agreements that failed. Somewhere a vehicle and a person both believed the space was theirs, and the system that should have made one of them wrong in advance was missing, stale or ignored. Traffic management is the practice of keeping that agreement current, and it has four parts.
Part one: the plan
Anything beyond a trivial site needs the traffic arrangement written down: entry and exit points, internal routes, reversing areas, delivery staging, pedestrian paths, and the location of every point where flows could meet. For work affecting public roads, this becomes a formal traffic management plan under the state scheme, prepared and implemented by accredited people, a legal requirement, not a Rentafence service, and the equipment then serves the plan.
The plan's most valuable output is the conflict point list: every place a vehicle path and a pedestrian path approach each other. Each conflict point gets a named control, or the plan is not finished.
Part two: the people
Every control decays without an owner. Barriers get moved for a delivery; the owner puts them back. Headcount doubles; the owner re checks the pedestrian routes. The wet season arrives; the owner walks the site asking what changed. On small sites this is the supervisor with a weekly loop; on large ones it is a role. Either way, a plan without an owner is a document, not a system.
Part three: the equipment
The gear divides cleanly by function, and the water barriers and traffic equipment guide covers the assignment logic in depth:
- Instruction: arrow boards where drivers need telling early
- Guidance: reflective cones shaping the path
- Separation: water filled barriers wherever pedestrians and vehicles share geography
- Containment: ricochet barriers for the road speed edge, detailed in the ricochet guide
- Definition: the perimeter itself, per construction site fencing
Part four: the maintenance loop
The failure pattern is always temporal: the setup was right in March and wrong by June, because the site moved and the controls did not. The loop that prevents it is boring and effective:
- Walk the routes weekly, as a pedestrian and as a driver
- Re check after every site change: new stage, new gate, new excavation
- Re check after weather, wind moves cones and rain moves everything
- Log near misses and treat each one as the system reporting a bug
- Re brief when the crew changes, because the agreement lives in heads as well as on paper
Why it pays beyond safety
Sites with real traffic management run faster: deliveries stage instead of queueing, plant moves without spotter improvisation, and the public interface generates neither complaints nor council attention. The discipline funds itself.
Equipping the plan
Bring the conflict point list, or the site plan and we will help find them, and the equipment schedule follows. Request a quote or get in touch.