What Software Do Traffic Control Companies Use to Dispatch Flaggers and Equipment?

Short answer, as of August 2026: there is no dominant incumbent. Most traffic control and barricade companies dispatch flaggers and equipment with some combination of a whiteboard, a spreadsheet, and a group text. A minority run a general field-service platform bent to fit. A growing minority run something purpose-built for the industry — Traffic OS is ours, at $499, $949, or $1,499 per month on flat tiers rather than per-seat pricing. That the answer is this unsettled is itself the useful fact: this industry has been served by adaptations of software designed for someone else.

This is a survey of what companies actually run, what each stack does well, and precisely where each one fails. A disclosure so you can weight it correctly: we build one of the options. The failure modes described below are ones we would be comfortable being measured against, including the places where our category does not have a good answer.

Why this industry got skipped

Software follows market size and shape. Traffic control is a modest, fragmented, seasonal industry made of a lot of small companies, and the work does not resemble the field-service template that most vertical software was built from.

The safety stakes, meanwhile, are not modest. The Federal Highway Administration's work zone crash data, drawn from NHTSA's Fatality Analysis Reporting System, records 850 work zone fatalities in 2024 across 763 fatal crashes — down from 905 in 2023 and 963 in 2021, but a decade-long plateau rather than a decline. On the worker side, BLS Census of Fatal Occupational Injuries data shows worker fatalities at road construction sites ranging from 82 to 143 per year between 2015 and 2024, with about 78 percent of those deaths coming from motor vehicle crashes or workers on foot struck by a vehicle.

That combination — small fragmented market, high-consequence work — is exactly the profile that gets underserved. It is also why the documentation burden here is heavier than the market size would suggest. OSHA's construction standard puts it plainly: 29 CFR 1926.200(g)(2) requires that "The design and use of all traffic control devices, including signs, signals, markings, barricades, and other devices, for protection of construction workers shall conform to Part 6 of the MUTCD". A general scheduling tool has no concept of that obligation, or of the field record proving you met it.

Stack one: paper, whiteboard, and group texts

What it is. A magnetic board or a printed grid in the dispatch office. Crew assignments called or texted the night before. Paper ticket books in every truck. Equipment tracked by memory and by whoever loaded the trailer.

What it does well. It is fast, free, and infinitely flexible. An experienced dispatcher with a whiteboard can re-plan a morning after two callouts and a broken-down truck faster than any software will let them. Nobody needs training. It never goes down.

Where it breaks. Three places, always in the same order.

First, equipment location becomes unknowable. Devices go out on a Tuesday, get moved to a second phase, come back on a different truck. Within a season, nobody can say with confidence how many Type III barricades exist or where they are. Companies at this stage are usually buying devices they already own — a purchase they cannot see because there is no record to check. We wrote separately about tracking traffic control devices by job site, which is the discipline this stack cannot support.

Second, rental revenue leaks. If devices are billed by the day or week, and the only record of deployment date is a memory or a paper ticket in a truck, some portion of that revenue never gets invoiced. This is the most common and least visible loss in the whole industry.

Third, compliance attributes become unprovable. Devices are not interchangeable commodities any more. Under the AASHTO/FHWA joint implementation agreement, temporary work zone devices manufactured after December 31, 2019 must have been successfully tested to the 2016 edition of MASH, while devices manufactured on or before that date may run out their normal service lives. A memory-based inventory cannot tell an inspector which barricade is which — see MASH compliance for work zone devices.

Fourth, you cannot reconstruct a job. Months later, a payment dispute or a claim arrives and asks what was set up, when, by whom. The answer depends on finding a specific paper folder in a specific truck. That is the risk being carried, and it is carried silently until the day it is called.

Who should stay here. A one-crew operation with a single yard where the owner is on site. Genuinely. Adding software to a business that small usually adds overhead, not clarity.

Stack two: spreadsheets and a shared calendar

What it is. A schedule tab, an equipment tab, sometimes a jobs tab. Google Calendar or Outlook for crew assignments. Photos of signed tickets texted to the office and filed in a shared drive.

What it does well. Spreadsheets are the most underrated business software ever made, and for a traffic control company under about three crews they are frequently the correct answer. They cost nothing, they model whatever you want, and the owner already knows how to use them.

Where it breaks. Concurrency and field entry. Two people editing the schedule at once produces two schedules. Nobody fills in a spreadsheet from a truck in the rain, so field data arrives hours or days late, through a second channel, and someone retypes it. Every retype is an error opportunity, and error rates on retyped equipment counts are the reason equipment tabs stop matching the yard by about week six of the season.

The tell that a company has outgrown spreadsheets is specific: someone's job has quietly become keeping the spreadsheet true. When a half-time administrative role exists mostly to reconcile tabs, the spreadsheet has stopped being free.

