Employee Shift Swap Request Form: Approval Log and Hours Check

An employee shift swap form is most useful before a schedule change takes effect. A text message saying "Sam can cover" leaves unanswered questions: which shift, who approved it, whether the replacement has the necessary skills, and how the change affects weekly hours. A small service business needs a lightweight approval trail without turning every change into a paperwork project.

This guide gives you an Excel-friendly request and decision log, plus a fully fictional weekly-hours example. It is about change approval and communication, not calculating payroll or replacing accurate time records.

Distinguish a swap from a shift pickup

In a shift swap, two employees exchange assigned shifts. In a shift pickup, one employee takes another person's shift without receiving one in return. Both can affect coverage, total planned hours, and overtime exposure. The request should identify the change type instead of using "swap" for everything.

Start with a published schedule as the baseline. For example, see VectoraWork's employee shift scheduling example. Its task is to assign service windows. The process here documents the request, review, and revision of that existing plan.

A request is not approval. The original assignment stays in force until the authorized manager decides otherwise and the affected employees receive the updated schedule.

What a useful request form must capture

For each request, record a unique ID; request timestamp; original employee; replacement employee; site; start and end dates and times; whether it is an exchange or pickup; any offered return shift; reason category if appropriate; employee confirmations; manager decision; effective time; and a link to the revised schedule version.

Use employee IDs rather than embedding private phone numbers in a broadly shared spreadsheet. Do not collect sensitive medical information to justify a shift change. A neutral reason such as "availability conflict" is sufficient for this operational log, unless another lawful process requires different information.

Provide a manager review area with eligibility, site training, overlapping assignments, required rest or meal coverage, worker availability, and weekly-hour impact. Keep those checks separate from the final Approved, Declined, or More information needed status. Approval should identify who made the decision and when.

Fictional example: Lakeside Support Services

Lakeside Support Services is an invented US field-service company. Its example workweek runs Monday through Sunday. Three workers have these planned paid-hour totals before a request: Avery 34 hours, Jordan 37 hours, and Sam 28 hours. These are not records of actual hours worked.

Avery requests that Jordan pick up a six-hour Wednesday shift. That would reduce Avery's plan to 28 hours and increase Jordan's to 43 hours if no other changes are made. A manager should flag the potential overtime and coverage implications. The flag does not by itself decide what someone must be paid or whether a particular worker is eligible for overtime.

The company instead considers Sam for that six-hour shift. If Sam is available, qualified, and approved, Avery would have 28 planned hours, Jordan would remain at 37, and Sam would increase to 34. All three new totals can be reconciled: 28 + 37 + 34 = 99, equal to the original 34 + 37 + 28 = 99. The team has moved the assignment without changing the total scheduled workload.

This is a pickup, not a two-way exchange. A manager must still verify that one person is not booked at two sites at the same time and that the required shift is covered during breaks.

Excel layout for a shift-change request log

Create a sheet named Requests. Keep one row per proposal, even if the proposal is declined. Suggested columns:

• A Request ID; B Submitted at; C Change type.
• D Original employee ID; E Proposed employee ID; F Shift start; G Shift end.
• H Planned paid shift hours; I Original employee hours before.
• J Replacement hours before; K Original hours after.
• L Replacement hours after; M Hour review flag.
• N Qualification checked; O Overlap checked; P Decision.
• Q Reviewer; R Decision timestamp; S Schedule version; T Notes.

Use real Excel dates and times in F and G. For a cross-midnight shift, record a complete end date and time rather than guessing whether 02:00 belongs to today or tomorrow. The scheduled paid hours in H should come from a validated scheduling formula and the applicable break assumptions, not an assumed eight hours for every row.

For a pickup request, put these formulas in row 2:

• K2: =IF(OR(H2="",I2=""),"",I2-H2).
• L2: =IF(OR(H2="",J2=""),"",J2+H2).
• M2: =IF(OR(K2="",L2=""),"Review inputs",IF(L2>40,"Review planned workweek hours","Check other rules")).

