How Far in Advance Should You Post Work Schedules?
Quick Answer
Most small businesses post schedules one to two weeks in advance, and two weeks is a strong standard for hourly teams. Federal law does not set a notice period, but some states and cities have predictive scheduling or fair workweek laws for certain employers. For example, Oregon requires covered large retail, hospitality and food service employers to provide schedules 14 calendar days in advance. Pick a regular posting day, publish by that deadline every time and keep a record of changes.
Ask hourly employees what they want most from a schedule, and many will say the same thing: to know it early. Late schedules make it hard to arrange childcare, classes, second jobs and appointments. They also lead to more call-outs, swaps and no-shows. Posting schedules further in advance is one of the simplest ways to improve attendance and keep good employees.
This guide explains how far in advance to post schedules, which laws may apply, how to handle changes and how to set a posting routine, with a free schedule posting policy template.
Quick Answer: How Far in Advance?
| Notice | Common for | Pros | Cons |
|---|---|---|---|
| Less than 1 week | Very small teams, unpredictable work | Flexibility for the business | More conflicts, call-outs and turnover |
| 1 week | Many restaurants and retail stores | Easy to adjust to demand | Short notice for employees |
| 2 weeks | Many hourly teams; some laws | Employees can plan ahead | Requires better forecasting |
| 3–4 weeks | Healthcare, manufacturing, stable operations | Most predictability | More changes after posting |
For most small businesses, two weeks is a good target. If that's not realistic yet, start with one week and work toward two.
Is There a Law on How Far in Advance to Post Schedules?
There is no federal law requiring employers to post schedules a certain number of days in advance. But some states and cities have predictive scheduling or fair workweek laws that apply to certain employers, usually large employers in retail, hospitality and food service. These laws can require advance notice, extra pay for late changes and rest between shifts.
Oregon is one example. According to Oregon's Bureau of Labor and Industries, the law covers large employers with at least 500 employees worldwide in the retail, hospitality or food service industry, and requires them to give employees a written work schedule at least 14 calendar days before the first day on the schedule. Several large cities have their own fair workweek rules. Check your state and city before setting your policy, especially if you have many employees or locations.
Some states also require reporting time pay when employees show up and are sent home early. See reporting time pay by state.
Rest Between Shifts
Predictive scheduling laws often include rest rules. Oregon's law, for example, says covered employees can't be scheduled during the first 10 hours after the end of the previous day's work unless they request or agree to it, and if they do work within that window, they're paid time and a half for those hours. Even where it isn't required, avoiding short turnarounds reduces fatigue. See clopening shifts.
Free Schedule Posting Policy Template
[Company Name] Schedule Posting Policy
1. Posting deadline. Work schedules will be posted by [day] at [time], at least [number] days before the first day of the schedule.
2. Where schedules are posted. Schedules are available in [scheduling app] and posted at [location].
3. Availability. Employees must submit availability changes and time-off requests by [day] at least [number] days before the schedule is posted.
4. Changes after posting. The company will try to avoid changes after a schedule is posted. When changes are needed, the manager will notify affected employees as soon as possible by [method]. Employees may decline additional hours added with less than [number] hours' notice [where applicable].
5. Shift swaps. Employees may swap shifts with qualified coworkers with manager approval through [method].
6. Records. Posted schedules and changes are kept for [number] years.
7. Local laws. Where state or local scheduling laws apply, the company will follow those requirements.
Why Posting Early Matters
- Fewer call-outs and no-shows. Employees can plan around shifts.
- Better retention. Predictable schedules are a major reason hourly employees stay.
- Fewer last-minute swaps. Conflicts surface before the week starts.
- Less manager stress. Fewer scrambles to fill gaps.
- Fairness. Everyone sees their schedule at the same time.
Set a Regular Posting Day
Pick one day and time to post every schedule, such as every Wednesday by 5 p.m. for the schedule starting two Sundays later. Consistency matters as much as lead time. Employees learn when to check, and managers build the schedule on a routine instead of the night before.
| Task | Deadline example |
|---|---|
| Availability and time-off requests due | Friday, 3 weeks before the schedule starts |
| Manager builds schedule | Monday–Tuesday |
| Schedule posted | Wednesday by 5 p.m., 2 weeks before it starts |
| Swap requests reviewed | Ongoing, approved within 24 hours |
How to Post Further in Advance
- Collect availability early. Set deadlines for availability changes and time-off requests. See the employee availability form.
- Use a template. Start each schedule from a standard week instead of a blank page.
- Forecast demand. Use last year's sales, reservations and booked jobs.
- Schedule core shifts first. Lock in shifts that rarely change.
- Leave a few open shifts to fill as demand becomes clearer.
- Publish on time, even if a few shifts are still open.
What to Include in a Posted Schedule
- Employee names and roles or stations.
- Start and end times, including the date each shift starts.
- Location or job site.
- Break times, if scheduled.
- On-call shifts, clearly labeled.
- Open shifts available to pick up.
- Manager or lead on duty for each shift.
See how to make a work schedule.
Handling Changes After Posting
Changes will happen: sick calls, sudden rushes and slow days. Limit them, and handle them consistently:
- Notify affected employees directly as soon as the change is known.
- Ask for volunteers before assigning extra hours.
- Avoid cutting shifts at the last minute when possible.
- Record every change with the date, reason and who approved it.
- Follow any local rules on extra pay for late changes.
Use a shift change request form so employee-requested changes are documented too.
How to Share Schedules
| Method | Pros | Cons |
|---|---|---|
| Printed schedule in the break room | Simple, visible | Employees must be on site to see changes |
| Group text or email | Fast | Hard to track versions |
| Spreadsheet link | Easy to update | Easy to edit by mistake |
| Scheduling app | Notifications, swaps and history | Requires setup |
Whatever method you use, make sure the latest version is clear and employees are notified when it changes.
Posting Schedules for Different Teams
Different teams may need different lead times. Office and production teams with steady hours can often post a month ahead, while restaurant floors that depend on reservations may need to stay at one or two weeks. Set a minimum for the whole company, then let departments post earlier where they can.
Example: A Fast-Casual Restaurant
A fast-casual restaurant posted schedules on Friday for the week starting Monday. Call-outs were high, and the manager spent weekends texting people to fill shifts. She moved to posting every Wednesday for the week starting 11 days later, set an availability deadline and left two open shifts per day to fill as needed. Within two months, call-outs dropped and fewer shifts went uncovered.
Common Mistakes
- Posting on a different day every week.
- Waiting for perfect forecasts before posting.
- Making unannounced changes after posting.
- Ignoring local scheduling laws.
- Not collecting availability before building the schedule.
- No record of what was posted and what changed.
Schedule Posting Checklist
| Step | Done? |
|---|---|
| Check state and local scheduling laws | |
| Choose a posting lead time | |
| Set a regular posting day and time | |
| Set availability and time-off deadlines | |
| Choose how schedules are shared | |
| Write a change notification process | |
| Keep records of posted schedules and changes |
Predictive Scheduling Laws: What They Commonly Include
| Requirement | What it usually means |
|---|---|
| Advance notice | Schedules provided a set number of days ahead |
| Predictability pay | Extra pay for certain changes after posting |
| Rest between shifts | Minimum hours off between shifts, or extra pay |
| Good faith estimate | Estimated hours given at hiring |
| Offer hours to current staff | Extra hours offered to existing employees before new hires |
| Recordkeeping | Schedules and changes kept for a set period |
Requirements, covered employers and exceptions differ by state and city, so read the rules that apply to you or ask an employment attorney. Even if no law applies, many of these practices make scheduling fairer and reduce turnover.
Balancing Notice With Flexibility
Posting two weeks out doesn't mean the schedule can never change. Build flexibility in without breaking the promise of predictability:
- Leave a few open shifts that employees can claim as demand becomes clear.
- Keep a voluntary list of employees who want extra hours.
- Use on-call shifts sparingly and label them clearly, where allowed.
- Let employees swap shifts with approval instead of managers rewriting the schedule.
Schedule Posting for Seasonal Businesses
Seasonal businesses often find it hardest to post early because demand swings. Use last season's data to build a base schedule for the whole season, post it in two- or four-week blocks and adjust the open shifts as you go. Seasonal staff appreciate knowing their hours early, which makes it easier to keep them through the end of the season. See the seasonal hiring guide.
Notifying Employees of Schedule Changes
A change is only useful if the employee actually sees it. Contact affected employees directly, by app notification, text or call, rather than just updating the posted schedule. Ask them to confirm they've seen the change, especially for added shifts or earlier start times. Keep a record of when they were notified.
Tracking Schedule Changes
Keep a simple log of changes after posting: the date, employee, original shift, new shift, reason and who approved it. Over time the log shows whether changes are coming from call-outs, poor forecasting or employee requests, and where your posting process can improve. If a scheduling law applies, these records may also be required.
| Date | Employee | Original shift | New shift | Reason | Approved by | Employee notified |
|---|---|---|---|---|---|---|
How Posting Early Helps Payroll
Schedules posted early give managers time to spot overtime before the week starts, check that each shift meets minimum staffing and confirm time-off requests. Comparing the posted schedule with time clock data afterward shows where actual hours drifted from the plan. See scheduled vs. actual hours.
Posting Schedules for Remote and Field Teams
Field crews and remote employees can't check a schedule taped to the break room wall. Publish schedules where they can see them on their phones, include job addresses and start locations and notify them when assignments change. For crews that travel between sites, include the first location of the day so they know where to report.
Getting Managers to Post on Time
Late schedules are often a manager workload problem. Make the posting deadline part of each manager's job expectations, give them a template and the forecast in advance and block time on their calendar to build the schedule. Track whether schedules go out on time each week, and help managers who regularly miss the deadline find what's slowing them down.
Common Questions From Employees
- "When will next week's schedule be posted?" On your set posting day, every week.
- "Can I request days off after the schedule is posted?" Yes, but approval may depend on finding coverage.
- "What if my shift changes?" You'll be notified directly.
- "Can I swap a shift?" Yes, with an approved coworker and manager approval.
Schedule Posting and Time-Off Requests
Set a time-off deadline that comes before you build the schedule, such as three weeks before the schedule starts. Requests submitted by the deadline are reviewed before posting, and requests after it depend on finding coverage. Clear deadlines are fairer than first-come, first-served approvals that change after the schedule is out. See how to deny a PTO request.
Holiday Schedules
Post holiday schedules even earlier, often four to six weeks ahead, since employees make travel and family plans well in advance. Share how holidays will be assigned, such as a rotation, before you build the schedule.
Schedule Posting Quick Reference
| Item | Recommendation |
|---|---|
| Lead time | 2 weeks for most hourly teams |
| Posting day | The same day and time every week |
| Availability deadline | Before the schedule is built |
| Changes | Notify directly, ask for volunteers, record every change |
| Laws | Check state and city scheduling rules |
Share this summary with every manager who builds schedules so the whole business follows the same routine.
Measuring Whether Posting Early Is Working
Track a few simple numbers before and after you change your posting routine: call-outs and no-shows, shifts filled at the last minute, swap requests, overtime hours and turnover. If these improve after you start posting earlier, share the results with managers so the routine sticks.
Final Thoughts
Posting schedules early is one of the easiest ways to improve attendance and keep hourly employees. Aim for two weeks, pick a regular posting day, collect availability before you build and keep changes to a minimum. Check whether state or city scheduling laws apply to you, and record what you post and what changes. Predictable schedules make life easier for employees and managers alike.
Post Schedules Early With Updoot
Updoot's scheduling lets you build schedules from templates, publish them to employees' phones, notify people of changes and keep a history of every posted schedule.
