Shift Swap Policy Template

Six clauses that answer who may swap, by when, who approves and whose no-show it is. It is free, it is on this page in full, and it is yours in one click.

Download Plain text Get PDF

No email address, no sign-up, no watermark. Free to use, change and share.

Shift swap policy

Template preview

Adapt the bracketed parts to your own organisation, then put it where staff will actually read it.

Organisation
Applies to
Effective from
Reviewed by

1. Who may swap

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

2. How to request a swap

Both people must agree before the request is made. Requests go through [the rota app / the duty manager] no later than [24 hours] before the earlier of the two shifts. A request made after the cutoff is treated as a request for cover, not a swap.

3. Approval

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

4. Responsibility once approved

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 somebody'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. No swap is agreed by text message alone.

Signed

Approved by [name and role], [date]. Next review [date].

Notes, and they are in the file too

  • Replace every bracketed value before you publish this. A policy with [24 hours] still in it will not be enforced.
  • Clause 4 is the one that ends most disputes before they start, so do not soften it.
  • Put it where staff already look, not in a handbook nobody has opened since induction.
  • Give it a review date. A swap policy written for twelve people does not fit forty.
Download Plain text Get PDF

What is on this page is exactly what is in the file: both are generated from one source, so they cannot drift apart. Last reviewed 7 August 2026.

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. The full wording is above. Copy it, change the bracketed parts, and it is done.

Why each clause exists

Eligibility (1) protects service quality and legal rest rules: a swap that leaves nobody on site who can open up is not a swap, it is a gap. The cutoff (2) protects the manager's ability to fix a bad swap while there is still time. Explicit approval (3) keeps the rota authoritative, which matters more than it sounds, because a rota nobody trusts stops being read. The responsibility clause (4) is the one that ends most disputes before they start: everyone knows exactly whose no-show it would be.

The two things people get wrong

The first is writing a cutoff nobody can meet. If half your swaps happen the night before, a 72-hour cutoff will simply be ignored, and an ignored clause weakens the five around it. Pick a cutoff that matches how your team actually behaves and tighten it later.

The second is approving swaps by text message. A swap that exists only in a WhatsApp thread is not on the rota, which means the person who turns up is not the person the rota expects, and nobody finds out until the shift starts.

Enforcing it without being the swap police

In OtisIO this stops being a document. 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.

A policy is only as good as its enforcement

Every clause here is a rule the rota could be applying for you

On paper, all six clauses are a manager's memory. The failure mode is not a bad policy, it is a good policy that nobody applies at 6am when somebody needs Saturday off.

  • Staff can only propose swaps to colleagues who could actually cover the shift, so clause 1 enforces itself.
  • The cutoff and the approval step are configuration, not vigilance, so a late swap cannot quietly happen.
  • The published rota updates the moment a swap is approved, which is clause 6 with no filing involved.

No card needed. Free forever for up to 10 people at one location, so the template may be the last spreadsheet you need.

More free templates

See the whole library