How to Plan Labour Cost Against a Sales Forecast

Why a full schedule can still lose money

A schedule can have every shift covered and still be wrong for the week. If Tuesday is slow and Saturday is busy but both are staffed alike, labour cost lands as a surprise percentage of sales only when the week is over and nothing can be changed.

Managers often keep the sales forecast in one place and the roster in another. The comparison happens in the head, or in a spreadsheet at the end of the week, when the money is already spent.

Putting the forecast and the target beside the schedule means each change to a shift immediately shows its effect on labour percentage, while there is still time to adjust.

Why this happens

• Expected sales are not written down anywhere the scheduler can see them.
• There is no agreed target labour percentage to measure against.
• Labour cost is only worked out after payroll or at month end.
• Shifts without a pay rate are silently left out of the cost.
• The weekly result is not reviewed with the people who made the roster.

Biznsbook addresses this through sales forecast panel in the builder, target labour cost percentage, Labour vs Sales grid and Monday email in Labour Scheduling, on the same roster, clock and swaps as the rest of the module.

Small gaps in scheduling rarely fail loudly. They show up later as numbers nobody can explain. Recording each step where it happens removes the guesswork.

Step-by-step: Plan Labour Cost Against a Sales Forecast

Written for owners, managers and shift supervisors who roster staff in Biznsbook Labour Scheduling, with or without HRMS.

1. Set the target. In Labour Admin → Settings, set Target labour cost % of sales, for example 30. Leave it blank to turn the red highlight off.
2. Open the forecast panel. Open the schedule Builder. The Sales forecast & labour % panel lists each day of the schedule.
3. Enter expected sales. Type the expected sales for a day. If Sales or POS is licensed and you leave a day blank, the builder uses the average of that weekday over the last four weeks, labelled avg of last 4 weeks.
4. Read the labour percentage. Each day shows scheduled labour cost and labour % (cost divided by forecast sales). A day over the target turns red, and the footer shows the week's figure and sales per labour hour.
5. Adjust the shifts. Move, add or remove shifts and watch the percentage change. The footer's Missing cost counts shifts that have no rate.
6. Review Labour vs Sales. Open Labour Analytics → Labour vs Sales to see each day's sales, scheduled and worked hours and cost, labour % and sales per labour hour. Download it as CSV.
7. Switch on the Monday email. In Labour Settings → Weekly report, switch on the Monday email and list recipients. It sends last week's grid.

Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.

Common mistakes to avoid

• Mistake 1: Expected sales are not written down anywhere the scheduler can see them. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.
• Mistake 2: There is no agreed target labour percentage to measure against. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.
• Mistake 3: Labour cost is only worked out after payroll or at month end. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.
• Mistake 4: Shifts without a pay rate are silently left out of the cost. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.
• Mistake 5: The weekly result is not reviewed with the people who made the roster. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.

Each of these turns into a question the manager cannot answer quickly. Fix the process on the record rather than in email threads or spreadsheets.

Best practices that hold up as you scale

• Set the target — In Labour Admin → Settings, set Target labour cost % of sales, for example 30.
• Open the forecast panel — Open the schedule Builder.
• Enter expected sales — Type the expected sales for a day.
• Read the labour percentage — Each day shows scheduled labour cost and labour % (cost divided by forecast sales).
• Adjust the shifts — Move, add or remove shifts and watch the percentage change.

Set the rule once in settings, let staff enter their own information, and review the results weekly before you publish the next roster.

How Biznsbook supports this workflow

sales forecast panel in the builder is part of Biznsbook and works on the same records as the rest of scheduling, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

target labour cost percentage is part of Biznsbook and works on the same records as the rest of scheduling, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

Labour vs Sales grid and Monday email is part of Biznsbook and works on the same records as the rest of scheduling, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

Labour Scheduling works on its own. Managers need the Labour Scheduling Manager role (or Shift Supervisor for schedules and attendance); invited staff get the Shift Worker role. HRMS, Payroll, Inventory and Accounting are optional.

Suggested implementation timeline

1. Week 1: Set up sales forecast panel in the builder and the permissions the people involved need.
2. Week 2: Run the real process in Biznsbook only, with no side spreadsheet, for one team or site.
3. Week 3: Review what was recorded with the people involved and tighten the rules where they disagreed.
4. Month 2: Roll out to every team or site.
5. Ongoing: A weekly planning rhythm.

Related guides

Cluster hub: Scheduling guides. Module: scheduling software. Also see build employee schedules and publish employee schedules.

What the labour percentage includes

Labour percentage is scheduled labour cost divided by forecast sales. The cost comes from each shift's estimate, which uses the hourly rate that applies to that shift. A shift with no known rate is not counted as zero; it is left out and counted in the footer's Missing cost, so you know the figure is understated until the rates are filled in.

Clearing a figure you typed returns that day to the four-week average, so you can try a number and put it back without losing the automatic estimate.

From planning to review

The builder tells you what the plan looks like. The Labour vs Sales grid tells you what happened: sales, scheduled and worked hours and cost, labour percentage and sales per labour hour for each day, for the dates and location you choose. Comparing the two each week shows whether your forecasts are too cautious or too hopeful, and whether the target itself is realistic.

The Monday email puts last week's grid in front of the people who need it without anyone having to open the page, and the same report triggers the labour.report.weekly Automation event for teams that want to route it further.

Metrics to track monthly

• Pending time-off requests
• Labour % against target by day
• Open shifts left after auto-fill
• Short-notice changes and premium hours
• Missed-break exceptions

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Manual workarounds vs Biznsbook

Compare common manual workarounds with Biznsbook sales forecast panel in the builder and the related capabilities.

A weekly planning rhythm

Set or confirm the target, enter the forecast for each day, adjust shifts until the days sit near the target, publish, and then look at the Labour vs Sales grid the following week. Record why a day missed so the next forecast is better.

Write the rule down in your staff handbook so the settings and the policy say the same thing.

Frequently asked questions

How this differs by industry