The federal calendar gives you 11 holidays. Your actual office calendar? Probably more. Maybe your shop shuts down the week between Christmas and New Year's, or observes the Friday after Thanksgiving even though that's not a federal holiday. When you're counting business days for a project deadline or a contract clause, those extra days matter — and if you ignore them, your count is off before you even start.
Here's the thing that trips up most people: a "business day" isn't defined by Washington. It's defined by whoever is doing the work. The federal holiday list is just the baseline. Real working schedules layer company holidays, state holidays, floating days, and shutdown weeks on top. So the accurate count almost always requires a custom exclusion list.
What Counts as a Custom Holiday?
Custom holidays fall into a few common buckets for US workplaces:
- Company shutdowns: The full week between Christmas and New Year's is the classic example. Many manufacturers also shut down the first week of July.
- Floating holidays: One or two personal days employees pick — these vary per person, so they only matter for individual scheduling, not team deadlines.
- State holidays: Patriots' Day in Massachusetts, Pioneer Day in Utah, César Chávez Day in California. If your team sits in one of these states, that day is gone.
- Industry conventions: Trade show weeks, inventory days, quarterly all-hands — anything that pulls the whole team out.
Why the Default Business-Day Count Misses
Most calculators do the same thing: strip Saturday and Sunday, strip the 11 federal holidays, hand you a number. That works fine for a bank or a government filing. It falls apart for a real office. If your team takes Black Friday off (most do), and you're counting 10 business days from the Monday before Thanksgiving, a default tool will count Friday as a working day and land you on a day nobody's actually in the building.
I ran into this last winter planning a year-end close. The default count said we had 12 working days. After I subtracted the shutdown week and two floating holidays, we had 5. That's not a rounding error — that's the difference between shipping on time and missing the deadline.
Building a Custom Exclusion List the Right Way
Start with your actual HR calendar, not the federal one. List every date the office is closed, including the ones that aren't on any official list. Then plug that list into a calculator that accepts custom exclusions. Our Custom Exclude Calculator is built exactly for this — you enter a start date, add the number of days, and mark any extra dates you want stripped out. It handles the weekends and federal holidays automatically and layers your custom days on top.
One small tip: name your exclusion list and save it. Next year you'll reuse most of the same dates, and having them documented beats rebuilding from scratch every January.
When Custom Exclusions Actually Change the Outcome
They matter most in three situations. Contract deadlines, where "30 business days" is legally binding and a missed exclusion can trigger a penalty. Payroll processing, where you need a fixed number of working days to run the cycle. And project plans with no slack, where a single uncounted holiday cascades into a late delivery. For anything with a one- or two-day buffer, the default count is usually fine. For anything tight, build the custom list.