Handling Overlapping Time-Off Requests Fairly
When two people want the same days off, you need a tie-break rule. Compare seniority, first-come, and rotation, plus how to communicate a denial well.
When two employees ask for the same days off and you can only spare one, the decision feels personal even when it is not. The fix is to remove the judgment call entirely: decide your tie-break rule before the conflict happens, write it down, and apply it the same way every time. This guide walks through the three rules that actually work, when to use each, and how to deliver a "no" that keeps the relationship intact.
First, decide whether you even have a conflict
Before you reach for a tie-break rule, confirm that both requests genuinely cannot coexist. Two overlapping requests are only a problem if granting both drops you below the coverage you need. A five-person support team can often run on four; a two-person front desk usually cannot run on one.
Set a minimum coverage number for each role or team, then the math is simple. If your shipping team needs at least three people on the floor and you have five, two can be out at once before anyone needs to be told no. Write the minimums down. Without them, every overlap looks like a crisis and you end up negotiating coverage from scratch each time.
Also check the request type before applying any rule. Some leave is protected and cannot be denied for a coverage conflict:
- FMLA leave (for eligible employees at covered employers)
- Jury duty and court-ordered appearances
- State-mandated sick leave in states that have it
- Voting leave and military leave where required
A coverage tie-break only applies to discretionary PTO and vacation. If one of the overlapping requests is protected leave, that one wins automatically and the discretionary request is the one that gets resolved.
The three tie-break rules
There are really only three durable ways to break a tie. Each rewards a different behavior, and each annoys a different group of people. The trick is choosing the one whose tradeoffs you can live with and then never improvising.
1. First-come, first-served
The earliest approved or timestamped request wins. This is the most popular rule for small teams because it is objective, easy to explain, and rewards the people who plan ahead.
Worked example. Maria submits a request for the week of July 7 on March 2. Devon submits for the same week on May 18. Under first-come, Maria gets it, full stop. Devon's manager tells him on May 18, not in late June, so he still has time to choose different dates.
The catch: first-come only works if you timestamp requests reliably. A request shouted across the office at 8 a.m. and one emailed at 8:05 a.m. need a clear, recorded order. This is exactly where a request system earns its keep, because the submission time is logged automatically and nobody can argue about who asked first.
Best for: day-to-day overlaps, teams where most requests are spread across the year, and managers who want the least defensible-decision overhead.
2. Seniority
The employee with the longer tenure wins the tie. Seniority is common in unionized workplaces and in industries where retaining experienced staff is the whole game.
Worked example. Both Priya (hired 2019) and Sam (hired 2024) request the week of December 22. Under seniority, Priya wins regardless of who asked first.
Seniority is clean and easy to defend, but it has a real cost: the same senior people can win every desirable week, year after year, which is one of the faster ways to push newer employees out the door. If you use seniority, consider capping it, for example, "seniority decides the first conflict per person per year, and after that we fall back to rotation." That keeps tenure meaningful without letting it monopolize every holiday.
Best for: workplaces with strong tenure norms, union environments, or roles where experience directly determines who can cover a shift.
3. Rotation
You keep a documented order and rotate who gets first pick on high-demand dates. Whoever lost the prime week last year moves to the front of the line this year.
Worked example. Your team of four all wants the week of New Year's. You keep a rotation list. In 2025 it was Devon's turn; in 2026 it rotates to Maria; in 2027 to Sam; in 2028 to Priya. Everyone gets the marquee week once every four years and they can see it coming.
Rotation takes the most upfront work, but it is the only rule that feels fair over a multi-year horizon for the genuinely scarce dates. It also kills the midnight-booking arms race that pure first-come can create around holidays.
Best for: a small set of high-demand periods (major holidays, the week of a big local event, the first week of hunting or ski season) where the same people would otherwise win every time.
Comparing the three at a glance
| Rule | Rewards | Main downside | Best use |
|---|---|---|---|
| First-come | Planning ahead | Penalizes anyone who decides late | Everyday overlaps |
| Seniority | Tenure and loyalty | Newer staff lose repeatedly | Tenure-driven roles |
| Rotation | Long-run fairness | Most admin to maintain | Scarce holiday weeks |
Most well-run small teams do not pick just one. They layer them: first-come as the default, with a documented rotation that overrides it for a short, named list of peak weeks. Seniority shows up only as a final tiebreaker when two requests land at the same timestamp, which is rare once you log submission times.
Write the rule before you need it
Set the rules of the game in advance
A tie-break rule only feels fair if people knew it before they submitted. Cover these four things in writing so the system runs itself:
- Notice windows. A typical standard is two weeks of notice for one or two days and 30 days for a full week or more. Longer notice means you can resolve overlaps before anyone books travel.
- Peak periods and blackout dates. List the weeks where rotation applies and any dates that are off-limits entirely (your busy season, inventory week, a product launch).
- The tie-break order itself. State plainly: first-come by submission timestamp, rotation for the listed peak weeks, seniority only on an exact tie.
- Coverage minimums. Publish the minimum staffing per role so employees understand why an overlap sometimes means a no.
If you do not have this language yet, the PTO policy generator will draft a section you can adapt, and our tools page has calculators for working out coverage and balances.
Communicating the decision
The rule decides who gets the days. How you deliver the news decides whether the person who lost stays motivated. The denial is the part managers get wrong most often.
Tell the person who lost quickly. The worst version of a denial is a late one. If Devon finds out on June 28 that he cannot have the July 7 week he assumed was fine, he has already told his family and maybe booked a rental. Resolve overlaps as soon as the second request comes in, not when the date approaches.
Name the rule, not the person. Say "the week was already approved for someone else and our policy is first-come," not "someone else asked and I gave it to them." Pointing at the rule keeps it from becoming a referendum on who you like better. You never need to name the other employee.
Offer the next-best option. A denial lands far better when it comes with alternatives. "I can't approve July 7 to 11, but July 14 to 18 is wide open, and a Thursday-Friday around the 7th would also work if you want a long weekend." This turns a no into a redirect.
Put it in writing. A two-line message creates a record and prevents the "but you said" conversation later. For example:
Hi Devon, I'm not able to approve July 7 to 11 because that week was already approved under our first-come policy. July 14 to 18 is fully open if that works, or I'm happy to find another window with you. Let me know.
Be consistent, and be ready to show it. The single fastest way to lose trust is to apply the rule to one person and bend it for another. If you make an exception, expect to explain it, so make sure you would be comfortable explaining it to everyone on the team.
A simple workflow for the next overlap
Put the pieces together and your process for any conflict becomes a short checklist:
- Confirm both requests actually breach your coverage minimum. If not, approve both.
- Check whether either request is protected leave. If so, it wins automatically.
- Apply your written tie-break order: rotation for peak weeks, otherwise first-come, seniority only on an exact tie.
- Notify the person who lost the same day, name the rule, and offer alternatives.
- Log the decision so the rotation and the timestamps stay accurate for next time.
Run that every time and overlaps stop being stressful. The decision is made by a system you published, not by you in the moment, which is precisely what makes it fair.
To estimate how much coverage you actually have on any given week, the working days calculator helps you count staffed days around holidays before you approve anything.
The bottom line
Overlapping requests are not a people problem; they are a process problem. Pick a tie-break rule you can defend, write down your coverage minimums and peak weeks, resolve conflicts the day the second request arrives, and always pair a denial with an alternative. Do that and "no" stops costing you goodwill.
SimplyPTO logs every request with a timestamp, shows you who is already off each week, and flags overlaps before you approve them, so your first-come or rotation rule runs on real data instead of memory. Start a free SimplyPTO account and let the system handle the tie-breaking for you.
Frequently asked questions
What is the fairest way to decide between two overlapping time-off requests?
There is no single fairest rule, but the fairest system is a written one that everyone knows in advance. First-come-first-served rewards planning and is the easiest to defend. Seniority recognizes tenure but can frustrate newer staff. Rotation spreads prime dates over the years. Pick one, write it in the handbook, and apply it consistently.
Can an employer deny a vacation request that overlaps with another approved request?
Yes. In most of the United States, PTO is a benefit, not a guaranteed right to specific dates, so an employer can deny or reschedule a request to maintain coverage. The exceptions are protected leave such as FMLA, jury duty, and state sick-leave laws, which you generally cannot deny. Always check the request type before applying a coverage rule.
How much notice should employees give for time-off requests?
A common standard is two weeks of notice for one to two days off and 30 days for a full week or more. Longer notice gives you time to resolve overlaps before both employees have booked flights. Put the notice window in writing and tie your tie-break rules to the request timestamp so early planners are rewarded.
Should I use seniority or first-come for holiday weeks?
For high-demand weeks like the days around Christmas or the Fourth of July, a rotation is usually fairest. Pure seniority means the same senior people get every prime holiday forever, and pure first-come turns the request system into a race at midnight. A documented rotation guarantees everyone a turn over a two or three year cycle.