What Is a Split Shift? When It Saves Money, What the Law Says, and How to Schedule One

What counts as a split shift, and what does not

A split shift is one workday worked in two separate blocks, with unpaid, off-duty time between them that the employer sets. Restaurants use a split shift schedule more than anyone, because their day has two rushes and a quiet stretch in the middle. Restaurants use split shifts to pay for the lunch rush and the dinner rush without paying for the quiet afternoon between them. The same pattern works anywhere the work comes in two waves with a slow stretch between.

Three things get called a split shift and are not one. A 30-minute meal break in the middle of a shift is a break. Split shift vs double shift is the one people mix up most: a double is two shifts worked back to back, and many restaurants use the word for any lunch and dinner day, so the test that matters for pay is whether the time between is unpaid. A close followed by the next morning's open is a clopening, which is about rest between two workdays rather than a gap inside one. Read what a clopening shift does to the next morning for that one.

The gap is only unpaid when the person is really off. Federal rules say time away is not hours worked when the employee is “completely relieved from duty” and the time is “long enough to enable him to use the time effectively for his own purposes” (29 CFR 785.16). Keep a cook on call through the afternoon, or ask them to stay behind and prep, and those hours can count as hours worked.

For example, let's say a cook works lunch from 11 to 2, leaves, and comes back for dinner from 5 to 10. That cook is on a split shift: one workday, two paid blocks, three unpaid hours in the middle.

When split shifts cost less than an all-day shift or a second hire

Split shifts cost less than an all-day shift whenever the quiet stretch between two rushes would otherwise be paid. They cost the same wages as hiring a second person for one of the rushes. The saving grows when an all-day week crosses 40 hours, because the quiet hours you stop paying are then the most expensive hours in the week.

Let's say your cook earns $20 an hour and works five days a week. There are three ways to cover both rushes.

Keep one cook on from 11 to 10 all week and you pay for 12.5 quiet afternoon hours, and every one of them is an overtime hour at $30. Those 12.5 hours are the afternoon from 2 to 5, less the half-hour meal, five days running, and they land exactly on the hours past 40. Split the same five days and the week is 40 hours × $20, which is $375 a week less for the same two rushes.

Hire a second person instead and the wages come out the same, but you now have one more person to find and train, and the lunch half is a whole trip to work for 3 hours × $20, which is $60. A split shift stops being worth it when the quiet stretch is short. If lunch and dinner are an hour apart, the gap is no use to anyone, and a straight shift is kinder to the person working it.

The pros and cons of split shifts, for you and the person working them

The pro of a split shift is covering both rushes without paying for the quiet between them. That is the $375 a week from the section above, for every cook you move off an all-day shift. The cons are a longer day for the same pay, two chances to lose the shift, and extra pay in some states.

A spreadsheet or an outdated restaurant scheduling tool checks none of these, so you find each one after the cook has already lived it. Every row on this list is decided when the schedule is written, so every one of them can be checked before anyone works it.

Split shift pay: what the rules say in California, New York and DC

Split shift pay is set by your state or city, not by federal law. California and Washington DC add one hour at minimum wage for a split day. New York adds one hour for restaurant workers whose day spans more than 10 hours.

The split shift premium California requires works as a floor on the day's pay, not always as an extra hour on top. In California, the day's pay has to reach minimum wage for every hour worked, plus one more hour. The Labor Commissioner's own example does the sum this way: a worker on $12 an hour with an $11 minimum wage, working six hours, has to be paid at least $77, and at $72 is owed the $5 difference. The rule covers restaurants through Wage Order 5.

For example, let's say your cook works the 11 to 2 and 5 to 10 day in California, where the state minimum wage is $16.90 an hour.

A worker paid $16.90 earns 8 hours × $16.90 = $135.20 for the same day, and is owed $16.90 more. If your city sets a higher minimum wage, use that number instead, and the answer can change. The Labor Commissioner also says no premium is owed to an employee who lives at the place of employment, or when the employee asks for the break for their own convenience, and that the premium goes on the pay stub as its own line.

New York counts the spread of hours, which is the time from the start of the workday to the end of it, breaks included. An 11 to 10 split day in a New York restaurant is an 11-hour spread, so it owes the extra hour whatever the cook earns. The rule applies “regardless of a given employee's regular rate of pay.” Other states and cities can add their own, and your state labor department decides how they apply to your restaurant.

How to schedule split shifts well, in seven steps

To schedule split shifts well, put the gap where business is actually quiet, offer them before you assign them, keep the gap the same each week, count both halves in the week's hours, protect the next morning, cap days in a row, and pay the day correctly. Every step works with a spreadsheet.

1. 1

   Put the gap where the quiet really is.

   Pull a few weeks of sales by the hour and find where they drop. Build the lunch half around the first rush and the dinner half around the second, so nobody is paid to stand through a slow hour at either end.

2. 2

   Offer split shifts before you assign them.

   Some people want the middle of the day free for school pickup, classes or a second job. Ask first, and give split shifts to the people who asked for them. The person who never says no should not end up with all of them.

3. 3

   Keep the gap useful, and keep it the same.

   Three hours is time a person can use. One hour is not. Keep the same gap on the same days each week. The same gap every week is a day the cook can plan around.

