Sales-based scheduling means building your staff schedule from the sales you expect, not from last week's roster or a gut feeling. You forecast sales for each day and daypart, turn that forecast into labor hours, and place shifts where the hours are needed. Done well, you stop paying for idle hours on slow shifts and stop running short when the rush hits.
This guide covers how it works, which data to use, a worked example you can copy, the U.S. labor rules to check when shifts change, and how to automate the routine so you stay in control.
TL;DR
- Sales-based scheduling sets staffing levels from forecast sales, hour by hour, rather than from habit.
- The cycle has four steps: forecast demand, convert it to labor hours, build the schedule, then monitor and adjust.
- Count non-sales work such as prep, cleaning and stocking in your labor plan, not just time spent with customers.
- Check weekly, not monthly, so overtime and overstaffing get fixed early.
- Before you move shifts, check overtime and predictive scheduling rules in your state or city.
Table of Contents
- What sales-based scheduling is
- The four-step cycle
- A worked example
- What data to use
- Sales-based scheduling in sales and call teams
- Labor rules to check before you change shifts
- Common mistakes to avoid
- How Heyhive automates sales-based scheduling
- Turn your forecast into a schedule
- FAQ
- Sources
What sales-based scheduling is
Most small teams start with a fixed template: the same people, the same shifts, every week. It is easy to run, but demand does not repeat that neatly. A Tuesday after a local event looks nothing like a typical Tuesday.
Sales-based scheduling flips the order. The forecast comes first, and the schedule follows it. You may also hear it called demand-based or demand-driven scheduling. The idea is the same: staffing built on real-time data and forecasting instead of repeating last month's pattern.
How it differs from other approaches:
- Fixed templates: the same roster every week, regardless of sales.
- Availability-first scheduling: you fill slots with whoever can work, then hope coverage matches demand.
- Instinct scheduling: the manager's feel for the week. Instinct scheduling is one of the most reliable ways to run a consistently high labor cost percentage.
- Sales-based scheduling: forecast sales first, derive hours second, then fit people to those hours while respecting availability and rules.
It works best where sales swing by day or hour: restaurants, cafés, retail stores, service businesses and multi-location operations.
The four-step cycle
Hospitality scheduling research describes the process as a cycle of forecasting demand, translating it into labor requirements, constructing the schedule, and monitoring and adjusting in real time. Here is how to run each step.
Step 1: Forecast sales by daypart
Start with what you already have: point-of-sale reports by hour and by day. Look at the same weekday over several recent weeks, not just last week, so one odd day does not skew the number.
Then layer in what you know is coming:
- Promotions, menu changes or sales events
- Local events, school calendars and holidays
- Weather patterns that move foot traffic
- Seasonal trends from the same weeks last year
The output is a sales number for each daypart, for example 7 to 11 a.m., 11 a.m. to 2 p.m. and so on. Retail teams can go finer. Our guide to retail labor forecasting by the hour shows how.
Step 2: Convert sales into labor hours
Pick a productivity target, such as sales per labor hour, or a labor budget as a percentage of sales. Divide forecast sales by the target to get the labor hours that daypart can support.
Two cautions make this step accurate:
- Count the work behind the work. A sound labor plan accounts for both customer-facing tasks and non-revenue work like prep, cleaning and stocking. Opening and closing tasks do not scale with sales, so schedule them as fixed blocks.
- Use a floor. Even a slow hour needs minimum coverage for safety and service. Set a minimum headcount per shift before the forecast adjusts anything.
If you want a calculator-style walkthrough, see how to schedule to a labor budget.
Step 3: Build the schedule
Now turn hours into shifts. This is where scheduling gets hard, because the forecast has to meet real people. Cornell workforce management researcher Gary Thompson frames it as managing hard constraints such as legal work-hour limits and soft constraints such as employee preferences.
In practice:
- Hard constraints: availability, certifications, overtime thresholds, required breaks, minimum rest between shifts, minors' hours.
- Soft constraints: preferred days, shift swaps, fair distribution of weekend and closing shifts.
Satisfy the hard ones first, then honor as many soft ones as the forecast allows. Putting your strongest people on peak hours is the point of the exercise, so check that the right skills sit on the right shifts, not just the right headcount.
Step 4: Monitor and adjust
A forecast is a best guess. Compare actual sales to forecast during the week and trim or add hours when the gap is large. Send staff home early on a slow shift if your policy allows it, and offer open shifts when the rush is bigger than expected.
Review results weekly. One analysis argues that tracking labor cost weekly rather than monthly lets you catch scheduling errors and unexpected overtime before they compound across the month. A monthly review tells you what went wrong after it is too late to fix.
A worked example
The numbers below are illustrative, to show the math. Replace them with your own.
A neighborhood café forecasts $4,800 in sales for Saturday. Its target is $80 in sales per labor hour, so the day supports 60 labor hours ($4,800 ÷ $80).
The manager splits the forecast by daypart using past Saturday sales patterns:
| Daypart | Forecast sales | Labor hours at $80/hour | Window | Staff on the floor |
|---|---|---|---|---|
| 7–11 a.m. | $1,600 | 20 | 4 hours | 5 |
| 11 a.m.–2 p.m. | $1,200 | 15 | 3 hours | 5 |
| 2–6 p.m. | $1,200 | 15 | 4 hours | 4 |
| 6–9 p.m. | $800 | 10 | 3 hours | 3 |
The staff column is rounded to whole people so the total stays at 60 hours (5×4 + 5×3 + 4×4 + 3×3). The manager then:
- Adds a fixed opening block before 7 a.m. and a closing block after 9 p.m. for prep and cleaning, which sit outside the sales-driven hours.
- Puts the two most experienced baristas on the 7 to 11 a.m. peak.
- Staggers start times so the 11 a.m. lunch bump is covered without everyone clocking in at once.
- Checks that nobody crosses an overtime threshold for the week.
If Saturday morning sales run 15% above forecast, the manager calls in one on-call person for the late morning. If they run well below, the last hour of a shift gets trimmed. The schedule is a living plan, not a fixed document.
What data to use
You do not need a data science team. Start with these inputs:
- Sales by hour and weekday from your POS, ideally for 8 to 12 recent weeks.
- Transactions or customer counts, because ticket size can hide traffic changes.
- Task workloads, such as deliveries to unload, orders to prep or appointments to run.
- Known events, promotions and seasonality.
- Employee availability, certifications and overtime hours so the forecast turns into legal, workable shifts.
- Labor cost to date for the week, so you can see whether you are tracking to budget.
McKinsey researchers studying retail stores name four prerequisites for strong activity-based scheduling: store-specific workload calculations, reliable forecasts of volume drivers, a flexible workforce and performance-management systems. The takeaway for a small operator: forecast per location, keep part of your team flexible, and measure results every week.
Sales-based scheduling in sales and call teams
The phrase also shows up in sales organizations, where the "demand" is call or lead volume rather than foot traffic. The same logic holds: forecast the volume, convert it to required agents, then schedule to match. A call center staffing model is one example of building coverage around expected inbound volume and service levels.
Labor rules to check before you change shifts
Schedules built on forecasts change often, and every change has legal consequences. Check these before you adjust.
- Overtime. Federal overtime is set by the Fair Labor Standards Act, and moving shifts mid-week can push someone over the threshold without anyone noticing. Our summary of FLSA overtime rules for employers covers the basics. Confirm your state's rules too, since some set stricter limits.
- Predictive scheduling laws. Some cities and states require advance notice of schedules and extra pay for late changes. See our guide to fair workweek laws and how 14-day advance notice schedules can help you avoid predictability pay.
- Penalty pay and regular rate. The U.S. Department of Labor explains that in places with scheduling laws, certain penalty payments for schedule changes may be excluded from the regular rate when calculating FLSA overtime, as long as they are not prearranged or anticipated. Ask your payroll provider or an employment attorney how this applies to your payroll.
- A written change policy. Spell out who can change a shift, how much notice staff get and how changes are recorded. Here are seven steps to a schedule change policy.
If you operate in a city with a fair workweek ordinance, build the notice window into your forecasting cadence. Forecast earlier, publish earlier and keep late changes rare.
Common mistakes to avoid
- Forecasting from one week. Use several weeks of the same weekday to smooth out noise.
- Ignoring fixed tasks. Prep and closing work do not shrink when sales dip.
- Matching sales exactly, hour by hour. Staff need workable shifts, so smooth the hours into blocks of at least a few hours.
- Skipping skills. Headcount is not coverage. Certifications and experience matter as much as numbers.
- Reviewing monthly. Check labor against sales weekly and correct early.
- Publishing late. Employees plan their lives around schedules. Earlier publishing improves reliability and keeps you clear of notice rules.
How Heyhive automates sales-based scheduling
Doing this by hand works for one small team. It gets heavy fast with several locations, changing availability and overtime to watch. Heyhive is built to take over the repetitive part.
- AI scheduling: generate a full week of shifts in seconds, with employee availability, certifications and overtime limits respected.
- Sales and labor forecasting: plan staffing against expected demand.
- Manager approval: you review and approve every shift before it is published, so you stay in control.
- Open shift coverage: fill gaps quickly when the day runs busier than planned.
- Payroll-ready hours: export clean hours at the end of the pay period.
You keep the judgment calls. Heyhive handles the work behind the work.
Our perspective
We built Heyhive on one belief: a forecast only helps if it becomes a schedule people can actually work. Many managers already know how many people a Saturday needs. What drains their week is turning that knowledge into shifts that respect availability, certifications and overtime limits, then fixing the schedule when the day changes.
That is why our AI generates a full week of shifts in seconds, and why nothing goes out until you approve it. We think the best scheduling combines machine speed with human judgment. The AI does the sorting. You make the call.
We also think scheduling should not live apart from the rest of the workday. When scheduling, time tracking, messaging and payroll-ready hours sit in one place, a change to a shift reaches the team immediately and shows up correctly in the hours you export. You are always in control, and the paperwork follows.
Heyhive
Turn your forecast into a schedule
If you already forecast sales and want the schedule to follow without hours of spreadsheet work, Heyhive's AI scheduling can generate your week for you to review and approve. Add GPS-verified time clocks and payroll-ready hours, and you can see how the week actually played out against the plan.
Start free and generate your first schedule at useheyhive.com.
FAQ
What is sales-based scheduling?
It is a way of building employee schedules from forecast sales. You predict sales by day and daypart, convert them into labor hours, and place shifts where those hours are needed. Staffing rises and falls with demand instead of repeating a fixed template.
How do I decide how many employees to schedule?
Divide forecast sales for a daypart by your sales-per-labor-hour target, or apply your labor budget percentage to forecast sales. Then add fixed tasks such as opening and closing, and set a minimum crew per shift. Review the result against actual sales each week and adjust the target.
Can you give an example of a work schedule based on sales demand?
Yes. The worked example above shows a café that forecasts $4,800 on Saturday and, at $80 per labor hour, schedules 60 hours: five people at the morning peak, five at lunch, four in the afternoon and three in the evening. Fixed opening and closing blocks are added on top.
Do predictive scheduling laws affect sales-based scheduling?
They can. Some cities and states require advance notice and extra pay when you change schedules late, and last-minute forecast tweaks may trigger them. Check the rules where each of your locations operates, and publish schedules early so changes stay rare.
How often should I review labor against sales?
Weekly. Weekly reviews catch overtime and overstaffing while you can still correct them, while monthly reviews show problems only after the month is over.
Sources
- Workforce Scheduling: A Guide for the Hospitality Industry (Cornell eCommons)
- The Key to Controlling Labor Cost: A Shift-by-Shift Strategy (Restaurant Owner)
- Restaurant Labor Cost Percentage Benchmarks 2025–2026 (CalStack)
- Smarter schedules, better budgets (McKinsey)
- Fact Sheet #56B: State and Local Scheduling Law Penalties and the Regular Rate (U.S. Department of Labor)
- Call center staffing model (RevRing Blog)