Time off, done right. From request to ledger.
Leave management for growing teams: realistic policies, approvals that route themselves and balances kept as a ledger — plus the people directory and org chart around them.
What waits on you, who's out today and what's left, on one page.
Who's out, team by team, with holidays, blackouts and a coverage row.
A directory everyone can browse: role, team, location and status.
Leave taken, liability, tenure and time to decision, by team and place.
- Ledger balances
Never stored — always the sum of the entries.
- Hour-accurate
Weekends and public holidays never cost a day.
- Audit trail
Every change with actor, target and time.
- Two-factor
Require it org-wide, on every plan.
1.0Policies & requests
Policies that match reality. Requests that compute themselves.
Set quotas per location, choose how balance is earned, and cap what carries over. Employees pick a type and dates; working days, holidays and the balance after are worked out before they submit.
Granted up front or accrued
Monthly, weekly, every two weeks or yearly, pro-rated for people who join mid-year.
Carryover with an expiry
“Up to 5 days carries over, expires Mar 31.” Year-end runs itself.
Hour-accurate
Weekends and public holidays never cost a day; half-days and custom hours are one click.
Blackouts and probation
Hard-block launch week or force manual approval, and keep a leave type off-limits during probation.
2.0Approvals & balances
Approvals that route themselves. Balances you can audit.
Build an approval chain once and attach it per policy; approvers get one queue, oldest first. Every balance is the sum of a ledger, so it can't drift and every change has an author and a time.
Multi-step chains
Up to ten steps: the direct manager, their manager, or a named person.
Delegation
Hand approvals to a substitute for a date range; requests reroute on their own.
Reminders and escalation
A stale step gets an email nudge, then escalates.
Reports finance trusts
Balances per leave type, leave liability in hours, and every request exportable to CSV.
How it works
Set the rules once. The rest runs itself.
Policies drive requests, requests drive approvals, approvals drive the ledger. Nothing is typed twice.
- 01
Set your policies
Per location and leave type: quota, accrual, carryover, and who approves.
- 02
People request in seconds
Pick a type, pick dates. Working days, holidays and the balance after are computed live.
- 03
Approve, and the ledger updates
Approval is the only thing that deducts. A balance is always the sum of its entries.
3.0Calendar & locations
See coverage before you approve. Built for more than one office.
One timeline per month with people grouped by department and a row counting who's out each day. Every location brings its own timezone, leave year, public holidays and policies.
Coverage row
People out per day, heat-shaded, with holidays and blackouts in their own lane.
Subscribe from your calendar
Approved leave in Google, Outlook or Apple Calendar, as “Out of office”.
A leave year per location
January in Athens, April in London: carryover and accrual follow the location.
Public holidays per location
Import a country's calendar in one click; holidays never draw from a balance.
4.0People
Everyone in one place. From first day to last.
A directory every member can browse and an org chart drawn from reporting lines, on top of the employee records HR keeps from someone's first day to their last.
Invite or import
Invite by email, keep records for people without a login, or bring everyone in from a CSV.
A scheduled last day
Set someone's last day ahead of time; their balances close out on the ledger when they leave.
Archived, not deleted
Leavers keep their history, and a rehire picks up the same record.
Single sign-onEnterprise
OpenID Connect or SAML 2.0 with your identity provider, verified domains and Require SSO.
The small things
Built for the people who run it. And everyone who uses it.
The details you notice on the hundredth day, not just the first — and what we're building next.
On the roadmapComing soon
See the roadmap- Documents
- Asset management
- Workflows
- AI assistant
- Access management
- API & webhooks
- MCP server
Changelog
Recently shipped
- Improved
Apply a policy change to balances already granted
Change a leave policy's allowance or pro-rating and you can now bring this year's balances in line, instead of waiting for the next leave year.
- New
Single sign-on with OIDC and SAML
Enterprise organizations can sign in with their identity provider, verify their domains, and require SSO for everyone on them.
- New
openbranchhq v1
The first public release: leave policies, hour-accurate requests, approval chains and ledger-backed balances, in the cloud.
FAQ
Frequently asked questions
Still have a question? Email us
Who is openbranchhq for?
Growing teams — roughly ten to a few hundred people — that have outgrown a spreadsheet for time off but don't want an HR suite. If you have more than one location, more than one approver, or a finance team that asks about leave liability, it's built for you.
How are balances calculated?
Every balance is the sum of a ledger: accruals, carryover, deductions, adjustments and expiries. Nothing stores a running total, so a balance can never disagree with its history. Everything is tracked in hours and shown in days or hours depending on the leave type.
Can I import existing employees and holidays?
Yes. Employees come in by CSV or by email invitation, and public holidays are imported per location by picking a country and a year.
What happens when someone leaves?
You schedule their last day, and from then on they show as leaving while they keep working normally. The night after it, their balances are closed out on the ledger, and once nothing blocks it they're archived, not deleted. If they come back, you rehire the same record.
Retire the leave spreadsheet. Start free today.
Set up a workspace in minutes. Your data stays yours: every leave request exports to CSV, any time.