Rehearse a last-minute roster handover before sharing

At 16:40, the day before a planned night shift, a supervisor learns that one worker cannot attend. Someone edits the Excel roster and sends a screenshot to the group chat. Is that a handover, or the beginning of three different versions? This fictional roster handover rehearsal helps a team practise the decisions between an edit and a worker checking tomorrow’s shift.

Run it with a roster administrator, a site supervisor and someone responsible for contacting affected workers. Use invented names and dates, not a live roster. The point is not to make the fastest possible upload; it is to discover which decision nobody owns.

Set the scene

The fictional Harbour Works project has a published roster for 5–11 October. Alex Chen is listed for Tuesday night, 18:00–06:00. At 16:40 on Monday, Alex reports they cannot attend. The supervisor proposes Samira Vale instead. Samira appears elsewhere in the workbook for Wednesday day shift. The crew also includes another worker named Samira at a different contractor.

Hand the group these three facts on separate notes: the original workbook is in a shared project folder; the supervisor has sent a proposed replacement by message; and one worker has saved a screenshot of the currently published roster. Do not assume the proposed change is authorised or that Samira has accepted it.

Walk through four decision points

1. Who may change the source? Have the administrator locate the approved workbook and the right project period. They should not overwrite a cell based solely on an ambiguous message. Ask the supervisor to confirm which Samira, which employer, which shift and whether the Wednesday assignment is affected. Check the appropriate approval and availability processes outside the publishing tool. Note the file name and who authorised the edit.

2. What should the review show? In the rehearsal, imagine exporting the revised CSV or XLSX from the existing Excel plan. Compare Alex’s Tuesday and Samira’s Tuesday and Wednesday against the intended plan, plus a few unchanged workers as controls. Check dates, employment numbers and any shift labels that may have changed. If the workbook uses formulas, verify saved results. An import preview needs to represent the approved change; a successful file upload alone is not approval.

3. Who releases a replacement? Name a release owner. Ask them to state out loud what differs from the last publication, what remains unchanged and whether any blocker or uncertain row remains. Only then would the administrator publish the reviewed replacement as the current project version. If the proposed cover is still unresolved, stop rather than publishing a guess to meet a deadline.

4. Who tells the people? List Alex, the correctly identified Samira, the night supervisor and anyone whose Wednesday cover changes. Decide who will contact each person using the organisation’s normal urgent-change procedure, when and how the contact is confirmed. A new published page does not send automatic SMS or prove that a person saw the update. The previously saved screenshot will not update itself.

Run a two-minute worker-view check

Have a participant play a worker with only the project link or QR code. They should search by name and find the intended current assignment, without an individual worker login. When two people share a name, verify the right result rather than assuming name search identifies a person uniquely. Someone with the link may share it; avoid including private planning notes just because this is a rehearsal.

Now introduce a final twist: at 17:05 the supervisor changes the cover worker again. Ask the group to repeat the approval, workbook edit, import review, publication and direct-contact steps. The previous approval and preview cannot silently transfer to a different person. A worker who saw the page at 16:55 may hold different information; identify who will resolve that conflict.

Debrief with a handover card

Capture one line for each item: source workbook location; change owner; approval owner; three control rows to check; publication owner; direct-contact owner; and where to record unresolved questions. Keep the card in your ordinary handover process. It should be short enough to use on a busy evening and explicit enough for the next shift to follow.

RosterField fits after scheduling: use the existing Excel plan, review its CSV/XLSX import and publish a checked project version rather than treating a screenshot as a release. For the import checks, see the Excel upload checklist. For what remains of older versions and offline copies, see roster version control. A rehearsal succeeds when the team can explain who makes each decision, not when it clicks through screens quickly.

Questions people ask

Should we publish a real roster during the rehearsal?

No. Keep the scenario fictional and talk through the decisions on paper or with a non-publishing demonstration. If you later apply the lessons to a real change, follow the actual project approval, import review and release process. A practice run should not create a confusing extra worker-facing version.

What if nobody can confirm the cover worker before handover?

Leave the proposed replacement unresolved. Identify the authorised person who can give immediate site instructions, and follow the organisation’s escalation and direct-contact procedure. Record the open decision for the next shift. Do not make a speculative spreadsheet edit appear approved by publishing it.