Handling Angry Drivers at Stop/Slow: What to Say in 8 Common Situations

Handling angry drivers as a traffic controller comes down to three things: keep yourself safe, say very little, and say it calmly. A short line that acknowledges the wait, gives the reason and a time, then lets you get back to the bat, defuses most situations. When a driver escalates, you step back and call the supervisor.

Abuse from the public is one of the recurring hazards in traffic control, alongside errant vehicles, fatigue and heat. This guide gives practical scripts for eight situations controllers meet at stop/slow, how to know when to stop talking, and how to record what happened. The scripts are examples to adapt to your company's procedures and training, not rules. For the employer side of the problem, including training and support, see abuse and aggression toward traffic controllers.

The ground rules before any script

Scripts only work if the basics are right:

• Stay at your station. Don't walk up to a car window in a live lane. If a driver wants to talk, they can do it from where they are while you stay off the travel path.
• Keep the bat steady. The sign must keep showing the right face while you talk. Turning to argue can show SLOW to the wrong driver.
• Keep your escape route clear and know where it is at every moment.
• Short beats clever. One or two sentences. No sarcasm, no lectures, no debate about the project.
• Don't promise what you can't control. "Two minutes" is fine if the cycle is two minutes. "Nearly done" when you have three hours left makes the next driver angrier.
• Your tone does the work. Calm, even, eye contact where safe, then turn back to traffic.

Eight common situations and what to say

1. "How long is this going to take?" Say: "About two minutes, I'll have you moving as soon as the lane's clear." Why: A specific time calms more than "not long". Use your actual cycle time. The stop/slow cycle time guide explains how it's worked out.

2. "There's nobody working, why am I stopped?" Say: "There's a truck coming through from the other end. I'll release you once it's past." Why: Drivers can't see the other end. Tell them what's coming.

3. "I'm going to be late for work / an appointment." Say: "I understand. I'll get you through as quickly as it's safe to." Why: Acknowledge it, don't argue with it, don't make an exception.

4. "I live just there, let me through." Say: "No worries. Let me check with my supervisor how we get you in." Then radio. Why: Residents' access is often planned in the TGS or traffic management plan. Don't improvise; ask. See resident driveway access during roadworks.

5. Horn blasts and gestures, no conversation. Say: nothing. Keep the bat steady, keep your face neutral, release when it's safe. Why: Engaging rewards it. Note the vehicle if it continues.

6. Swearing and personal abuse through the window. Say: "I'm not going to talk to you like that. I'll release you when it's safe." Then turn back to traffic and radio the supervisor. Why: You are entitled to set a boundary and end the conversation.

7. The driver who threatens to drive through. Say: "Please wait, there's oncoming traffic." Then radio: "TC 1 to all, possible non-compliant driver, white sedan, holding." Move towards your escape route. Why: You warn the crew early. If they go, you get out of the way. Never step in front of the vehicle.

8. The driver who gets out of the car. Say: "Please get back in your vehicle, it's not safe to stand in the road." Keep your distance, radio the supervisor and the other end immediately. Why: A pedestrian in the queue is a new hazard and a potential threat. Don't touch them, block them or argue.

When to stop talking and step back

Some signs mean the conversation is over and your job is to protect yourself and get help:

• The driver gets out of the vehicle, or reaches for something.
• They threaten you, the crew or the other end.
• They throw something or spit.
• They start to move the vehicle towards you or the shuttle lane while stopped.
• You feel unsafe, for any reason.

At that point: stop talking, keep your distance, use the escape route if needed, radio for help, and if you feel threatened call police on triple zero. Your company procedure may also include a duress or check-in process; see lone worker safety for remote sites.

Example scenario: an escalating driver at a suburban stop/slow

Here is how this plays out on a typical job. The site is a two-lane residential road with stop/slow at each end of a single lane while a water crew repairs a service. It is 8:20 am, school traffic is building, and cycles are longer than usual because a truck is unloading.

1. The wait builds. A driver at the front of TC 1's queue sounds the horn twice. TC 1 keeps the bat on STOP and does not respond (situation 5).
2. Window down. The driver calls out that they'll be late for school drop-off. TC 1 replies: "I understand. About three minutes, the truck's nearly done." (situations 1 and 3).
3. Abuse. The driver swears at TC 1. TC 1 says: "I'm not going to talk to you like that. I'll release you when it's safe," and turns back to face traffic. TC 1 radios: "TC 1 to supervisor, abusive driver at my end, grey hatch, I'm OK, just letting you know."
4. Escalation. The driver opens the car door. TC 1 steps back towards the escape route on the footpath and radios: "TC 1 to all, driver out of vehicle at my end, holding." The supervisor tells TC 2 to hold their end and walks to TC 1's station.
5. Resolution. The supervisor, standing with TC 1 and off the road, calmly asks the driver to return to the car. The driver does. When the shuttle lane is confirmed clear, TC 1 releases.
6. Record. At the next break, TC 1 and the supervisor record the time, vehicle description and registration if seen, what was said, what was done and the outcome, and submit it as an incident report.
7. Follow-up. The supervisor raises the long cycle at school time with the project contact, since the delay was a trigger. The next day, the truck unloading is moved outside the school peak.

Nothing dramatic happened, which is the point. The early radio call and the step back kept it that way.

Quick-reference script card

Print this and keep it in your vest pocket.

Reducing the triggers before drivers get angry

Scripts handle anger once it arrives. The supervisor and the planner can reduce how often it arrives in the first place. Most driver frustration at stop/slow comes from a handful of triggers:

• Waits that feel unexplained. Drivers who can see nobody working assume the controller is being difficult. Advance signs or a VMS message about expected delays, where the TGS includes them, set expectations before drivers reach the bat.
• Cycles that are longer than they need to be. Trucks unloading in the shuttle lane, plant crossing at awkward moments and slow radio calls all stretch the wait. Review the cycle at the morning briefing and again after the first hour.
• Peak-hour clashes. School drop-off, shift changes at a nearby factory and the evening rush all bring impatient drivers. Where the permit allows, schedule the slowest activities outside those windows.
• Inconsistent treatment. If one end waves locals through and the other doesn't, drivers notice. Agree the resident access arrangement at the pre-start and apply it the same way at both ends.
• Tired controllers. Fatigue shortens tempers on both sides of the bat. Rotate positions and relieve early.

When the same site keeps producing abuse reports, treat it as a planning problem, not just a people problem.

Recording abuse so something changes

Every incident of abuse should be reported, even when nobody was hurt. Reports let the company see patterns: the same site, the same time of day, long cycles, poor signage about delays. A useful record includes:

• date, time and location, including which station
• vehicle description and registration if safely seen
• what was said or done, in plain words
• what you did and who you told
• any injury, damage or witnesses
• what might reduce the risk next time

If there is a threat, assault or damage, the supervisor decides with you whether to report to police. Some serious incidents may also need to be notified to the regulator. The incident and near-miss reporting guide covers the process. For WHS guidance on managing violence and aggression at work, check SafeWork NSW or Safe Work Australia.

Next steps

Practise the eight lines out loud at the next toolbox talk, so they come naturally when you're tired and the queue is long. If you run crews, making incident reporting quick from the phone helps; tools like TrafWise let crews complete pre-starts and SWMS sign-on in the crew app, which is a good moment to remind everyone how to report abuse.