Why date ranges are off by one: the boundary, not the arithmetic

From August 1 to August 2, the mathematical date gap is one day. If both dates count as occupied days, the range covers two calendar dates. Both answers can be right depending on whether you need distance, hotel nights, or participation days.

Write the definition before calculating: “exclude the end date,” “include both ends,” or “count Monday through Friday only.” That sentence matters more than the calculator control because it decides whether one is added to the mathematical gap.

A hotel stay from August 1 to checkout on August 3 is usually two nights because checkout day does not use another night. An event scheduled every day from the 1st through the 3rd usually covers three calendar dates.

A generic weekday calculation usually skips only Saturday and Sunday. Public holidays, substitute working days, and organization-specific closures require another data source. A Saturday can be a working day, and a Monday can be a public holiday.

Monday–Friday is useful for early project planning and rough estimates. Payroll, attendance, limitation periods, and contract notice calculations must be checked against the official rules for the relevant place, year, and organization.

If the task cares only about dates, treat inputs as year-month-day instead of subtracting two local-midnight timestamps. During daylight-saving changes, a day can be 23 or 25 hours; dividing elapsed time by 24 hours can produce the wrong date count.

International flights, system logs, and precise countdowns are different: they care about exact instants and require a time zone or UTC offset. Decide whether the question is “how many calendar days?” or “how many hours?” before choosing the calculation.