When worker and supervisor rosters disagree: a playbook

A worker shows a phone screenshot saying day shift. The supervisor’s printout says night shift. Both insist they checked “the roster”. In a roster version disagreement, do not decide by who has the brighter screen, the newer-looking file name or the more senior job title. First establish what each person saw, then find the approved plan and determine whether the current published version needs correcting.

This playbook is operational, not legal advice about notice periods, pay or whether someone must work a disputed shift. Apply your organisation’s safety, consultation and workplace procedures. If a person may be travelling or performing work on conflicting instructions, escalate promptly to the authorised duty contact rather than asking them to guess.

Pause, record and avoid blaming

Ask both people for the project, worker name, date, shift time and where they obtained their information. Note when each reference was accessed or printed. A screenshot may have been accurate when taken and stale now; a printout might predate the last publication. Keep copies in an appropriate internal channel, not a broad group chat containing other workers’ details.

Use a small reconciliation grid:

Reference	What it says	When obtained	What still needs checking
Worker screenshot	Tuesday, day shift	Monday morning	Was this before the replacement publication?
Supervisor paper copy	Tuesday, night shift	Print time unknown	Which source file produced this sheet?
Current project page	Check directly, do not assume	Time checked now	Does it match the approved plan and right worker?

Write down facts before interpretations. “Worker ignored update” is not a fact until there is evidence of a communicated update. Likewise, “the page must be wrong” is only a hypothesis.

Trace the release back to its source

Have the authorised roster owner open the current project publication and the planning workbook used for that release. Check the exact date and person, including similar names; the worker-facing project link supports name search without individual worker logins, so a name alone may not resolve an identity question. Employment numbers belong to the import checks. Ask which CSV or XLSX was uploaded, who reviewed it, when it was published and whether a later edit exists only in the Excel plan.

If available to the administrator, compare the previous project roster in history with the current one. An older publication may explain a saved image; it does not decide which shift was approved or whether a worker was told of a change. A file timestamp also cannot establish that its contents were authorised. Where the source and published view differ, inspect date interpretation, selected rows, skipped identifiers and shift codes before making another release.

Decide what needs correction

There are at least three different outcomes:

• The published version matches the approved plan, but a copy is stale. Identify when the change was authorised and how it was communicated. Give the worker the current project link and use the normal direct-contact process for a material change; do not assume opening the page proves they have accepted it.
• The current publication is wrong. Escalate to the release owner, correct the source workbook, review the revised import and publish a checked replacement. Do not edit a screenshot and distribute it as an official fix.
• Approval itself is unclear. Hold any proposed replacement while the authorised people resolve the plan. Follow site procedures for an immediate safe interim instruction and document who gave it. Publishing one side of the disagreement would make a disputed plan look settled.

Avoid promising that a fresh publication sends SMS, updates offline screenshots or changes payroll. RosterField is a complement to scheduling, not the scheduler, a notification system or a payroll authority.

Close the loop with both people

Tell the worker and supervisor which project period and version to check, what was decided, when the decision applies and whom to contact if the displayed shift is still wrong. Use the organisation’s required direct channels and record the contact in the usual place. Replace labelled paper copies where possible; remind the crew that an undated saved image is not a live reference. If there is a disagreement about contractual obligations, refer it to the appropriate workplace specialist rather than treating a web page as a ruling.

Finally, ask why two references diverged. Was a change made only in Excel? Was an old printout left up? Did the team publish correctly but fail to contact affected people? Fix the handover step that failed before the next shift.

Read roster version control for the release sequence and sharing worker rosters for the link’s privacy implications. The aim is a clear, checked publication and a communication trail people can trust.

Questions people ask

Which roster wins if both copies are dated today?

Neither automatically. Record when each was obtained, check the current project publication and trace it to the approved source and any later authorised change. A print date or screenshot timestamp is evidence of a copy, not proof of approval or of communication to the affected worker.

Does correcting the published page settle the disagreement?

It corrects the online reference after review and publication, but it does not update saved copies or establish that anyone received notice. Tell the worker and supervisor what changed through the required direct channels, resolve any immediate safe-work instruction with the authorised contact and document the outcome.