Last updated on October 14, 2026
Multi-State PTO Policy: Benchmarks and a Template for Setting PTO Across Locations
A multi-state PTO policy sets how much paid time off employees get, how they earn it and what carries over across states. We recommend one base policy with state and employee-group addenda.
An employee asking why a colleague gets five more days needs a better answer than "different office." About 77% of US multi-location companies with complete state information operate within one state. Across US companies offering PTO in two or more locations, about 69% have different PTO rules in at least two of them.
The six decisions below help you decide which differences to keep, then write them into a usable policy.
Decision 1: Which rules apply to each employee?
Map employees by work state and employee group before choosing an allowance. That 77% same-state finding suggests that differences between locations likely reflect employee groups as well as geography. Record office and field teams, union coverage, seniority tiers and remote arrangements so your policy can account for them.
Consider a 200-person company with office staff, field crews and remote employees across four states. Its employee map should show what HR needs to decide, not just where everyone sits.
| Work state | Employee group | Headcount | What HR needs to establish |
|---|---|---|---|
| New York | Office staff | 55 | Base vacation allowance, tenure tiers and the New York sick policy |
| New York | Field crew covered by a collective agreement | 35 | Leave terms in the agreement and how they interact with applicable requirements |
| Texas | Office staff | 30 | Whether the shared office allowance and earning method can apply unchanged |
| Texas | Field crew without a collective agreement | 40 | Whether any difference from office benefits is intentional and justified |
| California | Remote office staff | 25 | Which office benefits they share and which carryover and payout terms need a state addendum |
| Colorado | Remote office staff | 15 | Local requirements and the process for reviewing a move to another state |
Keep tenure and part-time status as fields within each group. A long-serving remote employee shouldn't lose a tenure benefit just because they work outside headquarters. A change in work state should trigger a policy review, not an automatic reset of their allowance.
The map gives HR a useful question for each difference: is it driven by work location, an agreement, an employee-group decision or tenure?
Use the employee's work location as the starting point for checking applicable rules. Our US leave-law pages cover each state; review contracts and local requirements too.
What if an employee works in two different states?
Record where they work, how often and whether the arrangement is temporary. Have HR or counsel determine the applicable requirements before assigning the policy. An office address alone won't answer a cross-state question.
Our recommendation: map state, group and headcount before writing the rules.
Decision 2: One PTO policy or one per state?
For a PTO policy for employees in multiple states, we'd usually choose a base policy plus addenda. Keep shared terms in one document, then record state or group exceptions separately. You can update shared terms once while keeping each exception visible.
For the 200-person company above, each approach creates a different maintenance job:
| Decision | One national policy | Base policy plus addenda | Separate policies |
|---|---|---|---|
| What employees read | The same policy, with any unavoidable local terms identified | The base policy and their applicable addenda | Their location or group's complete policy |
| Vacation allowance | Shared allowance and tenure tiers | Shared starting allowance, with documented group exceptions | Set independently for each group |
| Sick leave and carryover | Use terms that satisfy each applicable requirement; a larger allowance alone may not do that | Put local rules in the relevant state addendum | Maintain the rules in each policy |
| A change to the company benefit | Update the central policy and check local effects | Update the base; check addenda for conflicts | Find and update every affected version |
| A move between states | Review whether local requirements change | Change the state addendum while checking group and tenure terms | Reassign the policy and reconcile balances and benefits |
| Cost and fairness | Can mean extending more generous benefits company-wide | Makes targeted differences visible, but each needs a reason | Allows more variation, with more differences to explain |
| Best fit | A company committed to uniform benefits and willing to review the combined requirements | A company with a shared benefit structure and a manageable set of exceptions | Groups with substantially different agreements or benefit structures |
In this example, the base could cover the office allowance, monthly earning schedule, tenure tiers and request process. State addenda would hold local sick-leave and carryover terms. The New York field crew would also have the relevant agreement terms recorded. HR would then decide whether the Texas field crew needs a separate benefit arrangement at all.
Give each addendum an owner and effective date, and state which clause it replaces. "See local policy" is little help if nobody can find the current version.
A generous allowance alone doesn't settle sick-leave use, carryover or notice rules. Check those separately.
Floating holidays can accommodate different observances within a shared policy. For calendars and coverage, use our guide to managing leave from multiple locations.
Our recommendation: start with a base policy and add only the exceptions you can explain.
Decision 3: How much PTO should each location or group get?
Different PTO policies by location are easier to explain when allowances follow clearly defined employee groups. About 69% of US companies offering PTO in two or more locations have different PTO rules in at least two of them. The allowance differs most often, suggesting that companies need flexibility in how much time they provide even when the process stays consistent.
Common allowance splits include 15 versus 20 days, 10 versus 15 or 20, and 5 versus 10. The median gap is about 1.5x. These are configuration benchmarks, not recommended entitlements.
Some locations have zero configured allowance while another has a full allowance. Treat that as a tracking setup to investigate, not evidence that employees receive no vacation.
Can I have different PTO policies for different employees?
Generally, yes, subject to applicable laws and agreements. The FLSA does not itself require paid vacation; state rules and other obligations still need review (DOL). Define groups consistently and have HR check the distinctions. For tenure-based benefits, document the milestones; seniority entitlements can apply them automatically.
Our recommendation: write the reason beside each allowance difference and make it available to employees.
Decision 4: PTO vs. sick leave: one bank or separate balances?
We recommend a separate sick leave balance for most multi-state teams. A combined bank gives employees one balance to understand, but separate balances make sick-leave rules and reporting easier to review. About 57% of US companies offering sick leave in multiple locations configure different rules between them.
| Decision | Combined PTO bank | Separate sick leave bank |
|---|---|---|
| Simplicity | One balance | Two balances |
| State-rule checks | Check the whole policy against sick-leave requirements | Review the sick policy separately |
| Employee use | Vacation and sickness draw from the same bank | Sick leave doesn't reduce the vacation balance |
| Reporting | Requires clear records of sick-leave use | Categories are already distinct |
Configured sick allowances have a median of 5 days in California, New York, Texas, Florida, Georgia and Illinois, and 10 in Tennessee. Most are provided upfront; a common difference is zero versus 5 days.
Don't copy that median as a legal minimum. New York requires up to 56 hours of paid sick leave at employers with 100 or more employees, and 40 at those with 5 to 99.
Approval settings differ in about 26% of eligible US companies. Review what "approval" means for protected leave; it isn't the same as deciding whether a vacation request fits the schedule. See the location-specific sick-leave setup.
Our recommendation: keep sick leave in a separate balance, standardize how it's reported, and document local exceptions.
Decision 5: Should PTO accrue or be given upfront?
Choose one earning method wherever practical, even when allowances differ. Accrual schedules differ between locations in only about 16% of eligible US companies, compared with the much broader variation in PTO rules. Companies appear to vary how much people receive more often than how they earn it.
Accrual builds the balance over time. It gives you a gradual earning schedule for new hires, but employees need to understand when enough time will be available for a planned trip.
An upfront allowance makes the year's balance available at the start. It's easier to plan around, though you still need rules for midyear hires and departures. Neither method removes payout obligations.
Where schedules differ, the usual split is accrual versus upfront allocation. Some companies use different accrual frequencies. Use our guide to calculating PTO accrual and PTO accrual calculator to test the setup.
Our recommendation: use a shared earning method unless a legal or operational reason calls for an exception.
Decision 6: What carries over, and what gets paid out?
Decide carryover, accrual caps and separation payouts separately. Rollover caps differ between locations in about 32% of eligible US companies. A shared allowance therefore doesn't necessarily mean a shared year-end rule. Review each policy with finance and check the applicable state requirements before setting a cap or expiry date.
A rollover cap limits what moves into the next leave year. An accrual cap pauses further earning at a balance ceiling. They aren't interchangeable: California prohibits forfeiture of earned vacation but permits reasonable accrual caps. See the California example in our operations guide.
Payout requirements vary by state and agreement. Use the relevant state leave-law page to start the check.
Have finance model the outstanding balance under each option using the PTO liability calculator. Our leave-liability guide explains the exposure; accounting treatment needs its own review.
Our recommendation: document lawful carryover and payout rules per policy, then model their cost before rollout.
Write it down: multi-state PTO policy template
Use this as a drafting worksheet, not an adopted policy. Replace every bracketed field and have the completed policy and addenda reviewed before sharing them with employees.
Base policy
Purpose and scope: This policy explains paid time off for [covered employees]. Applicable state and employee-group addenda form part of it.
Eligibility: Groups are defined by [role, agreement, tenure or other reviewed criteria]. Eligibility begins [date or condition].
Work location: HR records each employee's work state and reviews changes before assigning a new policy.
Allowance: Eligible employees receive [days/hours] per [leave year]. Group differences appear in the addendum.
Earning method: Time is [provided upfront/accrued] at [rate and frequency]. Midyear hires receive [reviewed treatment].
Carryover: Unused time [carries over under these terms]. Any lawful cap or deadline is [terms]. Accrual pauses at [lawful balance ceiling, if used].
Sick leave: Sick leave is [separate/combined], with [allowance, permitted uses, earning and carryover terms] in the applicable addendum.
Floating holidays: Employees receive [allowance and use rules].
Requests: Submit requests through [channel] to [approver]. Protected leave follows [separate notice process]; routine vacation approval rules do not override legal rights.
Separation: Unused balances are handled under [reviewed state-specific payout terms].
Part-time work: Allowances use [reviewed proration method], subject to applicable minimums.
Review: [Owner] reviews the policy each January and when applicable requirements change.
State or group addendum
These are examples only, not legal recommendations. The company below chooses 15 vacation days for its base office tier, 20 after five years, monthly earning and a separate sick leave balance. The entries show how to record the decisions; state-specific terms still need review.
| Addendum or group | Vacation allowance and earning | Sick leave | Carryover and caps | Payout and administration notes |
|---|---|---|---|---|
| New York office staff | Base 15-day allowance, earned monthly | Separate New York policy | Record reviewed state terms and any additional company benefit | Link the approved payout clause; name the HR owner |
| New York field crew | Allowance and earning schedule from the reviewed collective agreement | Record the applicable agreement and statutory terms | Record the reviewed agreement and legal requirements | Identify the agreement version and who checks conflicts |
| Texas office staff | Same 15-day base and monthly method | Separate company policy, reviewed for applicable requirements | State the company's reviewed carryover rule | Record payout terms explicitly rather than leaving the field blank |
| Texas field crew | Same 15-day base unless HR approves a documented group difference | Same reporting process; record any justified benefit difference | Use the office rule unless a reviewed exception is needed | Name the group approver without changing the benefit by manager preference |
| California remote office staff | Same 15-day base and monthly method | Separate California policy | Preserve earned vacation; record any reasonable accrual cap | Attach the reviewed California payout clause |
| Colorado remote office staff | Same 15-day base and monthly method | Separate Colorado policy | Enter locally reviewed carryover and accrual-cap terms | Attach the reviewed payout clause and relocation process |
| Office staff with five years of service | 20 days, earned monthly; specify when the new rate starts | Keep the applicable state sick policy | Keep the applicable state rules; review any cap tied to allowance | Apply alongside the state addendum rather than replacing it |
| Part-time office staff | Prorate the base allowance using the documented work schedule | Check applicable sick-leave rules separately | Record the units and any reviewed cap | Specify how a schedule change affects future earning |
An employee can have more than one applicable row. A California remote employee with five years of service would use the 20-day tenure tier alongside the California terms. The tenure addendum changes the allowance; it doesn't replace the state addendum.
Before approving the document, test a new hire, a tenure anniversary, a part-time schedule change and an interstate transfer. For each one, check the allowance, earning rate, existing balance and separation treatment.
Use the leave policy generator for a starting draft and the prorated PTO calculator for allocation examples.
Before rollout:
Canada: setting vacation policy across provinces
Use a shared vacation policy with provincial or group addenda. About 62% of eligible Canadian companies configure different vacation rules between locations; 38% differ on sick leave. Accrual schedules differ in only 3%, while rollover caps differ in 21%.
About 56% keep locations within one province. Ontario appears in most multi-province setups.
Configured sick-day medians are 3 in Ontario, 5 in BC and Alberta, about 5 in Saskatchewan, and zero in Quebec. A zero setting does not establish an employee's entitlement or what another leave category covers.
For eligible employees, Ontario provides 3 unpaid sick days; BC provides 5 paid plus 3 unpaid. Alberta's 5 unpaid days cover personal and family responsibilities, not just sickness. Quebec's first 2 paid absence days are shared across specified reasons, including illness and family obligations. Eligibility conditions apply; primary sources are below.
Check our Canadian leave-law pages for Ontario, Quebec and BC. Confirm whether federal or provincial rules apply. Keep holiday-calendar differences separate from vacation allowances.
How Vacation Tracker handles PTO across locations
Vacation Tracker runs leave policies and approvals alongside the HRIS or payroll tool you already use. Employees request time off through Microsoft Teams, Slack or Google Workspace, with mobile apps available too.
Leave policies are configured per leave type and location: allowance, rollover, accrual and approval rules can differ. You can set accrual caps, carryover caps and expiry dates, plus quota resets by location fiscal year or employee anniversary. Location Admins manage their assigned locations.
The Complete plan includes accruals, accrual caps and seniority entitlements. Core supports up to 3 locations; compare the plans. Approved leave can sync to ADP Workforce Now.
Bring your base policy and exceptions to a demo to see how they'd be configured.
FAQs
How do I set a PTO policy for employees in multiple states?
Map employees by state and group, choose a shared policy structure, then decide allowances, sick leave, earning method and carryover. Record exceptions in addenda and test the settings before rollout.
Do I follow the employee's work state or headquarters?
Start the review with where the employee performs work. Don't assume headquarters determines the answer. For remote or cross-state arrangements, confirm the applicable requirements before assigning a policy.
How much do PTO allowances usually differ between locations?
The median allowance gap in our data is about 1.5x. Common splits include 15 versus 20 days and 10 versus 15 or 20. A zero configured allowance needs investigation; it doesn't prove employees receive no vacation.
Which states don't allow PTO to be forfeited or capped?
Forfeiture and accrual caps are different. California prohibits forfeiture of earned vacation but allows reasonable accrual caps. Check each state's rules rather than assuming a ban on forfeiture bans all caps.
How do I set vacation policy for Ontario, Quebec and BC?
Use a shared base and separate provincial addenda for vacation and sick leave terms. Check eligibility, vacation pay and carryover requirements for each province, and confirm whether federal employment standards apply instead.
Final thoughts
A useful multi-state PTO policy makes each employee's allowance clear and gives HR a manageable list of exceptions. Start with the base policy, write down why each group differs, and review the addenda before configuring the software.
Sources
Vacation Tracker product data (anonymized, 2025 to 2026). Aggregated configurations from US and Canadian paying customers with two or more locations, supplied in the approved brief. A company is eligible for a leave-type comparison if it offers that type in at least two locations; it counts as different if any two have different rules. Groups under five companies are suppressed. Worked examples are illustrative and do not describe individual customers.
Only policies edited since September 2024 are included. State or province is known for about 42% of US locations and 62% of Canadian locations. The same-state figure uses companies with every location's state known. Hours are converted at eight hours per day. These are configuration patterns, not legal entitlements or a compliance assessment.
Primary legal sources, last reviewed October 13, 2026:
- United States: DOL vacation leave, New York paid sick leave, California DIR vacation FAQ.
- Canada: Ontario sick leave, BC paid sick leave, Quebec illness and accident leave, Alberta personal and family responsibility leave.
Sidenote: The examples and template require review for your workforce and jurisdiction. Not legal advice.
Lav Crnobrnja
The COO and co-founder of Vacation Tracker. He loves sharing his knowledge and passion for startups, business, and AI. When he’s not working, he can often be found experimenting with AI agents and exploring what the latest technology can do.
