How Public Holidays Quietly Break Your Distributed Team's Calendar

A distributed team's calendar tooling is usually very good at time zones and very bad at holidays. It knows exactly what time 2pm New York is in Bangalore. It has no idea that Bangalore might be half-empty that day for Diwali, that a US federal holiday means nothing in the UK, or that "Golden Week" in China isn't one day off but a rearranged block of workdays and weekends that doesn't map onto a normal five-day week at all. The time zone math is the easy 90%. The holiday calendar is where distributed teams keep getting quietly surprised.

Three Ways This Actually Breaks

• A meeting gets scheduled on a holiday nobody flagged. Not maliciously — the organizer's own calendar was clear, and most scheduling tools only surface the organizer's local holidays by default, not every attendee's.
• Sprint planning assumes full headcount that isn't there. A two-week sprint that happens to include a regional holiday effectively loses a day of capacity for that region — invisible in the plan, very visible in the burndown.
• Support and on-call coverage gets modeled off one country's calendar. A team that builds its coverage plan around the US holiday list will still get blindsided by Diwali, Golden Week, or Carnaval taking out a whole region's coverage at once.

Why "National Holidays" Is a Misleading List

The instinct is to grab each country's official public holiday list and merge them into one shared calendar. That undercounts reality in a few specific, recurring ways:

• India's holidays are largely state-level, not national. Beyond a small set of national holidays (Republic Day, Independence Day, Gandhi Jayanti), most of the calendar — Diwali, Holi, regional new year festivals — is set state by state and often includes "restricted holidays" employees choose individually. Two teammates in Bangalore and Mumbai can legitimately have different days off in the same week.
• China's Golden Week isn't extra days off — it's rearranged ones. The government moves adjacent weekends to create a longer contiguous block (commonly around October 1st and the Lunar New Year), then requires a weekend workday later to make up the difference. A team calendar that just marks "October 1–7: holiday" misses that the actual working-day count for the month barely changed — it just moved.
• Brazil's Carnaval isn't a fixed date or officially a public holiday in most cities — it moves with Easter, and the days immediately before it are unofficial but near-universal shutdowns in practice, especially outside major business hubs. A calendar sourced only from official statute misses days that function as holidays anyway.
• The US and UK overlap less than people assume. Thanksgiving has no UK equivalent; UK bank holidays (like the late-May and August ones) have no US equivalent. Teams that assume "we're both Western countries, our holidays roughly match" are wrong more often than they'd guess.

A Worked Month: October, Five Countries

Here's a real month showing how little these calendars actually agree, even among a fairly typical five-country distributed team:

Five countries, one month, and the only date with any overlap at all is Columbus Day landing in the same week as Gandhi Jayanti — which affects different countries for entirely unrelated reasons. There's no shortcut here: the calendar has to be built per-region, not assumed from one team's default.

A Three-Tier System That Fixes It

Trying to give everyone the same holidays is unfair to whoever's culture gets deprioritized. Trying to track everyone's holidays as individually optional is chaos. The middle path that actually works is three tiers:

1. Company-wide blackout days (keep this under 5 a year). A small set of days where literally nothing gets scheduled company-wide — no meetings, no on-call handoffs, no sprint deadlines. New Year's Day is the only date that's genuinely universal; beyond that, pick days deliberately rather than defaulting to whichever country the company happens to be headquartered in.
2. Region-specific holidays, respected locally, not blocked globally. Diwali blocks meetings for the India-based team, not for everyone — but it has to actually show up on the shared calendar as unavailable time for those specific people, not live only in a regional HR system nobody else can see.
3. Floating/flexible holidays, chosen by the employee. Common in practice for exactly the countries with the most religiously and culturally varied calendars — give people a bank of days (often 2–3) to use on whichever locally-meaningful date isn't already covered, rather than trying to enumerate every possible observance in a policy document.

The Practical Fix: One Calendar Feed, Not One Calendar

The tooling version of the three-tier system is simple: maintain a separate holiday calendar feed per region (most calendar apps support subscribing to public regional holiday calendars directly), and have each person subscribed to their own region's feed plus the company-wide blackout list — not one merged calendar that either includes everything (noisy, and still misses the individual/floating tier) or only the headquarters' country (the default almost every team ends up with by accident).

Pair that with a weekly async "who's out this week" post — a two-line message is enough — so that sprint planning and on-call handoffs account for regional absences without anyone needing to manually cross-reference five different calendars before scheduling anything. This is the same principle as an async standup with a named blockers field — the information already exists somewhere; the fix is making it visible in the one place people actually look before they schedule something.

Applying This

1. List every country your team has someone in, and pull each one's real public holiday calendar — not an assumption based on a similar country.
2. Cut the company-wide blackout list down to under 5 truly universal days.
3. Subscribe each person to their own region's holiday feed on the shared team calendar, not a merged global one.
4. Add a small floating-holiday allowance rather than trying to enumerate every regional observance in policy.
5. Before locking in a sprint deadline or on-call schedule, check it against every region's calendar, not just the one the plan was drafted in.