Overtime and FLSA Basics for Traffic Control Crews

Traffic control is a wage-and-hour trap dressed as a simple trade. The pay structure looks straightforward — hourly people, hourly rates — and then the operational reality piles on every complicating factor at once: night shifts, weekend closures, emergency callouts, crews held on standby while somebody else's work runs late, multiple job sites in a day, travel between them, per diem on out-of-town work, and shift differentials layered on top of base rates.

Each of those is a place the overtime calculation can go sideways. Most of the errors are honest, and honest errors are still liability.

This is an orientation, not legal advice. Wage and hour law is fact-specific, it varies by state, and the difference between compliance and exposure often turns on details of your particular practice. Nothing here should be applied to your company without review by qualified employment counsel. Where a number depends on your locality or classification, this article deliberately points you at the official lookup rather than quoting a figure.

The 40-hour rule, precisely

The federal baseline is one sentence in 29 U.S.C. 207(a)(1): an employer may not employ a covered employee "for a workweek longer than forty hours unless such employee receives compensation for his employment in excess of the hours above specified at a rate not less than one and one-half times the regular rate at which he is employed."

Three things in that sentence deserve attention.

"Workweek." Not the pay period. The workweek is a fixed, regularly recurring period, and overtime is computed within it. A company on biweekly payroll whose crew works 50 hours one week and 30 the next owes overtime for the first week's excess. Averaging the two to 40 is not permitted, and it is a common mistake in shops that grew out of an owner running payroll in a spreadsheet.

"Forty hours." Federal law sets no daily overtime threshold. Several states do impose daily thresholds and other requirements that go beyond the federal floor. Which state rules apply to your crews, and how they interact with the federal rule, is a question for counsel licensed where you operate.

"Regular rate." Not the posted hourly rate. This is the part that catches people.

The regular rate is broader than the hourly rate

Section 207(e) defines the regular rate to include all remuneration for employment paid to, or on behalf of, the employee — then carves out eight enumerated categories of payments that may be excluded, covering things like gifts, certain vacation and holiday pay, discretionary bonuses, insurance contributions, certain premium payments, and stock-based compensation meeting specified criteria.

The structure is inclusive-with-exceptions, not the other way around. The default is that a payment counts, and it is excluded only if it fits a statutory exclusion. The Department of Labor's interpretive regulations on all of this are in 29 CFR Part 778, which devotes an entire subpart to payments that may be excluded from the regular rate and another to exceptions from the regular rate principles.

Why this bites traffic control specifically: this trade runs on exactly the kinds of supplemental payments that raise regular-rate questions.

• Shift differentials for night work, which in this trade is routine rather than exceptional.
• Non-discretionary bonuses — safety bonuses, attendance bonuses, completion bonuses. The word doing the work is "non-discretionary." A bonus promised in advance to induce performance is generally a different animal from a genuine surprise gift, and the two are treated differently.
• Callout or minimum-hour premiums for emergency work.
• Per diem and travel allowances, whose treatment depends on their nature and structure. We wrote about the operational side of these in per diem and travel pay for traffic control crews, and the payroll treatment is a separate question to put in front of counsel.

The practical consequence is that an overtime rate computed as 1.5 times the base hourly figure can be too low if other remuneration should have been folded in first. Multiply that across a crew across a season and the exposure is not small.

Night work is not an edge case here

In most trades night work is unusual. In traffic control it is a staffing category.

The reason is capacity: agencies push lane closures into off-peak hours because closing a lane at rush hour is enormously expensive to the traveling public. The standard even recognizes the timing distinction structurally — Section 6N.01 of Part 6 of the MUTCD classifies nighttime work lasting more than 1 hour as intermediate-term stationary work, a category with heavier device requirements than the equivalent short daytime job, and treats work occupying a location more than 3 days as long-term stationary.

That regulatory nudge toward nights shows up in your payroll as differentials, in your scheduling as split and rotating shifts, and in your overtime as crews who worked Tuesday night and Wednesday night inside the same workweek. It also shows up in risk: FHWA recorded 94 highway worker deaths in work zones in 2022 and 108 in 2021, per FHWA's work zone facts and statistics. Fatigue management is a safety issue before it is a payroll issue, and the two are connected — a scheduling pattern that produces heavy overtime is also producing tired people standing next to live traffic. The operational side of nights is in night work traffic control: what changes.

