Net Hours for a Server on a Split Shift

Maria works a split at your restaurant on Saturday. She comes in for the lunch rush, clocks out mid-afternoon, goes home, and comes back for dinner. Two separate stretches of work, one day, one line on payroll. The question every restaurant owner hits is simple: how many hours do you actually pay her for, and how do you prove the number if she asks?

Walk through Maria's day with real punches and you will never have to guess again.

The four punches Maria leaves behind

Maria never logs in. She taps her name on the tablet by the kitchen door when she arrives and taps it again when she leaves. Over the day that produces four timestamps, two for lunch and two for dinner:

Each pair is a time entry. The gap between punch 2 and punch 3, from 2:30 to 4:55, is Maria off the clock. She is home, she is not being paid, and because she clocked out she generated no entry for that window. That is the whole point of a split: the unpaid break is not a deduction you have to remember, it is just the absence of a punch.

From punches to net hours

Net hours are the worked hours that remain after any unpaid time is removed. In Maria's case there is nothing to subtract inside either entry, because she was on the floor the entire time she was clocked in. So her net hours are just the two entries added together.

Lunch: 10:45 AM to 2:30 PM is 3 hours and 45 minutes. Dinner: 4:55 PM to 9:40 PM is 4 hours and 45 minutes. Add them and you get 8 hours and 30 minutes, which is 8.5 hours in decimal. That 8.5 is what goes on payroll, not the 10 hours and 55 minutes that span her first punch to her last. The 2 hour 25 minute break she took between shifts never enters the total, because she was clocked out for all of it.

If you want to see the arithmetic for a single shift laid out, the time card calculator for one shift does the start-to-end math, and the decimal to HH:MM converter turns 8 hours 30 minutes into 8.5 so you can type it straight into a pay run. For the formal definition and the edge cases, the net hours glossary entry is the reference.

Why you keep two entries instead of one

You could tell Maria to stay clocked in through her break and knock off two and a half hours at the end. Do not. If she stays clocked in from 10:45 AM to 9:40 PM as a single entry, you now have to remember the exact break length, do the subtraction by hand, and trust that nobody fat-fingered it. Two clean entries carry the break for you. The math is addition, and the record shows precisely when she was on the clock and when she was not.

This also matters the day Maria disputes her hours. With two entries you can point at four real timestamps: in at 10:45, out at 2:30, in at 4:55, out at 9:40. There is nothing to argue about. A single long entry with a mental deduction is a conversation; four punches is a fact.

What happens when she forgets to clock out

Real kitchens are messy. Say dinner ends, Maria hangs up her apron, and she forgets to tap out. The entry sits open. Left alone, an open entry could run to the current time and report her at 14 or 15 hours, which is nonsense.

Kangaroo Clock closes a stale entry at its start time plus a cutoff, never at the current moment. So Maria's forgotten dinner entry gets closed back near where it started rather than ballooning overnight. The auto-close rule for forgotten punches means a missed clock-out undercounts a bit at worst, and never inflates your reported hours. You review the flagged entry, fix the real time, and move on.

Rolling Maria's day into payroll

Maria's 8.5 hours is one day. Payroll wants the whole period. You run a CSV export of the period and every entry comes out with the same columns every time: worker, clock-in, clock-out, duration, tags. The two Saturday entries sit on their own rows, and the file totals correctly whether Maria worked one straight shift on Sunday or another split on Monday.

Tags help here if you track where time went. Put a lunch tag on the first entry and a dinner tag on the second, and you can filter the export to see how much labor each service actually cost. The hours are the same either way; the tags just let you slice them.

Across a two-week run those daily totals add up into the number your pay cycle cares about. If you pay every other Friday, the biweekly hours calculator stacks the days for you so you are not summing a column by hand.

The rule to take to your own floor

A split shift is not a special case you need special math for. It is two ordinary entries with an unpaid gap between them, and net hours are just those entries added up. Tell your servers to clock out when they leave for the break and clock back in when they return. The punches do the rest, and the report reads true the first time.

Want to see the tap-your-name flow before you commit? Try the live kiosk demo, then set up your own floor in a few minutes.