Calculate Workdays Between Two Dates: Free Business Day Calculator
If you have ever signed a contract that promises payment "within ten business days," planned a sprint around a two-week delivery window, or tried to figure out whether a Friday deadline is actually realistic, you have already wrestled with the concept of workdays between two dates. The number of working days in a given span is rarely the same as the number of calendar days, and that gap can shift payroll amounts, legal deadlines, shipping estimates, and project schedules by several days.
A month might contain 20 workdays or 23, depending on where the weekends fall and which public holidays land inside it. Getting the count right means understanding what your organization or jurisdiction considers a working day, choosing whether to include the start and end dates, and accounting for holidays that change every year. This guide breaks down the definitions, the math, the tools, and the traps so you can calculate workdays with confidence.
What Exactly Counts as a Workday?
At its simplest, a workday is any day on which normal business operations take place. In most of North America and Europe, that means Monday through Friday, excluding weekends and recognized public holidays. The count therefore depends on two moving parts: which days of the week are treated as non-working, and which specific dates are removed as holidays.
The distinction between calendar days and workdays is not a technicality. A 30-day payment term and a 30-business-day payment term can differ by more than two weeks. A 45-day notice period that runs through a holiday-heavy December can stretch far longer than one that runs through a quiet April. When you are calculating workdays between two dates, precision is the whole point.
Regional Work Weeks Vary More Than You Think
The Monday-to-Friday pattern is common, but it is far from universal. Several countries in the Middle East and North Africa use a Sunday-to-Thursday work week, making Friday and Saturday the standard weekend. Israel typically observes a Sunday-to-Thursday schedule as well, while some Gulf states have shifted their official working week in recent years to align more closely with global markets, moving the weekend to Saturday and Sunday.
These differences create real friction for international teams. If a project manager in London counts workdays using a Monday-to-Friday assumption while a counterpart in a Sunday-to-Thursday region uses their own calendar, the two will disagree about whether a given Wednesday deadline is achievable. Before you count anything, confirm which days your audience, contract, or jurisdiction treats as non-working.
Holidays, Half Days, and Shift Work
Public holidays are the second variable, and they are messier than weekends because they change annually and differ by country, state, and even city. National holidays, regional observances, bank holidays, religious festivals, and company-specific shutdown days all reduce the number of available workdays. Crucially, when a holiday falls on a Saturday or Sunday, it usually should not be subtracted twice.
Many workplaces also operate on schedules that defy a simple binary. Retail, healthcare, logistics, and manufacturing operations often run seven days a week with rotating shifts, so a "weekend" is simply whoever is off that day. Some offices close at midday on Fridays during summer, and others offer floating holidays that employees can take at will. In these environments, the standard five-day model produces an estimate at best.
How to Calculate Workdays Between Two Dates
Every workday calculation starts with a decision: are you counting the start date, the end date, both, or neither? Convention matters enormously here. Excel's built-in function includes both endpoints, meaning a request from Monday to Friday returns five workdays. Many legal and contractual documents, on the other hand, exclude the day of the triggering event and count forward.
Once that boundary decision is settled, the process becomes mechanical. You take the total span of calendar days, remove the days that fall on non-working weekdays, and then subtract any holidays that land on days you were otherwise counting. The order of operations matters, because subtracting holidays before removing weekends will give you the wrong answer.
Doing the Math by Hand
The manual method relies on a simple observation: every full seven-day period contains exactly five weekdays under a Monday-to-Friday schedule. To count by hand, calculate the total number of days in the range, divide by seven to find the number of complete weeks, multiply those weeks by five, then examine the leftover days individually to see how many are weekdays.
Consider a project running from Monday, March 3, 2025 through Friday, March 21, 2025, inclusive. That span covers 19 calendar days: two complete weeks (10 workdays) plus five remaining days from Monday through Friday (five more workdays). The total is 15 workdays. If a public holiday fell on, say, Wednesday, March 12, the answer drops to 14. This method scales well for short ranges but becomes error-prone across months and years, which is where software earns its keep.
Formulas, Functions, and Code
Spreadsheet users have the easiest path. Excel and Google Sheets both offer a function that calculates the number of whole workdays between a start date and an end date, with an optional list of holiday dates to exclude. A related variant lets you define custom weekends, so you can specify a Friday-Saturday or Sunday-Thursday week instead of the default Saturday-Sunday. A companion function works in reverse, returning the date that falls a set number of workdays into the future, which is invaluable for deadline planning.
For developers, most languages have libraries or native tools that handle the same logic. Python's scientific stack includes business-day functions and business-day date ranges, JavaScript has business-day plugins for popular date libraries, and database engines can generate date series and filter them with a weekday expression. Whatever tool you choose, the underlying rule stays the same: define non-working weekdays, remove holidays, and be explicit about whether endpoints count.
Where Workday Counts Matter in the Real World
Workday arithmetic is not an academic exercise. It shows up wherever money, obligations, or timelines are tied to business operations, and a small counting error can cascade into disputes, penalties, or missed commitments. The stakes explain why finance, legal, and operations teams tend to be unusually particular about their calendars.
In practice, most organizations need two or three standard counts rather than one. A payroll team may need workdays for a pay period, a legal team may need court days or business days depending on the filing rule, and a delivery team may need available working days net of local holidays. Keeping those definitions documented prevents the same argument from recurring every quarter.
Payroll, Billing, and Contracts
Compensation is frequently prorated by working days. If an employee joins mid-month or takes unpaid leave, the fairest calculation often divides the salary by the number of workdays in that month and multiplies by the days actually worked. That approach requires a precise workday count for each month, including any holidays your organization observes.
Contracts use the same unit of measure in a very different way. Phrases like "net 30," "within five business days," and "ten working days' notice" all hinge on how the parties define a business day and whether the clock starts the day of the event or the day after. When a term is ambiguous, the safest move is to write the interpretation into the agreement itself: which weekdays count, whether holidays extend the deadline, and whether the end date is inclusive.
Project Deadlines and Service Level Agreements
Project managers estimate duration in working days because that reflects actual capacity. A task scoped at ten working days does not finish on the tenth calendar day; it finishes roughly two weeks later, assuming no holidays and no interruptions. Converting estimates into calendar dates without accounting for weekends is one of the most common sources of schedule slippage.
Service level agreements rely on the same logic with financial consequences attached. Support contracts often promise a first response within a set number of business hours or business days, and banking settlement cycles are described in terms like T+1 or T+2, which skip non-business days entirely. If a holiday falls inside the window, the clock pauses, and the customer's expectation needs to reflect that.
Mistakes That Throw Off Your Count
Most incorrect workday totals come from a handful of recurring errors rather than exotic edge cases. Understanding them in advance is faster than debugging a spreadsheet at the end of a reporting cycle.
The good news is that each mistake has a straightforward fix. Once you build the right checks into your template or script, the count becomes reliable and repeatable, which is exactly what you want when the number feeds into a payment or a legal filing.
Inclusive vs Exclusive Endpoints and Time Zones
The single most common discrepancy is endpoint handling. Two people can look at the same range and disagree by one or two days simply because one counts both the first and last date while the other counts only the span between them. Decide the rule before you calculate, write it down, and apply it consistently across every team that uses the number.
Time zones add another layer. If the start timestamp is recorded in one zone and the end timestamp in another, converting both to calendar dates can shift the range by a day. This matters most for globally distributed teams and for systems that store timestamps in coordinated universal time but present them in local time. Normalizing to a single reference time zone before extracting dates eliminates the ambiguity.
Holiday Data and Edge Cases
Holiday lists are the second major source of error. Using last year's list, forgetting a regional holiday, or applying a country's holidays to a team in a different country will all produce inflated counts. Holidays that fall on weekends are a subtler trap: if you subtract every date on the list without checking the weekday, you deduct days that were never counted in the first place.
Edge cases deserve a deliberate policy. Does a half day count as one workday or half of one? If a holiday is moved to a nearby Monday by government decree, which date do you use? What happens when a contract spans a leap year or crosses a daylight saving transition? Documenting answers to these questions once turns a recurring debate into a settled rule.
Whether you are validating an invoice, scheduling a release, or drafting a clause that says "five business days," the value of an accurate workday count comes down to agreement: agreement on which days count, which ones do not, and how the endpoints are handled. Build those definitions into your templates and scripts now, and the next deadline you promise will be one you can actually keep.