How Far in Advance Should You Request PTO? Notice Norms by Trip Length (and Why Bridge Days Vanish First)

Every January, the same quiet race starts inside every team: the year's calendar publishes, a handful of holiday-adjacent workdays turn out to be worth double, and whoever files first — or has the most seniority, depending on the policy — takes them off the board. Ask in October for the Friday after Thanksgiving and you are not making a request; you are joining a waitlist. When you ask matters nearly as much as what you ask for, and the norms for "when" scale predictably with trip length.

This post lays out those norms, explains why bridge days are a scarcity market unlike ordinary PTO, walks through the two allocation systems companies actually use (first-come-first-served vs seniority), and ends with a timing playbook you can run every year. It pairs with How to Request Time Off: Email Templates That Get Approved — this post covers when to ask, that one covers how.

This is a research post written with sources, but notice-period figures below are observed norms and HR recommendations, not law — your employer's handbook is the only binding document, and policies change. US-specific legal points reflect federal rules as of mid-2026; state laws evolve. Verify your own policy before planning, and use the leave optimizer for your year's actual bridge dates rather than anything hard-coded here.

The short answer: notice scales with trip length

There is no statutory notice period for vacation in the US (more on that below), so norms come from HR practice. ADP's small-business HR guidance suggests roughly one week's notice for short vacations of one or two days and about a month for vacations of three or more days; employer-side policy guides commonly cite two weeks as a baseline with some companies requiring 30 days. Layer on the practical reality of competition for good dates, and the working norms look like this:

Two readings of this table matter. First, the policy floor is a minimum, not a target — meeting it guarantees your request is considered, not approved. Second, the right-hand column is driven less by rules than by competition: a random Tuesday in March needs little runway; the Friday before a Monday holiday needs months.

If your trip is anchored to a school break, a wedding, or peak-season flights, add more margin — those dates are the ones everyone else is anchored to as well.

Why bridge days get competed away first

Ordinary PTO days are abundant: there are ~250 workdays a year and most of them are interchangeable. Bridge days are not. A Tuesday holiday creates exactly one Monday that converts a weekend into a four-day block; a Thursday holiday creates exactly one Friday. The sandwich-day strategy everyone eventually discovers points the entire team at the same handful of squares on the calendar — and the ROI math is identical for all of you, so there is no clever alternative date. Whoever the policy favors gets the day; everyone else covers.

That makes the allocation rule — buried in your handbook or collective bargaining agreement — the single most important thing to know before you time a request. In practice there are three systems:

Union agreements frequently formalize the hybrid: sample CBA clauses have each employee pick in seniority order — typically a single continuous block, capped at a set length that varies by contract — sometimes run a second seniority round, and only then open the calendar first-come-first-served. Non-union employers mostly run informal FCFS, which means the January bridge-day race is real wherever you work: at FCFS shops the fastest requester wins outright, and even at seniority shops the leftover dates go FCFS.

The practical takeaway: run your year's calendar through the optimizer as soon as the new year's holidays are confirmed, identify the two or three bridge dates you actually want, and request those specifically and early — even if the rest of your vacation planning is months away. Bridge days and ordinary days should be requested on completely different timelines.

What US law does NOT guarantee

This is the part most workers get wrong, so it deserves precision.

Federal law does not require paid vacation at all. The Fair Labor Standards Act does not require payment for time not worked — vacations, sick leave, or holidays. The Department of Labor's own framing is that these benefits are "matters of agreement between an employer and an employee (or the employee's representative)." No federal statute obliges your employer to grant PTO, and none obliges them to approve any particular request.

That means, as a general rule:

• Approval is discretionary. An employer may deny a vacation request because of staffing, season, overlapping requests, or essentially any non-discriminatory business reason. They can impose blackout periods (no vacations at all) or "brownout" periods (restricted, e.g., no more than two days at a time) around their busy season.
• Timing rules are the employer's to set. Minimum-notice requirements, request windows, and caps on concurrent absences are all legal and common.
• Approved PTO can generally be revoked. No federal law prevents an employer from rescinding an approved vacation for business reasons — rare in practice, but not prohibited. (Whether unused PTO must be paid out is a separate, state-by-state question.)

The important exceptions — where "no" can be unlawful — are legally protected leave categories: leave qualifying under the FMLA, disability-related leave under the ADA, religious-observance accommodations under Title VII, protected sick or family leave under a growing list of state laws, and any denial that is actually discrimination or retaliation in disguise. We cover the boundaries in detail in Can Your Employer Deny Your Leave Request?

There is one place US federal law does codify advance notice, and it cuts the other way — it binds you: for foreseeable FMLA leave (a planned birth, adoption, or scheduled medical treatment), an employee must give at least 30 days' notice when practicable, or notice as soon as practicable otherwise; skip it without a reasonable excuse and the employer may delay FMLA coverage. Even where leave is a legal right, timing obligations still exist.

The strategic conclusion from all this: because approval is discretionary, your leverage is entirely soft — timing, framing, and coverage planning. Which brings us to the person actually clicking approve.

Manager psychology: what a PTO request looks like from the other side

A manager evaluating your request is not really evaluating your vacation. They are running a quick mental checklist:

1. Coverage — who picks up your work, and does that person also want the same week off?
2. Precedent — if I approve this, what am I obligated to approve for the next person?
3. Surprise risk — is anything likely to land during those dates that I'll regret not having you for?
4. Fairness optics — will the rest of the team see this as reasonable?

