PunchHow to Track Restaurant Split Shifts (AM and PM Service)
How to Track Restaurant Split Shifts (AM and PM Service)
The short answer: A restaurant that runs lunch and dinner service with overlapping crews needs to record each shift segment separately — one punch-in and punch-out for the lunch crew, another for the dinner crew, and a separate set for any employee who covers both. The critical part is making sure those separate segments combine correctly for overtime calculations at the end of the week.
This guide covers how split-shift scheduling works in practice, how a time tracking app should handle both segments, and what owners need to know about overtime and California's split-shift premium rule.
What a Restaurant Split Shift Actually Means
In restaurant scheduling, a split shift refers to an employee working two non-consecutive segments in the same calendar day — typically a lunch block (say, 10:30 AM – 2:30 PM) and a dinner block (5:00 PM – 10:30 PM), with an unpaid gap in between. The employee clocks out after lunch service, has a few hours off, and returns for the dinner rush.
This pattern is distinct from an employee who works one continuous long shift, and it creates two separate time-tracking events per employee per day: a punch-in and punch-out in the morning, and another punch-in and punch-out in the evening.
A reliable time tracking app handles this as two independent records — not a single shift with a long lunch break.
How Punch Records Split Shifts
When a split-shift employee uses Punch, each segment records as its own entry:
- Morning segment: Employee punches in at 10:30 AM → works lunch service → punches out at 2:30 PM. That creates one complete shift record.
- Evening segment: Employee returns at 5:00 PM → punches in for dinner → punches out at 10:30 PM. That creates a second complete shift record.
Both records show up under the employee's history for that date. Both appear in the manager's Approvals queue. Both count toward the employee's total hours for the workweek.
This structure is intentional. It keeps the records clean, makes approval straightforward, and ensures the two segments don't get tangled into one confusing entry with a four-hour "lunch break" that doesn't resemble any standard lunch.
Punch-In and Punch-Out Mechanics for Split-Shift Restaurants
Punch-In Requires a Signal
When an org uses job site geofencing, the punch-in checks that the employee is within range of the assigned location. This check requires a network connection. Employees arriving for lunch service or returning for dinner service typically have cell service when they walk in — the parking lot, the sidewalk, the front entrance all have connectivity — so this isn't a practical obstacle.
If an org has geofencing turned off, employees can punch in from anywhere on the app with no location check.
Punch-Out Works Without Service
The punch-out event doesn't require a geofence check. If an employee punches out from inside a kitchen or a basement prep area where signal is poor, Punch queues the action locally on their device and syncs it automatically when connectivity returns. The recorded time reflects when they actually tapped punch out — not when the sync happened.
The same applies to lunch breaks within a single shift: starting and ending a lunch break can happen without signal and will sync correctly once the device gets connectivity.
This matters for restaurant buildings with thick walls, basement dining rooms, or locations near large metal structures where cell service is unreliable in the interior.
Overtime Calculation Across Split Segments
Split-shift hours accumulate toward weekly overtime the same way any other hours do. Under federal FLSA rules, overtime applies once an employee exceeds 40 hours in a single 7-day workweek. The two segments from a split day both count.
For example:
| Day | AM Segment | PM Segment | Daily Total | |---|---|---|---| | Monday | 4.0h | 5.5h | 9.5h | | Tuesday | 0 | 5.0h | 5.0h | | Wednesday | 4.0h | 5.5h | 9.5h | | Thursday | 0 | 5.0h | 5.0h | | Friday | 4.5h | 5.5h | 10.0h | | Saturday | 0 | 5.0h | 5.0h | | Total | | | 44h |
In this example, the employee worked 44 hours in the week — 40 regular + 4 overtime, regardless of how many individual segments made up those hours.
Overtime isn't calculated per shift segment. A 4-hour lunch shift and a 5.5-hour dinner shift on the same day don't independently trigger overtime — they add up toward the weekly total.
California Daily Overtime
California adds daily overtime on top of the weekly rule: hours beyond 8 in a single day earn 1.5x, and hours beyond 12 earn 2x. In a standard restaurant split-shift, no individual segment typically hits 8 hours, so California daily overtime rarely applies to split-day segments themselves. But a full-day employee working a combined double that runs past 8 hours or 12 hours on a single punch-in/punch-out record would trigger it.
For an employee who punches out between segments and punches back in, Punch treats each segment as a separate shift. Whether California daily overtime applies depends on whether any single segment crosses the 8-hour daily threshold, and the weekly overtime calculation applies to the combined weekly total.
The Approval Workflow for Split-Shift Employees
When a manager opens the Approvals queue, they see each shift segment as its own row — the 10:30 AM–2:30 PM record and the 5:00 PM–10:30 PM record both appear for the same employee on the same date. Both require approval before the week can be marked as paid.
The weekly summary for that employee shows the combined total (9.5h, 5.0h, etc.), making it easy to see the full picture before approval. Individual segment records can be reviewed, edited with an audit trail, or rejected with a reason if something looks off.
A manager who notices that an employee's evening segment looks longer than expected can adjust the clock-out time directly from the Approvals view before approving — the edit writes an audit-log entry so there's a record of what changed and when.
California Split-Shift Premium Awareness
California law requires employers to pay a split-shift premium when an employee works two non-consecutive shifts in a single calendar day with a gap greater than one hour. The premium equals one hour of pay at the applicable minimum wage.
There's a notable offset rule: if the employee's total earnings for the day already exceed what they would have earned working one continuous shift at minimum wage, the premium is reduced or eliminated. Higher-paid employees often see a $0 net premium because the offset cancels the extra pay obligation.
The premium is a payroll calculation that depends on the applicable minimum wage for the employer's city or county — California has dozens of local minimum wage rates above the state floor. Owners in California with split-shift crews should verify the split-shift premium rules with a labor attorney or payroll provider before processing payroll, since the per-location rates and offset mechanics vary.
What to Look for in a Time Tracking App for Split-Shift Restaurants
Does it handle two punches in one day cleanly?
Some apps treat a punch-out followed by a punch-in on the same day as an error or force it into a "break" pattern. Split-shift records should appear as two clean, independent entries — not a single broken record.
Does it aggregate hours correctly for overtime?
Both segments need to roll up into the employee's weekly total for overtime. An app that calculates overtime per shift rather than per workweek will undercount — a 4-hour segment and a 5-hour segment never individually trigger 40-hour overtime, so the employee's hours never register.
Does it support approval of partial days?
A manager should be able to approve the morning crew's shifts independently of the evening crew's, without waiting for the full day to complete. In restaurants with closing staff who punch out at 11 PM, holding morning approvals until midnight is an unnecessary constraint.
Does it work inside the building?
The punch-out that matters most — the end of a closing shift at 11 PM from inside the kitchen — needs to work without full signal. Apps that require a live internet connection at punch-out fail at exactly this moment.
How Punch Handles Split-Shift Restaurants
Punch was built for service businesses with non-standard shift patterns, including restaurant AM/PM split-service crews.
Each service segment records as its own time entry. A lunch-service punch-in and punch-out creates one record. The dinner-service punch-in and punch-out creates another. Both show in the approval queue, and both count toward the weekly overtime total.
Overtime calculates per workweek, not per shift. The weekly total combines every approved shift segment across the full 7-day workweek, with Sunday as the default workweek anchor. California orgs get daily overtime on any single segment that crosses the daily threshold.
Punch-out queues offline when signal is poor. Closing staff punching out from inside the kitchen won't get a connectivity error. The action queues locally and syncs automatically — the timestamp reflects when they tapped punch out, not when the sync happened.
The approval workflow is per-employee, per-week. A manager can review and approve a full week's worth of segments — however many individual entries — in one workflow. The weekly summary shows combined hours, gross pay, and overtime before they confirm. The mark-paid action locks the week with a pay period record.
Pricing is per org, not per seat. A 15-person restaurant that has 3 managers and 12 servers pays for one plan, not 15 seats. Every plan includes every feature — approvals, overtime calculation, job site tracking, reports, CSV and QuickBooks-format exports, and the offline punch-out queue.
The 14-day free trial starts on signup, no credit card required: Start a free trial →
Frequently Asked Questions
Does each split-shift segment need its own approval?
Yes. Each punch-in/punch-out record is its own time entry and needs to be approved separately in the Approvals queue. The weekly view groups them by employee so a manager can see the full picture before approving any individual record.
What if an employee's second punch-in is later than expected?
The manager can edit the punch-in time from the Approvals view. Every time edit records an audit-log entry with the old time, the new time, the editor's name, and a reason — so there's a clear record of what changed.
Do split-shift segments each need a job site assigned?
If the org uses job site geofencing, the punch-in at each segment checks that the employee is within range of their assigned site. Both segments would be punching into the same restaurant site, so the geofence check is the same for both.
Does Punch handle California split-shift premium pay calculations?
Punch surfaces whether the split-shift pattern occurred (two segments in one day with a gap). The actual premium pay calculation depends on the applicable local minimum wage, the employee's daily earnings, and the offset rules — these vary enough by city and county that the premium should be calculated in the payroll system or with a payroll provider familiar with California wage law.
How does weekly overtime work when an employee covers both AM and PM service every day?
All segments in the workweek add up toward the 40-hour overtime threshold. An employee who works 4.5 hours at lunch and 5.5 hours at dinner, five days a week, is working 50 hours total — 40 regular plus 10 overtime. The overtime calculation doesn't care how many separate segments made up those 50 hours.
Can a restaurant owner see which employees worked split shifts most frequently?
The Reports surface in Punch shows hours by employee across any date range. An owner who wants to track split-shift frequency can look at the weekly totals by day — employees with two shift records on a single day are working split schedules. More granular split-shift analytics are a roadmap item.
Bottom Line
A restaurant that runs AM and PM service needs two clean time entries per split-shift employee per day, both counted toward weekly overtime, both visible in the approval queue. The time tracking system has to handle this naturally — not force split-shift records into a break structure, not miscalculate overtime by segment instead of by week, and not fail at punch-out when signal is poor inside a commercial kitchen building.
Punch handles the full split-shift workflow: separate records per segment, per-workweek overtime aggregation, offline punch-out for closing staff, and a clean weekly approval flow. The 14-day free trial starts on signup — no credit card required.