Practical guide
Write a shift swap request record with a named approver
A shift swap record that names both people, checks coverage and rest, and records one approver with a dated decision.
Published

Table of contents
Capture the trade before it happens
Record the name of the person requesting the swap and the name of the person who will take the shift. Add the date, the start and end time, and the role or location covered. A message that says can you cover me leaves too much open. The record should name both people and the exact shift.
Ask each person to confirm the trade in writing before the schedule changes. Record the date and time of each confirmation. A verbal agreement can be forgotten or misremembered. The written confirmation protects both people if the swap is later questioned.
Note the reason for the request only when the process needs it, and keep the note short. Record whether the reason affects eligibility, such as a rest period or a required certification. A medical detail should go to the appropriate owner, not into a shared schedule note. The record should collect what the decision needs and no more.
Check eligibility and coverage
Check that the person taking the shift is qualified for the work and cleared for the location. Record the certification or training that applies and the date it was last checked. A swap between two people with different roles can create a coverage gap. The check should happen before the approver signs.
Check the rest period and the hours already worked by both people. Record the hours before and after the swap so an overtime or fatigue issue is visible. A swap that looks even on paper can still create a long stretch. The record should show the pattern, not only the single shift.
Confirm that the new schedule does not leave another shift short. Record the coverage for the affected period and the person who confirmed it. A swap that solves one gap can open another. The scheduler should see the whole picture before approval.
Name the approver and the decision
Name the person who can approve the swap and the backup who acts when that person is away. Record the decision, the date, and any condition attached to it. An approval that lives only in chat is hard to produce later. The record should show who decided and when.
State the decision in plain words, such as approved, declined, or approved for one shift only. Record the reason for a decline in one sentence. A clear reason helps the employee correct the request next time. A silent refusal invites the same question again.
Send the decision to both people and to the scheduler in the same message. Record the recipients and the time sent. A decision that reaches one person but not the other can split the schedule. The notice should point to the updated roster.
Close the loop and update the schedule
Update the schedule system and the time record after the approval, and record the time of the change. Check that the old shift no longer shows the original owner. A roster that still lists the wrong person will produce the wrong attendance record. The update is part of the approval, not a separate task.
Confirm on the day of the swapped shift that the right person arrived. Record the confirmation and the person who checked. A swap that is approved but not worked should be flagged the same day. The record should show what actually happened, not only what was planned.
Review swap requests at the end of each month for repeated patterns. Record the number of requests, the share approved, and the shifts most often affected. A cluster on one shift may point to a scheduling problem rather than a personal one. The review should improve the roster, not punish the request.
Sources
References supplied with this guide.
| Source | Publisher | Context |
|---|---|---|
| U.S. Department of Labor, Recordkeeping | dol.gov | Primary reference supplied with this article. |
| National Labor Relations Board, What We Do | nlrb.gov | Primary reference supplied with this article. |
| National Institute of Standards and Technology, Privacy Framework | nist.gov | Primary reference supplied with this article. |