Early requests score better on every one of these. Asking four months out converts your request from a problem ("who covers next week?") into a planning input ("noted, I'll staff around it") — the manager gets to feel organized instead of squeezed, and the ask costs them almost nothing to approve. Asking ten days out forces them to solve a staffing puzzle on the spot, and the easiest solution to a puzzle is "no" or "can you move it?"

You can push every checklist item in your favor:

• Bring the coverage plan with the request. Name who agreed to backstop you, what you'll hand off, and what you'll finish before leaving. A request that arrives pre-solved is nearly impossible to refuse. (The email templates post has ready-made wording for exactly this.)
• Time the ask to the team's rhythm. Right after a launch or quarter-close beats the week before one. Never ask for peak-period dates in the middle of a peak period.
• Check the shared team calendar first — and say so. "I've checked the team calendar and no one else is out that week" removes the manager's biggest unknown in one sentence.
• Don't stack silently. If a teammate already holds adjacent dates, talk to them before your manager sees the conflict. Managers reward people who surface conflicts pre-solved and remember people who create them.
• Put approvals in writing. A verbal "sure, should be fine" is not an approval; a calendar entry plus a one-line confirming email is. This protects both of you when memories differ in six months.

One etiquette note on the bridge-day race specifically: winning every contested date every year is a visible pattern, and teams notice. If you took the marquee bridge last year, ceding it this year — and taking an equally good but less obvious window the optimizer surfaces — is both good citizenship and usually a better trade than fighting for the crowded one.

The request-timing playbook

Here is the annual routine, compressed:

1. The week the new year's holiday calendar is confirmed (often October–December for the following year): run your country and leave balance through the leave optimizer and shortlist your top bridge windows. Do not skip this — the shortlist is what everything below protects.

2. Immediately after (or the moment your company's request window opens): file requests for your holiday-adjacent bridge dates only. One to three days each, minimal coverage burden, maximal scarcity. This is the FCFS race; if your shop runs seniority rounds, learn the round schedule and prepare a ranked backup list instead.

3. Three to six months out: request any 2+ week trip. Pair it with a first-draft coverage plan and expect a conversation, not an instant yes.

4. One to three months out: request ordinary 1–2 week trips. Check the team calendar first; name your coverage.

5. Two to four weeks out: request casual long weekends on uncontested dates. These are the only requests where late-ish is genuinely fine.

6. Always: confirm in writing, re-confirm anything approved more than three months ago as the date approaches, and hold off on nonrefundable bookings until the approval is explicit — approval is discretionary, and discretion occasionally reverses.

FAQ

Is there a legally required notice period for vacation requests in the US?

No. Federal law does not require employers to offer paid vacation, let alone regulate how it is requested — the FLSA treats vacation as a matter of agreement between employer and employee. Notice periods come entirely from your employer's policy. The one federal notice rule that exists (FMLA's 30-day rule for foreseeable leave) binds the employee, not the employer.

Can my employer deny a request I submitted months in advance?

Generally yes — early submission earns goodwill and usually priority, but it creates no legal entitlement. Employers generally retain discretion to deny (or even revoke) vacation for business reasons, with exceptions for legally protected leave and for denials that amount to discrimination or retaliation. See Can Your Employer Deny Your Leave Request? for where the lines are.

Should I book flights before my PTO is approved?

Book nothing nonrefundable before written approval. A reasonable middle path for scarce fares: request the dates, tell your manager a fare deadline exists ("I'd like to book by Friday if you can confirm"), and use refundable holds in the meantime. A deadline attached to a well-timed, pre-solved request usually accelerates the yes.

What if a more senior coworker requests my dates after I've been approved?

Under pure first-come-first-served, your earlier approved request typically stands. Under seniority-governed policies (common in union environments), a senior employee's pick can displace yours during the formal selection round — but usually not after the calendar has closed and been approved. This is exactly why you should know which system your handbook or CBA specifies before the annual race starts.

How early is too early?

If your employer publishes a request window, its opening day is the answer. If not: requests more than ~6–9 months out mostly just risk being forgotten rather than rejected — managers hesitate to commit around unknown staffing. File the scarce dates as early as the system accepts them, put the approval in writing, and re-confirm a month or so before you go.

Sources

• Vacation Leave — U.S. Department of Labor — FLSA does not require payment for time not worked; vacation benefits are matters of agreement between employer and employee.
• Fact Sheet #28E: Employee Notice Requirements under the FMLA — U.S. Department of Labor — 30-day advance-notice requirement for foreseeable FMLA leave; consequences of late notice.
• Your Vacation Policy Checklist — ADP SBS HR Newsletter — typical notice recommendations (~1 week for 1–2 day vacations, ~1 month for 3+ days); blackout and brownout periods.
• Can Your Job Deny PTO? Rights and Exceptions — LegalClarity — employer discretion to deny PTO and the protected-leave / anti-retaliation exceptions.
• Can U.S. Employers Deny PTO? — PurelyHR — employer-side view of PTO denial rights and limits.
• Vacation Scheduling Methods — ScheduleTech — the strict-seniority / relaxed-seniority / first-come-first-served taxonomy.
• What Is Seniority Vacation Scheduling? — Vacation Tracker — how seniority-based vacation picks and multi-round selection work in practice.
• PTO Request Policy: A Comprehensive Guide for Employers — Business Management Daily — the common two-week notice cutoff example and guidance on setting notice requirements in written policies.
• Vacation Scheduling clause samples — Law Insider — real CBA clauses showing seniority pick rounds (with per-round caps) followed by first-come-first-served scheduling.
• 29 CFR § 825.302 — Employee notice requirements for foreseeable FMLA leave (Cornell LII) — the 30-days-when-foreseeable / as-soon-as-practicable notice text.