Roster the floor, not a spreadsheet.
Define your shifts, build the week as a draft, then publish it when it's right.
Draft the week, publish when it's right.
Define each shift once with its type and start and end times, then assign people to dates and set how many you need. Rosters stay in draft until you publish the week, so staff only ever see the version you mean.
Build the roster
/admin/attendance — shifts, draft to publish
Swaps and preferences, handled.
Staff request to swap a shift and it routes for approval before anything changes. They can also set preferred shifts, days they can't work, a weekly cap and minimum rest between shifts, so the roster starts from what actually fits.
Swaps & preferences
shift swaps and staff preferences
See the gap before the shift does.
Each roster date shows assigned against required, flagged when you're short so you can fill it in time. Turn overtime on and approved overtime feeds the payroll run.
Coverage & overtime
coverage-gap alerts, overtime to payroll
Shift & Roster works with what you already run.
Common questions
Can staff see a roster before it's ready?
No. Rosters sit in draft while you build them and only go live when you publish the week, so people see the final version rather than your working copy.
How do shift swaps work?
A staff member requests to swap a shift and it goes for approval. Nothing on the roster changes until the swap is approved.
Does overtime reach payroll?
Yes, once overtime is turned on. Approved overtime feeds the payroll run automatically, so you don't re-enter it. Shift & Roster is part of Time & Attendance.
Get the roster off the whiteboard.
Build the week in draft, publish it, and let coverage and overtime take care of themselves.