Approving a person's period does three things at once, and there's deliberately no separate "lock" step.
Approval Is the Lock
One more thing to forget before running payroll is one more thing that goes wrong, so approving is the finish line.
Approving
Snapshots vs Live Totals
The snapshot is what payroll was given on approval day. If someone edits a punch after approval (an un-approve, correct, re-approve cycle), the row shows both numbers: the original snapshot, and the live total, marked as drift. That way a paycheck disagreement is a visible discrepancy instead of history being silently rewritten.
Un-Approving
Click Un-approve on an approved row. You'll be asked for a reason (required, and audited). Un-approval reopens paid time for editing, the "we have to fix a paycheck" path.
Who Can Approve
Admin, owner, and dispatcher roles. Drivers and mechanics can see whether their own period is approved but can't approve or un-approve it themselves.
Why Per-Person, Not Whole-Org
Approval granularity is one person, one pay period. You can approve one person's week and export their hours while still chasing another person's missing punch, instead of blocking the whole export on one open case.