Time-Out Zone

Blackout dates that enforce themselves

Mark up to 20 date ranges per leave type, the year-end freeze, the seasonal peak, and any request that overlaps them is blocked at submission, with the exact conflicting dates in the message. Approvers keep judgment on edge cases, and every override goes on the record.

Get startedView pricing
  • Lab Test Analyzer logo
  • Promics Edge logo
  • SelfHacked logo
  • SelfDecode logo
  • OmicsEdge logo

Blackout periods: what the market and the law expect

1 in 5

US organizations run vacation blackout periods, mostly reserved for peak workload

49%

of PTO requests get approved in an average month; requests are growing faster than approvals

56%

of employees requested time off in January 2024, a four-year high around the turn of the year

12 days

the contiguous vacation block German law preserves, no matter how busy the season

  • In the US, no law regulates when PTO can be taken, so blackout dates are plain employer policy: about one in five organizations uses them, typically around peak season and holiday trade.
  • In the DACH region a blackout is the exception, not the default: Germany allows it only for urgent operational needs within clear time limits, Austria requires vacation timing to be agreed, and Switzerland lets the employer schedule but guarantees two consecutive weeks.

Figures from a 2024 US benefits survey, HR-platform data 2018 to 2024, and German statute. Rounded.

Blocked at submit, not in the approver's lap

Pick dates that cross a blackout range and the request never leaves the modal: the exact conflicting dates come back in the message, you pick a clean week, and it goes straight through to your approver. The rule does the enforcement before anyone has to play bad cop.

Concrete date ranges

Each blackout is a plain date range, like September 1 to October 31. A year-wheel preview shows how much of the policy year the ranges block before you save.

Per leave type

Blackouts live on the leave type. Freeze vacation through the holiday rush while other leave types stay untouched.

Enforced at submission

A request that overlaps a range is rejected on the spot, with the conflicting dates spelled out. Nothing lands in the approver queue.

Advisory for approvers

If a pending request drifts into a blackout later, approvers see a flag instead of a wall. Approving over it is allowed, and recorded.

The details, spelled out

Up to 20 ranges

Each leave type carries up to 20 blackout ranges, enough for seasonal peaks, inventory weeks, and a year-end freeze at once.

Clean ranges only

Duplicate ranges are rejected, overlapping ranges are rejected, and an end date can never sit before its start.

Overrides on the record

Approving a request over a blackout flag is captured in the audit trail, so exceptions stay explainable.

Team coverage, separately

Minimum-staffing and team-level blackout dates are a separate coverage mechanism that also checks at submission.

Values in the visuals are examples. Every range is configurable per leave type.

Ranges

One calendar wheel per leave type

Blackout ranges are configured on the leave type, in the same wizard as its other rules.

  • Each range is a concrete pair of dates; add the next one with a click, up to 20 per leave type.
  • The year wheel shows blocked stretches on the annual ring and totals them, like "25% of the year is blocked across 2 periods".
  • Validation keeps ranges honest: no duplicates, no overlaps, end never before start.

At submit

The rule fires before the request exists

Enforcement happens at submission, on the server, for every request shape.

  • A conflicting request is blocked with the exact dates of the range it crosses, spelled out in the message.
  • Single, half-day, bulk, and recurring requests all pass the same check, item by item.
  • Nothing conflicting reaches the approver, so the queue stays clean during the freeze.

At approval

Approvers get a flag, not a wall

Requests that were already pending when a blackout changed still need a human call.

  • The approve dialog re-checks every rule and shows a dedicated blackout row among its policy checks.
  • The flag is advisory: approvers can approve over it when the case deserves it.
  • Every approval over a flag is recorded in the audit trail.

Guardrails

Sharp edges, spelled out

The feature stays deliberately small and predictable.

  • Ranges are concrete calendar dates: for next year's freeze, you add next year's range.
  • Employees learn about a conflict at submission, in the request modal, not from a greyed-out calendar.
  • Team-level coverage rules and tag-level windows are separate mechanisms with their own configuration.

More resources

Feature

Advance notice and waiting periods

Feature

Spending limits

Feature

Time-off requests

Ready to get started?

Give us a call. We'll map your peak seasons into blackout ranges and show the year wheel before you commit to anything.

Advance Notice & Waiting Periods

Minimum lead time and new-hire waiting periods, per leave type.

Explore

Spending Limits

Caps per month, quarter, or half-year.

Explore

Frequently asked questions

What is a PTO blackout period?
A stretch of dates when a specific leave type cannot be requested, typically covering peak season or a year-end freeze. In Time-Out Zone a blackout period is a concrete date range on the leave type, and requests that overlap it are blocked at submission.
Are PTO blackout dates legal?
In the US, no federal law regulates when vacation can be taken, so blackout dates are ordinary employer policy; protected leave like statutory sick time sits outside them. In Germany and Austria a blackout must stay an exception with a clear operational reason, which is exactly why concrete, time-limited ranges matter.
What happens when a request hits a blackout period?
It is blocked at submission with the conflicting dates spelled out, and the employee picks new dates and resubmits. Nothing reaches the approver, so the queue stays clean during the freeze.
Can approvers override a blackout conflict?
Yes, for requests that were already pending. The approve dialog shows an advisory blackout flag among its policy checks, the approver decides, and approving over the flag is recorded in the audit trail.
How many blackout ranges can one leave type have?
Up to 20. Ranges cannot duplicate or overlap each other, and each leave type carries its own set, so a vacation freeze never touches other leave types.