See an example, start to finish.
A walkthrough built entirely on a synthetic roster for six fictional people over one week. It isn't customer data, and nothing here is uploaded or saved.
One row per shift.
An excerpt of the synthetic roster. After you upload it, RosterWise shows a preview like this and asks about anything it can’t read, before it checks a single shift.
| Row | worker_ref → Worker | start → Shift start | end → Shift end | role → Role |
|---|---|---|---|---|
| 13 | W-03 | Wed 5 Mar, 15:00 | Wed 5 Mar, 23:00 | Supervisor |
| 14 | W-03 | Thu 6 Mar, 15:00 | Thu 6 Mar, 23:00 | Supervisor |
| 15 | W-03 | Fri 7 Mar, 07:00 | Fri 7 Mar, 15:00 | Supervisor |
| 21 | W-06 | Mon 3 Mar, 09:00 | Mon 3 Mar, 17:00 | Team member |
What needs attention first, and why.
Schedule review
- OK
- Watch
- Review
- Limited data
| Mon | Tue | Wed | Thu | Fri | Sat | Sun | |
|---|---|---|---|---|---|---|---|
| Worker 01 · Lates | OK | OK | Off | OK | OK | Watch | Off |
| Worker 02 · Earlies | OK | OK | OK | Off | Off | OK | OK |
| Worker 03 · Mixed | OK | Watch | OK | Review | Review | Off | Off |
| Worker 04 · Nights | Off | OK | Watch | Watch | Off | Off | OK |
| Worker 05 · Lates | OK | OK | OK | OK | Watch | Watch | Off |
| Worker 06 · New starter | Limited | Limited | Off | Limited | Limited | Off | Limited |
Each flagged shift shows the reason.
Three findings from the example, and a decision a manager recorded.
Worker 03, Thursday into Friday. A 23:00 finish followed by an 07:00 start leaves 8 hours between shifts. Rule: Working Time · 11h daily rest. Evidence: the Thursday and Friday shifts in the upload.
Worker 04, Wednesday and Thursday. Both shifts run through the night, so each is flagged under the night-work rule. Rule: Working Time · night work. Evidence: the Wednesday and Thursday shifts in the upload.
Worker 06, every supplied shift. No earlier shifts were supplied, so rest and consecutive-day checks stay Limited data rather than being assumed fine. Adding a few weeks of earlier shifts would let them run.
Worker 03, Friday. Suggested change: reassign Friday's 07:00 shift to Worker 02, who is off on Thursday and already works at this site. A reviewer applied it, with the reason "Cover confirmed by Worker 02".
Example data Rows, rules and decisions shown are synthetic and for illustration.
Talk it through, then decide.
Each finding shows the shifts behind it, so you can talk it through with the people on the rota. Questions a manager and Worker 03 might discuss:
Example questions to discuss
- Worker 03 finishes at 23:00 on Thursday and starts again at 07:00 on Friday. That leaves 8 hours between shifts, under the 11-hour daily rest reference. Could Friday's start be later, or Thursday's shift end earlier?
- Wednesday and Thursday are both late shifts finishing at 23:00, followed by an early start on Friday. Is a run of lates into an early a regular part of the rota?
The findings describe the shift pattern only. RosterWise can't know how anyone slept or feels, and it isn't a medical or fitness assessment.
Staffing against trading, before you change it.
With sales data added, the same roster can be read against demand. This staffing-level scenario removes one worker from the quiet 07:00 to 11:00 period and compares the result with what was observed.
- Sales per labour hour is shown for every observed period; the strongest is highlighted
- The cost shown is allocated labour cost at an example rate, not a cash saving
- A scenario is a model and claims no saving
Hourly sales against staff on shift, for illustration; in the app, trading periods are grouped into two-hour slots. The shaded hours are the quiet morning. The dashed line models one fewer worker in that period.
- Sales
- On shift (observed)
- Scenario (modelled)
- Sales per labour hour, 07:00 to 11:00
- £95 → £120observed → modelled
- Paid hours
- 60 → 56one worker, four hours
- Allocated cost of those hours
- £50example rate; not a cash saving
The £50 becomes a saving only if you actually remove the hours. Workforce and service checks are shown with every scenario; where data is missing, a service check shows as unknown rather than OK.
Ready to see it on your own roster?
Tell us about your sites and the data you have, and we'll agree the right plan with you. This example is synthetic; analysing your own rosters starts once your plan is in place.