Using the roster: approvals, swaps, and cover
The day-to-day of running a schedule that survives contact with real life.
| You want to... | Do this |
|---|---|
| See who is on this week | The roster in the portal — published, always current |
| Request a shift change | Through your lead; confirmed in writing before it is real |
| Approve time off | Requests arrive with a coverage note attached |
| Report a gap | Urgent ticket — on-call escalation fills it |
| Get a roster export | One ticket; CSV, any date range |
A swap is not a swap until it is confirmed in the system — verbal agreements evaporate. Confirmed changes notify everyone affected automatically.
Every chronic gap gets flagged with a proposal: different hours, more heads, or automation. A schedule that needs weekly heroics is a schedule we redesign.
Related: Booking and rescheduling appointments.
Was this article helpful?