Step 1: Forecast demand
Before anyone goes on a shift, you need a view of what each part of the day, week and outlet will need. For a F&B outlet, that is typically a covers forecast (or transaction forecast for retail) broken down by hour or daypart.
Most operators forecast by looking at the same week last year, then adjusting for current trend, planned events and known factors (school holidays, new mall openings, a competitor closing). You do not need a data science team — a simple Excel pivot of last year's POS data plus a manager's read on the current period is enough to start.
For F&B
Forecast covers per daypart (breakfast / lunch / tea / dinner / supper). Translate covers into front-of-house and kitchen FTEs. A typical full-service outlet does 12-15 covers per FOH per hour during peak; quick-service does more.
For retail
Forecast footfall or transactions per hour. Translate into FOH cover requirements and operational coverage (open/close, restocking, deliveries).
Step 2: Capture availability
Before drafting shifts, capture each worker's availability for the period — and any known unavailability (annual leave, MC, NS, school exams for student part-timers). The cleanest way is to:
- Set a recurring weekly availability for each worker
- Allow workers to flag one-off changes (events, exams, family commitments)
- Lock in approved AL well in advance
For shift-heavy businesses, this is the single highest-leverage upgrade from spreadsheets to dedicated software. When availability is captured digitally, you do not have to chase managers' phones for "can you work Tuesday" queries during roster build.
Step 3: Draft the roster
Now you can build. Working from your demand forecast and the availability picture, place workers into shifts. The order matters:
- Place senior anchors first. Each shift needs a duty manager / shift lead. Lock those in first.
- Place full-timers next. They have fixed weekly contractual hours. Build their week so it hits target hours.
- Fill peaks with part-timers and casuals. This is where you flex headcount up and down.
- Leave gaps deliberate. If you cannot cover a shift with available staff, do not assign someone you know won't show. Leave it open and source.
Mind the rules as you build. Under Part IV of the Employment Act: max 44 hours per week, at least one rest day per week, max 12 hours per day including OT, max 72 OT hours per month. Soft constraints (workers' preferences, fairness) sit on top of these hard limits.
Step 4: Handle conflicts
Two common conflicts:
- Coverage gap — no one available for a shift. Options: ask for volunteers, pull from a casual pool, post on a gig platform, or accept reduced cover for that shift.
- Hours over- or under-allocation — a full-timer not hitting contracted hours, a part-timer over hours. Adjust before publishing.
Resolving conflicts after publication is harder than resolving them before. The discipline of holding the draft for a final review pass pays off.
Step 5: Publish
Publishing means making the roster live to workers. The two questions are how and how far in advance.
How
Push the roster to a mobile app workers already have on their phones. Email and WhatsApp groups work but are noisy and easy to miss. A dedicated app gives workers a single source of truth they can check anytime.
How far in advance
Two weeks is the practical standard in Singapore F&B and retail. MOM does not mandate a specific notice period, but two weeks gives workers time to plan and reduces no-shows. Some businesses publish four weeks for fixed-shift workers and two weeks for ad-hoc casuals.
Step 6: Manage swaps
Once the roster is live, things change. A worker gets sick, a school holiday is announced, a wedding suddenly demands attention. The two ways to handle this:
- Swap with another worker. The two workers agree, manager approves, the system records the change.
- Open the shift back up. Worker drops, the shift goes back into a pool other workers can claim.
Both approaches reduce no-shows compared with the rigid "come in or get a black mark" model. The key requirement is documentation — the changed roster needs to be the system of record for pay and compliance, not the original draft.
Rosta + PayOut, one platform
Build rosters, capture availability, handle swaps and feed approved hours directly into Singapore-compliant pay calculation.
Start free — 14 daysStep 7: Close the loop with pay
A roster is a plan. Pay runs on actuals. The final step is to compare scheduled vs actual hours at the end of the period and feed the actuals into payroll.
This is where roster software pays for itself fastest. Approved scheduled hours, adjusted for actual clock-ins, become pay inputs without any re-typing. OT, PH and rest-day multipliers apply automatically per Singapore rules.
Common mistakes
- Building the roster around managers' favourites. Fair distribution of shifts (and unpopular shifts) matters for retention.
- Ignoring leave applications until they conflict. Lock approved AL into the availability picture first.
- Publishing without checking against weekly hour caps. A worker over 44 hours or under their full-time contract is a problem at pay time.
- Treating Saturday as just another day. Singapore F&B and retail businesses see 30-50% of weekly revenue on Sat-Sun. Build with the peak in mind.
- Last-minute publication. Publishing 48 hours ahead means workers cannot plan and you cannot find cover.