It starts the same way every time. A U.S. manager approves a long weekend without blinking. Your employee in Toronto assumes public holiday rules will be handled correctly. Your new hire in Latin America asks a simple question about vacation accrual or payout on termination, and suddenly nobody is sure whether your “simple” PTO policy is legal, fair, or even readable.
That is the moment founders realize PTO is not a culture perk. It is an operations policy with legal consequences.
I've seen these policies fail from every angle. Vague language gives managers too much room to improvise. Rigid rules turn time off into a negotiation. “Unlimited” plans often produce the worst result of all: people take less leave, managers apply standards inconsistently, and HR ends up cleaning up the mess country by country.
The hard part is not writing a paragraph about rest and well-being. The hard part is building one policy that works for a team spread across the U.S., Canada, and Latin America, where vacation minimums, public holiday treatment, carryover rules, and termination payouts can differ a lot. A policy that looks tidy in a handbook can still blow up in payroll, employee relations, and compliance.
Single-country advice will not save you here.
If you are hiring across borders, your PTO policy needs to do three jobs well. It needs to set a fair baseline, respect local statutory rules, and give managers rules they can apply without Slacking legal every other Thursday. Pair it with a clear work from home policy example for distributed teams so leave rules and remote work rules do not contradict each other.
Good PTO policy design is boring in the right places. Clear definitions. Clean approval rules. No mystery math. No “manager discretion” doing all the heavy lifting. That is how you avoid resentment, payroll errors, and the classic spreadsheet called final_FINAL_v7 that tries to reconcile three countries' leave rules after the fact.
At some point, every founder opens a dozen PTO templates and realizes they all sound like they were written by people who've never had to approve a last-minute Friday absence before payroll closes.
One template says “employees may take reasonable leave.” Great. What's reasonable? Another says “unused time may be forfeited subject to applicable law.” Also great. Which law? Whose law? The employee's location or your HQ? That's how you end up with a handbook that looks polished and functions like a haunted house.
A template assumes your team works in one place, under one legal regime, with one leave culture. That fantasy lasts until your U.S. manager approves leave one way, your Canadian team expects something else, and your LATAM hires are operating under statutory rules your template never mentioned.
Your PTO policy isn't filler for the handbook. It's part of your operating system. It tells employees whether you trust them, whether managers have guardrails, and whether payroll can close the month without drama.
If you haven't already formalized your remote rules, pair your leave policy with a practical work from home policy example. PTO rules without expectations around availability, handoffs, and coverage are half a policy.
A useful PTO policy answers the questions people ask when things get inconvenient, not when things are calm.
Your team doesn't need a poetic policy. They need one that survives a resignation, a sick day, and a holiday crunch without Slack turning into a courtroom.
If your current document can't answer those four points in plain English, it's not a policy. It's décor.
There are three main models. All of them can work. All of them can also go sideways if you choose them for the wrong reason.
The wrong reason, by the way, is “this seems easiest.”
This is the all-in-one smoothie. Vacation, sick time, and personal days go into one bucket.
For a small company, this can be refreshingly simple. Employees like the flexibility. HR likes having fewer categories to track. Managers like not having to debate whether a dentist appointment is “personal” or “medical.”
The catch is that simplicity can hide real compliance issues when specific sick leave entitlements exist in a worker's location. It can also create weird behavior. Some employees will save the whole bank for vacation and then show up sick because they don't want to burn leisure time on a fever. Not exactly a leadership masterstroke.
This is the classic TV dinner. Not sexy, but reliable.
You separate vacation from sick leave and maybe personal days too. It's more admin. It's also cleaner when different types of leave have different legal treatment or different approval rules. For cross-border teams, this structure is often easier to defend because you can map mandatory sick leave and statutory vacation separately instead of pretending one giant bucket solves everything.
That doesn't mean employees love it. Separate buckets can feel stingy, especially if someone has plenty of vacation time but can't use it for a personal emergency because the categories are too rigid.
This is the one founders love to announce on LinkedIn and regret in operations.
In theory, unlimited PTO signals trust and reduces accrual administration. In practice, it often creates ambiguity. And ambiguity is where fairness goes to die. BambooHR notes that unlimited PTO can create a dual effect where autonomy improves wellbeing for some, while social pressure or fear of being seen as less committed suppresses leave-taking for others, sometimes resulting in employees taking less time off than under a traditional policy.
That tracks with real life. The extroverted senior employee takes a long break and posts beach photos. The junior employee stares at the policy, worries about optics, and takes three scattered days all year.
Practical rule: If you choose unlimited PTO, you still need guardrails. Minimum expectations for taking time off, approval workflows, coverage plans, and clear rules for consecutive days away.
If you're small and domestic, a PTO bank can work. If you're managing a global team, especially with LATAM hires, I'd usually pick traditional accrual with separate buckets where required by local rules.
Why? Because it's easier to administer fairly, easier to map to payroll, and easier to explain when someone asks the question every founder gets eventually: “Why does my leave work differently than theirs?”
Use unlimited PTO only when your management layer is disciplined, your culture supports taking leave, and your legal setup can handle country-specific overrides. Otherwise, you're not building a trust-based benefit. You're outsourcing policy risk to your employees.
Monday morning. Your California engineer resigns, your Toronto hire asks whether unused vacation carries over, and your new teammate in Latin America assumes your shiny U.S. PTO policy applies to them too. Same company, same Slack, three different legal answers. This is the part the generic templates skip.
If you hire across borders, one global PDF is not a policy. It is a misunderstanding waiting to hit payroll, termination, or both.
The federal U.S. baseline is loose. States are not. Some treat accrued vacation like earned wages, which means payout, forfeiture, and carryover rules can turn into a wage claim fast. A policy that feels neat in your handbook can get expensive the moment someone leaves, moves states, or challenges a denied payout.
If you employ workers in California or are trying to understand how paid holidays interact with private employment rules there, LA Law Group's private employers' holiday pay guide is a useful companion read. It shows how quickly a “simple PTO question” becomes a compensation issue.
Canada adds another layer. Provinces can set vacation minimums, accrual rules, and public holiday obligations differently. Then founders make the classic mistake and assume LATAM works like “Canada, but cheaper.” It does not. In much of Latin America, leave rights sit closer to statutory entitlements than company perks, and the gap between what your U.S. policy says and what local law expects can be wide.
A single PTO policy for U.S., Canadian, and Latin American employees should share principles, not identical terms.
Your principles can be universal. People should know how leave is requested, how approvals work, what coverage is expected, and who tracks balances. The legal terms should be local. Vacation minimums, sick leave treatment, public holidays, carryover limits, and termination payout rules often need country or province specific schedules.
That is the only version of fairness that survives contact with reality.
Founders usually get burned in one of two ways. They copy the U.S. handbook into every country and undercut local rights. Or they create a different policy for every hire and end up with an HR junk drawer nobody can explain. The fix is a core policy with local addenda.
Here's what causes trouble:
One more blunt point. LATAM hires deserve extra care here, as U.S. startups tend to get lazy in this regard. They call the policy “flexible,” skip the local schedule, and hope culture carries the day. Then someone takes protected leave, resigns with unused time, or asks why their statutory rights are missing from the handbook. Now your “simple benefit” is a compliance problem.
Build one framework. Localize the legal terms. Anything else is asking for a fight.
Your U.S. manager approves time off one way. Your Canadian employee assumes carryover works another way. Your hire in Colombia asks a completely reasonable question about unused leave, and suddenly three people are in Slack arguing over a policy nobody can explain.
That is a bad policy.
A PTO policy should read like operating instructions. Clear inputs, clear rules, clear outcomes. If a manager needs HR to decode every paragraph, you did not write a policy. You wrote future conflict.
Start with the rules people need on day one.
Eligibility
Say who gets PTO, when it starts, and whether part-time staff are prorated. If different countries follow different schedules, say that plainly and point to the local addendum.
How time is earned
State whether PTO accrues each pay period, monthly, or is granted upfront. Employees should not need a spreadsheet to figure out whether they have Friday off.
Carryover
Write the cap, the deadline, and any exceptions. “Company discretion” is not a rule. It is a fight waiting to happen.
How requests work
Explain where requests are submitted, how much notice you expect, who approves them, and what happens in emergencies. If managers can deny requests for coverage reasons, say so and define the standard.
What happens when someone leaves
Spell out how unused balances are treated based on work location and local rules. This clause gets expensive fast, especially across borders.
What happens if someone relocates
Include one sentence on country moves. If an employee changes work location, their leave treatment may change from the effective date of the move. For global teams, that sentence saves a lot of nonsense.
Fancy wording does not make a policy safer. It makes it easier to misunderstand.
Keep the sentence structure boring. Put one rule in each sentence. Use the same terms every time. If you call it “vacation” in one paragraph and “annual leave” in another, somebody will assume they mean different things.
Here's the difference:
Bad: “Employees may be eligible to utilize accrued leave in accordance with managerial discretion and operational necessity.”
Better: “Employees request vacation in the HR system. Managers approve requests based on team coverage and request order.”
Bad: “Unused balances may be treated according to applicable separation provisions.”
Better: “When employment ends, unused vacation is paid out or forfeited based on the employee's work location and local policy.”
Bad: “The company reserves the right to modify leave administration practices.”
Better: “The company may update this policy. No update reduces any right required by local law.”
That last line matters for global teams. One plain sentence can stop a U.S.-written handbook from sounding like it overrides local rights in Canada or LATAM.
Draft for the ugly cases. New hire starts in the middle of a month. A manager hoards approvals until the week before Christmas. An employee transfers from Texas to Mexico. Someone resigns with unused time and payroll has no idea what balance is payable.
Those are not edge cases. Those are normal operations once you hire across borders.
My recommendation is simple. Keep the main policy short, then attach local schedules that show country-specific rules in plain English. The core document should explain how your company handles requests, approvals, scheduling conflicts, and recordkeeping. The local schedule should explain what changes by work location. If you need a system for tracking those differences without turning HR into a help desk, set up a clear leave management process for global teams.
One last rule. If a manager cannot explain the policy from memory in under a minute, rewrite it. Shorter wins. Clearer wins. And for US, Canadian, and Latin American teams sharing one handbook, clarity is not a nice touch. It is how you keep a fair policy from becoming a cross-border mess.
Here's where a fair PTO policy usually falls apart. A U.S. employee accrues one way, your Canadian hire expects a different carryover rule, your team member in Latin America has statutory vacation rights you cannot paper over, and payroll still wants one neat formula.
If you force one global math model onto everyone, you create two problems at once. The policy feels arbitrary to employees, and compliance turns into cleanup work.
Use one default accrual method across the company unless local law requires something else. My vote is monthly accrual for global teams. Employees understand it, HR can audit it, and finance can forecast it without playing detective.
Tenure-based increases are common. As noted earlier, many employers use PTO as a retention ladder, with higher balances earned over time. Fine. Do that if you want. Just do not create five tiers, three exceptions, and a footnote nobody can calculate without a spreadsheet.
These are the only three methods worth considering:
For a U.S., Canada, and LATAM team, monthly accrual usually causes the fewest operational headaches. It also avoids weird conversations when pay frequencies differ by country.
Here's a plain example. Say an employee gets 15 days per year. That is 1.25 days per month.
| Month | Hours Accrued This Period | Total Accrued Year-to-Date (Hours) | Total Accrued Year-to-Date (Days) |
|---|---|---|---|
| Month 1 | 10 | 10 | 1.25 |
| Month 2 | 10 | 20 | 2.5 |
| Month 3 | 10 | 30 | 3.75 |
| Month 4 | 10 | 40 | 5 |
Boring math is good math. Boring math survives audits, manager turnover, and year-end payroll panic.
I do not recommend unlimited carryover. It piles up liability, encourages hoarding, and creates the annual drama where someone tries to disappear for four weeks during your busiest month.
Set three rules in writing:
That third point matters more than founders think. Some countries treat accrued vacation as a protected entitlement, not a nice company benefit you can trim with a handbook update. This protection makes global PTO policies expensive. The U.S. instinct is often, “just set a forfeiture rule.” Try that carelessly with LATAM hires and you can end up owing back pay, penalties, or both.
So keep the formula global where you can, and keep the exceptions local where you must. Track balances by work location, not by manager preference. If your current setup still relies on spreadsheets and memory, build a proper leave management system for global teams.
If an employee asks, “How much PTO do I have?” and your team needs to check payroll, Slack, and two spreadsheets, your policy is broken.
Fix the math before the math humiliates you.
A PTO policy rollout is not an HR announcement. It's a trust event.
If employees hear “we updated the policy” and immediately assume they're losing flexibility, you already lost the room. And if managers can't explain the new rules consistently, they'll improvise. Improvisation is fun in jazz. Less so in leave administration.
Treat rollout in layers.
First, send a short announcement that explains what changed, why it changed, and when it takes effect. No one wants a six-paragraph legal memo in their inbox.
Second, hold a live session. Let people ask the uncomfortable questions out loud. “What happens to my current balance?” “Can my manager deny leave in busy periods?” “Does this work differently by country?” If you don't answer those publicly, your managers will answer them privately and inconsistently.
This part gets skipped all the time. Big mistake.
A long-run study using 18 years of data and more than 32,000 observations found that 11+ paid days off produced the strongest retention effect, according to Florida Atlantic University's summary. But the same source makes the more useful operational point: this only works if employees use the time, and the bottleneck is often friction around taking leave.
So train managers on three things:
Don't announce a generous policy and then reward the people who never unplug. Your employees notice that contradiction immediately.
The handbook matters. The system matters more.
Update your HRIS, payroll rules, onboarding docs, and manager one-pagers at the same time. If the policy says one thing and the request tool shows another, employees will trust the tool. They should. It's the thing denying their request.
And yes, tools can help here. Platforms like HRIS suites, payroll systems, or cross-border hiring providers such as LatHire can support leave administration alongside payroll, contracts, and local employment workflows. The point isn't which logo you pick. The point is getting the rule out of static docs and into the system people use.
The edge cases are where paid time off policies stop sounding elegant and start sounding expensive.
If local law requires it, yes. If it doesn't, you still need a deliberate rule. I prefer prorated eligibility over vague exceptions because vague exceptions become manager favoritism in a hoodie.
Don't lazily copy employee PTO into contractor agreements and assume that's harmless. Contractors usually need different treatment, and local classification rules matter. Keep contractor time-off expectations separate from employee statutory or accrued leave.
Maybe. That answer annoys everyone, but it's the honest one. It depends on the employee's work location, your policy structure, and whether accrued vacation is treated like earned wages there. This is exactly why payout language belongs in the policy and in your offboarding checklist.
That's not a policy problem. That's a workload and management problem.
In a 2025 FlexJobs survey of 3,063 U.S. workers, 23% said they did not take a single vacation day in the previous year, and the biggest barriers were heavy workload at 43%, fear of falling behind at 30%, and guilt or pressure to appear committed at 29% according to FlexJobs' PTO survey summary.
So fix the actual blockers:
PTO isn't successful because it exists in a handbook. It's successful when people can take it without feeling they're creating a mess for themselves or their team.
Paid time off policies should do three jobs well. They should make expectations obvious, keep you compliant across locations, and help people rest. If your current policy only does one of those, it needs work. If it does none, congratulations, you own a very official-looking problem.