Standby, waiting, and the hours nobody bills

This is the most expensive gray area in the trade, and it is expensive twice — once because you may owe the crew, and again because you often did not bill the customer.

Whether waiting time is compensable turns on a fact-specific analysis that courts and the Department of Labor have framed around whether an employee is engaged to wait or waiting to be engaged. Applying that to real situations is genuinely difficult, and the situations in this trade are not clean:

• Crew arrives at 6 a.m. for a closure that cannot start until the utility crew shows at 9.
• Crew is held on site through a weather hold.
• Crew sets the zone, then waits for paving to reach them.
• Crew is dispatched, arrives, and the job is cancelled at the gate.
• Crew is released for four hours and told to come back for the night closure.

Each of those has a different shape. Some may be plainly compensable; some may not be; some depend on details like whether the employee could effectively use the time for their own purposes. Do not resolve these from a general article. Have your actual practices — the dispatch instructions, what crews are told, what they can and cannot do while waiting — reviewed by qualified counsel.

What you can do without a lawyer is capture the facts. Arrival time, who directed the wait, when the crew was released, and by whom. That record is what a wage claim, a customer dispute, or an audit will turn on, and it is the same data that tells you whether a customer is systematically wasting your crews' time. The billing side of that conversation belongs in the rate sheet before the dispute, not after.

The federal contract layer

Public work adds obligations on top of the FLSA, and they do not replace it.

The Contract Work Hours and Safety Standards Act requires that on covered federal and federally assisted construction contracts, wages include compensation at a rate not less than one and one-half times the basic rate of pay for all hours worked in excess of 40 in the workweek, per 40 U.S.C. 3702. The statute creates liability to the affected worker for unpaid wages and, separately, to the contracting agency — a two-sided exposure that a purely private job does not carry.

Davis-Bacon prevailing wage obligations are a different mechanism again. Where they apply, the required rates come from the applicable wage determination for the locality and classification. Those determinations are published and searchable at SAM.gov wage determinations, and that is where you should look them up rather than relying on a figure quoted anywhere else — including here. Rates change, classifications matter, and using last year's number is its own violation.

The reporting side of prevailing wage work — certified payroll — is an operational burden of its own, covered in certified payroll for traffic control contractors.

One thing worth stating plainly: prevailing wage compliance and overtime compliance are separate. Paying the correct prevailing rate does not by itself satisfy overtime obligations, and satisfying overtime does not establish that the base rate was right.

The workweek, worked through

Because the workweek is the unit, it is worth being concrete about what that means operationally.

A workweek is a fixed and regularly recurring period of 168 consecutive hours — seven consecutive 24-hour periods. It does not have to start Monday and it does not have to align with your pay period. What it has to be is defined, written down, and consistent.

Two failure modes follow from not having that.

Averaging across a pay period. A crew works 52 hours in the first week of a biweekly period and 28 in the second. The total is 80, so payroll runs 80 straight hours. That is wrong: overtime was owed on the 12 hours over 40 in week one, and the shortfall in week two does not offset it. This is the most common overtime error in small contracting shops, and it is a pure arithmetic mistake rather than a judgment call.

An undefined boundary on night shifts. A crew starts a closure at 9 p.m. Saturday and finishes at 5 a.m. Sunday. If the workweek boundary sits inside that shift, those hours split across two workweeks. Which side they land on changes whether either week crosses 40. A company that has never written down its workweek start cannot answer that question consistently, which means it is answering it differently on different weeks.

Neither of those requires a lawyer to fix. Write down the workweek, apply it, and compute within it.

Multiple sites in a day

The other structural feature of this trade is that a crew often touches more than one job in a shift. Set a closure in the morning, break it down, drive across town, set another.

That creates three questions at once. For payroll: what is compensable during the movement between sites, which is treated differently from ordinary home-to-work commuting. For job costing: how do the hours split between the two jobs. For billing: does each customer get charged for the mobilization they caused.

Companies that record only a daily total answer none of the three. The crew's card says ten hours, the accounting system charges ten hours somewhere, and the actual allocation is a guess made later by somebody who was not there. Recording the transitions — off one job, travel, on the next — is what makes all three answerable, and it costs the crew a few taps rather than a form.

Retention

Keep the records. Wage claims and audits reach backward, sometimes years, and a company's defense is its contemporaneous records. Specific retention periods are set by regulation and by state law and are worth confirming with counsel for your jurisdiction, but the practical guidance is simpler than the legal question: do not discard hours data, and do not store it only in a format that depends on one person's laptop.

Where the money actually leaks

Setting aside outright violations, here is where well-run companies quietly lose:

Unrecorded hours become unbilled hours. If a crew's real start was 5:40 a.m. loading at the yard and the timesheet says 7:00 at the job, you have a payroll accuracy problem and you have also thrown away 80 minutes of cost data. Your job costing is now wrong in the direction that makes bad jobs look profitable.

Overtime absorbed into the wrong job. When a crew hits hour 41 on Thursday, that premium belongs to the job that caused it. Companies that allocate overtime evenly, or dump it into overhead, cannot see which customers and which job types actually generate it. That is a bidding problem disguised as an accounting problem — see job costing for traffic control companies.

Loaded rate computed on base pay. If your estimating loaded rate uses the base hourly figure and your real cost includes differentials, callout minimums, and overtime premium, every bid is short by the gap. We walked through building that number in flagger labor cost per hour: the loaded rate.

Standby priced at zero. The crew got paid, the customer did not get charged, and nobody wrote it down. This is the single most common uncompensated cost in the trade.

The foreman question

One more structural issue specific to growing companies: as crews get supervisors, somebody decides those supervisors are salaried and stops tracking their hours.

Whether a particular employee is exempt from overtime is a legal determination that turns on their actual duties and their compensation, not on their job title, not on being paid a salary, and not on carrying the word "foreman" or "supervisor" on a business card. Misclassification is one of the more expensive wage-and-hour errors precisely because it compounds — it applies to every hour that person worked over 40, for as long as the classification was wrong.

In traffic control the risk is elevated because working foremen are the norm. The person supervising the crew is frequently also setting cones, driving the truck, and standing a flagger station when somebody calls in. That mix of duties is exactly what makes the analysis fact-specific.

The safe operational posture is straightforward even while the legal question is not: keep recording hours for everyone, including people you believe are exempt. Recording hours does not create an obligation, and if a classification is ever challenged, having the actual hours is far better than having to reconstruct them. Take the classification question itself to qualified counsel with a real description of what the person does all day.

Records are the whole defense

In a wage dispute or an audit, the employer's records are the battleground. Reconstructed timesheets — filled in from memory at the end of the week, or "corrected" to match what somebody thinks happened — are the weakest possible position, and they also make the job-costing numbers fiction.

What holds up is contemporaneous capture: clock-in and clock-out at the point of work, tied to the job, with the time and place the entry was made. That is precisely what a GPS time clock and signed daily ticket produce, and the same record does double duty — it is the payroll defense and it is the cost data that tells you which work to bid more of.

There is a broader habit here worth borrowing from safety compliance. OSHA's injury and illness recordkeeping regime, described at OSHA's recordkeeping page, works because the obligation to record is contemporaneous and structured. Payroll deserves the same treatment: a system, not a memory.

What to do this quarter

Three concrete steps that do not require a legal budget to begin:

1. Write down your workweek. Its start day and time, in a policy document. If nobody can state it, overtime is not being computed against a defined period.
2. List every payment your crews receive beyond base hourly — differentials, bonuses, callout minimums, allowances — and take that list to qualified counsel with one question: which of these must be in the regular rate?
3. Start capturing hours at the point of work, tied to the job. This costs the least and fixes the most, because it improves payroll accuracy, wage-claim defensibility, job costing, and customer billing at the same time.

Nobody gets into traffic control because they enjoy wage-and-hour law. But this trade combines night work, standby, travel, multiple sites per day, and public contracts — which is close to a complete list of the things that make overtime hard. The companies that handle it well are not the ones with the best lawyers. They are the ones whose hours were recorded accurately the first time.