How Many Working Days Until the Deadline? Three Things to Settle First

Ask “how long is 2026-10-01 to 2026-12-31” and there are four right answers: 91 days, exactly 13 weeks, 65 working days, 2 months and 30 days. They do not contradict each other - they answer different questions. A project plan wants working days, a lease wants months, a notice period wants “two months and thirty days”, a flight plan wants hours. When these numbers go wrong, it is almost never the arithmetic; it is that three things were never settled.

1. Do the first and last day count?

Scheduling tools normally count the first day and not the last, so 2026-10-01 to 2026-10-02 is 1 day. Hotel night rosters, leave forms and hospital bills use the other convention, where both endpoints count and the same two dates become 2 days. The days-between-two-dates page defaults to the first; the “count the last day too” checkbox switches to the second - 91 days becomes 92, and 65 working days becomes 66.

This is also why a spreadsheet and that page’s default can differ by one: Excel’s NETWORKDAYS counts both endpoints, and it expects you to pass the holiday range yourself. When two people disagree, compare conventions before checking the maths.

2. “Working day” stops at Monday to Friday

Weekdays here mean Monday to Friday. The count does not know public holidays, and it does not know make-up working weekends. So the seven days from 2026-10-01 to 10-07 come out as five weekdays, one Saturday and one Sunday - even though in that year nobody in the country was working any of them.

That omission is deliberate. Holiday arrangements are published year by year, and a swapped-in Saturday turns a weekend into a working day, so any holiday table baked into a page is guaranteed to go stale - and a stale table is worse than none, because it prints a confidently wrong number. Treat the weekday count as an upper bound and subtract the holidays yourself; for the authoritative list, use the current year’s official notice.

3. Where a whole month starts and stops

Two dates rarely differ by a whole number of months, so the exact figure is a breakdown: count whole months forward from the start, and if the target month has no matching day number, land on its last day; only the remainder is read as days. Hence:

• 2026-10-01 to 2026-12-31 is 2 months 30 days (whole months run to 12-01, then 30 days);
• 2026-01-31 to 2026-02-28 is 1 month, because February has no 31st;
• 2026-01-31 to 2026-03-01 is 1 month 1 day.

The calendar-day figure is fixed by the calendar while the breakdown depends on where month boundaries fall, so the two not “converting” into each other is normal. The date adding page uses the identical rule, which makes the pair self-checking: 2026-01-31 plus 1 month plus 1 day is 2026-03-01, whereas adding the same thing as one 32-day step gives 2026-03-04. Payroll, rent and interest schedules want the first answer, and whenever a pull-back happens the result line says so instead of hiding it.

Notice periods, warranties, due dates, ages: same shape

One date, one amount, one direction - and the answer has to land on a day that exists:

The order is fixed: years and months first (they are the only part that depends on which month you land in), then weeks and days (plain calendar steps), hours and minutes last (the only part that can push the date over). The amount box on the date adding page reads a sentence directly: 2y, 18mo, 3w, 45d, 6h, 90min, and mixtures such as 1mo 2w 3d. A bare m means months, so write minutes as min. Typing the sentence fills the six boxes underneath, and those boxes are what actually gets counted, so the exact amount behind every answer stays visible. Fractions are not read - write 1w 3d rather than 1.5 weeks.

On age specifically: the age calculator increments full years on the birthday itself, so someone born 1990-10-03 is still 35 on 2026-10-02 and 36 from 2026-10-03. The “years, months and days” line uses the same breakdown rule, so it never fights the full-years figure.

If you were born on 29 February

Ordinary years have no 29 February, so the anniversary falls on 28 February - the rule most calendars and reminder apps use, and the one the output names when it has been applied. A baby born 2028-02-29 sees anniversaries on 2029-02-28, 2030-02-28 and 2031-02-28 before returning to 2032-02-29. So “a birthday every four years” is not quite right, and 2100 will not be a leap year.

Where to run the numbers

• Between two dates: days between two dates - day count, weekday tally, weeks and whole months, the weekday of each end, plus hours when you add clock times.
• Forward from a date: date add and subtract - due dates, notice periods, a start date plus a duration.
• Only a birthday: age calculator - full years, days since birth, a countdown to the next birthday and what age it reaches.

All three pages share one month and clamp rule, so “start + duration = end” and “start to end = duration” agree with each other. Everything is computed in the browser on this device; what you type never leaves this device.

Related questions

“The contract runs 3 months from signature” - when does it end? On the matching day-number, clamped to the month end when that day does not exist. Signed 2026-11-30, three months later is 2027-02-28, not 2 March.

I want “days remaining”, not “days between”. Same figures, different reading: with the last day excluded, today to tomorrow is 1 day, which is exactly what a countdown means by “1 day left”.

Why do pregnancy dates have two algorithms? 40 weeks counts 280 days from the first day of the last period; from conception it is about 38 weeks. Decide which one your source uses before trusting the row above.

Does daylight saving break the day count? No. Days are counted midnight to midnight in local time, so a stretch crossing a clock change is still exactly as many days as it looks - no 23-hour or 25-hour stragglers.