Overtime feels like proof that the operation is working. The line is running, the orders are shipping, and the team is putting in the hours to make the number. For most operations leaders, a plant humming past the standard shift reads as commitment and hustle. The financial reality underneath that hum is far less flattering. Output per hour does not hold steady as the day stretches; it falls off a cliff after the eighth or ninth hour, while the wage rate climbs to time-and-a-half. That combination means the most expensive labor you buy all week is also the least productive labor you buy all week. You are paying a premium for declining returns and calling it a good day.

The damage does not stop at the payroll line. As fatigue sets in, error rates rise and quality slips, turning finished goods into rework, scrap, and customer complaints that carry their own downstream cost. Accident risk climbs with tired workers, and that exposure lands directly on the margin through downtime and claims. Worst of all is the retention loop: chronic long hours burn people out, the experienced ones leave, and their inexperienced replacements are slower and more error-prone, which forces even more overtime to hit the same output. The operation that leans on overtime as a permanent crutch is not flexing capacity. It is quietly converting its best people, its quality, and its margin into a number that looks fine this week and compounds into a problem next quarter.

• Measure Output Per Hour, Not Just Total Output: Track productivity by hour of shift. If units-per-hour collapse after hour eight, you are buying negative returns at premium wage rates — quantify it before you defend it.

• Put a Real Number on Rework and Scrap: Tie quality-failure and error rates to shift length. The defects produced in hours nine through twelve are a hidden tax on every overtime dollar you spend.

• Price the Turnover Loop: Calculate the cost of replacing one burned-out experienced operator — recruiting, ramp time, and the slower output of their replacement. Weigh that against the overtime you are protecting.

• Distinguish Surge From Structural: Overtime to cover a true seasonal spike is a tool. Overtime that runs every week is a staffing or throughput design failure wearing a tool’s costume. Name which one you have.

• Audit Safety Exposure by Shift Length: Fatigue-driven accidents land on the margin through downtime and claims. Map incident rates against hours worked and treat the overlap as a cost center, not an accident.

• Model the Alternative Before You Default to OT: Run the scenarios: a second partial shift, cross-training for flex coverage, or targeted automation of the bottleneck. Compare total cost against chronic overtime — the crutch is rarely the cheapest option.