The Numbers a Traffic Control Owner Should Actually Watch

Most traffic control owners can tell you last month's revenue and roughly how busy the trucks were. Fewer can tell you which job types actually made money, how much of their device inventory sat idle, or how long a signed ticket takes to become an invoice.

That gap is where the money is. Here is a short set of numbers worth carrying, what each one actually tells you, and — importantly — how each one gets gamed.

1. Revenue per truck-day

What it is. Total revenue for a period divided by the number of truck-days worked. One truck out for one day is one truck-day.

What it tells you. Whether your capacity is producing. In this trade the binding constraint is trucks and crews out the gate, not headcount, so this is the cleanest single measure of whether the fleet is earning.

How it gets gamed. By quietly excluding truck-days. A truck that went out for a half-day mobilization and came back gets left out of the denominator, and the number improves without anything improving. Define a truck-day once — any day a truck leaves the yard on billable work — and never adjust it.

Where the data comes from. Dispatch records joined to invoiced revenue. If dispatch lives on a whiteboard, this number does not exist, because the whiteboard is erased.

2. Crew utilization

What it is. Billable crew hours divided by paid crew hours.

What it tells you. How much of your payroll converts to revenue. It is the number that explains why a busy month was not a profitable one.

How it gets gamed. By reclassifying travel, yard time, and standby as billable when they were not billed. Standby that you were entitled to bill and did bill is billable. Standby you absorbed is not — counting it as billable makes the number look fine while the margin quietly disappears.

Where the data comes from. Time clock hours attributed to jobs, compared against payroll hours. That attribution has to happen at the punch, not in a Friday reconstruction. Full treatment in crew utilization metrics for traffic control.

3. Device utilization versus idle inventory

What it is. The share of your cones, drums, barricades, arrow boards, and message signs that were deployed and earning over a period, against total owned.

What it tells you. Whether your equipment purchases are working or parked. It also tells you whether the next truckload of drums is a real need or a habit.

How it gets gamed. By counting a device as utilized because it is off the yard, when it is actually sitting on a job that stopped billing rent weeks ago. Deployed and earning are different states, and only the second one counts.

Where the data comes from. Device tracking by job site joined to rental billing. See tracking traffic control devices by job site and, on the buy decision this number should drive, renting versus buying traffic control equipment.

4. Gross margin by job type

What it is. Revenue minus direct cost — labor, equipment, and consumables — segmented by the kind of work. Flagging, lane closures, sign rental, standing barricade rental, and emergency callouts behave completely differently.

What it tells you. Which work to chase and which to price differently or decline. This is the highest-value number on the list and the one most often missing.

How to segment it. If you need a segmentation scheme, the MUTCD's work duration categories are a defensible starting point — long-term stationary work over three days, intermediate-term, short-term stationary daytime work over one hour, short duration work up to one hour, and mobile operations (MUTCD 11th Edition Part 6, Section 6N.01). Those categories carry genuinely different cost structures, because mobilization is a fixed cost spread over very different amounts of billable time.

How it gets gamed. By loading cost inconsistently. If one job type carries fully loaded labor and another carries base wage only, the comparison is meaningless. Pick a loaded rate methodology and apply it to everything — the mechanics are in flagger labor cost per hour. Overtime belongs in that load: federal law requires at least one and one-half times the regular rate over 40 hours in a workweek (29 U.S.C. 207(a)(1)), and emergency and night work carry disproportionate overtime.

Where the data comes from. Job costing that joins hours, equipment time, and invoiced revenue per job. Nothing else produces it. See job costing for traffic control companies.

5. Quote-to-win rate

What it is. Quotes accepted divided by quotes sent, ideally segmented by customer type and by job type.

What it tells you. Whether your pricing is in the market and whether your quoting is fast enough. Both failures look identical in the aggregate number, which is why the segmentation matters.

How it gets gamed. By not recording losses. A quote that never got a response gets forgotten rather than marked lost, and the win rate floats upward on a shrinking denominator. Every quote needs a terminal status.

Where the data comes from. A CRM or quoting system that retains quotes after they go cold. Email does not do this. Related: quoting traffic control jobs faster and bidding traffic control jobs.

6. Ticket-to-invoice lag

What it is. Median days from signed daily ticket to invoice issued.

What it tells you. How much cash your own back office is holding up. This is entirely within your control, which makes it the most actionable number here.

How it gets gamed. By measuring the mean instead of the median. One invoice issued the same day offsets ten that took three weeks, and the average looks respectable while your cash position does not.

Where the data comes from. Ticket timestamps joined to invoice dates. If tickets are paper, this number is guesswork. Context in getting paid faster on traffic control invoicing and, on the accounting handoff, QuickBooks integration for traffic control software.

7. Days sales outstanding

What it is. Average days from invoice to payment received.

What it tells you. Whether your customers pay and whether your terms are being honored. Segment it by customer — one slow GC can carry your whole average and the aggregate number will not name them.

How it gets gamed. By excluding disputed invoices from the calculation on the grounds that they are "not really outstanding." They are the most outstanding thing you have.

Where the data comes from. Accounting. This is the one number on the list most shops already have.

8. A safety measure

What it is. Pick something you will actually record. Recordable incidents against hours worked is the standard construction measure. Near-miss and work zone intrusion reports are a leading indicator and often more useful at this size, because a company with 25 trucks may go a long time between recordables while intrusions happen monthly.

What it tells you. Exposure, and whether your setups and your training are holding. The national picture is a reminder of the stakes: FHWA reports 891 work zone fatalities in 2022, with 94 highway worker occupational deaths that year, speeding a factor in 34% of fatal work zone crashes and rear-end collisions accounting for 21% — 174 — of them (FHWA work zone facts and statistics).

How it gets gamed. By under-reporting, which is the default failure mode of every incident metric ever built. If your near-miss count drops to zero, the reporting stopped, not the near misses.

Where the data comes from. Your incident process. Recordkeeping and reporting obligations sit alongside it — OSHA requires reporting a work-related fatality within 8 hours and an in-patient hospitalization, amputation, or loss of an eye within 24 hours (OSHA recordkeeping). Regulatory reporting is a floor, not a management metric. More in measuring safety performance at a traffic control company.

What to leave off

Total revenue with no margin attached. Revenue can grow while the business gets worse, and in field services that is a common way to fail.

Jobs completed. Twelve flagging half-days is not comparable to one multi-week corridor closure.

Quotes sent. Activity, not outcome.

Anything you cannot source. A number nobody can trace to a record will be argued with in every meeting until it is quietly dropped. Better to run six sourced numbers than twelve plausible ones.

Why a whiteboard cannot produce these

Almost every number above requires joining two datasets that normally live apart — hours against jobs, devices against sites, invoices against tickets — and then retaining that join over time so you can see a trend.

A whiteboard is an excellent dispatch tool and a terrible system of record, because it is erased every morning by design. Spreadsheets retain history but require someone to maintain the joins by hand, which works until the week it does not. That transition is covered in migrating off spreadsheets.

Traffic OS keeps dispatch, tickets, device tracking, and invoicing in one place specifically so these numbers are a report rather than a research project — see pricing.