Research note
What share of shift swap requests name an approver and a decision date?
A local method for measuring how often shift swap requests name an approver and a decision date, with separate checks for the trade, the coverage, and the roster update.
Published

Table of contents
Question and scope
The question covers swap requests submitted for shifts in the review window. It includes requests sent through a form, a message, and a paper note where one was used. It excludes informal coverage arranged on the day and shifts that were traded without any record. The review covers one employer, one window, and the roles that use shift work.
A request enters the sample when a record shows two named people and a shift date. If the swap exists only as a conversation, the case enters as an informal trade. Record the source of the request and the date it was sent. A request submitted after the shift should be marked as late.
The stop point is a dated approval with an updated roster, not a message that says it is fine. An approval without a roster change can leave the time record wrong. The roster update should show the new owner and the time of the change. Report requests with an approval but no update separately.
Definitions and evidence standard
Define a complete request before reviewing any case. It should name both employees, the shift, the approver, the decision, and the date of the decision. A note that says swapped does not meet the standard. Record the definition with the case so a later reader applies the same rule.
Use the request form, the schedule export, and the approval message as the primary evidence. A memory of the conversation can add context but cannot replace a dated decision. If only a verbal report exists, mark the case as unverified rather than assigning a date. Report the share of unverified cases with the result.
Separate the request date from the decision date. A request can arrive a month early while the approval waits until the week of the shift. Measure both dates so a slow decision does not look like a late request. The two numbers answer different questions about the process.
Sampling and measurement
Freeze the list of swap requests before reviewing any of them. Include more than one manager, more than one shift pattern, and more than one month. Record the export date and the filter used. Do not remove a request because the approval is missing, since the gaps are part of the finding.
If the list is large, take a random sample and record the selection method. Keep the full count beside the sample so a reader can see the coverage. A replaced case should be reported as a deviation. The sample should be large enough to compare at least two schedules.
Measure the number of requests, the share with a named approver, the share with a dated decision, and the share with a confirmed roster change. Add the median and longest wait between the request and the decision. Report the counts by manager and shift. A single percentage hides which schedule drives the gap.
Findings and interpretation
Present the distribution before suggesting a cause. A cluster of unapproved swaps on one shift may mean the approver is not available during that period. A cluster in one team may mean the request route is unclear. Read the cases behind the largest cluster before naming a reason.
Compare the result with the approval method. A request form that names the approver may produce a faster decision than an open message to a group. Record the method and the first person who saw the request. The comparison can show whether the delay is in the request or the decision.
Check whether late decisions still protected the rest period and whether the roster was corrected before payday. A late approval that fixed the record is different from one that left a wrong entry. Record the date of the correction and the owner. The quality of the delay matters alongside its length.
Limitations
The review measures the presence of an approver and a date, not whether the swap was fair. A well-recorded request can still hide pressure from one employee. The result describes the documentation trail, not the working relationship. Report it beside a short employee check so a reader does not overread the number.
The request process may change during the window, and an older case may follow a rule that was appropriate at the time. Record the process version rather than applying the current rule retroactively. A case that missed an old standard may not be a current defect. Keep the version note with the case file.
A swap that no one recorded is invisible to this method. The count may understate the problem if teams trade shifts by conversation. Pair the review with a comparison of the roster and the attendance record. The answer can reveal a gap the request log cannot show.
Practical next step
Create one swap request form with required fields for both people, the shift, and the approver. Route it to a named approver with a backup. A required field is easier to enforce than a reminder. Tell employees where to find the form before the next schedule is published.
Set a decision target and record the date the target was met or missed. A short target such as two business days gives the approver a clear deadline. Tell both employees and the scheduler when the decision is made. The notice should point to the updated roster.
Test the process for one month and compare the documented share with the baseline. Keep the change if it improves the trail without slowing coverage. If the form or the approval step causes errors, fix that step. The goal is a clear swap, not more paperwork.
Sources
References supplied with this research note.
| 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. |
| U.S. Department of Labor, Training and Development | dol.gov | Primary reference supplied with this article. |