How to make a staff roster that doesn't blow your labour budget
Most rosters are copied from last week, which was copied from the week before, which someone wrote in 2023 based on a hunch. Meanwhile your sales data knows exactly when you're busy. Here's how to build a roster from demand — and keep labour under control without leaving the floor short.
Wemu Team
Product
Labour is usually the largest controllable cost in a service business, and the roster is where it's decided — days before the money is spent. Yet most rosters are built from memory and copied forward, which means they encode last year's trading patterns and every staffing mistake made since.
Start with demand, not availability
The order matters. Build the shape of the week from what your sales data says, then fill it with the people available — not the other way around.
- 1Pull sales by hour for the last 8–12 weeks from your POS, split by day of week
- 2Mark the peaks and the dead zones. Most venues discover at least one shift that's staffed out of tradition rather than trade
- 3Set a coverage rule for each band — for example, one staff member per $X of hourly revenue, or per Y covers, or per Z bookings
- 4Now lay in your people, matching your strongest staff to your busiest bands
- 5Check the total against your labour cost target before you publish, not after payroll runs
The overlap trick
Most understaffing complaints come from changeover, not headcount. Staggering starts by 30–60 minutes so shifts overlap through the peak usually fixes the "we're slammed at 12:30" problem without adding hours.
Know your labour cost percentage
Labour cost percentage is total wage cost (including on-costs like superannuation, payroll tax, and casual loading where they apply) divided by revenue for the same period.
| Business type | Typical labour cost | Notes |
|---|---|---|
| Café | 25–35% | Rises fast if you over-staff quiet mid-afternoons |
| Full-service restaurant | 30–40% | Kitchen plus floor; prime cost target is 60–65% with food |
| Salon / spa | 35–50% | Commission structures push this higher by design |
| Retail | 10–20% | Lower ratios; the trap is under-staffing peak conversion hours |
| Fitness studio | 30–45% | Instructor pay per class dominates |
Set the target before you build the roster, then check the projected cost as you go. Discovering you're four points over after payroll has run is a lesson you pay for twice.
The rules that keep a roster fair
- Publish at least two weeks ahead — short notice is the single biggest driver of resentment and turnover in hourly teams
- Rotate the undesirable shifts rather than assigning them to whoever complains least
- Respect availability you've agreed to, and hold people to the availability they gave you
- Set a swap policy in writing: who can swap with whom, and who approves it
- Honour minimum rest between shifts and any award or contract rules that apply where you operate
- Never roster to a number that only works if nobody calls in sick — build one flex person into peak days
Swaps, sickness, and the Saturday-morning phone tree
The roster you publish is not the roster you run. What separates a calm operation from a chaotic one is how changes are handled after publication.
The worst version is a group chat where a manager asks "can anyone cover?" and eight people ignore it. The better version is a system where a staff member posts the shift, everyone eligible sees it, the first to accept takes it, and the roster updates itself — with the manager approving rather than brokering. That's exactly what the Wemu Team app does: staff see their schedule, request swaps as open offers or direct trades, and accepted swaps update the roster immediately.
Close the loop: scheduled vs actual
A roster is a plan. Clock-ins are what happened. The gap between them is where labour budgets quietly die — the 15-minute early starts, the shifts that ran 40 minutes long, the overtime nobody approved.
- Compare scheduled hours against clocked hours every week, per person
- Flag overtime as it accrues, not when payroll runs
- Watch for consistent early clock-ins — usually a rostering problem (the shift genuinely needs to start earlier) rather than a discipline problem
- Track labour as a percentage of same-day revenue so a quiet day's over-staffing is visible immediately
When scheduling, clock-ins, and sales live in one system, that comparison is a report rather than a reconciliation project — and the next roster gets built from what actually happened instead of what was planned.
Roster from real demand
Wemu builds schedules alongside your sales data, gives staff their own app for shifts and swaps, and compares scheduled hours against actual clock-ins with overtime flagged. 7-day free trial.
Start free trial →