A changed crew shift needs a new confirmation

A confirmed shift describes a particular date, time, location and role. Changing one of those details can invalidate the person's original answer, even if the record still has a green confirmed label.

A practical sequence

1. Track the version of the shift the person accepted.
2. Show the old and new details in a change request.
3. Check overlaps, travel and availability again.
4. Resolve missing or declined reconfirmations before relying on the assignment.

Work through an example

A setup shift moves from 10:00 to 08:00. The crew member may have accepted the original time around another commitment. The team requests a fresh answer and keeps the gap visible until someone confirms the revised call.

Where judgement matters

An email delivered successfully does not establish availability. Treat delivery, acknowledgement and acceptance as separate signals. Give the person a clear way to explain a conflict rather than requiring a yes or silence.

Make it usable

Open the working tool and work through the decision with your own inputs. Adapt the structured template to preserve the choices and responsibilities. Keep an original copy so later changes remain understandable.

Work the decision

A practice case

An original fictional scenario. Numbers are illustrative inputs; this is not a customer result or a provider performance claim.

A crew member accepted a 12:00–18:00 shift. The setup moves to 10:00, creating an overlap with another job they already accepted. A new call sheet is useful information, but it is not a renewed acceptance. Treat the changed interval as a fresh availability and confirmation decision. Show the old confirmation as history and the new request as pending so dispatchers cannot mistake one for the other during a busy morning.

Three decisions and why each matters

Decision	Why it matters
Check conflicts across the whole interval.	Travel and setup may create a collision even when the two event start times differ.
Request reconfirmation after a material change.	The original acceptance referred to different hours and may no longer be workable.
Keep time and operational pay records separate from payroll filing.	A useful hours ledger should not imply that statutory payroll obligations have been completed.

Make one usable artifact

Create a revised shift brief with old hours, new hours, role, reporting point, conflict result and reconfirmation status. Name a replacement owner if declined.

Then test the difficult case

The crew member declines the earlier start. Preserve the response and find a replacement instead of marking the revised shift accepted on their behalf.

Use the linked tool or structured template below to record the result. Confirm it against the actual people, agreements and permissions before using it for an event.