4. 4

   Count both halves in the week's hours.

   A split day is still one person’s hours, and both halves add to their week. For example, let’s say a cook is on five split days. That is already 40 hours, so one extra lunch half puts every one of its 3 hours into overtime. The rest of that week is in how to prevent restaurant overtime.

5. 5

   Protect the next morning.

   A split day often ends on the dinner close. Before you put that person on the next morning’s open, count the hours between. A close at 10 and an open at 7 is nine hours off, before the drive home and the drive back.

6. 6

   Cap the days in a row, and count a split day as one.

   A split day is one workday, even with two start times. Set the most days in a row anyone works, and count the split day once toward that limit.

7. 7

   Pay the day correctly where your state adds an hour.

   In California, Washington DC and New York restaurants, check each split day against the rules in the section above before payroll runs.

Six of these seven steps are checks a schedule can run for you.

How XShift AI schedules split shifts

XShift AI schedules a split shift as two shifts on the same day for the same person, and checks the second half against the first, their week and your rules before it saves. In a spreadsheet or an outdated restaurant scheduling tool, every check below is something you do in your head, for every person, on every split day.

When XShift AI builds the week or fills open shifts, all twelve checks run for every person it considers. When a manager puts someone on a half by hand, it still refuses an overlapping shift, approved time off and anything your Autopilot rules block. The last six checks are those rules at work.

For example, let's say you wrote one Autopilot rule saying nobody goes into overtime. A cook already on 40 hours this week is never handed Friday's lunch half, because the rule adds the lunch half to their week first and refuses it. The same checks sit behind our scheduling software for restaurants. XShift AI runs these checks before the shift saves, and you can watch it refuse one live in a demo.

Build the lunch and dinner shifts once, then let them repeat

Type the lunch shift and the dinner shift into the AI Copilot once, confirm the pattern, and XShift AI lays them down for as many weeks as you ask.

For example, let's say you send exactly those two sentences. That is 5 days × 4 weeks × 2 halves = 40 shifts. By hand, that is forty shifts typed into a grid one at a time. Here it is two sentences.

Those shifts start empty, and filling them is the next step. When XShift AI builds the schedule, it fills each half with someone who clears the checks in the section above, so a cook who marked Tuesdays from 11 to 2 unavailable only lands on Tuesday dinners. AI schedule generation explains how that works. Once a week looks right, save it as a template, and it lays the same lunch and dinner shifts down on any future week you pick, ready to fill again.

When one half of a split shift calls off

When one half of a split shift calls off, Autopilot works through a fixed list of checks and finds the people allowed to take that half, without anybody making a phone call. It runs once you switch call-off coverage on, which is off when you first sign up. Depending on how you set it, Autopilot then gives the half to the best person who passed, or offers it to everyone who passed.

The check that matters most on a split day is the overlap check, because it looks at hours, not at the day. A cook already on tonight's dinner is still allowed to take the lunch half, because 11 to 2 and 5 to 10 never touch. That cook was coming in that day anyway. In a spreadsheet or an outdated restaurant scheduling tool, the cook on at 5 looks booked for the day, and the one person already planning to come in is the easiest person to skip.

For example, let's say the lunch cook calls off at 9 on a Friday. The rush starts at 11, two hours away. Autopilot drops anyone who does not work at that location, then anyone without the cook role, then anyone who marked Fridays or those hours unavailable. It runs your rules. It removes anyone with a shift that overlaps 11 to 2, moves anyone who would pass 40 hours that week to the back, and removes anyone on approved time off. Let's say your dinner cook is at 32 hours this week, so lunch takes them to 35. The dinner cook passes every check. A cook who only works at your other location never lands on the list. Nobody made a call.

How both halves show up on the time clock and in payroll

XShift AI's time clock records each half of a split shift as its own clock-in and clock-out, and the payroll export gives each half its own row. Clocking in for a scheduled shift opens two hours before it starts, and a clock-in earlier than that goes to a manager as a request. A new clock-in is refused while an earlier one is still open. The export writes one row per clock-in and clock-out, with any recorded break taken off.

That refusal is what protects the quiet afternoon from being paid by accident. For example, let's say the cook finishes lunch at 2 and forgets to clock out. At 5 they go to clock in for dinner, and the time clock will not start a new clock-in on top of the open lunch entry. The mistake surfaces at 5, the same afternoon, while everyone still remembers lunch ended at 2. Found on payroll day instead, that open entry would have paid the whole quiet afternoon. With a spreadsheet, a missing clock-out is just a long row that nobody reads until the pay run.

The payroll-formatted version of the export adds each person's hours up by week and splits them into regular hours and overtime hours, so both halves land in the right week's total.

What all-day shifts are costing you

All-day shifts cost you $375 a week for every cook you could have put on a split shift instead.

Here is what a week built this way looks like. Both rushes are covered and the afternoons are not on the payroll. A lunch half that calls off can go to the cook who was coming in at 5 anyway. A forgotten clock-out is found the same afternoon. Going back means paying for the quiet afternoon again, every week.

For a restaurant with 100 people, XShift AI is $29 plus $1 for each of the other 99, which is $128 a month or $1,536 per year. That yearly price is about 127 times smaller than what ten all-day cooks cost one location. Get fully set up in minutes.

Split shift questions