How to Count Business Days Between Two Dates (Without Miscounting Either End)

Counting working days between two dates sounds like the kind of thing that cannot go wrong. It goes wrong constantly, and almost never because someone miscounted. It goes wrong because two people applied different conventions and each was internally consistent.

The three questions that decide the answer

Before any arithmetic happens, three things have to be settled. Get them wrong and the count is wrong by a predictable amount every single time.

1. Does the first day count?

This is the inclusive-versus-exclusive question and it is the largest single source of off-by-one errors in deadline work. Most legal periods are exclusive of the day of the triggering event: a rule saying "within 10 days of service" almost always means the day after service is day one. Most project schedules are inclusive: a task starting Monday and taking five days finishes Friday, not the following Monday.

Neither convention is more correct. They are different tools. What causes damage is assuming your reader shares yours.

2. Does the last day count?

The same question at the other end. "From 1 June to 30 June" can mean 21 working days or 22 depending on whether the closing date is inside the range. Duration questions usually exclude it; deadline questions usually include it.

3. Whose weekend, and whose holidays?

A Monday-to-Friday workweek is an assumption, not a fact. Much of the Gulf runs Sunday to Thursday. Compressed four-day weeks are increasingly common. A count that silently assumes Saturday and Sunday are the non-working days will be wrong by roughly forty days a year for anyone on a different pattern.

Holidays are worse, because they are invisible until they are not. A ten-working-day period spanning the US Thanksgiving week, the UK late-May bank holiday, or the New Zealand Christmas shutdown covers a very different stretch of calendar than the same period in an ordinary month.

Why national holiday lists are not enough

Even a correct national calendar frequently is not the calendar you need.

• Regional holidays. Australian public holidays are largely state-set — Labour Day falls in four different months depending on the state. New Zealand's anniversary days are observed by region. The UK diverges between England, Scotland and Northern Ireland. A national-only count quietly misses all of these.
• Substitute days. When a fixed-date holiday lands on a weekend, most countries move the day off. New Zealand Mondayises, the UK grants substitute bank holidays, the US federal calendar observes the nearest weekday. The rules differ, and Christmas and Boxing Day have to move as a pair or they collide.
• Company closures. Nothing in any public list knows about your firm's shutdown week, a site stand-down, or an industry-wide break. Those have to be added by hand.
• Market versus civil calendars. If you are counting settlement days rather than office days, the exchange calendar governs. Good Friday closes the NYSE but is not a US federal holiday; Columbus Day and Veterans Day are federal holidays on which the market trades normally. Using the civil calendar for settlement is wrong in both directions.

A worked example

Count the business days from Monday 24 August 2026 to Friday 25 September 2026, inclusive of both ends, on a standard Monday-to-Friday week with the US federal calendar. That span is 33 calendar days. Eight of them fall at weekends and one is a public holiday — Labor Day, the first Monday in September. The answer is 24 business days.

Change one setting and the answer moves. Drop the holiday calendar entirely and you get 25, because Labor Day becomes a working day. Switch to a Monday-to-Thursday four-day week and it falls to 19. None of these is a bug; each is the correct answer to a slightly different question, which is exactly why the question has to be stated.

Counting days is not the same as counting deadlines

One more distinction worth keeping clear. Working out how many working days sit between two dates is a duration question. Working out when a deadline falls is a projection question, and the two use different mechanics: a deadline that lands on a non-working day usually rolls forward to the next one, which a duration count never does.

Most importantly, business-day counting only applies if the rule you are working under actually counts business days. A great many statutory periods are in calendar days — the WARN Act's 60 days, HIPAA's 60 days, the 45 and 180 days in a 1031 exchange — and applying a working-day count to them produces a date weeks too late. Read the rule before choosing the counter.

Write the convention down

If you take one thing from this: whenever you publish a count, publish the convention with it. "22 business days (excluding both end dates, Mon–Fri, US federal holidays)" is barely longer than "22 business days" and it makes the number checkable. Every dispute we have seen about a working-day count dissolved the moment both sides wrote down what they had assumed.

The Business Days Between calculator exposes each of these choices as a switch rather than burying it: inclusive or exclusive at each end, the workweek pattern, which national and regional calendars apply, and a box for your own closures. The breakdown shows the weekends and holidays it removed, so the number can be checked rather than trusted.

General information about date arithmetic, not legal advice. Where a deadline is set by statute, contract or court rule, that instrument governs how the days are counted — confirm the convention it uses before relying on any figure.