Imagine it's Sunday night and one of your line cooks still doesn't know whether she works Tuesday. Her sister can watch the kids, but needs an answer by tomorrow. So the cook texts you. You don't reply, because you're still building the schedule, and you're still building it because two people haven't told you what they need next week.
From your side, getting that schedule out on Sunday night feels like a win. From her side, she just spent a whole weekend unable to make a single plan.
So how far in advance should you post an employee schedule? For most restaurants, cafes, and small businesses with hourly teams, a good target is two weeks, with one week as the floor. That's an operator's rule of thumb, and your business may land somewhere else. Here's how to think it through, along with the employee scheduling best practices that make early posting stick.
Employee scheduling best practices start with a target
Two weeks tends to work because it balances two things pulling against each other. Your team needs enough time to arrange childcare, trade a shift at a second job, or say yes to a family dinner. You need the schedule to stay close enough to reality that you aren't rewriting it every few days.
Go much shorter than a week and people can't really plan around it. Go out a couple of months and you'll spend your time revising a schedule built on guesses about who's still around and how busy you'll be.
What matters as much as the number is consistency. A schedule that goes up every other Monday, without fail, is worth more to your team than one that sometimes lands three weeks out and sometimes lands on Saturday night. People can plan around a date they trust.
What short notice costs you, even when nobody complains
Late schedules rarely blow up in one dramatic moment. The cost tends to arrive in small pieces:
- Conflicts surface late. A conflict flagged ten days out is a quick conversation. The same conflict flagged the night before is a callout, and now you're the one scrambling.
- Questions land on you. Every "is the schedule up yet?" is a small interruption, and they tend to pile up in the group text that's already hard to manage.
- Swaps multiply. When people get their shifts after they've already made plans, more of those shifts end up back on the table.
- Your dependable people notice. Employees with options don't always tell you the schedule is the problem. They just quietly start looking for a place that runs better.
How to choose the right lead time for your business
Two weeks is a starting point. These questions will help you adjust it.
Is your week fairly predictable?
If your busy times barely change from one week to the next, you can probably post further out, or keep a repeating base schedule and only post the exceptions. A small cafe with the same opener every weekday doesn't need to reinvent Tuesday.
Do seasons, events, or weather swing your demand?
A shop near a stadium or a patio-heavy restaurant may never know the third week of the month with much confidence. Two weeks can still work here, with a few shifts marked as flexible (more on that below).
Whose calendars are you working around?
Ask your team what they're actually coordinating with. Students may be tied to class and exam dates. Someone with a second job may need your schedule before that employer's posting day. If most of your team needs your schedule by a certain day, that's useful information you can't get from a spreadsheet.
How long does your process really take?
Be honest here. If building the schedule takes a full week of chasing people for answers, no target will stick until that part gets fixed.
Work backward from your posting day
Schedules often go up late because nothing upstream of posting day has a deadline. Say your schedule week starts on a Monday and you want to give two weeks' notice. Your posting day is the Monday two weeks earlier. Working back from there, a simple rhythm might look like this:
- Thursday before posting: time-off requests and availability changes are due.
- Friday: build the draft, using the same order every week.
- Monday morning: review it against the things managers often miss, fix what you find, and post.
The specific days matter less than having them written down and shared. Once people know requests close on Thursday, you stop being the person who has to chase everyone, and a late request becomes a swap conversation instead of a rebuild.
"My business changes too fast for that"
It may. Plenty of operators hold the schedule back because they're afraid of posting something they'll have to change. But waiting doesn't remove the uncertainty. It just moves it onto your team.
A better option is to post what you know and label what you don't. Publish the core shifts on time, and mark the uncertain ones clearly: "Saturday patio shift, flexible, confirmed by Wednesday." Then keep that promise. People can work with a known unknown far better than with silence.
A few habits keep an early schedule trustworthy:
- Make a real change a real conversation. Talk to the person affected directly. Don't quietly edit the sheet and hope they notice.
- Ask before you assign. After posting, a new shift is a request, unless your own policy says otherwise.
- Keep a short list of what changed. If the same Saturday gets reworked every week, the problem is in your staffing plan, not your posting date.
That last one matters more than it sounds. A schedule posted two weeks out that changes constantly teaches people not to believe it, and then you've lost the benefit of posting early.
Check whether scheduling laws apply to you
In some places, advance notice is a legal requirement for certain employers. Two examples:
- Oregon: large employers (at least 500 employees worldwide) in retail, hospitality, or food services must provide a written schedule at least 14 calendar days in advance.
- Seattle: retail and food service establishments with 500 or more employees worldwide must post schedules at least 14 days in advance. Full-service restaurants must also have 40 or more full-service locations worldwide to be covered.
Other cities, including San Francisco, Los Angeles, Chicago, Philadelphia, and New York, have their own versions with their own coverage rules and notice periods. A lot of independent operators may fall outside these thresholds, but don't assume. Rules change, and this isn't legal advice, so check with your local labor agency or an employment attorney if you're unsure.
Move the date before you overhaul the process
You don't have to jump from Sunday night to two full weeks by next Monday. Pick a posting day a few days earlier than your usual one, tell your team, and hit it every cycle for a month. Then move it again. Ask a couple of people whether it's helping, because they'll tell you what's actually changed for them.
And somewhere along the way, that line cook stops texting you on Sunday night, because she already knows about Tuesday.
If the harder part is that requests, availability, and the schedule are all scattered, AcznTeams brings scheduling, training, tasks, team communication, and employee progress into one place for hourly teams, so your team has one place to look when the schedule goes up.