State calendar mistakes that quietly move a real deadline without notice

A deadline calculation can be arithmetically perfect and still be wrong, because it used somebody else's calendar. Sub-national closures are where that happens most, and the failure is quiet: you get a date, it looks reasonable, and nothing tells you it came from the wrong list.

Nine ways it goes wrong, and what to do instead. No dates appear on this page: see the last section for why.

What to take away

1. Treating the national list as complete

A national closure list is a floor, not a ceiling. Regions, states and provinces add days of their own that a national list has no reason to mention, and those days close the offices in that region just as effectively.

Massachusetts and Maine keep Patriots' Day, and state offices and courts there close for it; the federal list carries no such day. California closes its state offices for Cesar Chavez Day, which the federal list also omits. Those are single entries in a few states, and they show the shape of the problem: a day that certainly exists in one place and is invisible in a national feed.

A state holiday usually binds that state's own offices and its courts. It does not automatically close banks, private employers, or federal offices in the same city, so the same date can be open for one obligation and closed for another.

Counting with the national list alone gives you a date that is too early: you assume the office was open on a day it was shut, so your count runs out sooner than it should.

Fix: find the list at the level that actually closes the office you are dealing with, and use that one.

2. Applying one region's list to a neighboring office

Firms with several sites, and anyone working near a border, do this constantly. The list on the wall is the list for head office.

Fix: hold one calendar per location, not one per organization, and tag every deadline with the location it belongs to.

3. Using your own employer's calendar for someone else's deadline

Your firm's day off has no bearing on whether a filing is due. What matters is the calendar of the body imposing the deadline.

The trap is that the two mostly coincide, so the habit survives for years. Then it fails on the one day they diverge, usually a day your office is closed.

The receiving office is not, and that direction loses you the deadline rather than gaining you time.

Fix: compute against the receiving body's calendar and treat your own as a staffing question.

4. Not going to the deadline-setting body's own schedule

Courts, registries and agencies publish their own closure schedules. Those govern regardless of what any general calendar says.

For federal courts the rule is named, and it reaches down to the states: Rule 6(a) of the Federal Rules of Civil Procedure treats a day declared a holiday by the state where the district court sits as a legal holiday for counting time. Federal agencies follow the holiday schedule published by the U.S. Office of Personnel Management. A state court publishes its own holiday and closure notice, and a state agency follows its state government's published schedule.

They also carry what a public holiday list never will: administrative closures, early-closing days, and filing windows that end before the building does. A state calendars calculator should demand the governing body's own schedule as its first input, not a national list.

Fix: go to the body's own published schedule. It is the authoritative document for its own deadlines, and anything else is a proxy for it.

5. Assuming a list covers unscheduled closures

Weather, a building problem, a local emergency, a transport shutdown. A published annual list cannot contain these, and no calculator will know about them.

Fix: for a deadline landing within a day or two, check that the office is actually open before you rely on the count. For anything filed in person or by a channel that needs someone at the other end, check on the day.

6. Counting to a day nobody is there to receive it

The count can be correct, yet the filing can still fail.

Whether a deadline landing on a closed day automatically moves to the next open day is a rule of the relevant procedure, not a property of arithmetic. Where such a rule exists, it may move the deadline in one direction only, or apply only to some kinds of filing.

Rule 6(a)(1)(C) of the Federal Rules of Civil Procedure is the federal version: if the last day of a period is a Saturday, Sunday, or legal holiday, the period runs to the end of the next day that is not one. Every state has a counterpart in its own rules of civil procedure or its local court rules, and they are not all written the same way.

Fix: find out what the applicable rule says about a deadline landing on a closed day, and do not assume the tool implemented it. Most tools implement nothing at all here; they hand you a date and stop.

7. Not recording which version of the list you used

Lists get amended. If you cannot say which list, from which publisher, as at which date, produced your deadline, you cannot defend the date and you cannot reproduce it.

Fix: store the closure list itself alongside the calculated date, not a link to a page that will have changed. Record the start instant, the convention, the working week and the list's as-of date.

8. Computing a distant deadline once and never revisiting it

A date calculated months in advance rests on a list that may since have gained a day. Long-dated deadlines are exactly the ones nobody re-checks, because they were settled long ago and look finished.

Fix: re-run any deadline more than a few weeks out when it comes within striking distance, and compare it against the original. A change is not a disaster if you see it in time.

9. Trusting a tool's built-in sub-national data

Packaged holiday data is usually strongest at national level and thin below it. Coverage of regional variation is often incomplete, frequently undated, and rarely tells you which source it came from.

Fix: override it. A tool that lets you supply your own closure list is worth more than one with a longer built-in list, because you can point it at the schedule that actually governs. Before you rely on the result, check that the tool really used the list you gave it and that it will show you that list's as-of date.

Why this page has no dates on it

Any specific list here would be wrong for most readers and out of date for the rest. Sub-national closures vary by region, differ between a court, a bank and an employer in the same town, and get amended with little notice.

The correct source is the body whose deadline you are counting toward, or the official government list that body follows: the court's own holiday and closure notice, the state government's holiday schedule, or the federal schedule published by the U.S. Office of Personnel Management. Ask each source what it covers, who is bound by it, and as of when it applies.

The habit that catches the rest

For any deadline with real consequences, get the date confirmed by whoever will receive the filing, in writing, and put that date in the file next to the interval it came from.

It takes one email. It converts every mistake on this list from something you discover afterwards into something you discover while you still have time to act on it.

Common questions

Is the national list ever enough on its own?

Only where no sub-national layer applies to your obligation, and that is a question about the obligation rather than about the country. The layers and how they combine are under state and regional calendars.

Two lists name the same day. Does it count twice?

No. Closures combine as a set union, so a day named by two layers is one closed day. Adding the lengths of the lists instead over-deducts on every overlap, and the property that prevents it is plain idempotence.

Does the same problem exist between countries rather than within one?

Yes, and it is larger there, because the rest-day set can differ as well as the closure list. The cross-border version is under how country calendars work.

Can a regional list reopen a day the national list closed?

Very rarely, and only where the instrument says so. The usual relationship is additive, which is why the union model fits and why a negative entry has no meaning in it.

How do I tell whether a list applies to my deadline?

By reading its stated scope. A closure binding public offices is not automatically one binding banks or private employers, and the category being counted is defined by the obligation, as set out under business day.

What should I do when a tool ships its own sub-national data?

Treat it as a draft. Convenient, unversioned data is the wrong trade for anything that has to be reproduced later, and a tool that will not let you supply your own list is the wrong tool for a consequential deadline.