Restaurant scheduling: how to build a schedule that works

Why restaurant scheduling is different

Restaurants have sharp, predictable peaks and quiet periods, often within a few hours. Labor is one of the largest controllable costs, and a schedule that is a little too heavy at 3 p.m. every day quietly eats into profit, while one that is too light at 7 p.m. costs sales and tips and burns out staff. Many employees are part-time, students or working second jobs, so availability changes often. And tipped roles, minors and split shifts bring their own rules. See our restaurant industry page for an overview.

To build shifts, approve swaps and spot coverage gaps in one place, see EZTime employee scheduling software.

Step 1: forecast sales by day and hour

Start with your point-of-sale history. Look at sales or covers by hour for the same weekday over recent weeks, then adjust for known events: holidays, local games, weather, promotions and private bookings. You do not need a complex model. A simple table of expected covers per hour for each day is enough to begin. Review the forecast against actual sales every week and you will get better quickly.

Step 2: turn the forecast into labor needs

For each position, decide how much volume one person can handle. For example, a server might handle four to six tables at once, a line cook a certain number of tickets per hour, and a dishwasher a station regardless of volume. These are your own standards; set them from experience and adjust them.

Some positions are fixed regardless of volume, such as an opening manager or a closing dishwasher. Add those to your template.

Step 3: check the labor budget

Multiply the scheduled hours by wage rates (including any tip credit where it applies) and compare total labor with forecast sales. Most restaurants track labor cost as a percentage of sales. If the draft schedule is over budget, look for overlapping shifts, early starts before demand begins and late closes with more people than needed. Our labor cost percentage calculator can help.

Step 4: build shifts around demand

• Stagger start times. Bring servers in at 5, 5:30 and 6 instead of all at 5.
• Use first cuts. Plan who leaves first when the rush ends, and tell them in advance.
• Consider split shifts carefully. They match lunch and dinner peaks but are hard on staff. Some states require extra pay for split shifts. See our split shift guide.
• Avoid clopenings. Closing late and opening early the next day causes fatigue and turnover. See clopening shifts.
• Balance experience. Pair new hires with experienced staff on busy shifts.

Step 5: match people to shifts

Collect availability in writing and keep it current. Assign shifts based on availability, skills, fairness (who gets the good sections and the busy weekend shifts) and hours targets: some people need full-time hours, others want only a few shifts. Track weekly hours as you go so you do not create unplanned overtime.

Step 6: check the rules

Before publishing, check the schedule against the rules that apply to you:

• Overtime: non-exempt employees earn overtime after 40 hours in a workweek under federal law; some states, such as California, also have daily overtime. See FLSA overtime rules.
• Breaks: several states require meal and rest breaks. See California meal and rest break rules for one detailed example.
• Minors: federal and state child labor laws limit hours and times for workers under 18, especially during the school year. See child labor laws.
• Predictive scheduling: cities including New York, San Francisco, Seattle, Chicago and others require advance notice and premium pay for changes for many restaurant employees. See predictive scheduling laws.
• Reporting time pay: some states require pay when employees are sent home early. See reporting time pay laws.

Step 7: publish early and manage changes

Post the schedule at least a week ahead, and two weeks or more where the law requires it or where you can. Share it digitally so everyone sees updates. Set a clear process for shift swaps (approved by a manager, between qualified staff), for time-off requests (submitted by a deadline) and for call-outs (who to call, how early). Record every change and who asked for it.

Step 8: review actual vs. scheduled

After each week, compare scheduled hours with actual clocked hours and sales. Where were you overstaffed or short? Did people clock in early or stay late? Which shifts had call-outs? Adjust your standards and templates. This weekly review is how schedules improve from guesswork to a reliable system. Share the results with shift leads, too; the people running the floor often know exactly why a Tuesday lunch felt short-staffed.

A short example (fictional)

A 90-seat neighborhood bistro has labor cost running well above its target. The owner compares scheduled shifts with hourly sales and finds that all servers start at 4:30 p.m. although covers do not pick up until 6. Staggering server starts, adding a planned first cut at 8:30 p.m. and moving prep work to the quiet mid-afternoon bring labor back to target within a month, without cutting anyone’s tips on busy hours.

How EZTime helps

EZTime helps restaurants build schedules from templates, publish them to the team in the mobile app, manage swaps and time off, and compare scheduled with actual hours. Employees clock in from a tablet kiosk or their phone, breaks are recorded, overtime alerts help managers react before the week ends, and tip pooling helps distribute tips per shift.

Frequently asked questions

Where to go next