Public Holiday

Christmas in Germany means December 25-26 off. In the US, just December 25. Japan doesn't observe it at all. Now throw in Eid, Diwali, Golden Week, and the fact that some German states get Corpus Christi while others don't — and you start to see the problem.

For any agency with team members in more than one country (or even one country with regional variations), manually tracking public holidays is a recipe for scheduling mistakes.

The Distributed Team Challenge

Consider a real scenario: you're running a project with a designer in Berlin, a developer in São Paulo, and a project manager in New York. Brazil has 12 national holidays, Germany has 9-13 depending on the state, the US has 11 federal holidays — and they almost never overlap. That's potentially 30+ days across the year where at least one team member is unavailable, scattered unpredictably across the calendar.

If your resource scheduling tool doesn't know about these days, your allocations will land on days people can't work. The calendar says 100% availability; reality says otherwise.

Automatic Holiday Support

WrkSched ships with public holiday data for 200+ countries. Each team member's holidays are determined by their country setting, and those days automatically reduce their monthly capacity. No spreadsheets, no annual "please update your holidays" emails.

This feeds directly into the capacity report. When you're forecasting whether your team can handle a December deadline, the system already knows that your German colleagues lose two days to Christmas while your US team loses one — and that January 6 (Epiphany) takes out your team in parts of Spain and Italy but nobody else. The utilization rates and workload distribution reflect what's actually schedulable, not a naive 160-hour assumption.