Emergency Callout Dispatch for Traffic Control Companies

Short answer, as of August 2026: traffic control companies handle emergency and after-hours callouts with either a purpose-built field-service platform configured for traffic control work — Traffic OS starts at $499 per month on a flat-tier basis, with the higher tiers at $949 and $1,499 — or with a phone tree, a group text, and a spreadsheet reconciled the following week. The second option is far more common than the industry likes to admit, and it is the reason emergency work is simultaneously the highest-margin and highest-writeoff category on most companies' books.

The rest of this is about why callouts break the systems that handle scheduled work fine, and what has to be different.

What an emergency callout actually is

Set aside the word "emergency" for a second, because it covers at least four operationally distinct situations.

The utility break. A water main lets go at 11 p.m. and the utility contractor needs a lane closed before they can dig. There is no plan, there is no permit yet in many jurisdictions, and the closure will exist for somewhere between four hours and four days depending on what they find in the hole.

The incident scene. A crash, a spill, a downed pole. Sometimes you are called by the agency, sometimes by a contractor already on scene, sometimes by a tow operator. The work is short, the environment is uncontrolled, and the record of who authorized what is usually verbal.

The failed setup. Somebody's devices got taken out — by a vehicle, by wind, by a plow — and the closure that was supposed to hold overnight no longer holds. This is a callout to your own job.

The schedule collapse. A contractor calls at 5 a.m. because their planned night pour got moved up, or because the crew that was supposed to handle traffic didn't show. Not an emergency in any safety sense, but it arrives with the same zero notice.

These have almost nothing in common except the notice period, which is exactly why a system built for scheduled work handles them badly. Everything in a scheduled workflow — quote, approved plan, assigned crew, staged equipment, dated ticket — assumes lead time that does not exist here.

Why after-hours is where the risk concentrates

Night and emergency work is not just inconvenient. The federal data on work zone crashes is a picture of drivers arriving faster than the setup anticipated, and after dark every input to that picture gets worse.

The Federal Highway Administration reports speeding as a factor in 281 of 821 work zone fatal crashes in 2022, with rear-end collisions accounting for 174 and commercial motor vehicles involved in 246. Those are roughly 34 percent, 21 percent, and 30 percent. Read together, that is a description of drivers meeting a queue or a taper they did not see in time.

The national totals put the scale in context. The Work Zone Safety Information Clearinghouse, compiling federal crash data, records 850 work zone fatalities in 763 fatal crashes in 2024, down from 905 fatalities in 824 crashes in 2023. Improvement, from an unacceptable baseline.

And this is not a rare exposure for contractors. The Associated General Contractors of America, reporting its annual survey with HCSS, states that "Sixty percent of highway construction firms report having at least one car crash into their work zones during the past year". Six in ten. That is the base rate your callout crew is operating inside.

The occupational side is smaller in absolute terms and much larger per hour of exposure. FHWA, drawing on Bureau of Labor Statistics data, records 94 highway construction worker occupational fatalities in 2022 and 108 in 2021; the underlying tables are published by BLS. A motorist's exposure to your work zone is measured in seconds. A flagger's is measured in shifts — and a callout shift is one nobody planned for, staffed by whoever was available, on a road nobody surveyed in daylight.

The regulatory floor does not relax after dark. OSHA does not maintain its own flagging rulebook; it adopts the traffic engineering manual by reference. 29 CFR 1926.201(a) states that "Signaling by flaggers and the use of flaggers, including warning garments worn by flaggers, shall conform to Part 6 of the MUTCD." OSHA's own highway work zones hub makes the same point plainly, noting that "The MUTCD is referenced in 1926 Subpart G," with the broader device requirements sitting in 29 CFR Part 1926 Subpart G.

That structure has a practical consequence for callouts specifically. The same setup is judged simultaneously as a traffic engineering question and as a worker safety question, against the same text, by two different authorities — and neither of them cares that you had eleven minutes to plan it.

