Overview
A holiday policy turns “we’ll figure it out” into an agreed set of rules employees and managers can rely on. It defines what qualifies as paid holiday time off, which location’s calendar applies, how substitute (observed) days are treated, and how the organisation plans continuity when some regions are offline.
For organisations with multiple countries, the policy also needs to do something more subtle: make equal treatment visible. When rules are implicit, employees can end up negotiating for time off, and those negotiations tend to be uneven.
This guide is a practical framework you can adapt. It is written to help you make decisions once, document them clearly, and implement them in systems so the policy works day-to-day.
Why holiday policy is a high-impact document
It prevents predictable operational friction
Holiday confusion usually shows up as avoidable rescheduling, blocked approvals, or deadlines built around an assumed “normal working week” that only fits one region.
It reduces uneven workload
When holidays differ by location, some employees will be online while others are not. A good policy makes the plan for that reality explicit so continuity does not default to whoever is available.
It protects legal and contractual commitments
In many jurisdictions, statutory holidays and substitute days have specific rules. A policy does not replace local obligations, but it can ensure the company’s practice does not accidentally conflict with them.
Establish scope (who the policy applies to)
Employment types
State whether the holiday policy covers employees only, or also applies to contractors and temporary staff. If employment types are treated differently, keep that distinction explicit so people do not assume identical entitlements.
Locations and eligibility
Define where the policy applies: every country where you employ people, or only certain entities. This matters for organisations with multiple legal employers, acquisitions, or employees hired through different arrangements.
Define key terms so the rules are testable
Public holiday
Use this for government-recognised holidays in an employee’s applicable country or region.
Company holiday (closure day)
Use this for a day the company chooses to close or treat as paid time off regardless of local public holiday status.
Observed (substitute) day
Use this for a weekday off that replaces a public holiday falling on a weekend, where local practice or law recognises a substitute day.
Home location
Use this for the policy-defined anchor that determines which holiday calendar applies to a person.
Floating holiday
Use this for paid time off that employees can use for personal observances not covered by their public holiday calendar.
Bridge day
Use this for a workday between a holiday and a weekend (or between two holidays) where employees may request time off and where coverage planning may be needed.
Decide what determines an employee’s holiday calendar
Option 1: Payroll/tax location
Basing holidays on payroll and tax reporting location often aligns with statutory entitlements and reduces compliance risk. This approach is also easier to administer across the year because it is tied to the employment record.
Option 2: Current residence
Basing holidays on residence can match everyday closures and family schedules, which can improve practicality for employees. If you use residence, you’ll need a rule for when changes take effect so frequent travel does not create constant calendar changes.
Option 3: Declared home base
For globally mobile roles, a declared base can create stability. It works best when you define how the base is chosen and how often it can be updated.
A simple principle to document
Choose a single default and then document the narrow circumstances where an exception is allowed. This keeps the policy consistent while still handling predictable edge cases.
Choose a paid-holiday structure
Most organisations use one of the following structures. The best fit depends on how distributed your workforce is, how much shared downtime you want, and what your operational coverage requirements look like.
Structure A: Location-based public holidays
Employees receive paid holidays based on their applicable country and region. This aligns with local closures and norms without requiring the company to maintain a single “global list.”
Trade-offs to consider:
- Calendar accuracy becomes critical, especially for regional holidays.
- Cross-region coordination needs working norms because teams will not share the same non-working days.
Structure B: Company-wide holiday list
The company defines one list of holidays that applies to everyone. This can create a consistent rhythm, but it can also misalign with local closures.
Trade-offs to consider:
- Some employees may need to use other leave types for locally significant dates.
- A single list can create perceived cultural bias if it mirrors one country’s calendar.
Structure C: Shared closure days plus local public holidays
The company chooses a small number of closure days (often tied to business rhythms) and also recognises local public holidays. This can reduce coordination effort by creating a limited number of predictable quiet periods.
Trade-offs to consider:
- Total paid holiday days can vary across locations unless you set a balancing rule.
Structure D: Fixed holiday-day allowance (calendar-agnostic)
The company provides a fixed number of paid holiday days and employees choose when to use them. This approach can simplify administration across many locations, but it must be compatible with statutory public holiday obligations where they exist.
Trade-offs to consider:
- You may still need separate handling for statutory public holidays depending on jurisdiction.
Define observed-day and weekend rules
Your policy should include one clear rule for how you handle fixed-date holidays that land on weekends. Employees should be able to predict their entitlement for a given year without asking a manager.
Common approaches include:
- Following the local substitute-day convention for the employee’s applicable calendar.
- Treating the fixed-date holiday as the holiday regardless of weekend placement.
If you operate across many jurisdictions, the clearest policy language typically states that observed-day handling follows the applicable home location’s public holiday rules.
Handle regional holidays inside the same country
In many countries, public holidays differ by state, province, or city. Decide whether regional holidays are included automatically when they appear on the employee’s applicable calendar, and ensure your holiday data source supports that level of detail.
Also decide how you will handle mid-year changes that affect regional eligibility (such as relocation). This is less about listing every scenario and more about defining when a person’s applicable region changes.
Plan continuity for critical roles
Identify roles with genuine coverage requirements
Holiday coverage planning should start from business needs that cannot pause (for example, incident response or customer escalations) rather than from general workload. This keeps coverage narrowly scoped and easier to staff fairly.
Choose a staffing method
Whether you use rotations, regional handoffs, or scheduled holiday shifts, the policy should describe the method in a way that can be planned ahead. The goal is to avoid last-minute pressure or informal expectations.
Define how bridge days are managed
Bridge days can create concentrated leave demand. If your business needs minimum staffing on specific dates, define how approvals work (for example, a published rota or a minimum coverage rule) so decisions are predictable.
If you need employer-facing answers to common coverage questions, see holiday-faqs-for-employers.
Build inclusivity without listing every observance
Inclusivity is primarily a mechanism design problem: employees need a respectful way to take time off for personal, cultural, or religious observances that are not part of their public holiday calendar.
Floating holidays are a common approach because they make this possible without requiring the company to maintain an exhaustive list of observances. If you use floating holidays, specify the entitlement (how many), the time period they apply to, and how they are requested and tracked.
For distributed teams with many regions, see holiday-policies-for-remote-teams.
Implement the policy so it works in practice
Select a calendar source of truth
Choose the system that holds authoritative holiday calendars (often an HR system, then synced to shared calendars). The policy should name this source so employees know where to check non-working days.
Publish calendars on a predictable cadence
Set expectations for when next year’s calendars are published. Publishing early supports project planning and reduces conflicts during peak holiday periods.
Make manager application consistent
Managers are often the point where policies fail through inconsistent application. Provide a short internal guide that focuses on what managers need to decide (location eligibility, approvals for bridge days, and continuity expectations) rather than repeating the full policy text.
Governance: how the policy stays current
Annual review inputs
An effective review looks at three things: where you employ people, whether holiday data sources remain accurate, and whether continuity planning matched reality during high-impact periods.
Handling disputes and exceptions
Designate a single function (often HR or People Operations) as the owner for interpretation. When an exception is granted, record the reason and decide whether it indicates a missing rule that should be added at the next review.
A copy-friendly policy structure
If you need a starting structure for an employee handbook or policy doc, this outline keeps the essentials together:
- Purpose
- Scope (employment types and locations)
- Definitions
- Holiday calendar rule (how home location is determined)
- Paid holiday structure (which approach you use)
- Observed-day and weekend handling
- Regional holiday handling
- Floating holiday entitlement (if offered)
- Bridge days and continuity expectations
- Calendar visibility (source of truth)
- Governance (owner and review cadence)
FAQ
Should we name specific religious or cultural holidays in the policy?
Some organisations choose to do so, but many use a neutral public holiday calendar plus a floating holiday mechanism so employees can observe what matters to them without the company needing to enumerate observances.
What should we do when we hire in a new country?
Treat it as a policy extension: add the location to the scope, confirm the holiday calendar source for national and regional holidays, and ensure payroll and time-off tracking can represent the new rules accurately.
Explore country calendars
To apply the ideas from “Creating a holiday policy”, compare a few country calendars first, then expand to the full directory.
- United States — a useful baseline reference for “Creating a holiday policy”.
- United Kingdom — helpful when “Creating a holiday policy” involves observed dates or bank-holiday patterns.
- Canada — useful for “Creating a holiday policy” when provincial differences matter.
- Australia — useful for “Creating a holiday policy” when state and territory calendars differ.
- India — useful for “Creating a holiday policy” when national and regional holidays overlap.
Then browse /public-holidays to extend “Creating a holiday policy” to additional countries and years.
Next steps
- Read holiday-policies-for-remote-teams for distributed teams.
- Read holiday-faqs-for-employers for common policy questions.
- Visit /public-holidays to compare years and regions.