Every team swaps shifts. The only question is whether you know about it. In most restaurants I worked in, swaps happened by text between two servers, and the manager found out when the wrong person walked in at 5pm, or nobody did.
A good swap policy does not make swapping harder. It makes it easy enough that people use the official route instead of the group chat. Below is a policy you can copy, then the reasoning behind each rule, so you can adjust it for your place.
Why a written policy matters
- Coverage: the person picking up the shift has to be trained for it. A new busser cannot cover a bar shift.
- Overtime: a swap that pushes someone to 44 hours costs you four hours at time and a half. See how to calculate overtime for hourly employees.
- Compliance: in cities with predictive scheduling laws, an employee-initiated swap is usually exempt from premium pay, but only if you can show the employee asked for it.
- Fairness: without rules, the same three people get stuck covering everyone else's Saturdays.
The template
Copy this, change the bracketed parts, and give it to every employee with their first schedule.
[Business name] Shift Swap Policy
1. Who can swap. Any employee may offer a shift they are scheduled for to a coworker who is trained for the same role and position.
2. How to request. All swaps must be requested through [the Shiftnest app / the manager on duty]. Swaps arranged by text, social media or in person are not valid until approved.
3. Deadlines. Swap requests must be submitted at least [48 hours] before the shift starts. Requests made later need direct approval from [the general manager] and will only be approved for emergencies.
4. Approval. A manager will approve or decline every swap within [24 hours]. A swap is not final until it is approved, and the original employee remains responsible for the shift until then.
5. Hours limits. Swaps that would put an employee over [40] hours in a workweek, or leave fewer than [10] hours between the end of one shift and the start of the next, will not be approved without manager sign-off.
6. Minors. Employees under 18 may only pick up shifts that comply with legal hour limits for their age.
7. Responsibility after approval. Once approved, the employee who picked up the shift is responsible for working it. A no-show on a swapped shift is treated the same as a no-show on any other shift.
8. Drops and giveaways. An employee may offer a shift to the team without a swap in return. It stays theirs until someone picks it up and a manager approves.
9. Frequency. Employees may swap or drop up to [3] shifts per [month]. More than that will start a conversation about availability, not discipline.
10. Records. All swap requests and approvals are recorded and kept for [three years].
The rules, explained
Use one channel
Rule 2 is the most important rule in the policy. As long as swaps can happen by text, managers will keep getting surprised. The fix is not to ban texting; it is to make the official route faster than the text. If a server can post a shift from their phone in 15 seconds and see who picked it up, they will.
Set a deadline, keep an emergency route
A 48-hour cutoff gives you time to check coverage and hours. But people get sick and kids get sick. Keep a defined emergency path (rule 3) so that a genuine emergency never turns into a no-show.
Approve fast
If approvals take two days, staff go back to texting. Commit to 24 hours and keep it. Most swap tools let you auto-approve simple like-for-like swaps between people in the same role who stay under 40 hours, which handles about 70% of requests with no manager involved.
Cap frequency without punishing it
Someone swapping five shifts a month is telling you their availability has changed. Rule 9 is a prompt to update their availability, not a warning. Swaps are often an early sign that someone is about to quit, which is why we cover them in how to reduce employee turnover in restaurants.
Swap, drop or cover: the differences
| Type | What happens | Manager approval | Effect on hours |
|---|---|---|---|
| Swap | Two people trade shifts | Yes | Both stay roughly the same |
| Drop (giveaway) | One person gives a shift away | Yes | Giver loses hours, taker gains |
| Cover / pickup | Manager posts an open shift | Yes, or first-come auto-approve | Taker gains hours |
| Call-out | Employee cannot work at short notice | Not a swap; follow the attendance policy | Manager finds cover |
What a month of swaps looks like
Here is a real-shaped month from a 28-person restaurant after it moved swaps into an app with the policy above:
| Metric | Before (by text) | After (in app) |
|---|---|---|
| Swaps per month | Unknown, estimated 30 to 40 | 37 |
| Swaps the manager knew about | About half | All 37 |
| Auto-approved (same role, no overtime) | 0 | 26 |
| Swaps that created overtime | 4 to 6 | 0 |
| No-shows on swapped shifts | 3 | 0 |
The number of swaps did not go down. The surprises did.
FAQ
Should employees be allowed to swap shifts?
Yes. Banning swaps does not stop them; it just pushes them out of sight. Allowing swaps with clear rules gives staff flexibility, which helps retention, and gives you control over coverage and cost.
Who is responsible for a swapped shift?
The original employee until a manager approves the swap, then the employee who picked it up.
Do shift swaps count toward overtime?
Yes. Hours worked are hours worked, regardless of how the shift was assigned. Check weekly totals before approving.
Make swaps easy and visible
In Shiftnest, staff offer and pick up shifts from their phones, the app only shows the shift to people trained for the role, and it blocks swaps that would cause overtime or a clopen before they reach you. Simple swaps can auto-approve. See how shift swaps work.