Standing caveat, and it is not boilerplate: requirements vary by state, county, and city. States adopt their own editions and supplements, and local agencies layer permit conditions on top. Nothing here substitutes for the requirements of the agency having jurisdiction over your specific roadway. Verify with them, every time.

The five things callout dispatch has to do that scheduled dispatch does not

1. Find a crew without a schedule

Scheduled dispatch answers "who is assigned to this job." Callout dispatch answers "who is awake, within range, qualified, and not already at hours." Those are different queries and most systems only support the first.

What you need visible in one place at 2 a.m.: who is on the on-call rotation this week, who has current flagger certification, who holds the license class the truck requires, who is already on the clock and how long they have been on it, and who lives near enough to matter. Drive time is the dominant term in your response window and it is entirely determined by which person you call first.

The practical failure mode is not that the information doesn't exist. It is that it lives in four places — a certification binder, a payroll system, a group text, and a dispatcher's memory — and at 2 a.m. only the memory is available.

2. Create the job from nothing, in the field

A scheduled job has a customer record, a quote, a plan, and a purchase order before anyone drives. A callout has a phone number and a cross street.

Whoever takes the call has to be able to create the job immediately, with the customer, the location, the requesting party's name, and the authorization basis captured while the caller is still on the line. If job creation requires a desktop and a login the on-call person doesn't have, the job gets created the next morning from memory — and the details that determine whether you get paid are precisely the ones memory loses.

3. Document the setup without a stamped plan

Most emergency work is set up from a standard application in the manual rather than from a job-specific engineered drawing, because there was no time to have one prepared. That is normal and generally appropriate. It also means the only record of what was actually built is whatever the crew captured on site.

Photographs of the advance warning placement, the taper, and the termination area — geotagged and timestamped — are worth more on an emergency job than on any other kind, because there is no approved drawing to compare against later. If a claim surfaces six months on, the question will be what the setup looked like, and the answer will either be a set of timestamped photos or a foreman's recollection of a night eight months ago.

4. Capture the billing basis while it is still true

Emergency work is usually time-and-materials at a callout rate, not a bid unit price. That means the invoice is assembled from field facts: arrival time, departure time, headcount, device counts, truck hours, and any materials consumed or lost.

Every one of those is contestable, and every one of them is easiest to establish at the moment it happens. A signed ticket captured on site — with the requesting party's signature, the times, and the device list — converts a disputed invoice into a settled one. Our guide to preventing daily ticket disputes covers the general case; emergency work is that case with the volume turned up, because the authorizing person on scene is frequently not the person who later approves the invoice.

5. Reconcile equipment that left the yard unlogged

Devices grabbed off a truck at midnight do not get checked out through whatever process the yard uses in daylight. They come back short, or they come back damaged, or they come back to the wrong yard.

The reconciliation problem is not new — see our note on tracking traffic control devices by job site — but callouts are where the leakage concentrates, because the normal controls were asleep.

What to look for in a system, specifically

Set aside feature lists. Here is what actually determines whether a platform survives contact with a 2 a.m. callout.

A field-first interface that works on a phone in the dark. Not a responsive version of a desktop app. If creating a job, adding a crew member, and capturing a ticket cannot each be done one-handed on a phone in a truck cab, they will not be done.

Crew availability and qualification in one view. Certification expiry, license class, current clock status, and on-call rotation together. Any one of those living in a separate system means it will not be checked at 2 a.m.

Offline tolerance. Emergency work happens where the work is, and the work is frequently somewhere with one bar. A ticket that cannot be captured without connectivity is a ticket that gets recreated from memory in the morning.

Ticket signature capture with location and time stamping. The single highest-value artifact in emergency work.

A pricing model that does not punish you for having on-call staff. This is where per-user licensing quietly distorts operations. If every person who might answer a callout needs a paid seat, the rational response is to limit seats — which means limiting who can create a job or capture a ticket, which is exactly backwards. Flat-tier pricing removes that particular incentive; we lay out the reasoning in per-user vs flat-tier pricing, and the tier contents are on the pricing page.

