Policy writes the number.
Entitlement comes from company policy and tenure, including the country the person actually works in. Nobody types a balance to win an argument.
Part of Employee Management
The leave request that already knows the balance.
Entitlement comes from policy and tenure. Every movement sits on a ledger. Day counts respect her country’s public holidays. The moment leave is approved it appears wherever presence is shown.
- The balance is computed from policy and tenure. Nobody types it.
- The manager sees who else is away before they say yes.
- Public holidays for her country are skipped in the day count.
- Approval paints the calendar, the team view and Organo.
Your leave
- Annual leave14.5 remaining
- This request2 days, holiday skipped
- CoverKai Tanaka, informed
Current annual 14.5 days
Jawad Iqbal approvesHe sees who else is away first. Kai is covering.
The problem
Every leave request starts an argument about the balance.
Three versions of the truth.
The spreadsheet says 12 days, the manager remembers 9, and payroll deducted something else entirely. Every request begins with reconciliation instead of a decision.
Approvals made blind.
A manager says yes without seeing who else is away that week. The team finds the coverage gap on Monday morning, when it is too late to plan around it.
Patterns nobody catches.
Frequent short absences hide inside annual totals. By the time anyone notices, the pattern is a year old and the conversation is a difficult one.
How Leave fixes it
What Leave does on the connected record.
Balances calculated, never typed: entitlement derives from policy and tenure automatically, and every movement sits on a ledger you can audit
Country aware day counts: public holidays for each country are excluded from the day count, so the same week off deducts correctly wherever someone works
Carry over on autopilot: year end carry over is applied automatically under a cap, never unlimited, with every movement recorded on the ledger
Approvals with context: before you say yes, you see who else on the team is already away for the same dates
Cover while approvers are away: an approver can hand their queue to a named delegate for a set window, and the delegate sees their pending requests alongside them, so requests keep moving
Absence patterns surfaced: the Bradford factor reads frequent short absences early, with the working shown
Presence everywhere: approved leave updates the company calendar, team views and Organo the moment it is approved
Requests where people plan: drag a date range on the company calendar and the request form opens with the dates filled in
A real workflow
The life of one leave request.
- The request starts where planning happens.An employee asks from Leave, or drags a date range on the company calendar and the form opens with the dates filled in and a working day count that already excludes their country’s public holidays.
- The approver decides with context.Before saying yes, the manager sees who else on the team is away for the same dates. If the approver will be away themselves, they can set a delegate who sees their pending requests alongside them until they are back.
- Approval writes the ledger.The deduction is a ledger movement, not an edit to a number, so the balance can always show its working when someone questions it.
- Presence updates itself.Approved leave paints the company calendar, team views and Organo immediately, so cover is planned before Monday rather than discovered on it.
- The year end closes itself.Carry over applies automatically under a cap, so a balance can never grow without limit, and Bradford factor reads surface frequent short absences while the conversation is still an easy one.
One record. Nothing entered twice.
Leave does not live on an island.
Leave lives on the same record as everything else: approved leave feeds presence on Organo and the company calendar, day counts respect each country’s holiday calendar, and leave liability appears in Reports and Analytics without a separate export.
Why teams switch
A balance that can show its working.
Approvals see the week.
Before a manager says yes they see who else is away. Cover can be named. N/A is not promised a notification.
Presence updates itself.
Approved leave paints the company calendar, team views and Organo on that calendar day. A sticky status of on_leave is not what the chart reads.
Unused days come back.
Cancel all of a request or keep some days. Unused working days credit back. The request stays approved with a shorter end.
Already connected
The ledger is the only balance.
A deduction is a movement, not an edit. Cancel and shorten credit unused working days. Year end carry over applies under a cap. Payroll reads unpaid days from the same truth.
- Day counts skip weekends, public holidays and company holidays for that country.
- An approver who is away can name a delegate. The form says who will see the request before you type.
- You can cancel all days or keep some. The request stays approved with a shorter end. Unused working days return.
- Bradford factor names frequent short absences. The working is shown. It is a read, not a punishment.
Who it is for
The people who actually take and approve time off.
The employee
The person who asked.
Lina drags dates on the calendar. The form already knows the working day count, including Pakistan’s holidays if that is where she works.
A manager
The person who must decide.
He sees who else is away that week. Cover is named. He is not guessing Monday morning.
People
The person who set the policy.
Global or regional annual leave is the company’s figure. Provisioning no longer prefers a platform default over what you saved.
Payroll
The person who docks unpaid days.
Unpaid leave raises a durable input. It is not a number that lives only in the browser.
Keep reading
How time off should land.
Questions people actually ask.
Who writes the balance?
Policy and tenure, including the country the person works in. A typed number is not the source. The ledger is.
Does approved leave show on Organo and Company Calendar?
Yes. Approved leave covering the day paints on Organo and Company Calendar from the same ledger. Absent only means expected, no punch, and no approved leave.
Can I come back early?
Yes, on approved multi day leave. You pick the last day kept. Unused working days credit back. The request stays approved with a shorter end.
Does unpaid leave dock pay by itself?
It raises a durable unpaid_leave payroll input from the ledger. It is not a browser-only number that vanishes on reload.
Included with Employee ManagementLeave ships inside Employee Management at $5 per employee / mo · payroll included, with connected Organo included at no extra charge.Compare pricing →
More of Employee Management
The rest of the record.
Ready for leave
that lives on one record?
Leave arrives as part of Employee Management, connected to the same record every other module reads. Nothing to sync, nothing entered twice.
← Back to Employee Management