The shift swap app rules a trade has to pass.
A shift swap app has one hard job: let two people trade a shift without the manager finding out on Friday that nobody is opening on Saturday. That means checking the trade before it goes through, not after. Who is allowed to take the shift, whether it tips anyone over 40 hours, whether the rest rule holds, and whether a manager has to sign off. It is the corner of employee management apps most often left to a group chat, and the group chat is exactly where trades go wrong.
This page is about what that check consists of: the eligibility rules, the approval step, the difference between a swap, a drop and an open shift, and the record a trade has to leave behind in the places where labor law now asks for one.
See what a swap app has to checkThe short version
Four checks, one approval, and a record nobody gets to overwrite.
Before a shift swap app lets a trade complete, it confirms that the coworker holds the role and location the shift requires, that they are not already on the roster at that time, that the extra hours do not push them past 40 in the workweek, and that the gap to their last shift meets your rest rule. Then someone with authority approves, or the app approves within limits you set, and the trade is written down: who asked, who accepted, who approved, and when. In New York City fast food and Oregon retail, that record is the difference between a free, employee-initiated swap and a schedule change the employer pays a premium for.
The eligibility rules
What a shift swap app checks before the trade goes through.
Every scheduling tool with a trade feature runs the same short list, and so should anything you build. The list is short because a shift is a small object: a date, a start and end time, a role, a location, and a person. The checks split into three kinds, and the kind decides what the app does when one fails.
Hard rules: the shift should never be offered
- Role or qualification. The coworker holds the position the shift needs: bartender, registered nurse, forklift certified. Where a licence matters, check the expiry date on file, not just the job title.
- Location. They work at, or are cleared for, that site. A cross-site swap is a different transaction with two managers in it.
- Availability. They are not already scheduled at an overlapping time, and they have not marked that time unavailable.
- Status. Active, not on leave, and old enough for the hours involved. Minor work-hour limits vary by state, and the app can only enforce them if the birthdate is on file.
Soft rules: legal, but somebody should decide
Overtime is the one that never goes away. Under the Fair Labor Standards Act, non-exempt employees must be paid at least one and a half times their regular rate for hours over 40 in a workweek, the workweek is a fixed and recurring 168 hours, and averaging hours across two weeks is not permitted, per the US Department of Labor. So a swap that looks even on paper can still cost money if the two shifts sit in different workweeks, or if the person taking the shift already picked one up on Tuesday. The app needs the taker's projected hours for that workweek at the moment they accept, and the projection is only as good as the punches feeding it, which is the job of a time clock app for employees, not the swap app.
Rest between shifts is the second soft rule. Some cities set it in law: New York City's fast food rules bar a closing shift followed by an opening shift with less than 11 hours between them unless the worker consents in writing and is paid a $100 premium. Most employers set their own gap even where no law does. And pay rate is the quiet third: if the coworker earns a different rate, the shift now costs a different amount. Not a legal problem, a budget one, but the manager approving the trade should see it.
The flag that decides everything else: who asked
A trade two employees arrange between themselves and a reassignment a manager arranges look identical on the roster. In the growing list of places with predictive scheduling laws, they are treated completely differently: the first is free, the second can owe the employee premium pay. The app has to know which one happened, and it has to be told honestly. The law section below has the specifics.
Try it
Should this trade go through?
Tick each check the proposed trade passes. Anything left unticked counts as not confirmed, which is how the app should treat it too.
What the app should do
Tick the checks above to see whether the trade should be offered, approved, or sent to a manager.
The workflow
How a shift swap app works, step by step.
Five steps in a fixed order. The order matters more than the screens: a trade that can skip a step is a trade that will, eventually, skip the one that mattered.
- 1
Request
The employee opens the shift and chooses swap, drop or release, with an optional note. The shift is still theirs to work until someone takes it.
- 2
Offer
The app lists only eligible coworkers: right role, right location, free at that time. Everyone else never sees the offer.
- 3
Accept
A coworker accepts. For a swap they pick which of their shifts goes the other way. First acceptance wins and the others are told it is gone.
- 4
Approve
A manager confirms, or the app approves a trade that passes the overtime and rest checks on its own. A denial returns the shift with a reason.
- 5
Publish
The roster updates, both employees get the new schedule, and the trade record is written and locked.
Swap, drop, or release: three different transactions
A shift trade app that treats these as one button will get the overtime check wrong on the second one and the paperwork wrong on the third. They move different things and need different people to agree.
| Type | What moves | Who has to agree | Effect on hours | What to watch |
|---|---|---|---|---|
| Swap | Two shifts change owners | Both employees, then the manager | Roughly even for both people, as long as the two shifts fall in the same workweek | The rest gap between the new shift and each person's neighbouring shifts |
| Drop (cover, giveaway) | One shift changes owner | Requester and taker, then the manager | The taker gains hours, the requester loses them | Overtime for the taker. This is the trade that crosses 40 hours |
| Release to open shifts | The shift goes back into the pool | Requester, then whoever claims it, then the manager | The requester loses hours, the claimant gains them | Who posted it. Under New York City's fast food rules, an open shift the employer posted is not a voluntary trade |
Approval before the offer, or after the acceptance?
There are two common orders and they are not interchangeable. Approval-first sends the request to a manager before any coworker sees it. When I Work works this way by default: its help centre describes a request sitting in a Pending Approval state, then moving to Pending Acceptance once a manager has signed off, with eligible coworkers filtered by position and location. The manager approves the intention without knowing who will take the shift, so the overtime check has to run again at acceptance, or the approval is meaningless.
Acceptance-first lets eligible coworkers agree between themselves, then puts the specific pair in front of the manager with both people's projected hours. The manager sees the real trade, at the cost of employees waiting longer to know whether it is on. For most teams this is the better default, with the hard rules filtering the offer list automatically and auto-approval switched on only for trades that pass the soft rules too.
One rule to copy whichever order you pick: the shift never becomes nobody's. Until a coworker has accepted and the trade is approved, it is still the requester's shift to work, and the app should say so on their screen.
Why "who asked" matters
What labor law actually says about swapping shifts.
For most private employers, no federal rule requires a manager to approve a swap or a record to be kept of one. The obligations come from two directions: overtime, which applies everywhere, and predictive scheduling laws, which apply to covered employers in a growing list of cities and states and which care a great deal about who initiated a change.
Public agencies: the one federal rule written for trading time
Police, fire and other public agency employees have a rule of their own, 29 CFR 553.31, which implements section 7(p)(3) of the FLSA. Two employees of the same agency may substitute for one another at their own option, the agreement must be approved by the agency, and each is credited as if they had worked their normal schedule, so the substitute's hours do not count toward overtime. The agency is not required to keep a record of the substitute hours, and the decision has to be made, in the rule's words, "without fear of reprisal or promise of reward by the employer" and "exclusively for the employee's own convenience." That is the whole shape of a lawful swap in one paragraph: voluntary, approved, and the schedule of record stays intact.
Oregon: an employee-initiated swap is free, and the employer may not arrange it
Oregon's predictive scheduling law covers retail, hospitality and food service employers with 500 or more employees worldwide, requires written schedules 14 calendar days ahead, and pays employees extra when the employer changes a posted schedule. The exception at ORS 653.455(3)(b) is written for this exact app: no extra pay is owed when "an employee mutually agrees with another employee to employee-initiated work shift swaps or coverage." The employer "may require that work shift swaps or coverage under this paragraph be preapproved," and its help has to stop at "helping an employee identify other employees who may be available," because the exception "may not include the employer arranging the work shift swap or coverage." A swap app with a coworker-facing offer list and a manager approval step fits that sentence; a manager reassigning the shift in the same app does not. The Oregon Bureau of Labor and Industries summarises the law and lists the statute.
New York City: the documentation has to show the employee initiated it
New York City's Fair Workweek Law for fast food workers goes furthest on paperwork. The Department of Consumer and Worker Protection's Fair Workweek FAQ for fast food employers (dated September 15, 2023) says employers owe premiums of $10 to $75 for each change made to a schedule with less than 14 days' notice, and that no premium is owed "when employees voluntarily trade shifts with one another," including when one employee drops a shift in the scheduling application and another picks it up. It also lists what is not a voluntary trade: when a "manager asks an employee to fill in for, or trade a shift with, another employee," and when an employee picks up an open shift that the employer posted.
The record requirements read like a data model. To claim the exception, the employer must keep documentation with "enough information to show the date of the shift and that the employee initiated or requested the change." Where two employees agree offline, the manager "must change the work schedule and also record in writing that the reason is a voluntary trade and identify the shifts and the employees who traded." Software used to capture consent "must record the date and time of transmission." Records must be kept for three years, exportable to a nonproprietary, machine-readable format, and a scheduling application must retain, not overwrite, the original version of a schedule when it is updated. And employers "may not ask employees to sign documentation that falsely describes these types of changes as employee requests."
Other cities and states with predictive scheduling laws have their own thresholds and exceptions. If you run locations in more than one, the swap app needs the rule set per location, not one global toggle.
The record
What a completed swap should leave behind.
Take the New York City list as the floor even if you are nowhere near New York City, because it is also what a manager needs when an employee says "I never agreed to that" three weeks later. Every trade the app completes should store:
- A trade ID that never gets reused
- The original shift: date, start, end, role, location, and who owned it
- For a swap, the second shift going the other way
- Whether it was a swap, a drop, or a release to the open pool
- Who initiated the request, with the date and time they did
- Who was offered the shift, and who accepted, with a timestamp
- Who approved or denied it, when, and any note they left
- The taker's projected hours for that workweek at the moment of approval
- The schedule before and after, both kept, neither overwritten
The last item is the one spreadsheets and chat threads cannot do. Editing the cell destroys the evidence that there was ever a different schedule. A swap app should append a new version of the roster and keep the old one, so the answer to "what did the schedule say when it was posted" is always on file. If a manager does step in and reassign a shift, the app should record that as what it is, a manager change, with its own reason code, rather than dressing it up as a swap.
Picking an approach
Shift trade apps: free, paid, or your own.
None of the checks above need an expensive tool, but the free options fail at least one of them by design, and the paid ones run the vendor's rules rather than yours.
| Approach | Eligibility check | Approval step | Record that survives | Cost |
|---|---|---|---|---|
| Group chat | No | Whoever reads it first | No | Free |
| Shared spreadsheet | Manual | Whoever edits the cell | No | Free |
| Scheduling suite with trades | Yes | A setting, usually on by default | Yes | Homebase: from $30 per location a month on Essentials; the free Basic tier has no trades (September 2026) |
| Custom-built shift swap app | Your rules | Your chain, with as many steps as the job needs | Yes | Build cost plus hosting |
Homebase pricing checked on 20 September 2026 with monthly billing selected, on its pricing page. Basic is $0 for one location and up to 10 employees; the row "allow employees to trade, cover and claim open shifts" starts on Essentials at $30 per location a month.
For most small teams a scheduling suite is the right answer, and the trade feature costs less than one covered shift a month. The reason teams end up building their own shift swap app for employees is not price, it is fit. A union contract that hands open shifts out by seniority before anyone may trade. A hospital unit where the trade partner has to hold the same certification and the charge nurse signs off, not the scheduler. A two-site operation where a cross-site swap needs both managers. A floor where two employers' staff work side by side and cannot trade with each other at all. When the approval chain is the product, a generic "require manager approval" toggle is not enough, and that gap is what Newly is for: describe the trade rules you actually run, who can approve what, and it builds a real native app around them for $25 a month. If nobody is being paid, most of these rules fall away and the problem turns into a volunteer scheduling app, which has trade-offs of its own.
When to build your own
Building a swap shifts app around your approval chain.
Write the rules down before anything is built, because they are cheap to change on paper and expensive to change in an app employees already use. Which roles can trade with which. Whether a swap needs one approval or two. Where auto-approval is allowed and where it is not. What the rest gap is, per location if the law differs. Then two practical facts about shipping it to employees' phones: it needs a paid Apple Developer Program membership to reach iPhones, and Newly uploads the build to App Store Connect for you, where you test it in TestFlight and submit it for review. On the current version there are no Android release builds yet, which matters for a workforce app, because your employees' phones are split and a swap only works if both sides of it can open the app.
The rules are the part this page can help with. Wiring them to real accounts, so an employee sees only their own shifts and the offers made to them while a manager sees the approval queue, is a separate step, and it starts with adding user login and roles.
Sources
Where the specifics came from.
Four things on this page come from a primary source rather than general industry practice:
FAQ
Shift swap apps, answered.
A shift swap app lets an employee offer a scheduled shift to coworkers, lets an eligible coworker accept it, routes the trade to a manager for approval where the employer requires one, and then updates the schedule and keeps a record of who asked, who accepted, who approved, and when. It replaces the group chat and the whiteboard with a trade that is checked against role, location, availability, overtime and rest rules before it goes through.
Write the rules, then build the app.
A shift swap app is an approval workflow with a schedule attached. Decide who may trade with whom, who signs off, and what gets recorded, then build the app around those rules in Newly.