Time-Out Zone

Spending caps that pace time off across the year

Cap how much of a leave type can be used per month, quarter, or half-year, in days or as a share of the yearly allowance. Requests over the cap are blocked at submit, with existing bookings counted in, so the year never empties out in one season.

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

How time off actually gets spent: US and DACH

46%

of US workers with paid time off take less than they are offered

48%

of US workers say they will not use up their vacation days by year end

43%

of German employees used their full entitlement in 2025, the highest share in Europe

5 days

is the average unused remainder a German employee still holds at year end

  • In the US, no federal law paces how vacation is spent across the year. Employers set the rhythm, and a cap per month or quarter is how that rhythm gets enforced.
  • In Germany, when leave is split, one block of roughly two working weeks stays legally protected. Spending caps set a pace per period; they do not shorten how long one vacation can be.

Figures from public US and German workplace surveys and statutory frameworks, 2023 to 2025. Rounded.

A cap per period

Up to ten caps per leave type, each tied to a month, a quarter, or a half-year of the policy cycle. Set them once in the leave type wizard.

Days or a percentage

A cap is a fixed number of days or a share of the yearly allowance. Tenure-scaled policies save caps as percentages, so they follow each person's allocation.

Counts what is already booked

A new request is checked together with pending and approved requests in the same period, never in isolation.

Advisory at approval

Approvers see a spending limit flag on pending requests and can still approve. Approving over a flag is recorded in the audit trail.

The details, spelled out

Days or %

Fixed day caps or a percentage of the yearly allowance. A monthly percentage derives from one twelfth of the year.

Month, quarter, half-year

Periods follow the policy cycle, calendar or anniversary. Monthly caps apply to every calendar month.

Blocked at submit

Over-cap requests fail with a message that names the period, the usage, and the maximum, before they enter anyone's queue.

Audited overrides

When an approver accepts a flagged request, the override is written to the approval audit trail.

Values in the visuals are examples. Every cap, unit, and period is configurable per leave type.

Caps

Ten caps, one leave type

Each leave type carries its own set of spending caps, configured in the same wizard as its grant model.

  • Up to ten caps per type, and duplicate periods are rejected while you configure.
  • Holidays and non-working weekdays are not charged against a cap.
  • Half days and hourly requests count as fractions of a day, not as full days.

Periods

The policy cycle sets the clock

Caps are anchored to the same cycle that grants the time off, calendar or anniversary.

  • A monthly cap applies to every calendar month the request touches, and multi-month requests are split and checked month by month.
  • Quarter and half-year caps guard the first quarters or half-years of the cycle, where front-loading does the most damage.
  • Percentage caps are computed from the yearly allowance, so richer policies get proportionally larger caps.

At submit

Blocked where fixes are cheap

The check runs when the request is created, not days later in a queue.

  • Usage is cumulative: the new request plus everything pending or approved in the same period.
  • The rejection message names the period, the total usage, and the allowed maximum.
  • Editing a pending request re-runs the same check before the change can be saved.

At approval

Advisory, with a paper trail

Approvers keep their judgment; the system keeps the record.

  • Pending requests show a spending limit flag in the policy checks panel.
  • Approving over a flag stays possible and is recorded in the approval audit trail.
  • Unlimited leave types skip caps entirely: they already run on a guaranteed base plus manager-discretion overage.

More resources

Feature

Advance notice & waiting periods

Feature

Policy engine

Feature

Balance tracking

Ready to get started?

Give us a call. We'll model your busiest months and show how caps keep coverage without policing anyone.

Advance Notice & Waiting Periods

Notice and waiting rules, per leave type, blocked at submit.

Explore

Policy Engine

Leave policies per location, team, tag, or person.

Explore

Frequently asked questions

How much PTO can employees use at once?
As much as the leave type's spending caps allow in that period. Admins cap usage per month, quarter, or half-year, in days or as a percentage of the yearly allowance, and a request that would push the period over its cap is blocked at submit.
What is a PTO spending limit?
A per-leave-type cap on how much time off can be used within a period of the policy cycle. It paces consumption across the year, so one team or one season cannot absorb the whole allowance at once.
Can spending limits be a percentage instead of fixed days?
Yes. A cap can be a fixed number of days or a percentage of the yearly allowance. Policies with tenure-based allowances save caps as percentages, so the cap scales with each person's allocation.
Does a spending limit count requests that are already approved?
Yes. The check is cumulative: the new request is added to everything pending or approved in the same period before it is compared against the cap.
Can a manager approve a request over the spending limit?
Requests over the cap are blocked at submit, so they normally never reach a manager. When a pending request carries a spending limit flag, approving stays possible, and the override is recorded in the approval audit trail.