Policy engine
Define leave policies once and let them cascade across the organization, with a clear precedence order that resolves exactly one effective policy for every employee.
How does Time-Out Zone resolve the effective policy?
Time-Out Zone resolves exactly one effective policy for each employee by applying a fixed precedence order. A direct assignment at the user level always wins. Tag-based rules come next, then team, then department, and finally location as the baseline. Location is the fallback layer for statutory minimums and applies only when no higher level sets a policy. This lets you define a baseline policy per location, refine it per department or team, and adjust individual people through tags or a direct assignment, without duplicating rules. Any change to a higher level automatically affects everyone who inherits its value. The resolved policy is transparent and traceable, so employees and admins can see which level contributed each value. The result is fewer manual edits and a predictable answer to the question of which rule applies to whom.
What the policy engine does
The engine separates the definition of a policy from its assignment. You maintain policies in one place and assign them to organizational levels or individual people. The effective policy per employee is computed from those assignments, not maintained by hand.
- One source of truth per policy, assignable many times.
- Inheritance across location, department, team, tag, and user.
- Changes at higher levels cascade automatically.
Precedence order
The order is fixed and predictable: user before tag before team before department before location. Location is the lowest level and serves as the compliance baseline for a region.
- User: direct assignment, highest priority.
- Tag: segmentation with replacement or additive mode.
- Team and department: organizational defaults.
- Location: statutory baseline and fallback.
Transparency and traceability
For each employee you can see which level contributed each value. That reduces back-and-forth and makes audits easier. TODO: verify the exact inheritance view presentation before publish.
Concept-level description of the inheritance logic. TODO: verify product UI naming and presentation before publish.
Frequently asked questions
- Which level wins in a conflict?
- A direct assignment at the user level always wins. After that the order is tag, team, department, and finally location.
- Is location an override level?
- No. Location is the fallback baseline for statutory minimums and applies only when no higher level sets a policy.
- What does additive tag mode mean?
- A tag can replace a policy or additively stack extra days on top of the inherited baseline. You choose the mode per assignment.
Related
See the policy engine in action
Explore the live demo to see how inheritance and effective policies resolve for each employee.
Last updated: