It's 10:40 on a Thursday night. The restaurant closed an hour ago, and you're in the back office with last week's schedule open, a sticky note that says "Maria, no Sundays??", three unread texts asking for next weekend off, and a nagging feeling you're forgetting someone. Next week's schedule was supposed to go up this morning.
You'll finish it. You always do. But by Saturday, two people will say they never saw it, one shift will be double-booked, and you'll be on the phone at 4 p.m. looking for a closer.
If that sounds familiar, the problem usually isn't effort. It's that the schedule is being built from memory, scraps and good intentions instead of a repeatable process. This guide walks through how to make employee schedules that hold up in real life, whether you run a restaurant, a cafe, or any small business that depends on hourly shifts.
Start with the work, not the people
The most common scheduling mistake is starting with names. You look at who's available and spread them across the week until the grid looks full. That gives you a schedule that's full, but not necessarily right.
Start instead with what the business needs, block by block:
- When do you get busy? Use your sales or ticket history if you have it, or your own notes from recent weeks. A cafe might need three people from 7 to 9:30 a.m., then two until the lunch bump.
- Which roles have to be covered? A shift with four servers and nobody who can run expo is not a covered shift.
- What non-customer work has to happen? Deliveries, prep, deep cleaning, inventory counts. If it isn't scheduled, it gets squeezed into the busiest hour.
Write this down as a simple staffing template: day, time block, role, number of people. It becomes the skeleton you fill each week, and it's the part that changes least.
Collect availability the same way every time
Availability that arrives by text, sticky note, hallway conversation and "I told you last month" is impossible to track. Pick one way for people to submit availability and time-off requests, and one deadline.
For example: "Time-off requests for next week are due Sunday by 8 p.m. After that, it's a shift swap, not a schedule change." Then hold to it, kindly and consistently.
A few practical tips:
- Ask for standing availability (the days and times someone can generally work) separately from one-off requests (a wedding, an exam, an appointment).
- Revisit standing availability every few months or at natural change points, like a new school semester.
- Keep it all in one place you check every time you build the schedule. If requests are still scattered across a group chat, here's why that keeps breaking down.
Build the schedule in the same order every week
Once you have your staffing template and availability, fill the schedule in a consistent order. Doing it the same way each week saves time and cuts down on mistakes.
1. Place your anchor shifts first
Openers, closers and shift leads set the tone for everything else. Put the people who can run a shift on the shifts that need running.
2. Cover your peaks
Fill the busiest blocks next, using your strongest people where they make the biggest difference: the fastest barista on the morning rush, the steadiest cook on Friday dinner.
3. Fill the rest, then pair for training
Fill the remaining blocks. Where you can, pair newer employees with experienced ones instead of stacking every new hire on the same slow Tuesday.
4. Check for fairness
Before you publish, scan the week for patterns. Is one person closing five nights while someone else gets every Saturday off? Did anyone land a "clopen," closing late and opening the next morning? Uneven schedules are one of the quieter reasons good employees leave.
Leave room for real life
A schedule that only works when everyone shows up healthy, on time and in a good mood is a fragile schedule. Build in a little slack:
- Know your backups. For each busy shift, know who you'd call first if someone drops, and rotate who that is so it isn't always the same person.
- Don't run your riskiest shifts at the bare minimum. If Saturday brunch falls apart when one person is out, it was understaffed on paper too.
- Set a clear swap rule. Decide whether employees can trade shifts on their own, whether a manager approves it, and who is qualified to cover what. Write it down once so you aren't deciding it fresh every time.
Publish it early, in one place
The best schedule in the world doesn't help if people can't find it, or find out about it too late. Pick a consistent day to post the schedule and stick with it. The more lead time people get, the more chances they have to flag a conflict before it turns into a callout. If you operate somewhere with scheduling or notice rules for hourly workers, check what applies to you.
Post it where everyone already looks, the same place every time. Once it's out, treat changes as changes: tell the affected people directly instead of quietly editing the sheet and hoping they notice.
Let the schedule carry expectations, too
A good schedule tells people more than when to show up. It tells them what they're responsible for. Adding a role or station to each shift ("Open: espresso bar," "Close: dish and floors") removes a surprising amount of confusion at the start of a shift. It also makes accountability fairer, because everyone can see who owned what. For more on that, see how to set clear expectations for employees from day one.
Review last week before you build next week
Before starting the next schedule, spend five minutes with the last one:
- Where were you overstaffed or short?
- Which shifts had callouts or swaps?
- Did anyone push back on their hours, or go quiet in a way that worries you?
- What did you have to fix on the fly?
Adjust your staffing template based on what you find. Over a few weeks, the schedule stops being a guess and starts reflecting how your business actually runs.
A quick checklist for your next employee schedule
- Staffing template by day, time block and role
- Availability and time-off collected in one place, with a deadline
- Anchor shifts and peak blocks filled first
- New hires paired with experienced staff
- Fairness check on closes, weekends, clopens and extra shifts
- A backup plan for high-risk shifts
- A clear shift-swap rule
- Published on the same day, in the same place, every week
- A role or station noted on each shift
- A quick review of last week before building the next
The goal is a schedule you don't have to rescue
A schedule that works isn't a perfect one. People will still get sick, cars will still break down, and some Saturdays will still be chaos. The difference is that a well-built schedule absorbs those hits instead of collapsing, and it doesn't depend on you remembering every request at 10:40 on a Thursday night.
Start with the staffing template. Then pick one habit from the checklist and make it routine before adding the next. As we wrote in Your Schedule Isn't the Problem, the grid itself is rarely the hard part. The system around it is.
If you'd like that system in one place, AcznTeams brings scheduling, training, tasks, team communication, and employee progress together for hourly teams, so the schedule and everything connected to it live side by side.