Shift Swap Request Form Template
Trade shifts without the group-chat archaeology. One record captures who gives, who takes, and whether the two have agreed yet.
Found someone to trade with? Log it here so the schedule stays current. A swap counts only once your manager approves it.
Shift swaps are the folk economy of every rota-based workplace, and the source of half its scheduling disasters. Two people agree the trade in a group chat at 11pm, the manager never sees it, and on Saturday both believe the other one is opening the store. A swap request form does not stop the trading. It makes the trade legible, so the schedule of record and the schedule in people's heads stay one schedule.
How the fields referee the trade. The form assumes the swap is already negotiated, which is by design. Managers should approve trades, not broker them, so the teammate field carries a placeholder reminding requesters to secure agreement first. Date and start time pin down which shift moves, because "my Tuesday shift" has ruined more rotas than weather. The confirmation question is the load-bearing field, and separating "we agreed" from "still waiting" stops the classic failure where a hopeful half-agreement gets treated as a done deal. The return-shift field records whether this is a one-way give or a true trade, which matters for hour balancing and overtime thresholds. Location routes the request to the right manager when several sites share one link, and the optional context field lets people volunteer the why without an interrogation.
Left to the manager's judgment. Policy quizzes, qualification matrices, and manager-side approval checkboxes all stay off it. Whether the taker is trained for the shift is the approver's call, made against information the form now delivers, and encoding every rule as a question only slows the 95% of swaps that are routine.
Who trades shifts with it. Restaurant and retail managers running rotas across locations, hospital and care-home coordinators where an uncovered shift is a safety issue, warehouses balancing overtime, and volunteer coordinators trading event slots.
The clock sets your triage. Every swap carries two timestamps, when it was filed and when the shift starts, and the distance between them is your triage order. A trade logged ten days out can wait for the weekly schedule pass, while one logged tonight for tomorrow morning's shift needs an answer before anyone goes home. Set a visible cutoff in the intro (24 hours is typical) and make "still waiting to hear back" rows the first thing you chase, because an unconfirmed taker plus a near shift is how a counter ends up unstaffed when the doors open.
Make it fit your sites. Swap the location options for your own sites, or delete the question for a single site. Turn on email notifications so each request lands in the manager's inbox the moment it is filed, or point a signed webhook at the channel where scheduling happens. The responses table becomes the season's swap ledger: export the CSV at review time and you see at a glance who gives shifts, who absorbs them, and which shift nobody wants, which tells you more about staffing than scheduling.
Frequently asked questions
Does submitting the form make the swap official?
It does not. The ending says as much: the original rota stands until the manager confirms with both people. The form is the request and the record, not the approval.
Should both employees fill it in?
One submission from the person giving up the shift is enough, since it names the taker and their confirmation status. Some managers ask the taker to reply to the notification email as their yes.
How does the manager hear about new requests?
Enable email notifications in Settings, or add a webhook to post each request into your scheduling channel in real time.
Can we spot swap patterns over time?
Export responses as CSV, and a quick pivot shows frequent givers, frequent takers, and the shifts that always need trading, which is useful evidence at rota-planning time.