TL;DR: A two-week notice rule isn't a PTO policy — it's a deadline floating in space. A real policy answers six questions: minimum notice, maximum lead time, who wins when requests overlap, how you keep popular weeks fair, what managers can and can't decline, and where the source of truth lives. This piece walks through each one with patterns that work and the traps to avoid.
A manager recently posted in r/managers asking what should be a simple question: how far in advance is reasonable for employees to request PTO? Six months? A year? Their company's only stated rule was "two weeks in advance." They had a five-person team, a no-overlap-beyond-one-day constraint, and no idea what to do when someone wanted to lock down Christmas 2026 in April.
The replies were all over the map. One manager said any request, anytime — they never reject PTO and just figure out coverage. Another capped requests at three months out unless the trip required serious advance booking (international, cruise, wedding). One shared a story about getting an email at 12:05 AM on January 1st locking in the Fourth of July and Christmas because "it was the new year."
That spread isn't because PTO is uniquely complicated. It's because most companies treat the request deadline as if it were a request policy. It isn't. A deadline tells employees when they have to ask. A policy tells everyone — employees, managers, and HR — what happens after they do.
If you're in HR or People Ops and your handbook says some version of "submit PTO at least two weeks in advance," your managers are improvising the rest. Some are doing it well. Some are creating quiet resentment that won't show up until an exit interview. Here's how to give them a real framework.
Why "two weeks notice" isn't a policy
A two-week minimum is one rule. A working PTO policy needs at least six. Without the rest, you end up in one of three predictable failure modes:
- First-come-first-served chaos. Whoever submits first wins, which rewards the people with the simplest schedules and quietly punishes parents, caregivers, and anyone whose plans depend on someone else's calendar. The 12:05 AM January 1st emailer is the canonical example, but the pattern shows up year-round.
- Seniority hoarding. When there's no rotation rule, the same one or two people end up with Thanksgiving, Christmas, and New Year's every year. Eventually the rest of the team starts taking sick days to even the score, and morale takes the hit.
- Manager-by-manager improvisation. One team approves anything; another denies anything that overlaps; a third quietly retaliates against the employee who got their request in first. Same company, three different employee experiences, and you find out about it in the engagement survey.
A real policy makes the answers consistent without making them rigid. It gives managers cover when they have to say no, gives employees confidence about what's allowed, and gives HR something to point to when a manager is being unreasonable.
The six questions your PTO request policy needs to answer
1. What's the minimum notice?
This is the part most policies already cover. Two weeks is a reasonable default for vacation requests of more than a day or two. For a single day off — especially flex time, mental health days, or appointments — a 24-to-48 hour minimum is more realistic. Sick leave shouldn't have a minimum at all.
The mistake is making the minimum the whole policy. State it, but don't stop there.
2. What's the maximum lead time?
This is the part most policies skip. Without a cap, you get the January 1st gold rush — employees racing to lock in popular weeks twelve months out, blocking everyone else from planning around them.
A common cap that works: requests can be submitted up to three to six months in advance for normal time off, with an exception for trips that genuinely require longer lead time (international travel, cruises, destination weddings, IVF and adoption timelines). For those, employees can flag dates earlier in writing — they go on a tentative calendar, but they don't formally consume the slot until the standard window opens.
The point isn't to make planning harder. It's to give everyone a fair shot at the same prime weeks.
3. Who wins when requests overlap?
If your team has a coverage constraint — and most do — you need a stated tiebreaker. The options:
- First-come-first-served within the standard window. Simple, but combine it with a max lead time and a holiday rotation (below) or you'll recreate the hoarding problem.
- Rotation for high-demand periods. Whoever had Christmas off last year doesn't get first pick this year. Whoever was bumped from Thanksgiving gets priority next time. This is the most equitable approach for teams where the same five weeks every year drive 80% of the conflict.
- Manager judgment based on documented criteria. Things like religious observance, school-aged children at home, family caregiving needs, or pre-booked non-refundable travel. Document the criteria so it doesn't look like favoritism.
Most healthy policies blend the three: first-come-first-served by default, holiday rotation for the contested weeks, and documented exceptions for genuine hardship.
4. How do you keep popular weeks fair?
Related to #3 but worth its own answer. The Reddit thread surfaced a pattern that works: limit each person to one "premium" holiday week per year. Pick Thanksgiving or Christmas, not both. Pick the first week of summer or the last, not both. Whoever didn't get their pick last year goes first this year.
You don't need to write this as a hard rule for every company. But your policy should at least say how the team will distribute popular weeks — whether that's a rotation, a draft, or a team conversation in Q4. Silence on this question is what produces the senior-employee-takes-everything pattern.
5. What can a manager actually decline?
This is the question that most consistently goes unanswered, and it's the one that causes the most resentment. Be specific:
- Managers can decline a request that creates a coverage gap that can't be filled, that overlaps with a critical project deadline that was communicated in advance, or that violates the team's stated overlap rule.
- Managers cannot decline a request because they personally think the employee should be working, because they don't like the timing, or because the employee has "taken too much" PTO when the time is within their accrual.
Spelling this out protects employees from arbitrary denials and protects managers from being painted as the bad guy when they have a real reason. Pair it with an escalation path — if an employee feels their PTO was unreasonably denied, they can talk to HR.
6. Where does the source of truth live?
Every working PTO system has one place where the team's time off is visible to everyone. Spreadsheets technically work and consistently fail in practice — they're never up to date, and the version on the manager's laptop is different from the one in the shared drive.
What works: a shared team calendar that updates automatically when PTO is approved, plus a way for employees to mark tentative dates so the team knows that someone is eyeing a particular week even before it's officially booked. The tentative-marking pattern, surfaced repeatedly in the Reddit thread, prevents two people from independently planning the same week and then having an awkward conversation about it.
Three traps to avoid
Pure first-come-first-served with no cap. You're rewarding planning behavior, not need. Pair it with a max lead time and a holiday rotation.
"Manager discretion" with no guardrails. Different managers will interpret this completely differently, and your top performers will eventually compare notes. Either give managers a rubric or accept that you're going to lose people over inconsistency.
Treating PTO as a privilege. Multiple managers in the thread made the same point: PTO is part of the compensation package. Once it's on the offer letter, it's owed, not granted. Policies that read like the company is doing the employee a favor produce the worst retention numbers.
A starting template you can adapt
Here's a baseline policy structure you can edit for your handbook:
Submitting PTO requests
Submit requests through [system] as early as you reasonably can. Minimum notice for any planned PTO is two weeks (24 hours for single-day flex time; no minimum for sick leave). Maximum lead time is six months in advance, with exceptions for international travel, cruises, weddings, and medical procedures that require longer planning windows — flag these to your manager and they will be tracked on the team's tentative calendar.
Overlap and approval
Within team coverage limits, requests are approved on a first-come-first-served basis. For Thanksgiving week, the week between Christmas and New Year's, and the first and last weeks of school summer break, we use a yearly rotation: anyone who took the week off last year is second priority this year.
What managers consider
Managers approve PTO unless the request creates a coverage gap that can't reasonably be filled, conflicts with a critical project deadline that was communicated to the team in writing in advance, or violates the team's stated overlap rule. If you feel your request was unreasonably denied, contact [HR contact].
Visibility
All approved PTO appears on the team's shared calendar automatically. Mark tentative dates as soon as you're considering them so the team can plan around possibilities, not just confirmed plans.
Adjust the specifics — your minimum notice, your max lead time, your rotation rules, your overlap caps — to fit your team. The structure is what matters: every question above gets a stated answer.
Where tooling makes this easier
Most of the conflict above isn't a policy problem so much as a visibility problem. When the source of truth is a spreadsheet or a Slack thread, requests get lost, calendars go stale, and the same person ends up surprised three different times that someone is out.
The teams that get this right have one place where requests, approvals, balances, and the team calendar all live, and the calendar updates automatically the moment a request is approved. That's exactly what we built PTOflow to do — request and approval workflows in Slack, automatic Google Calendar sync, leave bank tracking, and the customizable categories you need to encode the policy you just wrote. It's free for 14 days and takes under ten minutes to set up.
A two-week notice rule isn't a policy. The six answers above are. Get those written down, and the rest of this stops being a recurring HR fire.
If you're rolling out a new PTO policy and want a template you can drop into your handbook, PTOflow's onboarding walks you through the common categories and rules so you're not starting from a blank page.