How to use (3 steps)
- Choose your start and end date & time. For simple day counts you can leave the time at 00:00.
- If needed, turn on “Include the end date” and adjust business‑day and working‑hours options.
- Press Calculate to see days, business days, working hours, and the year–month–day breakdown. Use “Copy result URL” if you want to reopen the same setup later.
Total duration
—
Choosing the right date difference output
Date difference can mean different things depending on context. Project planning often needs business days, billing often needs exact elapsed time, and age/tenure reporting may prefer years-months-days.
When to use each mode
- Total duration: precise elapsed time between two timestamps.
- Business days: operational timelines excluding weekends/holidays.
- Working hours: staffing and effort estimation windows.
- Y-M-D: human-readable summaries for contracts and profiles.
Example
A task from Monday 10:00 to next Monday 10:00 is 7 days total, but can be 5 business days under a Mon–Fri schedule and custom holiday exclusions.
Always confirm regulatory or payroll calculations with official rules in your region.
Date difference outputs: pick the one your workflow actually uses
Two teams can calculate “the same” date range and still report different answers if they use different counting rules. Project management may prioritize business days, legal documents may care about inclusive calendar days, and payroll often relies on specific working-hour windows. Choose the output format before you interpret the number, then document that choice for consistency across reports.
How to choose the right mode
- Calendar days when contracts or policies reference consecutive dates.
- Business days when weekends/holidays are explicitly excluded.
- Working hours when staffing cost or effort windows matter.
- Y-M-D when you need human-readable tenure/age style reporting.
Common mistakes to avoid
- Mixing inclusive and exclusive counting between reports.
- Assuming public holidays are removed automatically without adding them.
- Ignoring local time zone when comparing timestamps from different regions.
Interpretation notes
If your process crosses daylight-saving boundaries or multiple time zones, verify assumptions before publishing totals. For operational dashboards, save one canonical policy (weekend set, holiday list, include-end toggle) and reuse it across teams to prevent reconciliation issues.
Mini policy example
A team reports SLA in business days while finance reports penalties in calendar days. For the same incident window, the totals differ and can appear contradictory unless policy labels are explicit. If you add one reporting note such as “Business days, Mon–Fri, holidays excluded, start included,” most disputes disappear. Use a fixed policy string whenever results are shared outside your immediate team.
When exporting results, store your weekend and holiday configuration with the output so future recalculations remain reproducible even after policy updates.
See also
- Business days calculator for focused weekday/holiday counting.
- Time add/subtract calculator for duration arithmetic workflows.
- Timezone converter to validate local vs remote timestamp interpretation.
- Date and time calculator for combined date/time operation chains.
FAQ
How is the date difference calculated?
We normalise each input to local noon to avoid daylight-saving shifts, then compute the gap. The start date is always counted. Selecting “Include the end date” adds the end date to day, business-day, and Y/M/D counts; it does not add 24 hours to Total duration.
What counts as a business day?
When you enable business days, any weekday you mark as a weekend and any dates in the holiday list are removed from the count. Official national calendars will be offered later as presets.
How are working hours calculated?
The tool intersects your selected working-hours window with each business day between the start and end times. Time that falls outside the window is ignored automatically.
How are years, months, and days derived?
For the Y/M/D count, we advance the end date by one day when “Include the end date” is on, then subtract the calendar components.
Inclusive vs exclusive difference?
By default, the start date is counted and the end date is excluded. Inclusive mode also counts the end date.
Do time zones or DST affect results?
We normalise inputs to local noon to avoid DST boundaries. Business‑day counting ignores public holidays unless you add them to the list.