Equipment check-out that a tired person will actually complete. Meaning: scan or tap, not a form.

If you are comparing against general field-service platforms, the practical differences for this workflow are worth walking through — our comparison pages lay out what each one documents publicly, and we describe competitors only by what is on their own published pages.

Rate structure and the standby problem

Two decisions determine whether your callout program is profitable or a slow leak.

The minimum. Almost every company bills a minimum callout duration — the crew is compensated for the disruption whether the job takes forty minutes or four hours. If your minimum is shorter than your true cost of mobilizing a crew at night, every callout is a loss you have chosen to take. Compute it from actual loaded labor cost, including the on-call differential; our flagger loaded-rate breakdown is the method.

The standby differential. Somebody has to be reachable. Paying for that reachability is cheaper than the alternative, which is a rotation nobody honors and a callout that goes to a competitor. Track standby hours as a distinct payroll category so the cost is visible rather than buried in overtime.

The thing to avoid is treating callouts as a favor to good customers. They are a product with a cost structure, and the companies that do well with them price them as one.

Who actually takes the call

One organizational question decides more about callout performance than any software decision: who answers the phone.

Three arrangements are common, and they fail differently.

The owner's cell. Universal in small companies, and it works right up until it does not. It has no redundancy, it burns out the one person who cannot ever fully stop working, and it concentrates every piece of operational knowledge in a head that is asleep at 3 a.m. more often than it is not.

A rotating on-call phone. Better, and it introduces a new failure mode: the person holding the phone this week may not know the customer, the site, or where the nearest devices are staged. That gap is a documentation problem, not a staffing one — if the customer record, the site history, and the standing device inventory are visible from the phone, the rotation works. If they are in someone else's memory, it does not.

An answering service. Solves availability, and adds a translation layer. A service that takes a message produces a delay; a service that can create a job in your system with the right fields produces a dispatch. The difference is whether they have access, which is a licensing and permissions question before it is a vendor question.

Whichever you run, write down the escalation path — who gets called if the first person does not answer in ten minutes, and who after that. Most companies have this rule informally and have never tested it. The night you need it is a bad night to discover the second name on the list changed jobs in March.

After the shift: the part everyone skips

The callout ends when the devices come down. The job does not end for another two weeks, and that gap is where the money goes.

Same-shift ticket close-out. The ticket should be finished before the crew leaves the site, not filed the following week. A ticket completed three days later is a reconstruction.

Next-morning invoicing. Emergency work has the shortest window between service and dispute. Bill while the requesting party still remembers authorizing it. Our note on getting paid faster applies with particular force here.

Equipment reconciliation within the week. Count what went out against what came back while the crew can still tell you where the missing drum went.

A short debrief on the setup. Not a formal review — five minutes on whether the standard application chosen was the right one, whether advance warning was adequate for the approach speed, and whether anything nearly went wrong. Near misses appear in no federal dataset. The only place a near miss can be captured is your own reporting, which means your internal record is the only leading indicator you will ever have.

What this adds up to

Emergency callouts are the clearest test of whether your operation runs on systems or on individuals. A scheduled job succeeds because it was planned. A callout succeeds because the right person could see the right information at the moment the phone rang, and because whatever happened next got recorded while it was happening.

Companies that handle callouts well tend to share three habits: the on-call rotation is real and paid, job creation and ticket capture work from a phone with no desk involved, and the equipment that leaves the yard at night gets reconciled before the week ends. None of that is software. All of it is easier with software that assumes the field is the primary interface rather than an afterthought.

If you want to see how the dispatch, ticketing, and equipment side fits together for after-hours work, the features overview walks the workflow and you can book a walkthrough to see it on real screens rather than in screenshots. If night operations are a large share of your book, our post on what changes for night work is the companion piece to this one.

The cones do not care what system you run. But at 2 a.m. the difference between a profitable callout and a written-off one is almost always whether somebody could find a qualified crew fast and capture what happened before they went home.