Leave management gets more complicated the moment a team stops sharing an office. When people work from different locations, sometimes different time zones and different countries, the questions multiply. Whose public holidays apply? Does the work from home policy interact with PTO? How do you even know someone is out if you cannot see their desk?
The leave rules built for a single-office setup do not transfer cleanly to distributed teams. What follows is the practical side: building a policy that holds up across jurisdictions, setting up the approval workflow, and making sure the whole thing does not quietly fall apart over a quarter.
What leave management actually involves
Leave management is how a company tracks, approves, and records employee time off. PTO, sick days, parental leave, bereavement, jury duty, unpaid leave, all of it.
For a single-site team, this is fairly simple. One set of holidays, one set of local labor laws, one manager who can see that the office is half empty on a Friday.
For distributed teams, those assumptions fall apart:
- Employees in different states or countries have different legal leave entitlements
- Public holiday calendars do not match across locations
- Managers cannot visually assess who is available
- Leave requests may arrive outside the approver’s working hours
- Payroll may need to handle multiple accrual rules at once
The goal stays the same regardless of team structure: people take the time off they are entitled to, the team can still function while they are out, and the company stays compliant. The execution just requires more structure when people are spread out.
Why this is harder for distributed teams
Multiple legal jurisdictions
A five-person team with members in California, New York, Texas, and two European countries is subject to at least five different leave frameworks.
In the United States alone, there is no federal mandate for paid vacation or paid sick leave. The Family and Medical Leave Act (FMLA) provides up to 12 weeks of unpaid, job-protected leave, but only for employers with 50 or more employees within a 75-mile radius. On top of that, 15 states plus Washington D.C. and several cities have mandatory paid sick leave laws, each with different accrual rates, caps, and carryover rules (National Conference of State Legislatures, 2025 data).
In the European Union, the Working Time Directive guarantees at least 20 paid vacation days per year. Individual countries go further: France mandates 25, Germany averages 30 in practice (statutory minimum is 20), and the United Kingdom requires 28 including public holidays (Eurofound, 2024 data).
A single company-wide “15 days PTO” policy may violate local law in half the locations where your employees sit.
Timezone and availability gaps
When a team member in London takes a bank holiday, their counterpart in Los Angeles may not know about it until they send a message into the void at 9am Pacific. This shows up as missed deadlines and slow client responses, not as something anyone planned for.
The reverse is just as bad. American holidays like Thanksgiving mean nothing in European calendars. Without a shared visibility system, teams discover the gap after it causes a problem.
Invisible absence patterns
In an office, a manager notices when someone has been out three Mondays in a row. On a remote team, that pattern goes undetected unless it shows up in data. Chronic absenteeism can signal disengagement or burnout, and uneven absence distribution quietly overloads the people who are always present.
How to build a leave policy for distributed teams
Step 1. Map every jurisdiction
Before writing any policy language, list every state and country where your team members are based. For each, document:
- Statutory minimum paid vacation days
- Mandatory sick leave (accrual rate, annual cap, carryover rules)
- Protected leave categories (FMLA equivalent, parental leave, bereavement)
- Public holidays
- Restrictions on use-it-or-lose-it policies or PTO payout at separation
Your policy can be more generous than local law. It cannot be less.
Step 2. Decide on a policy structure
Three approaches show up most often:
Location-based policies. Each employee gets the leave entitlements their jurisdiction requires, plus whatever the company adds on top. An employee in France gets 25 vacation days. An employee in Texas gets whatever your company policy says, since Texas has no state-mandated paid leave. Most compliant, most complex to administer.
Unified global floor. One PTO allowance that meets or exceeds the most generous jurisdiction. Say, 25 paid vacation days for everyone regardless of location. Easy to communicate. Expensive if your team spans locations with very different baselines.
Regional tiers. Group locations into regions (Americas, EMEA, APAC) and set a leave package for each. A middle ground between compliance and simplicity.
Whichever you choose, write it down clearly. Ambiguity is what creates complaints and inconsistent treatment.
Step 3. Set up a leave request and approval workflow
For distributed teams, the workflow matters more because you cannot tap someone on the shoulder.
Define where employees submit requests (a leave management tool, not email or Slack), how far in advance they need to request planned leave (two weeks for vacations is standard; same day for sick leave), who approves, what happens if the approver is also out, and the maximum turnaround time for approval. 24 to 48 hours is reasonable.
Manual approval chains break down across time zones. Automate what you can.
Step 4. Create a shared availability calendar
Every approved leave should automatically appear on a team calendar that everyone can see. The calendar shows who is out, what type of leave (without revealing medical details), location-specific public holidays, and upcoming approved leave for the next four to eight weeks.
Without this, teams end up doing leave management informally: asking around, checking Slack statuses, guessing. It sounds trivial, but it is the operational step that prevents most of the confusion.
Step 5. Handle public holidays by location
A company with employees in the US, UK, and India has three completely different public holiday calendars. Most distributed teams get tripped up here.
Options:
- Grant each employee the public holidays of their work location. On any given holiday, only part of the team is off. Most compliant.
- Offer a “floating holiday” pool. Everyone gets a fixed number of floating days and applies them to their own local holidays. Useful when holiday counts vary a lot. India has 15 to 20 national and state holidays per year; the US federal calendar has 11.
- Combine both: a few universal company holidays (New Year’s Day and one winter holiday, say) plus floating days for the rest.
Put every location’s holiday calendar into the shared availability system. “I did not know it was a holiday in Germany” is a planning failure.
Step 6. Track and audit
Review leave data quarterly:
- Are accrual balances accurate, especially for employees with mid-year start dates or part-time schedules?
- Is anyone accumulating a large unused balance? This could mean understaffing, a culture that discourages time off, or a growing liability
- Are absence rates even across the team, or are certain locations or roles absorbing more than their share?
- Are you compliant everywhere? Laws change. Colorado expanded its paid sick leave rules in 2024. New York City updated its safe and sick time accruals. If you are not watching for legislative changes, you are guessing at compliance.
Leave accrual math for distributed teams
Accrual is where leave management turns into arithmetic, and where most spreadsheet-based systems start to crack.
The most common PTO accrual method in the US is per-pay-period accrual. If an employee earns 15 PTO days per year and is paid biweekly (26 pay periods):
| Calculation | Result |
|---|---|
| Annual PTO entitlement | 15 days x 8 hours = 120 hours |
| Per-period accrual (biweekly) | 120 hours / 26 pay periods = 4.62 hours |
| Part-time adjustment (24 h/week, 60%) | 4.62 x 0.6 = 2.77 hours per pay period |
In the EU, accrual works differently. In France, an employee who joins on April 1 earns 2.5 days per month worked, reaching the full 25 days after 10 months. Statutory carryover rules vary by country.
Every jurisdiction you add makes the math harder. Somewhere between 10 and 25 employees, most distributed teams move from spreadsheets to leave management software just to keep up.
Common leave management mistakes in remote teams
Applying a single PTO policy globally without checking local law. “Unlimited PTO” is popular in US startups but may not comply with accrual requirements in states like California or in EU countries where employees must receive a minimum number of mandated days. A Mercer 2024 survey across the US, UK, Ireland, and Singapore found that 82% of workers reported feeling at risk of burnout, which suggests that generous-sounding policies do not always translate to people actually resting.
Not tracking time off at all. Some remote teams run on a “just let your manager know” basis. That works until there is a payroll dispute, a compliance audit, or a termination where accrued PTO has to be paid out. In California, Colorado, Illinois, Massachusetts, and several other US states, accrued vacation is classified as earned wages and must be paid at separation.
Ignoring timezone overlap when approving leave. Approving PTO for three people on a five-person cross-timezone team without checking whether anyone remains available during the overlap window is a scheduling failure. It just shows up as missed deadlines instead of a leave management problem.
Treating remote and office employees differently. If in-office employees get casual flexibility (“just leave early”) while remote employees must formally request every hour, you have a consistency problem and possibly legal exposure. Same rules for everyone.
Track team availability and manage leave with actiPLANS
actiPLANS handles the operational side of leave management for distributed teams. Employees request leave through the system, managers approve from wherever they are, and the shared timeline shows who is out, who is scheduled to be out, and how much PTO each person has left.
Leave balances update automatically based on the accrual rules you configure. Location tracking shows who is working remotely versus in the office on any given day, which matters when you need to assess coverage across locations. Reports export to CSV for quarterly audits, payroll reconciliation, or board reporting.
FAQ
What is leave management?
Leave management is how a company tracks, approves, and records employee time off across all leave types: PTO, sick leave, parental leave, public holidays, and unpaid leave. For distributed teams, it also means handling multiple legal jurisdictions and maintaining shared visibility across time zones.
How do you manage leave for employees in different countries?
Map the legal leave requirements in every country where you have employees. Build a policy that meets or exceeds each local minimum. Use a centralized system that supports multiple accrual rules and holiday calendars. Review compliance quarterly, because labor laws change and the penalties for getting it wrong are real.
What is the difference between leave management and absence management?
The terms overlap. In practice, “leave management” tends to mean planned time off (PTO, vacation, scheduled medical leave) while “absence management” also covers unplanned absences like sick days and no-shows. Most systems handle both.
How many PTO days should a remote company offer?
No single number works for everyone. In the United States, private industry workers with one year of service average 11 PTO days, rising to 15 after five years and 20 after 20 years (Bureau of Labor Statistics, 2024 data). Companies with employees in the EU usually find that the statutory minimum of 20 days or more sets the practical floor for the whole organization.
Is unlimited PTO a good policy for remote teams?
It depends on where your employees are and how your company handles time off in practice. Unlimited PTO eliminates accrual tracking but creates problems in jurisdictions that require payout of accrued time at separation (California, Colorado, and others). It also tends to result in people taking less time off, not more. A 2023 Namely analysis found that employees under unlimited PTO plans took an average of 12.1 days per year versus 11.3 for traditional plans.
Do remote employees accrue PTO the same way as office employees?
Yes. Work location does not change accrual rates or legal entitlements. A remote employee in California accrues leave under California law regardless of where the company is headquartered. The jurisdiction that applies is determined by the employee’s work location, not the employer’s.
How do you handle public holidays for a globally distributed team?
Grant each employee the public holidays of their work location, offer a pool of floating holidays employees assign to their own calendar, or combine a few universal company holidays with floating days. Whatever you pick, put it in writing and put every location’s calendar into a shared system.
What should a leave management policy include?
Leave types offered, accrual rates and schedules, the request and approval process, advance notice requirements, carryover and forfeiture rules, payout terms at separation, public holiday treatment, and a compliance statement for each jurisdiction that applies. For distributed teams, also cover timezone coverage expectations and location-specific entitlements.
Related content on this blog:
