Net Hours With Two Unpaid Breaks in One Shift

A line cook clocks in at 8:00 and clocks out at 17:00. That looks like nine hours. It is not the number you pay, and it is not the number that belongs on a grant report either. Two unpaid breaks sit inside that shift, and until you subtract them, every downstream total is wrong.

Here is the shift, exactly as it happened on one Tuesday:

• Clock in: 8:00
• Morning break: 10:15 to 10:30 (15 minutes, unpaid)
• Lunch: 12:30 to 13:15 (45 minutes, unpaid)
• Clock out: 17:00

The three numbers that matter

Start with gross hours, the time between clock in and clock out. From 8:00 to 17:00 is nine hours flat. Nobody disputes that part. The trouble starts when you assume nine is what you pay.

Next, add up the breaks. Fifteen minutes plus forty-five minutes is sixty minutes, exactly one hour. Both breaks are unpaid because the cook left the station and was free to do anything. That distinction matters: a paid break stays inside the total, an unpaid break comes out.

Now the net hours: nine gross minus one hour of breaks equals eight hours. Eight is the number you pay for and the number you report. Everything else on the timesheet supports that single figure.

Where the arithmetic actually trips people

The clean version above uses round quarter-hours on purpose. Real shifts rarely cooperate. Say the cook came back from lunch at 13:20 instead of 13:15, and the morning break ran to 10:32. Now your breaks total 15 plus 52, which is 67 minutes, and the subtraction stops being something you can do in your head.

Sixty-seven minutes is 1 hour and 7 minutes. Nine hours minus 1 hour 7 minutes is 7 hours and 53 minutes. If your payroll wants a decimal, 53 minutes is 53 divided by 60, or 0.883, so the shift is 7.88 hours. That last conversion is where most hand-typed timesheets go wrong, because people write 7.53 by copying the minutes straight across. If you convert minutes to decimals often, keep a converter between HH:MM and decimal hours open so 53 minutes never becomes 0.53 by accident.

To reproduce this exact shift and change the times until they match your own, run it through the lunch-break time calculator. Enter 8:00 and 17:00, then subtract your two break lengths, and it returns net hours in both HH:MM and decimal so you can check your math against it.

Two breaks or one long one, and why it changes nothing

People sometimes think two short breaks are treated differently from one long break of the same length. They are not, arithmetically. A single 60-minute lunch and two breaks of 15 and 45 minutes both remove exactly one hour. The reason to record them separately is not the total. It is that a 15-minute break and a 45-minute break may fall under different rules, and a labor auditor or a grant officer wants to see each one, not a lump.

So record both. If you track breaks by hand, a printed timesheet with columns for each break keeps them visible instead of buried inside a single net figure. One column for break start, one for break end, one line per break. The person totaling the week can see where the hour went.

What forgetting to clock out does to this shift

Now the failure mode. The cook gets slammed at closing, walks out at 17:00, and never taps out. The next morning the entry is still open. If your system closes it at the current time, the cook now shows something like 23 hours on the clock, and your eight-hour shift becomes a payroll problem you find three days later.

Kangaroo Clock handles this with a rule that closes stale entries at the start time plus a cutoff you set, never at the current moment. If you set the cutoff to nine hours, a forgotten clock-out on an 8:00 start closes at 17:00, matching the real shift. The forgotten tap-out never inflates the total. You still adjust the breaks, but you are correcting eight hours, not twenty-three.

Running the number for a full crew

One cook on one Tuesday is easy. The math is the same for every worker, but doing it by hand for a fifteen-person kitchen across a two-week period is where errors multiply. Each shift needs its gross calculated, its breaks subtracted, and its result converted to decimal. Miss the conversion on three shifts and your payroll total is off by more than an hour before anyone notices.

This is where recorded clock-ins earn their keep. When workers tap in and out at a kiosk or a posted code, every start and end is a real timestamp, not a memory. Breaks are their own entries. When you export, you get gross, breaks, and net already separated per person, so nobody retypes 7.88 as 7.53. If you want to see how the raw taps become a payable total, the Kangaroo Clock overview walks through the path from clock-in to export.

Take your own worst shift from last week, the one with the odd break times, and run it: gross, minus breaks, converted to decimal. If the number you get matches what you paid, your process is sound. If it does not, you just found the leak.