Calendar days — unless the contract explicitly says business days. Silence means calendar days, and that's the assumption courts and vendors will both start from.

But the reason this question matters isn't the default. It's the size of the gap. On a 60-day notice period, the two readings land about 25 days apart. That's not a technicality to be resolved later — it's most of a month, and it is routinely the difference between exiting a contract and owning it for another year.

The gap, concretely

Why the gap is so large

Sixty business days is twelve working weeks. Twelve weeks is 84 calendar days before you remove a single holiday. Add Memorial Day, or Christmas, or whatever else falls in the window, and you're at 85 or more. So "60 days" read one way is 60 days, and read the other way is nearly three months.

The rule of thumb: business days multiply by roughly 1.4 to reach calendar days. Thirty business days is about six weeks. Sixty is about twelve. Ninety business days is more than four months, which is why 90-business-day notice periods are rare and worth reading twice when you see one.

What counts as a business day

Monday to Friday, excluding public holidays. The complication is whose public holidays.

United States

  • Federal holidays — 11 of them
  • Weekend holidays shift: Independence Day 2026 falls on a Saturday, so the federal observance is Friday 3 July
  • State holidays generally don't count unless named

England & Wales

  • Bank holidays — 8 in a typical year
  • Easter moves annually; Good Friday and Easter Monday are both bank holidays
  • Scotland and Northern Ireland have different sets

If the agreement defines "business day" in its definitions section — and well-drafted ones do, usually as something like "a day other than a Saturday, Sunday or public holiday in the State of New York" — that definition wins over any general assumption. Check there first.

When the clause is silent, count the safe way

Here's the asymmetry that makes this easy to resolve in practice.

Calendar-day counting produces the later deadline. Business-day counting produces the earlier one. If you act by the earlier date, you have satisfied both readings at once. If you act by the later one and the vendor argues the clause meant business days, you have already lost — there is no way to un-miss a deadline.

🎯

Ambiguity resolves toward the earlier date. When a clause doesn't say, calendar days is the more likely legal reading — but business days is the safer operational one. They cost you the same effort. Only one of them can cost you a year of spend.

Two edge cases worth knowing

The deadline lands on a Sunday

Unless the contract says a deadline falling on a non-business day rolls forward to the next business day, it doesn't roll. The deadline is the deadline. Some agreements do include a rolling provision; plenty don't. Sending notice before the weekend is always safe, and waiting until Monday only works if the contract says it does.

Business days and delivery time stack

If your notice must be received rather than sent, and the counting is in business days, you're now working backwards twice: back from the renewal date by the notice period, then back again by however long the required delivery method takes. Certified mail doesn't move on weekends either. More on given-versus-received →

Just count it correctly

None of this is hard arithmetic — it's just arithmetic that's easy to get subtly wrong, and expensive when you do. The deadline calculator counts both ways, skips US federal and UK bank holidays, and accounts for notice-on-receipt. It also exports a calendar reminder, because the actual failure mode here isn't miscounting — it's counting correctly in March and forgetting by October.

AZ

Alec Zakhary

Alec builds the AI intake layer at SynapticRelay. He writes about contract operations, document extraction, and the systems that decide what happens to a document before anyone opens it.

Keep reading