Saturday shifts that pay for Monday blindness
By Thursday the planner has already penciled Saturday. The scheduled week is not over. The loss that Saturday will repurchase is still sitting, in pieces, on screens nobody opens together.
Saturday becomes the default because the week stays blind
The visible request is capacity. The plan is behind, customers still want the volume, and a weekend crew is the lever everyone already knows how to pull. What the request often hides is that Monday through Friday already paid for hours the line did not convert. Micro-stops, material still in transit, a bottleneck waiting on the wrong trade, and a late call-off never shared one picture before the shift ended. Saturday then looks like demand. A large share of it is a second purchase of output the roster already funded.
How a lead recovers those joins before the overtime request is a factory-management method, under same-shift recovery from joins, not overtime. This page is the money question that method does not price: what the Saturday line-hour actually costs, and when that premium is an honest peak versus a tax on weekday blindness. Night-premium roster design is a different ledger, under what an operational digital twin costs and what it buys for shift structure.
The overtime line-hour is more than the wage premium
Most plants stop the cost stack at time-and-a-half or double time. Ops teams that price a weekend crew in full usually find four more layers. Output per hour drops, because the crew is thinner, people are tired, and a line that sat cold does not make rate in the first hour. The maintenance window that used to live on Saturday becomes production, so the stops that created the backlog get worse next week. Overhead sits on fewer lines: utilities, a supervisor, quality, and a driver spread across a skeleton shift. Start-up eats the front of the extra day.
Put together, a fully loaded overtime line-hour often lands around 1.6 to 2 times a scheduled line-hour when you measure cost per good unit, not only cost per clock hour. Treat that band as a prompt to build your own multiple. It is not your plant's invoice until you fill premium, output, overhead, and the lost preventive slot with your numbers. The wage line on the timesheet will understate the bill either way. Lost margin, idle labor while the line is down, restart scrap, and expedited freight sit in the same family as the premium. They rarely share one cost center, which is why Saturday looks cheaper in the meeting than it is on the month.
Honest peaks versus buying the week twice
Overtime is honest when the constraint was already full, the joins were clean, and scheduled hours at a normal OEE still cannot cover demand. In that case the premium is a capacity purchase, and the later question is a fourth crew or more equipment, not a sharper dashboard. Overtime is a repurchase when the scheduled week lost recoverable hours to micro-stops, changeovers over standard, speed loss, and unplanned stops, and the weekend exists to make the output those hours should have made. The roster looks identical. The ratio does not.
A practical test on one line over two ordinary weeks is enough to see the mix. Count scheduled production hours, recoverable hours lost on that scheduled time from a source better than memory, overtime hours worked, and your fully loaded cost per overtime line-hour. If recoverable scheduled loss is on the same scale as the overtime hours, you are close to buying the week twice. Plants that have lived on structural overtime for a year are often surprised how much of it sits in that second bucket. Operator logs alone will undercount the short stops, so the diagnostic needs machine or sensor time, not only the sheet the team fills at handover.
What same-shift recovery is worth as avoided spend
An operational digital twin earns a place in this ledger when the pieces of a recoverable loss share one hall while the hour is still open. Under-threshold lines, material still moving, an idle cell with no order, and a crew already rolling to the wrong bay are each a Saturday seed if they stay on separate screens until Friday. Seeing them at 14:00 does not delete demand. It lets the lead spend straight time on the loss instead of premium time on the symptom. That is avoided operating cost, measured as overtime hours you do not book, not as a generic efficiency percent.
The join has to become a call, not another report at end of shift. The gap between data that already exists and a decision someone will make today is under the daily gap between data and a call. Opening a third specialist screen to rebuild the same bay recreates the blindness the premium is paying for, which is why one hall view before another screen is an OPEX rule as much as a habit. Production monitoring is the shift surface for that call. Minutes recovered before the overtime request, and Saturdays that remain after the joins are clean, are the two numbers finance should see.
Price the tax before you buy another screen
1. Pick the line that owns the most weekend hours - One line, two weeks, four numbers: scheduled hours, recoverable loss, overtime hours, fully loaded cost per overtime line-hour.
2. Split honest peak from repurchase - If recoverable scheduled loss is small against overtime, keep the premium and debate lasting capacity. If it is large, Saturday is funding weekday blindness.
3. List the joins that were still red at mid-shift - Material, crew, energy, and delay. Unowned reds are not a reason to book hours. They are the blindness.
4. Compare one avoided Saturday crew with the cost of seeing those joins in time - Use your multiple, not a borrowed one. How a rollout is priced sits on pricing. What the hall can show sits on the features overview.
Do that arithmetic before the next weekend is treated as weather. Get in touch if Saturday is still the default answer to losses that were visible, and split across screens, before the shift ended.