A split shift divides one workday into two separate blocks with an unpaid break of several hours between them. A server works 11:00-14:00 for the lunch rush, goes home, then returns for 18:00-22:00 for dinner service. One workday, two commutes, zero uninterrupted time off.
Split shifts are common in food service, retail, healthcare, and transport. They solve a business problem - matching staffing to demand peaks - while creating a personal problem for the worker who has to structure their day around two unpaid gaps.
When split shifts make sense
Split shifts justify themselves when:
- Demand concentrates in two distinct windows (lunch + dinner, morning rush + evening rush)
- You need specific roles covered in both windows (supervisor, specialist)
- Part-time hours would otherwise mean hiring two people for one combined schedule
They do not make sense when:
- The gap is less than 2 hours (not enough rest to justify two commutes)
- Public transport forces workers to stay near the workplace for the unpaid break
- The same worker could cover a shorter continuous shift instead
The pay question
Some jurisdictions require a split shift premium - an extra payment to compensate workers for the inconvenience. California pays a split shift premium equal to one extra hour of minimum wage when the combined shift doesn't bring total daily earnings above minimum wage times hours worked plus one hour.
Even where there's no legal requirement, consider paying a small premium. Workers who accept split shifts regularly - without an incentive - tend to accumulate grievances. A €5-10 per split shift payment signals that you recognize the inconvenience.
Gap length matters
A 2-hour gap is annoying. A 4-hour gap is usable - a worker can go home, rest, run errands, or pick up children from school. Under 2 hours puts the worker in limbo: not enough time to do anything meaningful, long enough to be frustrating.
Design split shifts with a gap of at least 3 hours where possible. If you can't, consider whether a continuous shift is more appropriate.
Consent and rotation
Don't default to the same workers getting all split shifts. Rotate them. If three servers share split shift duty across a two-week cycle, each gets four per cycle instead of eight. The cumulative fatigue difference is significant.
More importantly: ask workers which shifts they prefer before assigning. Some workers with childcare responsibilities actually prefer split shifts - they can be home for school pickup during the gap. Others find them unworkable. Collecting this preference takes five minutes and dramatically reduces friction.
The fatigue math
A worker on a split shift works 7 hours but is "at work" (including commute and mandatory presence) for 12 hours. Their effective personal time is compressed to evenings and possibly a window during the gap.
Avoid scheduling split shifts on consecutive days. If a worker does a split on Monday, give them a continuous shift or a day off on Tuesday. Consecutive splits exhaust people faster than continuous long shifts.
Track who gets split shifts in your scheduling system and set a cap - for example, no worker gets more than 2 split shifts per week.
Communication makes a difference
Post split shift schedules further in advance than regular shifts. Workers need more planning time for a split shift because they have to arrange two commutes, potentially two childcare pickups, and an afternoon that's neither rest nor work.
Two weeks' notice for split shifts, one week minimum for regular shifts. Workers who know the split is coming can plan around it. Workers who find out on Thursday for Saturday develop resentment.
What good looks like
A well-managed split shift program:
- Pays a premium per split shift
- Keeps gaps above 3 hours
- Rotates across workers who've opted in
- Posts schedules 2 weeks ahead
- Caps split shifts at 2 per worker per week
- Tracks cumulative split shift hours by worker
Rezano tracks split shifts, collects availability preferences, and flags overloaded workers. Try it at rezano.lv.