Your Company's Closure Days Break Every Standard Business-Day Count

Every business-day calculator you'll find defaults to the same assumption: the only non-working weekdays are the ones on a government's public holiday list. For plenty of organizations that assumption is quietly wrong. The week between Christmas and New Year when the whole company is dark. The founder's-day Friday in June. The regional fair day your city observes but the national calendar doesn't. The plant shutdown for retooling. None of those appear in any standard holiday set — and every one of them silently inflates a business-day count that ignores it.

Where the standard calendars stop

Public holiday data is built around what a government officially observes: the days banks close, courts recess, and statutes pause. That's the right baseline for legal deadlines and interbank settlement. It is the wrong baseline for questions like "how many working days does my team actually have this quarter?" because your team's calendar is the government calendar minus everything your organization adds on top.

The additions are more common than people think:

• Company-wide shutdowns — end-of-year closures, summer shutdowns in manufacturing, university breaks.
• Floating and company holidays — a birthday-off policy, a wellness day, a founder's day.
• Regional observances — days honored in one state, province, canton, or city that a country-level list omits.
• Industry closures — market holidays, plant maintenance windows, school terms.

Miss three shutdown days in a 60-business-day project plan and every downstream milestone is 5% optimistic before anyone has done any work.

The arithmetic of a custom closure

A custom holiday behaves exactly like a public one in the math: if it lands on a day that would otherwise be a working day, it removes that day from the count. Two consequences follow that catch people out.

First, a closure on a weekend costs nothing. If your company's fixed December 27 shutdown falls on a Saturday this year, it doesn't reduce the business-day count — the day was already excluded. Fixed-date closures cost a different number of working days each year depending on where the weekend lands, which is why last year's "we lose eight days in December" figure can't be reused this year without re-checking.

Second, custom closures stack with public holidays, not against them. If your shutdown week contains a public holiday, you don't lose an extra day for it — a day can only be removed from the count once. A December 25–31 closure in a country that already observes December 25 and 26 costs only the remaining weekdays.

Building a closure list that stays correct

The practical failure mode isn't the math — it's the list. A few habits keep it honest:

• Write dates, not rules. "The week between Christmas and New Year" is a rule that resolves to different dates every year. Expand it to concrete dates (2026-12-28, 2026-12-29, 2026-12-30, 2026-12-31) for the year you're planning.
• One source of truth. Keep the company closure list in one shared document that HR owns, and paste from it rather than reconstructing it from memory per project.
• Re-derive it every year. Fixed-date closures shift against the weekend annually; floating closures get re-declared. A closure list has a shelf life of one calendar year.
• Don't duplicate the public calendar. If the tool already applies your country's holidays, your custom list should only carry the days on top of that. Duplicates won't break the count, but they make the list harder to audit.

Layering it all in one count

The Custom Holiday Business Day Calculator is built for exactly this layered picture. Pick the date range, choose the country calendars that apply so the public holidays come in automatically, then paste your own closure dates — one date per line in YYYY-MM-DD format — and every one of them is excluded from the count alongside the built-in holidays. You can also switch the workweek preset if your organization doesn't run Monday to Friday, and toggle whether the start and end dates themselves count, which is the classic inclusive-versus-exclusive question that produces off-by-one disputes.

The result breaks the range down into business days, weekend days, and holiday days, so you can sanity-check that the closures you pasted actually landed where you expected — a shutdown day that shows up as a weekend day in the breakdown is one you didn't need to enter.

When to reach for it

Any time the question is about your organization's capacity rather than a statutory deadline: sprint and quarter planning around a shutdown, quoting a delivery date that spans your December closure, computing real working days for a contractor's statement of work, or checking how many working days a new hire's first month actually contains. For court and compliance deadlines, stick with the official calendar the rule specifies — but for everything your own calendar governs, count with the calendar you actually keep.