Leave Management for Remote & Distributed Teams
Managing leave across timezones, countries, and public holidays is hard. Here's how remote and distributed teams track time off fairly — without the hallway.
In an office, you sort of know who's off. You see the empty desk, you overhear "I'm out Friday," you notice the lights off in the corner. None of that happens when your team is spread across four cities and three countries. Someone in Berlin books the week of a German public holiday your US lead has never heard of; two of your three engineers quietly take the same sprint off; a leave request sits unanswered because the approving manager is asleep when it lands.
Remote work doesn't create new leave problems so much as it removes the accidental safety nets that used to catch them. Here's what actually goes wrong on distributed teams, and how to fix it without micromanaging anyone's calendar.
Why leave is harder when you're distributed
The core issues are all the same theme: the informal signals are gone, and the rules are no longer the same for everyone.
- Different public holidays per country. A "company-wide" leave policy quietly assumes everyone shares a holiday calendar. They don't. Your Albanian, Polish, and US teammates each have their own statutory days — and someone has to track all of them correctly.
- Timezones break approvals. When the requester and the approver are eight hours apart, "quick approval" becomes a two-day round trip. Requests stall, plans get made anyway, and the process feels like theatre.
- No hallway visibility. You can't see who's out. So people book over each other, and a manager finds out a key person is away the morning a deadline is due.
- Fairness wobbles across locations. If one office's leave year starts in January and another's in April, or one location's holidays eat into a "shared" allowance and another's don't, people compare notes and (reasonably) feel hard done by.
- "Just ask in the team chat" doesn't scale. It works at five people. At twenty across timezones, requests scatter across DMs and threads with no record of who approved what.
None of this is a reason not to go remote. It's a reason to make leave explicit, visible, and async rather than relying on proximity.
Five practical fixes
1. Set public holidays per location, not per company. Each location should carry its own statutory holidays. Then a German teammate isn't burning annual leave on a day the business already treats as a holiday, and a US teammate isn't expected to be online on one. Browse the public holiday calendars for each country your people sit in so you're working from real dates, not memory.
2. Make every request and approval async by default. Don't require a live conversation to book a day off. A request goes in, the right manager approves it on their own schedule, and the system records it. No timezone tax.
3. Put availability on one shared calendar. The single biggest replacement for hallway visibility is a calendar everyone can see before they book. People self-resolve most clashes when they can simply look.
4. Write the policy down — and make it the same logic everywhere. Allowance, accrual, carry-over, and what counts as a working day per location. When the rules are explicit and applied consistently, "this isn't fair" conversations mostly evaporate.
5. Bring requests to where work already happens. Remote teams live in Slack or Teams. A leave request you can file and approve in chat — and a daily "who's out today" digest — closes the visibility gap without anyone opening another tab.
Async approvals: a simple flow
The goal is that no one is waiting on a human in another timezone to make a plan. A workable pattern:
- Requests can be submitted any time, from chat or the app.
- Each request routes to a named approver with a clear backup for when that manager is themselves away.
- Approvers get a target response window (e.g. two working days) so requests don't rot.
- Approve or decline asynchronously — no meeting required.
- Every decision is logged, so "who approved this?" always has an answer.
For more on keeping this even-handed across people and locations, see how to approve leave requests fairly.
Office-based vs. one-size-fits-all
Most leave tools assume one company = one set of rules. That falls apart the moment your people sit in different countries. The better model treats each office (or location) as its own unit:
| One-size-fits-all | Per-location model | |
|---|---|---|
| Public holidays | One shared list | Correct per country |
| Working days | Fixed Mon–Fri | Set per location |
| Timezone | Single, assumed | Per location |
| Leave-year start | One date for all | Per location |
| Fairness across sites | Hard to defend | Rules are explicit |
"Per-location" doesn't mean chaos — the logic (how allowance, accrual and carry-over work) stays consistent. Only the inputs that genuinely differ by place are allowed to differ.
A note on the legal side: statutory leave, public holidays, and notice rules vary widely by country, and remote employment can raise questions about which jurisdiction's rules apply. This is general guidance, not legal advice — check the rules where each person is actually employed.
How Absenca fits remote teams
Absenca is built around an office-based model, which maps cleanly onto distributed teams. Each office carries its own work days, timezone, public holidays, and leave-year start — so a Friday holiday in one country doesn't quietly distort balances in another. Public holidays are built in for 190 countries, and you can pull any location's calendar from the holidays pages.
Approvals route to the right manager and run asynchronously, with a full audit log — no one waits on a timezone. A shared leave calendar shows who's off across every office and department, so people see clashes before they book. And because remote teams live in chat, requests and approvals work directly in Slack and Microsoft Teams, with a daily "who's out" digest to replace the missing hallway.
It's free for up to 15 people (a real free tier, not a trial), then $0.75/user/month — which suits the lean, multi-country teams that go remote first.
Frequently asked questions
How do we handle different public holidays for each country? Give each location its own holiday calendar rather than forcing one shared list. Then statutory days are correct everywhere, and people in one country aren't expected to work — or spend annual leave — on another country's holidays. Absenca includes per-location holidays for 190 countries out of the box.
Do approvals have to be instant on a remote team? No — and trying to make them instant across timezones is what causes the friction. Treat approvals as async: requests can be filed any time, route to a named approver with a backup, and carry a clear response window. Decisions get logged either way.
How do we keep leave fair across locations? Keep the logic identical everywhere (how allowance, accrual and carry-over work) and only let genuinely local things — holidays, working days, timezone, leave-year start — differ by location. Writing the policy down and making availability visible removes most of the "that's not fair" friction.
What if our managers are in different timezones than their reports? That's the normal case remotely, and it's exactly why async approvals and a shared calendar matter. Managers approve on their own schedule, everyone can see availability without asking, and chat integrations surface requests where people already are.
Run leave across timezones without the chaos — Absenca gives each office its own holidays and rules, a shared calendar, and Slack/Teams approvals. Free for up to 15 people. Next, set up your shared team leave calendar.