Published November 16, 2026.
A shift swap is a small transaction with a large effect on trust. When a request is decided before the schedule is posted, people can plan childcare, transport, and rest around a stable answer. When the same request is decided after the schedule goes live, the roster becomes a draft that changes under the team's feet. This review sets out a bounded way to measure what share of shift swaps are approved before the schedule is published. It does not estimate a national rate or claim that a late approval is always worse. The protocol is designed so a single employer can read its own pattern from records it already keeps.
Question and scope
This review asks what share of shift swap requests are approved before the schedule that contains the swap is published. The unit is one swap request involving two employees and one shift. The study records when the request arrived, when it was decided, and when the affected schedule was published. It does not judge whether the swap was a good idea or whether the employees were satisfied.
Set the scope to one employer, one site, and one schedule cycle. Record the length of the cycle and the rule for when a schedule counts as published. If the process changes during the window, keep the original definition for swaps already in progress. Analyze later swaps separately so a process change is not mistaken for an improvement.
Exclude swaps that were withdrawn before a decision, and state the exclusion. Include swaps that were denied, because a denial before publication is still a timely decision. Test the definition on a small set of recent requests before collecting the full sample. A clear unit is what makes the share comparable across cycles.
Definitions that make the measure reproducible
Define a swap request as a written request from one employee to exchange a shift with another named employee. Define the publication point as the date and time the schedule becomes available to the whole team. Define an early decision as one recorded before that point. A decision after publication is late even if it is approved quickly.
Define an approved swap as one where both employees and the manager record agreement. A message from one employee that says a swap is fine is not an approval. Keep the three parties separate in the record so a later reviewer can see who agreed. This matters when a dispute appears after the roster is fixed.
Define a denied swap as a request that received an explicit no or a stated condition that the employees did not meet. Silence is not a denial. Keep a separate category for requests that remain open at the publication point. An open request is late, not approved, and the distinction changes the result.
Evidence standard and data dictionary
For each request, capture the request date, the employees involved, the shift, and the reason category if one is offered. Add the decision date, the decision, and the publication date of the affected schedule. Record whether the decision was written in the same channel as the request. A verbal approval that never reaches the record is difficult to audit.
Record the swap direction and whether the exchange created a rest-period problem. A swap that moves one person from a close directly into an open is not neutral. Add a field for the rest interval that resulted. This detail lets a reader see whether speed came at the expense of a safe schedule.
Add a field for who approved the swap and whether that person was available during the request window. A process that depends on one manager's inbox will look slow when that manager is away. Record the approver role rather than a personal name in any shared summary. The role is enough to reveal a single point of failure.
Sampling and collection
Draw the sample from the swap request log, not from the published schedule. The schedule shows the swaps that succeeded and hides the requests that were denied or ignored. If no log exists, reconstruct one from messages for a defined window and say so. A reconstructed log should note the source of each entry.
Collect requests across at least two full schedule cycles. One cycle may be unusual because of a holiday, a launch, or a weather event. Two cycles give a first view of whether the timing is a habit or an accident. If the volume is very small, describe each request instead of computing a share.
Record the collection date separately from the decision date. Add the time zone used for all timestamps. A publication at the end of a Friday and a decision on the following Monday can look like a two-day delay or a one-day delay depending on the boundary. State the boundary rule and apply it consistently.
Analysis and reporting
Report the number of requests, the share approved before publication, the share denied before publication, and the share decided after publication. Show the counts by site, shift, and approver role. Use the same denominator for every share and list the requests with incomplete dates. A share without a denominator invites a misleading comparison.
Present the median days between request and decision alongside the share decided early. A high early share can still hide a long tail of requests that waited until the deadline. The median shows the typical experience, while the share shows the risk of a late answer. Report both rather than choosing the more flattering number.
Inspect the late decisions without assuming that they were careless. A late request may have arrived after the publication point, which is a different problem from a slow approver. Split late decisions into requests that arrived early and requests that arrived late. The first group points to process capacity, while the second points to communication.
Limits of the evidence
The record cannot show whether an employee avoided requesting a swap because of a past refusal. A low request rate may indicate a healthy match between schedule and life, or it may indicate learned silence. The protocol measures decisions, not the willingness to ask. Report the request rate beside the approval rate so the reader sees both.
A small site may have too few swaps to support a stable share. Describe the cases and the decisions instead of ranking managers. If one approver handles most requests, report that concentration. A general rate would hide a single habit.
The definition of publication varies by employer. A schedule posted on a board and a schedule released in an app may not reach everyone at the same moment. Record the channel and the reach. A swap decided before the app release but after the board posting is genuinely ambiguous, and the record should say so.
Applying the result
Give the finding to the person who owns the schedule and ask for one observable change. The change might be a decision deadline, a named backup approver, or a rule that requests close before the schedule is built. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions in the next cycle.
If most swaps are decided after publication, test a simple earlier deadline for requests. A deadline gives the scheduler a fixed window and gives employees a clear expectation. Pair the deadline with an exception route for emergencies. An exception route without a deadline becomes the normal route.
If most requests arrive late, the problem may be communication rather than capacity. Check whether the team knows when the schedule is built and how to submit a request. A short note at the top of the schedule can move the request window earlier. Measure the arrival time again after the note.
Data Sources and Methodology
The review uses public labor-market, workplace safety, and records-management guidance to bound the definitions and to keep the recommended fields within common practice. The sources below are used as context, not as evidence that any employer follows them in the same way. Each measure is defined from the employer's own swap log, then compared with these public references where a reference is relevant. The citations are listed with the topic they support so a reader can check the boundary without searching an entire site.
- U.S. Bureau of Labor Statistics, Job Openings and Labor Turnover Survey
- U.S. Bureau of Labor Statistics, Employment Projections
- U.S. Department of Labor, Employment Law Guidance
- U.S. Department of Labor, Workplace Safety and Health
- U.S. Equal Employment Opportunity Commission, Recordkeeping Guidance
- Society for Human Resource Management, Onboarding Resources
- Society for Human Resource Management, Turnover and Retention Topics
- National Institute for Occupational Safety and Health, Total Worker Health
- Centers for Disease Control and Prevention, Workplace Health Promotion
- U.S. Office of Personnel Management, Human Capital Framework
- Occupational Safety and Health Administration, Safety Management
- Occupational Safety and Health Administration, Recordkeeping
- CIPD, Turnover and Retention Factsheet
- Harvard Business Review, Onboarding Topic
The method is deliberately descriptive. It does not pool employers or estimate a national rate. A reader who repeats the protocol should use the same definitions, the same observation window, and the same sampling rule, then report the counts beside the shares. Keep that report with the study record so a later reviewer can repeat the comparison.
Sources
- U.S. Bureau of Labor Statistics, Job Openings and Labor Turnover Survey - accessed November 16, 2026.
- U.S. Department of Labor, Employment Law Guidance - accessed November 16, 2026.
- U.S. Equal Employment Opportunity Commission, Recordkeeping Guidance - accessed November 16, 2026.
- Occupational Safety and Health Administration, Recordkeeping - accessed November 16, 2026.
