How to Schedule Employees in a Small Restaurant

It's 10:47 PM on a Sunday. You've been on your feet since 7 AM. morning prep, lunch rush, afternoon inventory, dinner service. Now you're sitting at the bar with a glass of something you probably deserve, staring at a spreadsheet that's supposed to become next week's schedule.

Maria wants Thursday off. Again. Javi can't do mornings until his class schedule changes. You already promised Leo the Saturday dinner shift but now you need him at lunch because your prep cook just texted. his car won't start, "maybe all week."

You don't have an HR department. You don't have a scheduling manager. You have a phone full of texts and a spreadsheet that's one accidental delete away from chaos.

Sound familiar? Let's fix it.

Why Small Restaurant Scheduling Is Its Own Animal

If you've read general restaurant scheduling guides (including our complete guide), you've probably noticed they assume a certain size. A GM who only manages. A dedicated scheduler. Clear role separation between front and back of house.

That's not your reality.

In a small restaurant. say 6 to 20 employees. the scheduling looks different:

• You wear every hat. You're the owner, the manager, sometimes the line cook. Scheduling is something you do between closing out the register and mopping the floor.
• Everyone knows everyone. There's no hiding behind policy. When you schedule Rosa for the shift she hates, you'll hear about it. At length.
• One absence breaks everything. In a 40-person restaurant, losing a server is inconvenient. In a 10-person restaurant, it's a crisis.
• Roles overlap. Your hostess buses tables. Your bartender runs food. Your dishwasher preps salads. That's not a bug. it's survival.

The good news? Small also means nimble. You can build a scheduling system that actually works, without the bureaucracy.

The Sunday Night Method (Step by Step)

Here's the framework that works for small restaurants. It takes about 30-45 minutes once you've got it down.

Step 1: Lock in Your Anchors

Every week has a few shifts that matter more than others. For most restaurants, that's Friday dinner and Saturday dinner. Maybe Sunday brunch if that's your thing.

Start there. Put your strongest people on those shifts first.

Pro tip: Your best server on a Tuesday lunch is wasted. Your worst server on a Saturday night is a disaster. Match talent to volume.

Step 2: Build the Skeleton

Before plugging in names, map out what each shift actually needs:

This doesn't change much week to week. Save it as a template. Copy it every Sunday and just swap names.

Step 3: Collect Availability (Without the Text Chaos)

The old way: "Everyone text me your availability by Friday."

What actually happens: three people text Friday, two text Saturday morning, one never texts, and you're left guessing.

Fix it: Pick ONE method and make it non-negotiable.

• A shared Google Form (free, simple, collects everything in one place)
• Your scheduling app's availability feature
• A physical sign-up sheet posted by Wednesday

The method matters less than the consistency. Whatever you pick, the rule is: if you don't submit availability by Thursday night, you get scheduled wherever I need you.

People learn fast.

Step 4: Fill by Constraint, Not Preference

Don't start with "where does everyone want to work?" Start with "what constraints do I have?"

1. Legal constraints. rest periods, max hours, minor labor laws
2. Hard requests. pre-approved time off, medical appointments
3. Skill requirements. shifts that need specific certifications or experience
4. Availability. who's actually free
5. Fairness. distribute desirable shifts (and undesirable ones) equitably over time
6. Preferences. now, and only now, consider who wants what

This order prevents the trap of scheduling around favorites while the B-team gets whatever's left.

Step 5: The 48-Hour Preview

Post the schedule by Wednesday for the following week. But here's the move that saves you grief: mark it as "draft" for 48 hours.

During that window, employees can flag conflicts you missed. Not "I don't feel like working Tuesday". genuine conflicts. You adjust. Then Friday morning, it's locked.

This catches the stuff you'd otherwise deal with as Monday-morning emergencies.

Cross-Training: Your Secret Weapon

In a small restaurant, cross-training isn't a nice-to-have. It's the thing that keeps you from closing early when someone calls out.

Here's how to think about it:

The Coverage Matrix

Map out who can cover which roles, even partially:

When Leo calls out sick on a Saturday, you don't need another bartender. You need someone who can pour drinks and keep the bar moving. Rosa's done it before. Problem solved in one text instead of five.

How to cross-train without chaos:

• Pick one person per month to learn one new station
• Start on slow shifts (Tuesday lunch, not Saturday dinner)
• Pair them with your strongest person in that role
• Give it 3-4 shifts before expecting independence

The investment pays off every single time someone calls out. Which, in a small restaurant, is every single week.

The Call-Out Protocol

Speaking of call-outs. stop improvising.

When someone can't make their shift, here's the system that works:

1. Employee texts YOU and the team group, not just you, not just the group
2. You check your scheduling app (or mental list) for who's off and might want hours
3. First person to accept gets the shift. no favoritism, no complicated bidding
4. If no one bites within 2 hours, you start making calls to your shortlist

Keep a mental (or actual) list of the 2-3 people who always want extra hours. Those are your call-out lifeline. Treat them well.

