A shift change request form is how a guard asks to swap, drop or move a shift, and how a manager approves or rejects that change on the record. It sounds like a small piece of admin. In practice it is the difference between a roster you can trust and a roster where a post quietly goes uncovered because two people agreed a swap in a WhatsApp message no supervisor ever saw.
Most shift change request form entries fail for the same reason a paper visitor sheet fails: the request is verbal or informal, so there is no record of who agreed to what, and no approval step to confirm the site is still covered. This guide sets out the seven fields every shift change request form should capture, and why a digital request beats a paper slip or a text message.
Why a shift change request form matters
Security rosters are coverage promises. A client pays for a post to be manned from a set time to a set time, and the roster is how you keep that promise. The moment a guard cannot make a shift, that promise is at risk, and the shift change request form is the control that protects it.
A good shift change request form does three things. It captures the request in writing so there is no dispute later about who asked for what. It forces the swap to name a replacement, so a change never leaves a gap. And it routes the request to a manager for approval, so no change goes live until someone accountable has confirmed the post is still covered.
Without a form, changes happen in the gaps: a guard tells a colleague they will cover, the colleague forgets, and the first anyone hears of it is an empty post at 2am. The form exists to stop that conversation ever being informal.
The 7 fields every shift change request form needs
- Requesting employee – the guard asking for the change, so the request is attributable.
- Original shift – the date, time and site or post the guard is currently rostered for.
- Type of change – a swap with a named colleague, a drop, or a move to a different date or time.
- Replacement or cover – who will work the shift instead. A swap request that names no replacement is not a plan, it is a gap.
- Reason – why the change is needed. This lets a manager judge the request and spot patterns, such as one guard repeatedly avoiding night shifts.
- Date submitted – when the request was made, so late requests can be distinguished from those raised with proper notice.
- Manager decision – approved or rejected, by whom, with the date and time. This is the field that turns a request into an authorised change.
Keep the form to these fields and it stays quick to complete, which matters because a form guards will not fill in is no better than no form at all.
Paper shift change slip versus a digital shift change request form
A paper slip or a group chat works right up to the moment it matters. The recurring failures are always the same: a swap agreed verbally that one party forgets, a slip that never reaches the supervisor, a change approved by someone with no authority to approve it, or a request lost so completely that no one can say whether it was ever agreed.
A digital shift change request form captures the same seven fields as structured data and routes it for approval automatically. In AVES, shift change requests are raised by staff and sent to a manager for approval, so a change is only live once it has been authorised, not the moment two guards shake hands on it. Because the request sits against the roster, an approved swap updates the schedule the whole team is working from rather than living in one person’s memory.
The roster it updates is generated and managed in the same system. For how the underlying schedule is built, see the AVES security guard duty roster. For what the guard coming on shift should confirm at handover once a change has gone through, see the shift handover checklist. And because a swap only counts once the replacement actually turns up, geofenced attendance is what confirms the covering guard was on site.
Common shift change request form mistakes
No named replacement. A request to drop a shift without saying who covers it is not a swap, it is a hole in the roster waiting to be found.
Verbal-only agreements. A swap agreed in a corridor or a chat leaves no record. When the post is missed, there is nothing to show what was agreed or by whom.
No approval step. If a change goes live the moment two guards agree, no manager has confirmed the site is still covered or that the replacement is qualified for that post.
Approval by the wrong person. A colleague saying “fine by me” is not authorisation. The decision field must record a manager, not a peer.
Late requests treated the same as planned ones. Without a submission date you cannot tell a request raised a week ahead from one raised an hour before the shift. The reason and date fields let you manage notice periods fairly.
Shift change request form checklist
- The requesting guard and their original shift are named.
- The type of change is clear: swap, drop or move.
- A replacement is named for every swap or drop.
- A reason is recorded.
- The submission date is captured.
- A manager, not a peer, approves or rejects the request.
- The decision, the approver and the date and time are all recorded.
- An approved change updates the roster the whole team works from.
Frequently asked questions
What is a shift change request form?
A shift change request form is a record of a guard’s request to swap, drop or move a rostered shift, capturing the original shift, the replacement, the reason and a manager’s approval. It keeps roster changes authorised and on the record rather than informal.
What should a shift change request form include?
The requesting employee, their original shift, the type of change, the named replacement or cover, the reason, the date submitted and the manager’s decision with the date and time.
What is the difference between a shift swap and a shift change request?
A shift swap is one type of change, where two people exchange shifts. A shift change request is the broader form that also covers dropping a shift or moving it to a different time, each still needing a named replacement and manager approval.
Why does a shift change need manager approval?
Because only a manager can confirm the post is still covered and the replacement is qualified for it. Without an approval step, a change agreed between two guards can leave a site uncovered or manned by someone not cleared for that post.
Can a shift change request be handled digitally?
Yes. A digital shift change request form captures the same fields, routes the request to a manager automatically and updates the shared roster once approved, which removes the verbal agreements and lost slips that paper processes rely on.
Take shift changes off the group chat
If your shift swaps still happen in a group chat, the missed post is only a matter of time. AVES lets a guard raise a shift change request that names the replacement and routes to a manager for approval, so no change goes live until the coverage is confirmed and the roster is updated for everyone.
Book a 30-minute demo and we will show you the actual shift change request and approval screens: Book a demo
Prefer to explore first? Start a free account: Start a free account
Follow AVES on Instagram: Instagram