Business-Day Boundary Rules: Day 0, Day 1, and Reversed Ranges

Day 0 is the event or starting date before any decision is made about whether it counts. If the rule includes the start and that date passes every calendar test, day 0 can also be day 1. If the rule says after, following, or excludes the start, the first later eligible date becomes day 1. Inclusion never turns a weekend or applicable holiday into a business day.

End inclusion is a separate decision. It matters when counting a bounded range, while an add-business-days calculation usually stops when the requested ordinal is reached. Record both settings instead of assuming that a spreadsheet, contract owner, and calculator use the same convention.

The trace begins on Monday, June 29, 2026. The selected calendar closes Saturday and Sunday and applies the US 2026 national-only verified snapshot. The source ledger confirms July 3 as the observed federal closure date in that subset. With the start included, June 29 is day 1 and July 6 is day 5. With the start excluded, June 30 is day 1 and July 7 is day 5.

No other input changes. The one-day ordinal difference crosses a holiday and a weekend, so the displayed result moves by one calendar day after a three-day excluded block. This is why a result should preserve the trace rather than only the final date.

First identify the event that starts the obligation. Second decide whether that date can count. Third apply recurring non-working weekdays. Fourth apply only the holiday scope and custom closures that govern the obligation. Fifth decide whether an eligible end date is included. The same sequence should be used when another person reproduces the result.

A date excluded for more than one reason is still skipped once. For example, a company closure entered on a public holiday does not create two skipped days. The evidence should retain both reasons if they matter operationally, while the count retains one calendar date.

When a range is entered from a later date to an earlier date, DeadlineDays orders the calendar for review and exposes that the input was reversed. The magnitude can be inspected against the same included and excluded dates, but the sign or reporting meaning must follow the surrounding workflow. A negative count can describe direction; it does not by itself mean an overdue balance, service breach, or payroll correction.

Do not silently swap dates in a permanent record. Keep the original input order, the normalized earlier-to-later ledger, and the rule used to report the result. That makes an accidental reversal distinguishable from a deliberate backward-looking report.

The July 3 exclusion comes only from the source ledger's verified US 2026 subset: 11 observed federal closure dates for Monday-Friday federal employees, compared with the U.S. Office of Personnel Management schedule on July 28, 2026. The ledger explicitly excludes state, local, bank, school, employer, and regional observances.

A private warehouse, bank, court, customer, or employer may use a different calendar even on a federal holiday. Treat the official subset as one named layer, then add the organization calendar that actually controls the obligation.

Save the starting event, original input order, start and end inclusion settings, non-working weekdays, country and coverage, public-holiday status, custom closures, calculation date, and source-verification date. If the result becomes binding, also retain the contract or policy version and the responsible owner's confirmation.

Recheck future dates when the governing calendar changes. Do not rewrite a historical result without preserving the assumptions and source version originally used.

This guide demonstrates a whole-day calculation. It does not resolve partial days, cutoffs, time zones, DST gaps or overlaps, queue pauses, market sessions, or contract interpretation. The US example is not a complete American business calendar and does not establish that any private organization closes on July 3.

For a binding deadline, verify the exact wording and applicable official, regional, bank, carrier, employer, customer, and organization calendars. A reproducible trace can expose an assumption; it cannot choose the legally or operationally correct assumption.

For a non-sensitive correction, send the guide URL, input dates, boundary settings, disputed closure, official source URL, and expected trace to [email protected]. Do not send contracts, customer records, or personal data.