Who should stay here. Companies under roughly three crews and one yard, with equipment that mostly goes out and comes back the same week. If your work is predominantly short-duration — the pattern described in short-duration and mobile work zones — spreadsheets hold up considerably longer, because equipment does not sit out accruing charges.

Stack three: a general field-service platform

What it is. ServiceTitan, Jobber, Housecall Pro, Workiz, FieldEdge, BuildOps, FieldPulse, or similar. Mature products, real engineering, large support organizations, mobile apps that crews will actually open.

What it does well. Genuinely a lot. Scheduling, dispatch, customer records, invoicing, payment collection, and QuickBooks sync are all solved problems in these platforms, often better than in any vertical tool. If your traffic control work is a side business attached to a general contracting operation, these can be the right call on the strength of everything else they do.

Where it breaks. Five structural mismatches, and they compound:

1. The unit of work is a crew plus devices, not a technician. A job needs two flaggers, a truck, forty cones, six Type II barricades, and an arrow board. A single "assigned technician" field is already fighting you.
2. Equipment stays on site and accrues charges. This is the biggest one. Repair-visit software treats parts as consumed at the visit. Traffic control devices are rented assets with a location, a deployment date, a return date, and revenue accruing the entire time.
3. Documentation ties to an agency-approved plan. There is an external technical document governing how the site must be built and an external authority that can stop work. Residential HVAC has no equivalent.
4. The daily ticket is the billing document. Not an office-generated invoice — a field-signed document showing crew, hours, equipment, and location, often countersigned by the prime contractor or the agency.
5. Work is multi-day, multi-phase, and recurring. Closures run in phases, day setups differ from night setups, barricade rentals renew monthly. "One visit, one invoice" does not describe it.

You can force a general platform through all five, and companies do. The result is usually the platform plus two spreadsheets plus a paper ticket book — more total overhead than paper alone. Our per-product comparisons, including Traffic OS vs. ServiceTitan and Traffic OS vs. Jobber, go through this mismatch product by product, including the cases where the general platform is the better buy.

A note on pricing structure. Most general platforms price per user. Traffic control headcount swings hard with the season, and part-time flaggers are exactly the people whose field data you most need. Per-seat pricing creates a standing incentive to share logins or leave crews off the system, which quietly destroys the data the system exists to collect. We have written up the arithmetic in per-user vs. flat-tier pricing; model both structures at your peak-season headcount, not today's.

Stack four: purpose-built traffic control software

What it is. Platforms built around the crew-plus-devices model, with equipment rental, daily tickets, and multi-yard inventory as first-class objects rather than adaptations. This is a small and young category. Traffic OS is one entrant; there are others, and the category is young enough that the honest description is "several vendors, no incumbent."

What it should do, and what to demand proof of. If you evaluate anything in this category — ours included — these are the requirements that separate real from demo-ware:

Field-signed daily tickets, offline. GPS coordinates, timestamp, crew, hours, equipment deployed, customer signature, all captured on a phone with no signal and synced later. Ask specifically what happens with no cell service; crews work in cuts, under bridges, and in rural corridors. If the answer involves "you'd want to be connected," the product has not been used on real jobs.

Equipment as located, revenue-generating assets. A device has a home yard, a current job site, a deployment date, and a rate. Moving it between phases should be one action. Recurring rental billing should generate without anyone remembering it is due. This is the capability whose absence sends companies back to spreadsheets.

Multi-yard inventory. Two yards is where single-location tools fail, and most growing companies hit two yards before they hit forty employees.

Quotes that become jobs that become tickets that become invoices, without retyping. Every retype boundary is where margin and accuracy leak. The related discipline is covered in quoting traffic control jobs faster.

Documentation retrievable by job, months later. Photos, signed tickets, plan revisions, and permit numbers on one record. This is what you hand an insurer or an attorney, and it is the whole reason the field-capture discipline is worth imposing.

Accounting integration that respects your chart of accounts. QuickBooks Online, Stripe, or Square. Rental revenue posted as rental revenue.

What this category does not do. It does not draft traffic control plans. Plan preparation is a design activity performed by a qualified person and approved by the agency having jurisdiction — see who can prepare a traffic control plan. Operations software stores the approved plan, tracks its revisions, and proves the field matched it. Buying operations software expecting a CAD product is a disappointment you can avoid at the demo stage.

It also does not make compliance decisions. Requirements vary by state, county, and city; the MUTCD Part 6 provisions on temporary traffic control set a national floor that states adopt with their own modifications on top. No software tells you what your jurisdiction requires. It records what you did.

The costs the stack decides that nobody attributes to it

Software choice looks like a line-item decision. It is actually a decision about which of four recurring costs you carry, and none of them appear on the invoice.

