Working Days Calculator

Think of a calendar as a grid where roughly two out of every seven squares are shaded out before you even begin. The moment you set a start and end date, you are working with a block of time where weekends — Saturday and Sunday — reduce the usable count by about 29 percent before any holidays are considered. Most people underestimate how much of their nominal deadline window is already gone before the working week even starts.

The calculator counts every calendar day from start to end, inclusive of both endpoints. It then identifies how many of those days fall on a Saturday or Sunday and subtracts them. If you have added public holidays, it subtracts those next. What remains is the true number of days you can expect work to happen, emails to be answered, and deliveries to be made.

The inclusive counting convention matters in practice. A notice period that starts on a Monday and ends on the following Sunday spans seven calendar days but only five working days. Courts, employment tribunals, and project managers all need to agree on whether day one or day zero is the start. This tool counts day one as the start date itself — the most common convention in employment law and project planning contexts.

Use this tool whenever a deadline, notice period, or contractual obligation is measured in business or working days rather than calendar days. Common cases include employment notice periods, statutory response windows for legal documents, project sprint planning, SLA tracking, and financial settlement periods. Anywhere a weekend or bank holiday could let someone legitimately claim more time is a context where exact working-day counting matters.

It is also the right tool when you need to communicate a realistic completion date to a client. Quoting a calendar date that happens to fall at the end of a short working week — or just after a bank holiday — can damage trust if your team is not actually available on those days. Working out the true number of working days first gives you an honest anchor for the conversation.

This tool is not appropriate when the context uses calendar days explicitly, such as certain legal limitation periods, loan repayment terms, or insurance policy durations. Read the governing document carefully. If it says 30 days without qualification, assume calendar days. Only convert to working days if the document explicitly uses the phrase working days or business days. Getting this wrong in a legal context can invalidate the entire calculation.

Mistake 1 — Counting calendar days instead of working days. Many people grab a calendar, count squares, and use that figure for a deadline. The cause is that calendar days are visible and intuitive. The consequence is that a 30-calendar-day deadline might only contain roughly 21 working days, making targets that felt comfortable suddenly tight. Always convert to working days before committing to a date.

Mistake 2 — Forgetting to account for public holidays. The most common error in notice period and contract calculations is leaving the holidays field at zero. The cause is that people assume holidays are rare enough to ignore. The consequence can be a legally invalid notice period or a missed SLA. In a period with even two bank holidays, the working day count drops noticeably — as shown in the example where 2 holidays reduce the count to 28 days days.

Mistake 3 — Confusing inclusive and exclusive counting. Some tools count from the day after the start date to the end date (exclusive start), which gives a result one day lower. If you are comparing this tool to a contract clause or court ruling, confirm which convention applies. An off-by-one error in a notice period can trigger a legal dispute, particularly in employment or tenancy law.

The calculation works in three stages. First, the total calendar span is found by subtracting the start date from the end date in milliseconds and dividing by 86400000, then adding 1 to make both endpoints inclusive. For the example period entered, that gives 40 calendar days.

Second, weekends are removed using a full-weeks arithmetic approach. The total days are divided into complete seven-day weeks, each contributing 5 working days. Any remaining days are checked individually against the day-of-week index to see whether they fall on a Saturday (index 6) or Sunday (index 0). This avoids looping through every individual date, which would be slow for multi-year ranges.

Third, any public holidays you entered are subtracted from the weekday count. For the example with 2 holidays, this gives a final result of 28 days working days. Dividing that by 5 gives approximately 5.6 working weeks, which helps translate the number into a felt sense of duration.

The arithmetic shortcut of counting full weeks then handling remainders is fast but assumes a perfectly regular Monday-Friday schedule. It does not account for split working weeks at the boundaries — a detail that becomes visible when the start or end date falls on a Saturday or Sunday. In this tool, those edge days simply contribute no weekday count, which is correct for inclusive counting. However, if a system counts from Monday-after-start when the start is a weekend, results will diverge by up to two days. Always verify the day-of-week assumption in any downstream system you are reconciling against.

The holidays field is a blunt instrument by design. It assumes every holiday you enter falls on a weekday within the range — a reasonable user responsibility, but one that breaks if the user enters a holiday count that includes weekend holidays. A holiday that falls on a Sunday is already excluded, so counting it again overstates the reduction. For high-stakes calculations spanning multiple jurisdictions, verify each holiday date manually before entering the total.