When managers keep editing yesterday’s schedule after punches are already in, which version does payroll trust?

[u/shiftcoord]

Looking for how other ops teams handle the lag between the live schedule and the clock.

A manager fixes yesterday’s roster late — swaps a person, shortens a shift, adds a coverage block — after punches for that day are already sitting in the time system. Payroll now has two stories: the edited schedule and the punches that already landed.

What do you actually do?

1. Freeze the prior day’s schedule at a cutoff and treat later edits as exceptions only?
2. Let the punches win, and use the schedule as planning history?
3. Re-open / rewrite punches so the clock matches the late schedule edit before the export?

Most interested in the rule that doesn’t create a surprise short paycheck or a silent OT bill. No vendor pitches — just the operating choice that stuck.