A shift swap policy is a short set of written rules for how employees trade shifts and who signs off. The version that works: every request goes through one place, the person taking the shift must be qualified for it, a manager approves before anything is final, and the swap can’t push either person into overtime. A copy-and-paste template is further down.
It’s 4:40 on a Thursday and someone in the group chat writes, “Can anyone take my Saturday?” Two people say yes. A third says she thought she was already covering it. By Friday nobody is sure who is working, and you find out on Saturday morning when the front desk is empty.
Swaps themselves are not the problem. Letting your team trade shifts helps with retention, and most people only ask when something real comes up. The trouble starts when swaps have no rules and live in texts and chats where you can’t see them.
What a shift swap policy actually covers
A good policy answers five questions in writing: who can ask, how they ask, who can take the shift, who approves, and what happens if the person taking the shift doesn’t show up. That’s all. It doesn’t need to read like a legal contract. One page is enough, and a one-page policy is far more likely to be read.
It also helps to separate three things people mix up. A swap is two employees trading shifts. A pickup is someone claiming an open shift nobody was assigned. A cover request is an employee asking anyone at all to take their shift. Decide which of these you allow, because each one raises different questions about hours and approval.
Why group chats make swaps harder
Three things tend to go wrong when swaps happen in a chat.
There is no record. When a swap is agreed in a message thread and you update the schedule later, you are working from memory about who asked for what. That matters more than it sounds, and we’ll get to why in the legal section.
It isn’t fair. The loudest and best-connected employees get their swaps sorted. Quieter people either don’t ask or get missed in the scroll.
Nobody checks hours. The person who says “I’ll take it!” might already be at 38 hours for the week.
The 7 rules every shift swap policy needs
1. One channel only. Pick a single place for swap requests and state that verbal and text agreements don’t count. If the swap isn’t in the system, the original employee is still on the schedule.
2. A notice period. Many employers ask for 24 to 48 hours for routine swaps, with real emergencies going straight to a manager. Choose a number you will actually enforce.
3. Same role, or qualified. A server can’t swap into a kitchen shift, and a trainee can’t take a shift that needs a certification. Match on role, location and any licence the shift requires.
4. Manager approval before it’s final. Until you approve, the original assignment stands. This one line prevents most no-shows.
5. No surprise overtime. Check both people’s weekly hours before approving. If a swap pushes either of them past your overtime threshold, decline it, or approve it on purpose as a cost decision rather than by accident.
6. The new owner owns the shift. Once approved, the person who accepted is responsible for working it. If they don’t turn up, it’s their attendance issue, not the original employee’s.
7. Record who asked. Keep the request, the date and who approved it. It’s dull, and it will save you later.
Overtime and predictive scheduling: the part most policies skip
Two legal points are worth knowing. Neither is complicated.
Overtime. Under US federal rules, non-exempt employees are owed overtime for hours over 40 in a workweek, and it makes no difference who started the swap. If a trade takes someone to 43 hours, those three hours are overtime. The U.S. Department of Labor’s overtime page covers the basics.
Predictive scheduling. Some places, including New York City, Chicago, Seattle, San Francisco and Oregon, have fair workweek rules that require employers to pay a premium when they change a posted schedule at short notice. The exception that matters here is that changes an employee genuinely asked for are generally exempt from that premium. In several of these places, though, you need to be able to show that the employee was the one who asked. A swap a manager arranged, or one typed in later from a verbal agreement, is much harder to defend. That is the practical reason behind rules 1 and 7.
Rules vary by city and state, so check the ones where you operate. This is general information, not legal advice.
Free shift swap policy template
Copy this, replace the brackets and adjust it to your team.
Shift Swap Policy: [Company name] Effective [date]
Purpose. This policy lets employees trade shifts while keeping every shift covered.
How to request. Submit all swap requests through [scheduling app]. Agreements made verbally or by text are not recognised and do not change the schedule.
Notice. Submit requests at least [48 hours] before the shift. Emergency requests go directly to [manager name].
Eligibility. Swaps are allowed only between employees with the same role, location and required certifications.
Approval. A swap is not final until a manager approves it. Until then, the original schedule applies.
Hours. Swaps that cause either employee to exceed [40 hours per week or daily limits] will not be approved unless a manager pre-authorises them.
Responsibility. After approval, the employee who accepted the shift is responsible for working it.
Records. [Company name] keeps a record of each request, including who asked and who approved.
Exceptions. Management may decline a swap that leaves a shift understaffed. Where local scheduling laws apply, we follow them.
How to run swaps in Calendza
If you handle swaps with a spreadsheet and a group chat, the template above still works, but you do all the checking by hand. In Calendza, an employee submits a swap request from the app. You see the shift, the day and the hours, then tap Approve or Decline. Time-off requests sit in the same workspace as the schedule, so you can look at coverage before you decide, and built-in team messaging keeps the “can you cover?” conversation next to the schedule instead of in a separate chat.
You still check weekly hours before approving, so rule 5 stays on your list. If you haven’t set up your team yet, the how it works page walks through it, and the features page shows everything else in the workspace. Weighing up other tools first? We compared Calendza honestly with Deputy and Zoho Shifts.
Mistakes to avoid
Writing a policy nobody can find. Pin it where the schedule lives and mention it at onboarding.
Approving everything to avoid conflict. Consistent rules protect you from claims of favouritism.
Having no cut-off. Without a notice period, changes land minutes before the shift starts.
Forgetting minors. Younger employees have limits on hours and times of day. Check them before approving a swap.
Calling a manager-made change a swap. If you ask someone to cover, it’s a schedule change, and scheduling laws may treat it differently.
Common questions
What is a shift swap?
A shift swap is when two employees trade scheduled shifts with approval from a manager. Each person ends up working the other’s shift, so total coverage stays the same.
Do shift swaps need manager approval?
They should. Until a manager approves, the original schedule should stay in force. Approval lets you check qualifications, hours and coverage before the change is real.
Can a shift swap cause overtime?
Yes. If the swap takes either employee over 40 hours in a workweek, overtime is owed no matter who requested it. Check both people’s weekly totals before approving.
How much notice should employees give?
There is no single legal number for employee-requested swaps in most places. Many employers use 24 to 48 hours for routine requests and allow exceptions for emergencies, as long as the rule is written down and applied the same way for everyone.
Try it with your own team
A written policy gets you most of the way. A schedule where requests, approvals and messages all live in one place gets you the rest. Calendza is in free early access with no credit card, so you can create your workspace and try swaps with your real team.