Ana ran a 12-person Mediterranean place in Valencia. She kept a "flex list". three employees who got first dibs on extra shifts, plus a free meal when they covered last-minute. She went from scrambling every week to solving call-outs in under 20 minutes. "It's like having an on-call team, except they actually want to be there."

For more on handling call-outs and no-shows, we've got a separate deep dive. The short version: a system beats panic every time.

Split Shifts: The Small Restaurant Dilemma

Small restaurants often run lunch and dinner with a dead zone in between. That creates a choice:

Option A: Split shifts. Same person works 11-2 and 5-10. They get a break in the middle. You get continuity.

Option B: Separate crews. Lunch team and dinner team. Clean handoff. No one works 12-hour days.

The honest answer: It depends on your team.

Some employees prefer split shifts. they live nearby, they'd rather work one long day than two short ones, or they want the tips from both services.

Others hate it. Three hours off isn't enough to go home but too much to just sit around.

What works for most small restaurants:

• Core kitchen staff work split shifts (they're needed for prep anyway)
• Floor staff split into lunch/dinner crews when possible
• Saturday is the exception. everyone works, no splits needed because service is continuous

The rule: Never assign split shifts without asking. And if someone does it regularly, acknowledge it. A split shift is harder than it looks on paper.

How to Stop Playing Favorites (Even Accidentally)

Every small restaurant has the same dynamics:

• The reliable ones get the busy shifts and the good tips
• The newer ones get the slow shifts and wonder why they were hired
• The owner's favorite gets the schedule they want without asking

Over time, this creates a two-tier team. The A-team feels overworked. The B-team feels ignored. Both resent you.

Fix it with a rotation tracker. Nothing fancy. a simple tally of who's worked which premium shifts this month. When Maria has worked four Saturday dinners and Javi has worked one, you know what to do next week.

This isn't about being robotic. It's about having data to back up your decisions when someone says "you always give her the good shifts."

When to Ditch the Spreadsheet

Look, we make scheduling software. We'd love you to use it. But we're also going to be honest: not every small restaurant needs software.

Spreadsheets are fine when:

• You have fewer than 6-8 employees
• Your schedule is mostly the same every week
• You don't deal with frequent swaps or call-outs
• You're comfortable with the time it takes

Software starts making sense when:

• You're past 8 employees and juggling complex availability
• You're spending more than 30 minutes a week on scheduling
• Shift swaps happen over text and things get lost
• You've had double-bookings or missed shifts
• Your team asks "what's the latest schedule?" more than once a week

We wrote a whole guide on spreadsheets vs. scheduling software if you want the full breakdown. If you're comparing tools specifically, see our Homebase alternatives comparison or the full software guide. The short version: the tool matters less than the system. A disciplined manager with a spreadsheet beats a lazy manager with the fanciest app.

The 5 Mistakes Every Small Restaurant Makes

After talking to dozens of small restaurant owners, these come up every time:

1. Posting the Schedule Too Late

If your team sees next week's schedule on Sunday night, they've already made plans. Post by Wednesday. Non-negotiable.

2. Scheduling by Memory Instead of Data

"I think Rosa was off last Saturday" isn't good enough when Rosa remembers perfectly that she wasn't. Track it.

3. Ignoring Split Shift Burnout

That cook who's been doing 11-2 / 5-close six days a week? They're going to quit. It's not a matter of if.

4. Having No Call-Out Protocol

"Just text me" is not a protocol. It's an invitation for chaos at 6 AM.

5. Never Saying No to Availability Requests

If you approve every request, you'll never have enough coverage on the shifts nobody wants. Sometimes "no" is the right answer. but pair it with "I'll get you that day off next week instead."

A Simple Weekly Scheduling Routine

Here's the routine, condensed. Print it. Tape it to the wall next to the walk-in.

That's it. Four touchpoints per week. Everything else is noise.

Getting Started

If you're reading this at 10:47 PM on a Sunday with a spreadsheet that's giving you heartburn, here's what to do this week:

1. Build your shift skeleton template. what each shift actually needs, role by role
2. Set an availability deadline. pick a day, announce it, enforce it
3. Create your call-out protocol. write it down, share it with the team
4. Cross-train one person. start small, one person, one new station, slow shift

You don't need to overhaul everything overnight. Start with the system. The tools. whether that's a spreadsheet, a whiteboard, or scheduling software. just support the system.

We wrote scheduling guides for every major industry, not just restaurants.

And if you're curious about what a simple scheduling tool looks like, If you want to see how it looks in practice, the Turnozo restaurant scheduling page walks through the setup.

Turnozo was built for exactly this. Small teams, simple schedules, no bloat. Thirty days free. But honestly, if the spreadsheet works and you've got a system. keep the spreadsheet. The system is what matters.

---

Need help building your schedule template? Grab our free employee schedule template. it's the skeleton from Step 2, ready to fill in.

More on restaurant operations: Restaurant Staffing Statistics (2026). the turnover and labor data behind scheduling decisions.