Set a clear restaurant shift-swap process before staff trade shifts
Two servers agree to trade next week’s shifts. Check availability, closing and setup duties, coverage and applicable constraints before confirming the schedule.
Two servers have agreed to trade next week’s shifts. Before you change the schedule, check both assignments, confirm each person can do the work and tell them exactly which version to follow.
Keep the process small: one request, one manager decision and one updated schedule. Here’s a practical way to handle it.
Separate a direct trade from an emergency absence
For this process, a direct trade means two employees exchange two existing shifts. Neither shift disappears. That’s different from giving away a shift or asking someone to cover an absence; 7shifts distinguishes these trade types.
Use this process for a planned exchange that both people want. If someone cannot attend work, handle that through your absence process instead. Don’t make finding a swap a condition of reporting an absence.
Get one request and both people’s agreement
Choose one place for requests, such as your manager email inbox. Tell the team which manager reviews them, who covers that manager’s days off and when to raise a planned trade so you have time to check it. Set a review window your venue can actually support, not a promised instant approval.
Ask for:
- Both employees’ names.
- The dates, start and finish times, location and duties of both shifts.
- Who would work each shift after the trade.
- A reply from each person confirming they want the trade and are available for the whole incoming shift.
You need the work details, not private personal reasons. Don’t ask staff to post health information or other sensitive details in a group chat.
Example: next week’s dinner and lunch shifts
Suppose Lee and Sam are two trained servers at a neighborhood restaurant. Lee wants Sam’s Saturday lunch shift, and Sam wants Lee’s Thursday dinner shift. Both say they are available for the full incoming shift.
| Existing shift and duties | Current server | Requested server |
|---|---|---|
| Thursday, 5–10pm: dinner floor service and closing tasks | Lee | Sam |
| Saturday, 11am–4pm: lunch setup and floor service | Sam | Lee |
Keep those times and duties attached to the shifts. The request is to exchange the people, not quietly shorten dinner cover or move lunch setup to someone else.
A request could read:
Lee and Sam would like to exchange next Thursday’s 5–10pm dinner-and-close shift and Saturday’s 11am–4pm lunch-setup-and-service shift. Sam would work Thursday; Lee would work Saturday. We both agree and are available for those full shifts. Please review before changing the schedule.
Review both shifts before deciding
Look at the whole schedule, not just the two boxes being exchanged. Scheduling staff hours and assigning duties belong together in the manager’s review.
Work through these checks:
- Availability: check each person’s existing assignments and time off against the incoming shift. Ask about any conflict rather than guessing from a free square on the grid.
- Role readiness: check the actual duties. In this example, Sam needs to handle Thursday’s close; Lee needs to handle Saturday’s setup as well as floor service. Being a server isn’t enough if one of those tasks is unfamiliar.
- Coverage: review who else is working each service. Can the team still cover the floor and the opening or closing work? If Sam needs help with the close, identify who could provide it without leaving another task uncovered.
- Hours and applicable constraints: have the person responsible for scheduling and pay review the full week and adjacent shifts, including any relevant overtime, rest, notice or agreement requirements. Use the rules for your venue and employees; agreement between two coworkers is not legal clearance.
For an Australian venue, start with Fair Work’s roster guidance and identify the applicable award or agreement before deciding. Don’t use another restaurant’s notice period as your rule.
If a check is unresolved, keep the trade pending or decline it with a clear explanation. For example: “I haven’t confirmed Thursday’s closing cover, so I can’t approve this trade yet.” Don’t mark a shift covered while that question is still open.
Confirm one schedule and who communicates it
If the checks support the trade, the reviewing manager updates the venue’s authoritative schedule. Keep a short record of the request, both replies, the decision and when the schedule changed. Tell the duty managers too, so an old printout doesn’t become a competing instruction.
For Lee and Sam, the confirmation could be:
Trade confirmed: Sam will work next Thursday, 5–10pm, dinner service and close. Lee will work Saturday, 11am–4pm, lunch setup and service. Both assignments are now on the updated weekly schedule in the staff area. Please reply to confirm you’ve seen your new assignment.
Use your actual schedule location and dates when you send it. Acknowledgement confirms receipt; it doesn’t replace the earlier agreement or the manager’s checks. Replace or clearly mark old copies, and follow up directly if either person hasn’t seen the change. Until you confirm a trade, make clear that the requested change is still pending; handle any inability to attend separately.
Start with the schedule you already use
You don’t need a new app to make the decision. Keep the request beside your current paper or digital schedule and update the same record once you’ve decided.
If you want to build a weekly plan first, try CrewCentral’s free schedule maker. You edit it manually in your browser without an account or email, then print it or export CSV. The draft stays in that browser; the tool doesn’t notify employees or provide a shared cloud schedule.
For a team workspace, explore CrewCentral Scheduling. Hiring, onboarding, training and scheduling share team context. Account-based AI roster drafts are separate from the public manual tool, and a manager reviews and adjusts them before publishing. Keep the shift-trade decision with the manager, whichever planning method you use.
