Two counting styles
Every incident review has someone waving a calendar saying “It’s three days, right?” Inclusive counting says yes—start and end both count. Exclusive counting treats the end as the first day after the interval, so the same span shrinks by one. February 1–3 inclusive equals three days; exclusive equals two. Neither mode is “standard.” Use the one your contract, SLA, or HR policy names, otherwise you will redo the math mid-escalation.
Example: PTO tracking
An engineer requests March 4–8 off. HR counts the return day as “back at work,” so only the 4th–7th burn balance. Run the range through the Date Difference tool, screenshot both modes, and attach it to the approval reply so payroll, the manager, and the employee can’t claim they saw different math.
Example: Service outage window
An SLA credits every full hour between 01:15 and 04:45 UTC. Most SLAs define the window as [start, end), so you subtract and get 3.5 hours. Call it inclusive and suddenly finance owes four hours of credits. Confirm the clause, then document “inclusive start, exclusive end” in the postmortem so nobody relitigates it.
Guidelines to stay consistent
- List which programs require inclusive math (launch timelines, ceremonies) vs exclusive (leave, SLAs) so new PMs don’t guess.
- Save Date Diff share links with descriptive names so anyone can reload the correct interval and mode.
- Spell it out in client updates: “Counting inclusive of start and end date” or “exclusive of end date.”
Audit your historical data
Quarterly, sample old projects and verify the recorded spans match the policy written at the time. If you uncover mismatches, add a note explaining which rule was applied instead of silently editing numbers—that context saves you when finance audits. Recreate the intervals in the Date Diff tool and stash the screenshots in the audit folder.
Edge cases to flag
Mid-day starts confuse everyone: “three days” to ops means 72 hours; to HR it means a partial first day plus two full ones. Agree on units before quoting timelines. Likewise, inclusive spans that cross DST will contain a phantom 23rd or 25th hour—call it out when you share the count and say whether you’re reporting calendar days or absolute hours.
Try the tools
Related guides
FAQ
- Which method do calendars use?
- Most digital calendars highlight every day but still behave as inclusive start, exclusive end. That’s why an all-day event ending Friday shows as ending Saturday morning in ICS files.
- How do I explain this to stakeholders?
- Paste the Date Diff screenshot or sketch the interval. Seeing which boxes are shaded ends the debate faster than paragraphs.
- Does inclusive always equal exclusive plus one?
- For whole days, yes. For hour/minute spans it only holds when the window is half-open; a fully open/closed interval can change the offset, so check the definition before quoting it.
Need to prove another count? Run it through the Date Difference tool.