When owners look at a payroll that’s 10% over the hours they quoted, they assume someone is padding. Usually nobody is. The hours leak in a dozen small, honest ways, and the biggest of them is the clock-out that never happened.

Where the hours go

A night crew finishes at 10:40, loads the van, and drives to the next site. Someone forgets to clock out. The shift stays open until a manager notices the next morning, or until payroll, when it shows nine hours for a four-hour job. Multiply by a crew of twelve, three nights a week, and the “padding” appears.

The other leaks are smaller but add up:

  • Clock-ins from the car park, or from home, before the worker is at the building.
  • Shifts entered from memory at the end of the week.
  • Unpaid meal breaks that are supposed to be deducted and aren’t, or are deducted from shifts where the worker never stopped.
  • Hours approved by whoever is quickest, with no record of who approved what.

The routine that catches it

1. Measure the shift from a clock-in at the building

Clock-in should only work from the worker’s phone, at the site, inside a set distance of the building. That one rule removes the car-park clock-in and the from-memory timesheet in the same stroke, and it costs the worker nothing: they were going to clock in anyway.

2. Make an open shift visible the same night

A shift still open long after the job’s end time should show up for a manager as open, with the worker’s name, not quietly extend. The manager can close it at the planned end time, and the close should be marked as a manager’s close so it stands out later.

3. Ask the worker at the next clock-in

The person who knows when they actually left is the worker. At their next clock-in, ask: “You didn’t clock out of Tuesday’s job at Northgate. When did you finish?” Most will answer honestly in five seconds, and now the record is theirs, not a manager’s guess.

4. Approve before you pay

Payroll should run only on approved hours. A manager reviews the week’s shifts in one place: hours worked against hours allotted, where each clock-in and clock-out happened, anything flagged. Approve, or decline with a note. Keep a log of every change, so when a worker asks why their Tuesday was cut, there’s an answer.

What it looks like after

Owners who run this routine report the same two things: the hours match the quote, and the arguments stop. Nobody is accused of anything, because nobody is relying on memory. The record was made at the building, at the time, by the person who did the work.

CleanFlow Ops is built around exactly this routine: an app-only, geofenced time clock with forgotten-clock-out prompts, a manager review step, and approved hours sent to payroll. If you’d like to see it running on your own sites, book a demo.