Time-Out Zone

Team management software built for time off

Model departments with accountable heads, nest teams under them or keep teams standalone, and let leave policies, holidays, and calendars flow down the structure to every member.

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

Almost everyone works in more than one team

84%

of US employees work on multiple teams at least some of the time

5

levels policies flow through: person, tag, team, department, location

1

primary functional team decides the policy when someone is on several

2

kinds of teams: functional carries policy, project is reporting only

  • Gallup calls it matrixed work: nearly everyone sits on more than one team. The structure here answers the question that matters for leave, which team's policy applies.
  • A department head is required on every department, so approvals and accountability never dangle.

Gallup survey of 4,000 US workers (reported 2016; cited by McKinsey, "Revisiting the matrix organization"). Product values are current behavior.

Departments with a named head

Every department carries a required head of department and an optional location. Names are unique per company and the structure stays deliberately flat.

Functional teams carry the policy

A functional team can hold leave policies, a location override, and its own holiday calendar, and its members inherit all of it.

Project teams stay lightweight

Mark a team as a project team and it becomes membership for reporting only: no leave policy, no approver authority, safe for temporary groupings.

Policy flows down the structure

Effective policy resolves person, then tag, then team, then department, then location. The org structure is the spine that makes inheritance predictable.

The details, spelled out

Teams without a department

Standalone teams configure their defaults directly and require a named approver up front.

A head on every department

Department heads are mandatory and serve as the accountability and approval fallback for their people.

Calendars that follow the org

Filter the admin calendar by company, department, or team; managers get calendars scoped to the teams they lead.

Archive first, restore any time

Departments and teams archive instead of vanishing, with an inactive lane and one-click restore.

Values in the visuals are examples. Moving a team to another department or location recalculates member balances automatically.

Structure

Built to answer "whose policy applies"

Flat on purpose, precise where it counts.

  • Departments hold teams; teams hold members; standalone teams work without a department.
  • When someone is on several functional teams, one primary functional team decides the policy.
  • Assign policies, holiday calendars, work schedules, and tags at each level from the same rows.

Team kinds

Functional and project, told apart honestly

One switch, very different behavior.

  • Functional teams carry leave policy, deputies, and inheritance; project teams are reporting-only membership.
  • The system refuses to assign a policy to a project team instead of silently ignoring it.
  • Team edit views show inheritance explicitly, so overrides are visible instead of surprising.

Views

Calendars and rosters that follow the structure

Scope is a first-class filter.

  • The admin calendar scopes to the whole company, one department, or one team.
  • Managers get a Team tab and calendar for exactly the teams they lead or deputize.
  • Employees see their own team's who's-out view; org health counts headcount and out-today per unit.

More resources

Feature

Policy engine

Feature

Deputy approvers

Feature

Multi-step approvals

Ready to get started?

Give us a call. We'll model a department with two teams, attach a policy, and show you the inheritance landing on every member.

Policy Engine

Define leave policies.

Explore

Work Schedules

Set working days per level.

Explore

Frequently asked questions

What is the difference between a department and a team?
Departments are the top structural unit, each with a required head and optional location. Teams live inside a department or standalone, hold the members, and can carry leave policies. In Time-Out Zone policy inheritance runs person, tag, team, department, then location.
Can a team exist without a department?
Yes. Standalone teams are a first-class concept with their own section in settings. They configure defaults directly, require a named approver at creation, and can be moved into a department later. Time-Out Zone treats them exactly like nested teams for policy resolution.
What is a functional team versus a project team?
Functional teams carry leave policies, deputies, and inheritance; project teams are membership for reporting only and refuse policy assignment. When people join several functional teams, Time-Out Zone uses their primary functional team to decide which policy applies.
Who can edit the org structure?
Admins and owners create, edit, archive, and restore departments and teams. Managers get read access plus team-scoped views and approvals for the teams they lead; they cannot change the structure itself. Time-Out Zone enforces this through database-backed permissions.
Does moving a team break existing balances?
No. Moving a team into another department or location, or changing its holiday calendar, triggers an automatic balance recalculation for its members, so entitlements and counts follow the new inheritance in Time-Out Zone without manual fixes.
Is there an org chart view?
Not a visual chart. The structure is managed as expandable department and team rows with search, location filters, and an inactive lane. What Time-Out Zone optimizes for is inheritance and calendars that follow the structure, not drag-and-drop org drawing.