One Holiday Calendar Will Not Survive a Multi-Province Team

Hire your second employee in another province and your holiday calendar quietly becomes wrong. Not dramatically — nobody gets fired over it — but wrong in the way that produces a payroll correction in February, an awkward Slack message in August, and a slow erosion of confidence in the numbers your leave system reports.

The cause is almost always the same. The company was founded in one province, someone entered that province's statutory holidays as the holiday list, and the system has been treating that list as universal ever since. It worked perfectly until it didn't.

Canada Does Not Have One Holiday List

There is a federal set of statutory holidays, and there is a set for each province and territory, and they are not the same. Some days are observed almost everywhere — New Year's Day, Good Friday, Canada Day, Labour Day, Christmas Day. Others are genuinely regional: BC Day, Family Day in the provinces that have it, Saint-Jean-Baptiste Day in Quebec, and so on. Federally regulated employers follow a different list again from provincially regulated ones in the same city.

This post is not going to enumerate them, because the lists change, the rules around substitution and holiday pay differ by jurisdiction, and getting that detail from a blog rather than from your provincial employment standards office is how errors happen. What matters here is the structural fact: the correct holiday list is a property of the employee, not of the company.

Almost every problem in this area comes from software — or a spreadsheet — that assumes otherwise.

What Actually Breaks

The failure is rarely the calendar looking wrong. It is the arithmetic downstream of the calendar.

Leave deduction. A statutory holiday inside a leave period should not usually consume a day of the employee's entitlement. If your system is holding the wrong list for someone, their week off either costs them a day it shouldn't or fails to cost them one it should. Neither is visible until someone reconciles a balance by hand.

Working-day counts. Anything that counts business days — notice periods, accrual, probation milestones, deadline calculations — is silently using the wrong denominator for anyone whose region does not match the default list.

Coverage planning. A manager in Toronto looks at the team calendar in early August and sees a normal working Monday, because the company list has no BC Day on it. Two of their four people are in Vancouver and are not working. This one is usually discovered at 9am.

Payroll. The most expensive version, and the one that surfaces last.

The Off-By-One Problem Underneath It

There is a second, sneakier failure that sits below the list itself, and it is worth naming because it produces the most confusing bug reports.

A public holiday is a calendar day. Canada Day is July 1st — not a moment in time, just a date. But software loves to store dates as precise instants, and an instant always belongs to some time zone. Store July 1st as midnight in one zone and read it back in another and it can silently become June 30th. Now the holiday renders on the wrong square, a one-day leave appears to span two, and the deduction lands against the wrong day.

The result looks identical to a wrong holiday list, which is why the two get confused. The distinction matters when you are diagnosing it: a wrong list means the holiday is absent or shouldn't be there; an off-by-one means the right holiday is present on the wrong day, and it will usually be off by exactly one in a consistent direction. We wrote about the general shape of this in managing PTO across time zones, and it applies just as much to a team spread across Canada as one spread across continents.

What to Check in Your System

Whatever you are using, these are the questions that separate a holiday calendar that will hold up from one that will need a correction next year.

Is the holiday region set per employee, with a sensible org-wide fallback? Not a global setting. Not a per-department setting, unless your departments happen to map cleanly onto provinces, which they will stop doing the first time someone relocates. Per employee, defaulting to the organisation's region so you are not entering it forty times.

Can you override an individual day for an individual person? Real employment throws up cases the standard list does not cover: a federally regulated contract, a collective agreement with additional observed days, an employee who works a schedule where a particular holiday is substituted. If the only way to handle these is to abandon the automatic calendar entirely, you will end up maintaining the whole thing by hand.

Does leave deduction actually consult the employee's list? This is the one worth testing rather than assuming. Book a leave period for an employee in a province with a regional holiday, spanning that holiday, and check the deducted day count against what you expect. It takes five minutes and it is the only way to know.

Does the shared calendar render each person's holidays, or one list for everyone? A manager looking at their team should see the days each of those people is actually not working.

Where does the list come from, and how does it stay current? Hand-entered lists rot. Someone maintains them in year one, that person changes role, and by year three the calendar is confidently displaying last year's dates. A system that sources holidays from a maintained public dataset — BookYourPTO uses Nager.Date for public holidays across more than 100 countries — removes an annual chore that is very easy to forget.

A Sensible Way to Set It Up

For a team spread across Canada, the configuration that causes the least trouble looks like this.

Set the organisation's default region to wherever most of your people are — usually the head office province. Set the region individually for everyone who differs, at onboarding, and treat it as real employment data rather than a display preference, because it drives deduction arithmetic. Handle genuine exceptions with per-employee overrides on specific days rather than by forking the whole calendar. Then, once a year, spot-check a leave request that spans a regional holiday for someone outside the default province.

That last step is the one people skip. It is also the only one that would have caught any of the failures above before payroll did.

Worth Getting Right Early

None of this is difficult. It is just easy to defer, because the cost of getting it wrong is invisible for exactly as long as everyone works in the same province — and the moment that stops being true, the system does not warn you. It just quietly starts producing numbers that are slightly off for a subset of your team.

If you are running a Canadian team across more than one province, our leave management for Canada page covers how per-employee holiday regions, overrides, and deduction rules fit together. And if you are currently maintaining any of this by hand in a spreadsheet, that is the thing to fix first — everything above assumes the calendar is at least being applied consistently, which a spreadsheet cannot guarantee.