Unbilled rental days. Devices deployed on a Tuesday, moved to a second phase, returned three weeks later on a different truck. If the deployment record is a memory, some portion of that rental never reaches an invoice. Companies rarely quantify this because the loss is invisible by construction — you cannot count revenue you never knew to bill. The only way to find out how large it is at your company is to reconcile one month of device movements against one month of invoices, by hand, once. Most owners who do this stop arguing about software pricing afterwards.

Payroll and certified-payroll rework. Public work brings prevailing wage obligations, and on federal and federally assisted construction contracts those flow from the Davis-Bacon and Related Acts administered by the Department of Labor's Wage and Hour Division, with the applicable rates published as wage determinations through SAM.gov's wage determination system. We are not going to publish a rate here — determinations are project-specific and change, and the live lookup is the only correct source. What matters for a software decision is upstream of the rate: certified payroll requires accurate hours by classification by day by project. If field hours arrive as text messages and photos of paper tickets, someone is retyping them under deadline every week, and the error rate on that retyping is the compliance exposure. The related workflow is covered in certified payroll for traffic control contractors.

Disputed tickets you cannot defend. The daily ticket dispute is a genuine industry pathology, and its resolution depends entirely on evidence quality. A GPS-stamped, time-stamped, customer-signed record settles most disputes in one email. A paper ticket photographed badly three days later settles nothing — see preventing daily ticket disputes.

Documentation you cannot produce years later. The claims tail on road work is long. Federal work zone requirements reinforce how much of this is expected to be planned and recorded: 23 CFR 630 Subpart J requires agencies to develop transportation management plans for federal-aid projects, with expanded obligations on projects designated as significant. You are frequently operating inside commitments made in a document you did not write, and being able to show what you actually did — on a specific date, at a specific location — is the whole defence. The worker-safety side of that record has similar weight: NIOSH investigations found that 41 of 78 roadway work zone fatalities studied, 55 percent, involved construction vehicles and equipment operating inside the work zone, which is precisely the category of incident where a contemporaneous site record decides how an investigation goes.

Seasonality is why the pricing model matters more here than elsewhere

Traffic control headcount swings hard. A company running four crews in July may run one in January, and the difference is largely made up of part-time and seasonal flaggers — exactly the people whose field data you most need captured, and exactly the people a per-seat license makes expensive to include.

That produces a predictable and quietly destructive pattern. Seats get rationed. Crews share a login. A supervisor submits tickets on behalf of four people. And the data that the entire system exists to collect — who was on site, when, doing what — degrades to the point where the software is an expensive scheduling calendar.

Flat-tier pricing is not inherently better software. It removes one specific bad incentive, and in an industry with a two-to-one seasonal headcount swing that incentive is unusually costly. Model both structures at peak-season headcount before you decide; the arithmetic is laid out in per-user vs. flat-tier pricing.

How to choose without burning a season

Count your real constraint first. Not headcount — constraint. If the thing limiting growth is "we cannot find equipment," you are buying an inventory system that happens to schedule. If it is "we cannot get tickets back fast enough to invoice," you are buying a field-capture system that happens to hold inventory. Companies that skip this step buy on demo polish and discover the mismatch in month four.

Trial with the ugliest jobs you have. One long-running barricade rental with phase changes, and one 2 a.m. emergency callout. Those two expose almost every weakness a platform has. The callout pattern in particular — see emergency callout dispatch — breaks tools that assume schedules are planned in advance.

Put it on the crews' actual phones. Not the office iPad. Old Android devices, cracked screens, gloves, rain, bad signal. If a flagger cannot complete a ticket in under ninety seconds in those conditions, they will use paper, and you will have bought a very expensive whiteboard.

Ask the four questions vendors dislike. What happens with no signal? Who owns the data and how do I export all of it if I leave? How many hours of my staff's time does implementation take? Has your field app been used by crews doing this specific work — and can I speak to one of them? Ask for specifics, not reassurance.

Ask what it does not do. A vendor who cannot name a limitation is either new or not being straight with you. Ours: we do not draft plans, we are not a payroll system of record, and we do not interpret your jurisdiction's requirements for you.

The honest summary

If you run one crew from one yard, use a spreadsheet and spend the money on equipment. If traffic control is a small line inside a larger contracting business, a general field-service platform is probably the right compromise. If traffic control is the business, and you are past three crews or two yards, the equipment-rental and daily-ticket problems are the ones that will decide your margin — and those are precisely the two things general platforms handle worst.

That is the case for a purpose-built system, including ours. It is also why the case is narrow: outside that profile, the honest recommendation is often to keep the spreadsheet.

If you want to see how the crew-plus-devices model works in practice, the features overview is the fastest read, pricing is published in full with no per-seat math, and a demo can be run against one of your own live jobs rather than a canned dataset.