The Roster Manager Fortnight Rhythm — Day-by-Day
The Roster Manager Fortnight Rhythm
A typical fortnight as a Roster Manager has a predictable shape. Following this rhythm keeps the build calm and the period stable.
| When | What you're doing | Where in the app |
|---|---|---|
| Days 1–3 of build | Confirm vacancy plan; refresh the Master Roster if anything changed | Vacancy Planning, Master Roster |
| Day 3 | Apply the Master Roster to generate the Living Roster for the upcoming period | Master Roster → Apply |
| Days 3–7 | Fill the remaining gaps (use IRIS first, manual for the few it can't safely fill) | Living Roster |
| Day 7 | Publish the roster | Living Roster → Publish |
| Days 8–14 | Handle changes — swaps, sick calls, open shifts | Living Roster, Shift Deck |
| Throughout | Approve leave requests as they land | Leave Planner |
| End of period | Review fairness, cost, and hours reports | Reports, Fairness, Cost Monitoring |
The two principles that explain almost every screen
- Time-based availability, not fixed patterns. Clinicians declare when they can work; the system picks shifts that fit.
- The roster is built once, then evolves. You don't redraw it from scratch when something changes — you react at the right level (usually Level 5).
Common mistakes
- Re-building the Master Roster every fortnight. That defeats the point — build once, apply each fortnight.
- Fixing Level 5 problems by editing Level 3. A sick day is a Level 5 problem; the Master Roster is your "normal", not today's reality.
- Filling empty cells one-by-one before trying IRIS. IRIS usually fills 70–90% of gaps in seconds and chooses fairer matches than the eye.
Tip: Open the Dashboard → Intelligence Hub every morning for 30 seconds. It surfaces what needs your attention today.