Roster
Labor vs sales, and demand forecast
Set projected sales and a target labor %. The schedule shows labor as a share of sales per day while the week is still editable. Forecasting is included, not an upsell.
Labor vs sales is a budget on the week you are still editing, not a month-end surprise. Demand forecast is included — not a premium SKU.
Set the target
Admins, in Settings:
- Turn labor target on.
- Set target labor % (e.g. 28 means scheduled labor should stay at or under 28% of projected sales).
- Enter projected sales per weekday, per location. There is no POS integration; a manager types the plan.
Those daily sales sit on the location. The schedule compares assigned labor $ against them.
Read it on the schedule
On Schedule, each day shows labor cost as a share of that day's sales, colour-coded against the target. The week has a rollup.
This is visible while the week is editable. Move a shift, re-run Auto-Fill, or drop a double, and the share updates. Waiting for timesheets to learn you overspent is what this page exists to avoid.
Labor $ uses the wages on Team. Members do not see those numbers.
Demand forecast
Forecasting estimates expected staffed hours per weekday and position from recent history, with day-of-week seasonality and recency weighting. It is a guide for how many shifts to draw, not a purchase order.
It does not auto-create shifts. You still build the week. It does not override Auto-Fill eligibility.
What this is not
- Not a till feed. If Saturday sales were actually $14k and you typed $9k, the % is honest against a bad plan.
- Not payroll. Actuals from the time clock can be compared on the dashboard; they do not rewrite the schedule's projected %.
- Not an upsell. If a vendor charges extra for "AI forecasting", that is not this.