Shift Swap Policy Template

A shift swap policy answers four questions before they become arguments: who may swap, by when, who approves, and who is responsible if it goes wrong. Copy the wording below and adapt the bracketed parts.

The policy (copy and adapt)

1. Who may swap. Staff may swap shifts with colleagues who are trained for the role on the shift, are not on leave, and would not exceed [48] hours that week or break rest-break rules by taking it.

2. How to request. Both people must agree before the request is made. Requests go through [the rota app / to the duty manager] no later than [24 hours] before the earlier of the two shifts.

3. Approval. Swaps are not effective until approved by [the rota owner]. Approval is normally quick, and refusal comes with a reason, most commonly a skills gap, an overtime cost or a rest-rule breach.

4. Responsibility. Once a swap is approved, the incoming person owns the shift completely. A no-show on a swapped shift counts against the person who accepted it, not the person who gave it away.

5. Fairness. Managers keep an eye on swap patterns. Persistent one-way swapping that reshapes someone's contracted pattern gets a conversation, not a quiet drift.

6. Records. All approved swaps are recorded on the published rota, so the rota always shows who is actually expected.

Why each clause exists

Eligibility (1) protects service quality and legal rest rules. The cutoff (2) protects the manager's ability to fix a bad swap. Explicit approval (3) keeps the rota authoritative. The responsibility clause (4) is the one that ends most disputes before they start: everyone knows exactly whose no-show it would be.

Enforcing it without being the swap police

On paper, every clause above is a manager's memory. In Team Pilot, it is configuration: staff propose swaps to eligible colleagues only, cutoffs and approval rules apply themselves, and the rota updates the moment a swap is approved. The scheduling page shows the flow.