Leave types carry a stable key, labels in fourteen languages and a default annual allowance. Policies bind a type to a scope — the whole workspace, a department or a position — and where several policies match one person, the most specific wins.
Balances are not incremented and decremented; they are computed from the approved requests themselves, per employee, per type, per year, as allowance, used and pending. That is a deliberate design choice: a counter that is nudged up and down eventually disagrees with reality, and a computed one cannot.
Working days come from the calendar minus weekends and active holidays, and they are frozen at the moment a decision is made, so adding a company day off next month does not silently rewrite a request approved last week. Employees submit their own requests; managers can submit on behalf of someone; approvers see the whole timeline of submissions, edits, decisions and comments on every request.
Key Benefits
Leave types with allowances and labels in fourteen languages
Policies scoped to workspace, department or position
Balances computed, never incremented — they cannot drift
Working days frozen at decision time
Self-service requests plus manager-on-behalf submission
Month calendar of who is off, and an iCal feed for personal calendars
Use Cases
"Can I take that Friday?"
The calendar shows who else in the department is already off that week, so the answer takes a glance rather than an email thread.
Mid-year starter
The allowance prorates from the hire date, so their first-year entitlement is right without anyone reaching for a calculator.
Sick note attached
Supporting documents go on the request itself, where the approver and the audit trail can both see them.