Every super has stood in the trailer on a Thursday afternoon doing the math: we're a day and a half behind on the deck pour, the inspector's booked for Monday, and the only lever left to pull is hours. So you authorize Saturday, maybe some ten-hour days, and you tell yourself it's a one-time thing to get back on the wire. Then it happens again the next week, and the week after, and by the time the job's half done overtime isn't a tool anymore — it's a habit you can't afford and can't seem to break.
Overtime is one of the few real accelerators you have on a jobsite. Poured on the right activity at the right moment, it buys back schedule and gets you out of a hole. Poured on reflexively, it just burns premium labor to paper over planning you should have fixed weeks ago. The whole game is knowing which one you're doing — and building your look-ahead so you can tell the difference before the check clears.
Strategic overtime vs. reactive overtime
These are not the same thing wearing different hats. Strategic overtime is a decision you make in advance, tied to a specific outcome: hit a concrete milestone, close a weather window, keep a continuous pour going, or line up two trades that only sequence cleanly if one of them stretches a couple of days. You know going in what the hours are supposed to buy, and you can check afterward whether they bought it.
Reactive overtime is what you spend to recover from a problem you didn't see coming. It's more expensive per unit of work and it delivers less, because you're usually authorizing it when crews are already tired, materials are already tight, and the sequence is already scrambled. A rule of thumb worth carrying: the later in the week you decide on overtime, and the less specific the goal, the more likely it's reactive — and the more likely it's a symptom rather than a fix.
When overtime actually earns its premium
There are a handful of situations where the extra cost genuinely pays for itself:
- Milestone recovery. You're chasing a hard, external date — a certificate of occupancy, a tenant move-in, a concrete inspection that gates everything downstream — and a focused push of hours on the critical path activity closes the gap. Key word: critical path. Overtime on an activity with three days of float is money set on fire.
- Weather windows. The forecast gives you two clear days before a week of rain, and you've got earthwork, waterproofing, or a pour that has to happen dry. Extended hours inside that window can be the cheapest schedule you'll ever buy.
- Continuity. Some work wants to finish in one motion — a mat slab, a large deck, a roof dry-in ahead of a storm. Stopping and restarting introduces cold joints, re-mobilization, and quality risk. A few hours of overtime to finish the push can be worth more than the hours themselves.
- Trade alignment. Occasionally you overtime one trade specifically so a following trade can start Monday instead of Wednesday, and that two-day head start ripples through the whole sequence. That's leverage — as long as the following crew is actually ready to take the handoff.
When it's a symptom, not a solution
The tells that overtime has stopped being a tool:
- It's chronic. If a crew is running overtime most weeks, you don't have an overtime opportunity, you have a manpower or planning shortfall that overtime is masking. The honest fix is more bodies, better sequencing, or a schedule that was never realistic to begin with.
- It eats the next day. Ten-hour days that produce eight hours of work and then a slow, sloppy morning aren't buying you anything. You paid a premium for hours and lost regular-rate hours on the back end.
- Quality starts slipping. Punch lists that grow, rework that shows up at inspection, mistakes that trace back to tired crews working late — that's overtime costing you twice.
The productivity math nobody wants to hear
Overtime hours are not as productive as regular hours, and everybody in the field knows it even if the estimate pretends otherwise. Fatigue compounds. The first week of sustained fifty- or sixty-hour weeks might hold up reasonably well, but push it for a month and productivity on every hour — including the straight-time ones — starts to sag. There's decades of industry data behind this, and while the exact curve depends on the trade and the work, the direction is never in doubt: the longer you run extended weeks, the less you get per hour.
Which means the real cost of overtime isn't just the 1.5x on the premium hours. It's the premium plus the productivity loss plus the drag it puts on the following weeks. When you're weighing an overtime push, do the honest version of the math: if you're paying time-and-a-half for hours that produce two-thirds of a normal hour's output, your effective cost per unit of work can easily run double the regular rate. Sometimes that's still worth it to hit the milestone. Often it isn't, and a second crew or a revised sequence gets you there cheaper.
Make the hours visible in your look-ahead
You can't manage what you can't see, and overtime has a way of hiding — a few Saturdays here, a couple of ten-hour days there, spread across trades so no single line item looks alarming. The fix is to pull it into the same weekly work plan where you're already tracking the work.
When you build a short-interval schedule, you're committing specific crews to specific activities in specific weeks. That's exactly where overtime belongs too: planned extended hours shown as part of the plan, not scribbled on a separate sheet. A look-ahead tool like LookAheadWall earns its keep here simply by keeping the crews, the activities, and the trade-flow sequence in one visual place — so when you're staring at a week that only closes with overtime, you can see whether the problem is that one activity or the whole run of them. Seeing three straight weeks of planned OT on the same crew is the signal to stop and fix the plan instead of buying another Saturday.
A few things worth tracking week over week:
- OT as a percentage of total hours, by crew and by trade. A creeping percentage is your early warning that a planning problem is turning chronic.
- Work accomplished per overtime hour versus regular hours, at least roughly. If the ratio is ugly, you've got your answer on whether to keep authorizing it.
- The trend line. One heavy week is an event. A rising trend is a diagnosis.
Authorize it, don't just let it happen
Overtime should require a decision, not a shrug. That means a real approval step — the foreman who wants the hours has to name the activity, the goal, and roughly what it's going to cost, and someone with budget awareness signs off. It sounds bureaucratic until you've watched an unmanaged jobsite bleed six figures in OT that nobody can account for by closeout.
Document the why while you're at it. Not for the paperwork's sake — for the next time. "We ran Saturday to close the weather window on the podium pour, gained a day and a half" is a note that makes you smarter on the next job. "We ran a lot of overtime in Q3" is not.
Fatigue, safety, and the human limit
Crews are not machines and hours are not infinitely stackable. Fatigue is a schedule risk and a safety risk in the same breath — incident rates climb with sustained long hours, and the correlation is well enough established that it's worth treating as a hard constraint, not a soft preference.
Some practical guardrails:
- Watch total weekly hours per crew, not just per day. Sixty-hour weeks that run for a month are a different animal than one hard week.
- Rotate the overtime across crews where the work allows it, so the same guys aren't carrying every push. Spread fatigue is more manageable than concentrated fatigue.
- Pull overtime off your high-risk activities first. Steel erection, crane picks, energized electrical, deep excavation, work at height — these are the last places you want a tired crew, and the first place to cap the hours. If a high-risk task has to run long, add supervision, don't just add hours.
Before you reach for overtime, look at the alternatives
Overtime is rarely the only lever, and often not the best one. A second shift can beat overtime outright on the right work — you're paying a shift premium instead of time-and-a-half, and you get fresh crews instead of tired ones. The catch is the handoff: shift work only pays off if the day and night crews communicate cleanly, or you'll spend the morning untangling what got done in the dark. Weekend work has its own tradeoffs — premium rates, and on occupied or urban sites, real noise and access constraints that can put you sideways with the neighbors or the owner.
And the biggest lever of all is upstream: most overtime traces back to a schedule that was never realistic, or constraints that weren't cleared in time. Durations padded to the bone, deliveries that slip, inspections that stack up, a following trade that shows up before the area's ready. Clean constraint management in your look-ahead — knowing a week ahead that the material, the access, the prior work, and the manpower are all actually going to be there — prevents more overtime than any Saturday ever recovered. The best OT is the OT you engineered out of the job three weeks before it would have happened.
Keep the crews in the loop
Last thing, and it's not a small one. If you're going to ask for hours, ask like a person. Give crews advance notice — a Wednesday heads-up beats a Friday-at-quitting-time ambush every time, and it lets guys plan around it. Tell them why: "we need the deck closed before the rain Monday" lands very differently than "we're behind." And when they carry the push, say so. Overtime spends more than money; it spends goodwill, and the crews who feel jerked around on hours are the ones who quietly slow down on the regular-rate work you actually depend on.
Handled deliberately, overtime is a genuine accelerator — a way to buy back schedule when it counts. Handled reflexively, it's a tax on bad planning that gets more expensive every week you keep paying it. The difference isn't the hours. It's whether you saw them coming, aimed them at something specific, and knew what you got for them.