Managing Distributed Teams Across Holiday Calendars

A product manager in Manchester books a sprint review for a Thursday in early May. The engineers in Munich do not turn up, because it is Ascension Day and they are at home. Nobody did anything wrong: the meeting invite looked fine in every calendar app, and nobody had told the British half of the team that Germany would be closed. Multiply that by a dozen countries and a few hundred people, and holiday blind spots become one of the most predictable sources of friction in a distributed team.

The fix is not complicated, but it does need to be deliberate. A distributed team has no single working calendar. It has several, and the useful working time is where they overlap.

Start by listing every calendar your team actually lives under

Begin with an inventory, not a policy. For each person, record the country they work from and, where it matters, the region. Germany, Spain, Switzerland, Canada, Australia and the United States all have holidays that apply only in some states, provinces or cantons, so "Germany" on its own is not precise enough for a team member in Bavaria.

Then note anything that sits outside the public calendar but affects availability in practice: company-wide shutdown days, days that are customarily taken off even though they are not official holidays (24 and 31 December in much of Europe, for example), and religious holidays that individual team members observe.

Once you have that list, pull the official holidays for each location. Our country pages, such as public holidays Germany and public holidays United Kingdom, are a starting point, and each one notes where dates are regional.

A worked example: one month, three countries

Take a small team split across Germany, the United Kingdom (England) and the United States, and look at May 2027. May 2027 starts on a Saturday and has 31 days, which gives 21 weekdays.

Now count:

• Germany: 21 weekdays minus Ascension and Whit Monday = 19 working days (Corpus Christi on 27 May would remove a further day in states that observe it).
• England: 21 minus 3 May and 31 May = 19 working days.
• United States: 21 minus Memorial Day = 20 working days.
• Days when all three are working: 21 minus the four distinct holiday dates (3, 6, 17 and 31 May) = 17 days.

Each office sees a normal month of 19 or 20 days. The team as a whole has only 17 days on which everyone is available, and that is before time zones cut into those days. If your planning assumes 20 shared days, you have lost three days of collaboration without noticing. The business days calculator will do this count per country, and the team overlap tool shows the shared days directly.

Make the calendars visible where people already look

The most effective step is often the plainest: get every location's holidays into the shared calendar system people already use, labelled with the country or region. "DE: Whit Monday" in everyone's calendar does more than a policy document nobody opens.

A few practical habits help:

• Show other locations' holidays as all-day, free-time events, so they inform without blocking anyone's own schedule.
• Add a team-level view showing which locations are out on a given day, rather than expecting each person to check five calendars.
• Refresh the data once a year, and again when a government announces a change. Holiday dates do move, and one-off holidays are added at short notice.

Decide what a holiday in one country means for everyone else

Teams get into trouble when this is left unsaid. Agree a few norms in advance.

Meetings

Recurring meetings that fall on a holiday in any core location should be moved or cancelled, not held with half the team missing. For one-off decisions, the rule of thumb is simple: if the people affected by the decision are off, the decision waits.

Handovers

Before a holiday in one location, the people going out should leave a short written handover: what is in progress, what might come up, who to ask. Asynchronous teams already work this way, but holidays are where gaps show.

Response expectations

State clearly that nobody is expected to answer messages on their own public holiday. People in other countries should not read silence as a lack of commitment. If on-call cover is genuinely needed, arrange it explicitly and compensate it according to your contracts and local rules.

Fairness across unequal calendars

Countries differ in how many public holidays they have, and in how many fall on weekdays in a given year. Some companies even this out by giving everyone the same number of total days off, combining public holidays and annual leave. Others give staff a number of floating holidays they can use for days that matter to them. Both approaches can work. What matters is that the policy is written down, that it respects any statutory minimums in each country, and that managers apply it consistently. Check employment contracts and local rules before changing anything, because public holiday entitlements are often set in law or collective agreements.

Plan sprints and milestones in shared days, not calendar days

A two-week sprint is not ten working days for everyone. In the May 2027 example, a sprint from 3 to 14 May has ten weekdays, but the English team members lose one day and the German team members lose one different day. If the work depends on both groups, the effective collaboration time is eight days. Plan capacity per person using their own calendar, then check the shared days for anything that needs the whole team at once: reviews, demos, incident drills and launches.

For longer horizons, look ahead to the long weekends in each location. A page such as long weekends in Germany 2027 shows where people are likely to take bridge days, which affects availability as much as the holidays themselves.

A checklist for team leads

1. Record each team member's country and, where relevant, region.
2. Load every location's public holidays into the shared calendar, labelled by place.
3. Count shared working days for each month or quarter, not only per-office working days.
4. Agree written norms for meetings, handovers and response times around holidays.
5. Review recurring meetings each quarter against the next three months of holidays.
6. Recheck holiday data at least yearly and whenever a government announces a change.