Business Days Counter
The problem: Contract deadlines, notice periods and SLA timers run in business days — counting weekends and holidays by hand slips every time.
ASG Privacy VerifiedVerified
100% In-Browser Execution. Zero server uploads. Your data never leaves this tab — disconnect your internet and the tool keeps working.
Business Days Counter: the complete guide
A business days counter answers a deceptively simple question — 'how many working days between these two dates?' — with the precision that contracts, SLAs and project plans require. The naive answer (divide total days by seven and multiply by five) ignores where weekends actually fall, ignores holidays entirely, and produces numbers that are wrong in ways you discover at the deadline. This tool walks the actual calendar: it counts every day in your range, skips Saturdays and Sundays, subtracts any holidays you list — with a one-click US federal holiday preset that correctly handles observed weekdays for dates landing on weekends — and reports the full breakdown: total days, weekend days, holidays excluded, and the final business-day count. Inclusive and exclusive end-date handling matches the two ways teams define deadlines ('through Friday' versus 'by Friday'), and every computed number updates live in your browser. Use it for net-30 payment terms measured in business days, sprint and phase planning, legal notice periods, HR onboarding timelines, and delivery estimates that survive contact with reality.
Why counting by hand — or by average — fails
Every business-day question has three failure modes in casual math. Division by average (30 days ÷ 7 × 5 ≈ 21.4) ignores alignment: a range that starts on Saturday loses different days than one starting on Monday, and the same 30-day span can contain 20, 21 or 22 working days depending on its start. Holiday blindness compounds it: a quarter with two public holidays in the window has two fewer deliverable days than the calendar suggests, and forgetting that is how a '30 business days' SLA quietly becomes 28. Boundary ambiguity is the third: does 'net-30 business days' include the invoice date, the end date, or neither? This tool eliminates all three: it iterates the real calendar day by day, applies your holiday list explicitly, and shows the boundary choice as a toggle so the number you present matches the definition you agreed to. The breakdown display also serves as the audit trail when a client asks how you arrived at 23.
Holiday handling with US federal presets
Holidays are where most calculators stop and where the arguments start, because 'observed' rules matter: when July 4 lands on a Saturday, the federal observance moves to Friday, and when New Year's Day lands on Sunday, it moves to Monday. The built-in US federal holiday preset computes these correctly for any year — fixed-date holidays with weekend observation shifts, plus the nth-weekday holidays like Memorial Day (last Monday of May), Thanksgiving (fourth Thursday of November) and MLK Day (third Monday of January). The preset inserts the dates into your exclusion list, where you can delete items that do not apply to your organization or add company-specific closures alongside them. For non-US teams, the holiday field accepts any date list in YYYY-MM-DD format, so UK bank holidays, Diwali, Golden Week or regional observances work identically. The report lists every excluded holiday by date, so the final count is never a black box — each removed day is visible and defensible.
Deadline semantics: inclusive, exclusive and direction
Count definitions are contractual, so the tool makes them explicit. With 'include end date' enabled, a Monday-to-Friday range counts five days — the 'through Friday' reading used for durations like 'the sprint runs 10 business days.' Disabled, the same range counts four — the 'by Friday' reading used for deadlines like 'payment due 30 business days from invoice.' The same toggle answers the question 'what date is 15 business days from today?' by binary-searching ranges, but the direct way is to count from today and read the count for candidate end dates. Direction is validated too: an end before start is caught with a clear message rather than a negative number, and same-day ranges count as one day when inclusive or zero when exclusive. Because the arithmetic runs locally in UTC-anchored date math, it is immune to the DST and timezone quirks that make naive Date arithmetic skip or double-count a day twice a year in many timezones.
Practical workflows across teams
Project managers use the counter to convert calendar Gantt bars into realistic working-day estimates: a six-week calendar phase with two holidays is a 28-day workstream, and staffing it as if it were 30 is how slip accumulates. Finance teams apply it to payment terms — 'net-30 business days' from an invoice date is a specific, calculable date, and this tool produces it with the holiday policy visible. HR uses it for notice periods, probation windows and payroll cutoffs; legal teams for response deadlines in contracts; agencies for SLA timers like 'first response within 4 business hours' by scaling the same logic. Developers get a quieter benefit: the counter's logic demonstrates the UTC-walk pattern that avoids Date pitfalls, and the holiday preset is a handy reference table. Whatever the use, the workflow is identical — two dates, an optional holiday list, and a breakdown you can paste into the email that settles the discussion.
Step by step: how to use Business Days
- 1
Pick the start date and end date of your range using the date inputs.
- 2
Choose whether the end date counts: enabled for 'through' durations, disabled for 'by' deadlines.
- 3
Click the US federal holidays preset to populate the exclusion list for the relevant year, or type your own dates (YYYY-MM-DD).
- 4
Edit the holiday list to match your organization — remove non-observed days, add company closures.
- 5
Read the breakdown: business days, total days, weekend days, and every excluded holiday listed by date.
- 6
Copy the summary into your project plan, invoice, contract email or sprint ticket as the agreed counting.
Security & privacy
Date arithmetic needs no server, so this tool uses none: the calendar walk, weekend checks and holiday filtering all run in your browser with local JavaScript and UTC-anchored math. Project timelines, legal deadlines and payroll schedules are commercially sensitive — here they never leave your tab, and there is no account, telemetry or storage behind the calculation. Disconnect after loading and the counter keeps working offline. The US federal holiday presets are computed locally from standard rules, not fetched, so the tool is equally useful on a plane, in a secure environment, or anywhere a network policy blocks external calls.