Time-Out Zone

Company locations as the compliance baseline

Define offices and regions with country, state code, and timezone. Attach leave policies and holiday sets at the location level so distributed teams inherit the right baseline when nothing more specific is assigned.

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

Geography changes the floor

4 weeks

EU minimum paid annual leave under the Working Time Directive

0 days

US federal minimum for paid vacation (no FLSA floor)

24 days

German statutory minimum under BUrlG for a six-day week

9-13

statutory holidays in Germany, depending on the federal state

  • Legal leave floors and public holidays differ by country and state. Location is where Time-Out Zone stores that geographical baseline in the policy hierarchy.
  • Track a compliance minimum per location and compare it in the gap report. Tracking is not the same as blocking an under-minimum assignment.

EU Working Time Directive 2003/88/EC Art. 7; BUrlG section 3; Feiertagsgesetze der Laender. US: no federal paid-vacation mandate under the FLSA. Rounded.

Offices with country and timezone

Each location carries a name, ISO country, optional state or province code, and an IANA timezone derived from the country on create.

Lowest rung of the policy ladder

Effective policy walks employee, tag, team, department, then location last. Location is the geographical fallback when nothing higher wins.

Holiday set per location

Attach a holiday calendar to the location so employees who resolve there see the right non-working days.

Legal minimums you can track

Record minimum PTO days and a legal source per location, then use the compliance gap report to spot shortfalls. Time-Out Zone tracks; it does not block under-minimum policies.

The details, spelled out

Inherited when not set directly

An employee keeps at most one direct location. Otherwise location resolves employee, then team, then department.

People roster by effective location

Filter the People table and exports by the resolved hierarchy location, not only the raw column.

Archive first, delete when clear

Archiving or deleting is blocked while employees, departments, teams, or location policies still reference the location.

Timezone on the card

Location timezone is stored and shown. Cron and accrual date math still use the company timezone.

Values in the visuals are examples. Work schedules can also be assigned at the location level through the same hierarchy.

Hierarchy

The compliance baseline of the policy ladder

Geography is the last word, not the first.

  • Assign leave policies to a location as the fallback for everyone who resolves there when no user, tag, team, or department policy wins.
  • A location can carry one policy per leave type.
  • If no location exists anywhere in the chain and nothing higher wins, the resolver returns null with an honest empty state.

Holidays

One location, the right holidays

Regional calendars need a place to hang.

  • Attach a holiday set to each location (for example different German federal-state calendars).
  • Employees inherit that set through their effective location unless a team override wins.
  • Pair this page with Holidays and Calendars for import and day-counting detail.

Operations

Built for distributed teams

Assign, filter, retire safely.

  • Set location on invite, in the profile, from the location card, or via the CSV column "Location Name (optional)".
  • Filter People and reports by effective location across the org chain.
  • Archive when the location is empty of dependencies; permanent delete stays equally guarded.

More resources

Feature

Holidays & Calendars

Feature

Policy engine

Reference

Public holidays in Germany 2026

Ready to get started?

Give us a call. We'll set up two locations with different holiday calendars, assign a location policy, and show you how the hierarchy resolves it.

Holidays & Calendars

Maintain and import holiday sets.

Explore

Policy Engine

Define leave policies.

Explore

Frequently asked questions

What is a location in Time Out Zone?
A company site defined by name, country, optional state code, and timezone. It is the lowest-priority fallback for leave policies and the usual place to attach a holiday set in Time-Out Zone.
How do employees get a location?
Directly on the profile or invite, from the location card, or by matching the optional Location Name column on CSV import. If none is set, Time-Out Zone resolves employee, then team, then department.
Can different locations have different leave policies?
Yes. Location policies are the geographical fallback in the hierarchy User > Tag > Team > Department > Location. More specific assignments always win in Time-Out Zone.
How do I model holidays by German federal state?
Create a location with the state code, attach a holiday set that matches that Bundesland, and let employees inherit it through their effective location. Details of import and day counting live on the Holidays and Calendars page.
Does the system enforce legal minimum leave?
No. You can record a compliance minimum and source per location and review gaps in the compliance report. Time-Out Zone tracks those floors; it does not block an under-minimum policy assignment.