Shift swap policy template
Copy and adapt this policy for your business. Fill in the bracketed fields with your own details. Review with your HR or employment lawyer before finalizing if you have specific compliance requirements.
Shift Swap Policy — [Business Name]
Effective date: [Date]
1. Purpose
[Business Name] allows employees to swap scheduled shifts when doing so does not negatively affect operations, coverage requirements, or labour cost guidelines. This policy sets out how swap requests are submitted and approved.
2. Eligibility
Shift swaps are available to all employees who have completed their [probationary period / first 30 days]. Employees must swap with another employee who holds the same role and has the required certifications or training for the shift.
3. How to request a swap
Employees must submit a swap request at least [48 hours / other timeframe] before the shift they wish to swap. Swap requests submitted less than [48 hours] before the shift may be denied at manager discretion.
Requests must be submitted through [Opyris app / written form / email to manager / other method]. Verbal requests or text messages are not sufficient to initiate a swap.
4. Manager approval required
All shift swaps require manager approval before they take effect. A confirmed agreement between two employees does not constitute an approved swap. The schedule is not updated until the manager approves the request.
Managers aim to respond to swap requests within [24 hours].
5. Coverage responsibility
The employee who originally held the shift remains responsible for coverage until the swap is approved. If the employee taking the shift does not show up, the original employee may be called in.
If a swap is approved and the replacement employee does not show up, the absence is recorded against the replacement employee, not the original.
6. Reasons for denial
A swap request may be denied for any of the following reasons:
- The replacement employee is not qualified for the role
- The swap would result in overtime for either employee
- The replacement employee has an approved absence that affects coverage
- The request was submitted less than [48 hours] before the shift without prior manager approval
- Operational requirements prevent the swap
7. Open shifts
If no eligible employee is available to take a shift and a swap cannot be arranged, the shift may be posted as an open shift and offered to eligible employees. Open shifts are not guaranteed to be filled.
8. Questions
Direct questions about this policy to [Manager name / HR contact / email].
This policy is a template and not legal advice. Adapt it to your specific business, location, and applicable employment legislation. Consult a qualified employment lawyer or HR professional before finalizing.
Why shift swaps need a written policy
Without a policy, swap expectations are communicated inconsistently. One manager approves a text-message swap; another requires a written request. One employee thinks a verbal agreement with a coworker is sufficient; the shift goes uncovered. A written policy sets the same expectation for everyone and removes ambiguity about who is responsible for coverage.
The problem with text-message swaps
When shift swaps happen by text, the manager often doesn't know about them until something goes wrong. The schedule doesn't reflect who is actually working. Coverage gaps are invisible until someone doesn't show up. There's no record of who agreed to what, or whether a manager ever approved it.
How Opyris handles this
In Opyris, swap requests go through a structured workflow. Employees submit through the app. Managers review in a task queue with full context (both employees, the shift, coverage impact). Approved swaps update the schedule immediately. Denied swaps notify the employee. There is no ambiguity about whether a swap was approved.
Shift swap requests. Manager queue. Approved changes.
Opyris moves shift swaps into a structured workflow. No more tracking swap status in a text thread.