In the fictional first proposal, H2 is 6, I2 is 34, J2 is 37. The result is Avery 28, Jordan 43, with a review flag. In the alternative proposal, J2 is 28 for Sam and the result is 34, with no over-40 flag. Record the two proposals as separate rows, never overwrite the rejected option.

This formula is only a simple US federal planning prompt. It is not a complete overtime determination and should not automatically approve or reject a shift. Exempt status, actual compensable work, state rules, and the employer's defined workweek may matter. For true exchanges, both outgoing shifts must be separately subtracted and added; the pickup formula above is not suitable without modification.

Why weekly hours need a separate payroll check

The US Department of Labor's overtime guidance explains that covered, nonexempt employees generally receive overtime for work over 40 hours in a fixed workweek, subject to applicable law. The workweek does not have to match the calendar week. Do not average two workweeks to make an overage disappear.

A swap form captures planned work, not time actually worked. The DOL's recordkeeping requirements call for accurate daily and weekly work-hour records for covered, nonexempt workers. A manager must ensure that actual work time, not just the approved plan, reaches the timekeeping process. VectoraWork's timecard correction guide discusses a separate audit trail for correcting actual hour records.

Prevent overlapping assignments and silent changes

A valid swap needs more than the right total. Compare start/end intervals against the replacement's other assignments, travel between sites, required qualifications, and access permissions. A worker scheduled from 4:00 to 8:00 p.m. at Site A cannot automatically cover a 5:00 p.m. start at Site B.

For multiple approvers, designate who has final authority. The approved request should point to a new schedule revision. Both affected employees and the site supervisor should receive confirmation through the agreed communication channel. If confirmation is pending, show the shift as requiring action rather than silently marking it covered.

Record declined requests without displaying detailed personal explanations to the entire team. Limit access to the data needed for staffing. Store a revision history and back up exported records if your scheduling app works offline. A local browser file is not a shared, synchronized workforce system unless the product actually provides that feature.

Check what happens to the original assignment

After approval, verify that the original employee has been removed from the affected shift and the new worker has been added exactly once. The old and new schedule versions should reconcile to the same required service windows unless the authorized scope also changed.

For the Lakeside example, the six-hour Wednesday window remains assigned to one qualified person. The overall planned hours stay at 99. This tells the manager that the hours moved; it does not prove the employee accepted the assignment or that the time was actually worked.

A useful weekly audit asks: Are any shifts still assigned to people who were replaced? Are any requests approved but not reflected in the live schedule? Are any assignments double-booked? Is there a record of who notified the customer or site manager where relevant?

Frequently asked questions

Does an employee-to-employee agreement make a swap official?

Not necessarily. The business should define who approves schedule changes and how workers receive the final decision. Employee agreement is important but does not by itself establish that the employer has updated its coverage plan.

Should a request be deleted after it is declined?

Keep a limited audit record according to the organization's retention and privacy policy. A history helps managers explain why a schedule changed and prevents the same proposal from being mistaken for an active assignment.

Does the over-40 flag calculate overtime pay?

No. It checks proposed scheduled hours against a basic threshold. Actual compensable hours, the defined workweek, worker classification, and applicable state and local law require independent review.

Is a shift swap the same as a PTO request?

No. A shift change assigns work to someone else; a leave request addresses time off under an employer policy and applicable rules. They may interact, but they should not share one unexplained status field.

Practical takeaway

Use a shift-change log to record who requested the change, which exact shift is affected, who will cover it, what it does to planned hours, and who approved the final revision. The fictional six-hour pickup moves Avery from 34 to 28 hours and Sam from 28 to 34 without changing the 99-hour team total. Approval, communication, and accurate actual-hour records remain separate controls.

Editorial disclosure: Lakeside Support Services, all employee names, weekly hours, and shift-change scenarios are fictional. This is workflow education, not employment-law or payroll advice.