Crew Utilization: The Metric Most Traffic Control Companies Don't Track

Most traffic control owners can tell you their wage rates to the penny and their utilization not at all.

That is backwards. Utilization has the larger effect on profitability, and unlike market wage rates it is something you directly control. This is a short case for measuring it, and a practical guide to doing so without adding administrative work.

The definition, and the part people get wrong

Utilization is the share of paid field hours spent on revenue-generating work.

The numerator is easy. The denominator is where honesty is required, because it has to include everything you pay for:

• Yard time — loading, unloading, staging, maintenance
• Travel you do not bill
• Standby waiting on another trade, an inspector, or a permit window
• Weather holds
• Training, safety meetings, certification time
• Seasonal idle time when crews are on payroll and jobs are not there

A company that quietly excludes those from the denominator will produce a flattering number that is useless for decisions. The uncomfortable version is the actionable one.

Note also that utilization is not comparable between companies with different contract structures. A company that bills mobilization as a separate line will show higher utilization than one absorbing it in a day rate, doing identical work with identical economics. Compare your number to your own history and between your own crews, not to a figure someone quoted at a conference.

Why it dominates the arithmetic

The reason is structural: an unbillable paid hour returns nothing, while a wage difference adjusts margin on an hour that is still earning.

Put concretely, a crew paid somewhat above market at high utilization out-earns a cheaper crew idling in the yard, every time. This is worth stating because the instinct in a thin-margin trade runs the other way — toward shaving the wage. Market wage context for this occupation is published by the Bureau of Labor Statistics under Crossing Guards and Flaggers, SOC 33-9091, with national, state, and metro detail; look it up rather than guessing. But treat it as a recruiting-competitiveness check, not as the lever on profitability. The lever is the denominator. And when you build a loaded labor rate properly — dividing annual burdened cost by realistic billable hours rather than 2,080 — utilization is the single input that moves the resulting rate furthest. That method is in building a loaded labor rate, and it is worth doing before you start optimizing utilization, because it tells you what a recovered point is worth in dollars.

Four cuts that tell you something

The headline number is a starting point. The value is in the segments.

By crew. Persistent differences between crews are rarely about effort. They are usually about which work each crew gets assigned, which is a dispatch decision, not a performance one.

By job type. Short-duration private work with heavy mobilization typically shows poor utilization; long-duration agency work with stable crews typically shows good utilization. This cut frequently reorders which work you want.

By day of week and season. Most traffic control operations have a shape — a slow Monday, a dead February. Knowing the shape is the difference between managing it and being surprised by it annually.

By shift, if you run nights. Night work is a large share of lane closure activity because that is when closures are permitted, and it behaves differently: fewer jobs, longer shifts, different travel patterns, and a differential on the wage. It also carries different risk — FHWA's work zone facts and statistics records that of 821 fatal work zone crashes tallied for 2022, 174 were rear-end collisions and speeding was a factor in 281, and agencies inspect night setups specifically. Blending night and day into one utilization figure hides both the cost structure and the exposure.

By cause of non-productive time. This is the most actionable and the least commonly captured. Standby waiting on a prime is a contract problem. Travel is a routing and yard-siting problem. Weather is neither. Aggregating all three as "downtime" hides three different fixes.

The measurement, without new paperwork

The blocker is almost never willingness. It is that paper timesheets record a day, not a job, so the data to compute utilization does not exist in a usable form.

The change that fixes it is small: tie clock-in to a job rather than to a date. Once time entries carry a job reference, utilization becomes a report instead of a project, and it comes with two by-products worth as much as the metric.

First, job-level labor cost stops requiring after-the-fact allocation, which means job profitability becomes real rather than estimated.

Second, GPS-stamped clock events are contemporaneous evidence of who was where. That matters in a trade where disputes are routine and where documentation is the difference between a billable ticket and a discount — see preventing daily ticket disputes.

Scheduling and time capture that work this way are covered in what to look for in flagger scheduling software, and Traffic OS ties time clock entries to jobs by design for exactly this reason.

What to do with a bad number

Assume the first honest measurement is worse than you expected. That is normal and it is not a verdict on your crews.

Three responses that work, in order of typical payoff:

Attack standby before travel. Standby is usually caused by sequencing — arriving before the site is ready, or holding a crew for a window that moved. Much of it is recoverable through better coordination with the prime, and some of it is billable if you ask for it in the contract.

Then attack travel. Yard siting, route-aware dispatch, and simply not sending a crew across the metro for a two-hour job. Some of this is a pricing decision rather than a routing one: if a job type reliably costs more in travel than it returns, the answer may be to price it accordingly or decline it.

Then look at crew sizing. Overstaffed setups are invisible on a schedule and obvious in a utilization report. This is the one most likely to surface a genuine finding nobody suspected.

What does not work is exhorting crews to be more productive. Utilization is overwhelmingly determined by decisions made in dispatch and in the contract, not by how fast people set cones.

The reporting habit worth building

Look at it monthly, not annually. Utilization is volatile enough that an annual figure hides everything interesting, and it responds quickly enough to dispatch changes that a monthly cadence lets you see whether an intervention worked.

Pair it with one other number and you have a usable dashboard: utilization and job-level margin. Utilization tells you whether the hours were sold; margin tells you whether they were sold well. Companies that watch both stop being surprised at year-end.

If you want to see what that reporting looks like against your own data, bring a month of timesheets to a walkthrough. Pricing is flat monthly tiers rather than per user — relevant here, because a per-seat model penalizes exactly the seasonal hiring pattern that makes utilization hard to manage in the first place.