How to Handle Overlapping PTO Requests: Fair Rules for Approving Time Off
Quick Answer
To handle overlapping PTO requests, first decide how many people can be off at once in each team or role. Then pick one approval rule and write it down: first-come, first-served by request date, seniority, a rotation for peak dates or a lottery. Set request deadlines for busy periods, use a waitlist when the limit is reached, apply the rule the same way to everyone and give a clear answer quickly so employees can plan.
It happens every year: three people on a five-person team want the week of July 4, or half the kitchen asks for the same weekend in December. Approving everyone leaves the business short. Denying people without a clear rule feels unfair and damages morale. Overlapping PTO requests are a scheduling problem and a fairness problem at the same time.
This guide explains how to set limits on time off, choose a fair approval rule, handle holidays and peak seasons and communicate decisions, with a free PTO conflict policy template.
Step 1: Decide How Many People Can Be Off at Once
Before you can decide who gets time off, you need to know how many people can be off without hurting service or safety. Work this out by team or role, not just for the whole business.
| Team | Total staff | Minimum needed on shift | Maximum off at once |
|---|---|---|---|
| Front desk | 6 | 4 | 2 |
| Kitchen | 8 | 6 | 2 |
| Field technicians | 5 | 4 | 1 |
| Office | 3 | 2 | 1 |
These numbers are examples. Start from your minimum staffing levels and remember that the limit may be lower during busy seasons. See minimum staffing levels.
Step 2: Choose an Approval Rule
| Rule | How it works | Pros | Cons |
|---|---|---|---|
| First-come, first-served | Earliest request wins | Simple and easy to explain | Rewards people who plan far ahead; can lock out others for years |
| Seniority | Longest-serving employee wins | Rewards loyalty; common in unions | Newer employees may never get popular dates |
| Rotation | Priority for popular dates rotates each year | Fair over time | Requires records year to year |
| Lottery | Random draw among requests submitted by a deadline | Feels fair for high-demand dates | Can seem arbitrary |
| Business need | Manager decides based on coverage and skills | Flexible | Can look like favoritism |
Many businesses combine rules: first-come, first-served for normal dates, plus a request window and rotation or lottery for holidays and peak weeks. Whatever you choose, write it down and apply it the same way to everyone.
Free PTO Conflict Policy Template
[Company Name] Time Off Request and Conflict Policy
1. Maximum time off. No more than [number] employees from [team/role] may be scheduled off at the same time. During [peak periods], the limit is [number].
2. Request deadlines. Requests for regular dates must be submitted at least [number] days in advance. Requests for [holidays/summer weeks] must be submitted between [date] and [date].
3. Approval order. For regular dates, requests are approved in the order they are received, as long as the limit is not reached. For [holidays/peak dates], requests submitted during the request window are approved by [rotation/seniority/lottery].
4. Waitlist. When the limit is reached, additional requests are placed on a waitlist in the order received. If an approved employee cancels, the next person on the waitlist is offered the time off.
5. Response time. Managers will approve or deny requests within [number] business days.
6. Swaps and coverage. Employees may ask a qualified coworker to cover a shift so a request can be approved, subject to manager approval.
7. Protected leave. Leave required by law, such as qualifying medical, family, military or jury service leave, is handled under the applicable law and is not subject to this approval process.
8. Consistency. These rules apply to all employees in the same role. Exceptions require approval from [role] and will be documented.
Step 3: Set Request Deadlines and Windows
Deadlines give managers time to plan and give everyone a fair chance. For normal dates, a deadline such as two to four weeks before the date works for many teams. For holidays and peak seasons, use a request window: for example, all requests for December 20 to January 2 must be submitted between September 1 and September 30, and decisions go out by October 15.
| Period | Request window | Decisions announced |
|---|---|---|
| Summer (June–August) | February 1–28 | March 15 |
| Thanksgiving week | August 1–31 | September 15 |
| Winter holidays | September 1–30 | October 15 |
Step 4: Use Tie-Breakers
Even with a clear rule, ties happen, such as two requests submitted the same day. Decide in advance how ties are broken:
- Who had the date last year (the other person gets priority this year).
- Who has had fewer approved peak-date requests over the past two years.
- Seniority, as a final tie-breaker.
- A coin flip or random draw, recorded and witnessed.
Write the tie-breakers into the policy so managers don't have to make it up on the spot.
Step 5: Keep a Waitlist
When the limit is reached, don't just deny later requests. Put them on a waitlist in the order received and tell employees where they stand. Plans change, and approved employees sometimes cancel. A waitlist turns those cancellations into approvals fairly instead of whoever happens to ask the manager first.
Holidays and Peak Seasons
Holidays are where most PTO conflicts happen. Rotation systems work well here: an employee who gets Christmas week off this year goes to the back of the line for that week next year. Some businesses split the holidays, giving one group Christmas and another New Year's, then switching the following year. See the employee holiday planner.
| Year | Christmas week | New Year's week |
|---|---|---|
| 2026 | Team A off | Team B off |
| 2027 | Team B off | Team A off |
| 2028 | Team A off | Team B off |
Blackout Periods
Some businesses block time off during their busiest periods, such as tax season for an accounting firm or the weeks before a big event. If you use blackout periods, list them in writing well in advance, keep them as short as possible and allow exceptions for emergencies. Blackouts work best when they're rare and predictable. See whether employers can control when PTO is used.
Handling Requests That Don't Fit the Rules
Some requests deserve special consideration: a wedding, a family emergency, a long-planned trip booked before the employee was hired. Allow exceptions, but require them to be approved by a senior manager and recorded with the reason. If exceptions start happening often, update the policy instead of making one-off decisions.
Protected Leave Is Different
Time off protected by law isn't part of the PTO competition. Depending on your size and location, that can include qualifying family or medical leave, military leave, jury duty and paid sick leave under state or local laws. Handle those requests under the applicable rules, even if the PTO limit for that week has been reached. See whether an employer can deny sick leave.
Communicating Decisions
- Respond quickly, within the time your policy promises.
- When denying, explain which rule applied and whether the employee is on the waitlist.
- Suggest alternative dates or a shift swap when possible.
- Put decisions in writing so there's no confusion later.
- Publish the approved time-off calendar so everyone can see open dates.
See the PTO request and response email templates and how to deny a PTO request.
Make Open Dates Visible
Much of the conflict disappears when employees can see who is already off before they ask. A shared time-off calendar shows which dates are full and which are open, so people can plan around them. Employees are less frustrated by a denial when they could see the limit had already been reached.
Free Time-Off Request Tracker
Time-Off Request Tracker
Team: __________ | Maximum off at once: ____ | Period: ______
| Date requested | Employee | Dates off | Hours | Status | Waitlist # | Decided by | Notes |
|---|---|---|---|---|---|---|---|
| ☐ Approved ☐ Denied ☐ Waitlist | |||||||
| ☐ Approved ☐ Denied ☐ Waitlist | |||||||
| ☐ Approved ☐ Denied ☐ Waitlist | |||||||
| ☐ Approved ☐ Denied ☐ Waitlist |
Example: A Dental Office
A dental office with four hygienists had the same two employees off every summer because they always requested in January. The other two complained every year. The office manager set a limit of one hygienist off per week in summer, opened a February request window for June through August and used a rotation for the most popular weeks, with a waitlist for the rest. Over two years, every hygienist got at least one of their preferred summer weeks, and complaints stopped.
Common Mistakes
- No written rule, so decisions depend on who asks or who the manager likes.
- No limit on how many can be off at once.
- Slow responses that leave employees unable to book plans.
- Pure first-come, first-served for holidays, letting the same people win forever.
- Treating protected leave like ordinary PTO.
- Inconsistent exceptions.
PTO Conflict Checklist
| Step | Done? |
|---|---|
| Set maximum off at once by team | |
| Choose an approval rule | |
| Set request deadlines and holiday windows | |
| Write tie-breakers | |
| Create a waitlist process | |
| Publish a shared time-off calendar | |
| Separate protected leave from PTO approval | |
| Set a response time |
Overlapping Requests in Small Teams
In a team of three or four, even one person off can strain coverage, and two off at once may be impossible. Small teams need cross-training more than anyone, so more than one person can cover each role. Consider allowing only one person off at a time in critical roles, and ask employees to talk with each other before requesting popular dates so conflicts get worked out early. See cross-training.
Requests That Span Busy and Slow Periods
A two-week vacation that starts in a slow week and ends in a busy one can be approved in part, or the employee can be offered alternative dates. Be clear about which days fall under peak-period limits. Splitting requests should be the employee's choice where possible, since they may have already booked travel.
When Employees Change Their Plans
Ask employees to cancel approved time off as soon as plans change, so the dates can go to the next person on the waitlist. If someone repeatedly books popular dates and cancels at the last minute, address it directly; holding dates you don't need blocks coworkers. Some businesses require a minimum notice to cancel approved peak-period time off.
Manager Time Off
Managers and supervisors should follow the same rules, with one extra step: arranging coverage for their duties. Avoid having all managers off at once, and publish manager time off on the same calendar so employees know who to contact. When managers follow the rules, employees trust the system more.
Tracking Fairness Over Time
Keep a simple history of who got which peak dates each year. It makes rotations easy to run, helps settle disputes and shows over time whether the system is fair. If the same employees are consistently denied, review whether your limits or rules need to change.
| Employee | 2025 peak dates | 2026 peak dates | 2027 priority |
|---|---|---|---|
Announcing a New PTO Conflict Policy
Changing how time off is approved can upset employees who have benefited from the old way. Announce the new rules before they take effect, explain why, show examples and honor requests already approved under the old system. Give employees a chance to ask questions, and review the policy after the first holiday season to see what needs adjusting.
Common Questions From Employees
- "Why was my request denied when I asked first?" For peak dates, the rotation or lottery applies, not request order.
- "Can I trade dates with a coworker?" Yes, if both agree and a manager approves.
- "How do I know if dates are open?" Check the shared time-off calendar before requesting.
- "What if I have an emergency?" Emergencies are handled separately; talk to your manager right away.
PTO Conflicts Across Departments
Limits usually apply within a team, but some roles affect several departments, such as the only bookkeeper or the person who runs payroll. Identify those roles and plan backups before their time off is approved. If two departments depend on each other at certain times, such as sales and fulfillment during a promotion, coordinate time-off limits between their managers.
A short monthly check-in between managers to review the shared calendar catches most of these conflicts before they become problems.
PTO Conflict Quick Reference
| Item | Recommendation |
|---|---|
| Limit | Set maximum off at once by team |
| Normal dates | First-come, first-served |
| Peak dates | Request window plus rotation or lottery |
| Ties | Written tie-breakers |
| Overflow | Waitlist in order received |
| Response | Within a set number of business days |
Post this summary next to the time-off calendar so employees can check the rules before they request popular dates, and update it when limits change.
When the policy and calendar are visible and consistent, most employees will plan around each other without needing a manager to decide.
Final Thoughts
Overlapping PTO requests are inevitable, but conflict doesn't have to be. Decide how many people can be off at once, choose a written approval rule, set deadlines and windows for busy periods, keep a waitlist and respond quickly. When employees can see the calendar and know the rules in advance, they plan around each other, and managers spend less time refereeing.
Manage Time-Off Requests With Updoot
Updoot's PTO tracking shows who is already off before you approve a request, and the PTO calendar lets employees see open dates, so overlapping requests are easier to manage fairly.
