The Deadline Calculator estimates a target date from a date-only start, a non-negative whole-number period, and either Working days or Calendar days. Working days skip Saturday and Sunday; Calendar days include every date. The entered start is not counted for a positive amount. This is a planning estimate—not a legal, employment, filing, contract, or official holiday determination.
Share the start, amount, mode, start-date convention, and holiday assumption. Verify important commitments against the governing policy or official calendar. reviewedAt records content update and executable fixture testing, not official human review.
How this is calculated
Working-day mode uses addBusinessDays: it advances from the start, then counts eligible Monday–Friday dates. Calendar mode uses addDays. Deadline mode currently has no country, regional, custom, or public-holiday selector, so its workday answer is weekend-only. Invalid dates and non-integer or negative amounts do not produce a deadline.
Assumptions and limits
Inputs are calendar dates, not timestamps; the result is a date in the browser’s calendar context.
The start is excluded. A positive amount begins counting after the entered date, even when the start is a weekend.
Do not call every Monday–Friday result holiday-adjusted: public holidays, company closures, half-days, and regional observances are not applied here.
Use the controlling contract, policy, filing instruction, or official calendar when its inclusion rule differs; this tool is not legal advice.
Age is separate: the parent fix clamps Feb 29 birthdays to Feb 28 in non-leap years and normalizes years/months to 0–11. If the engine is still old, model a planned policy with addYears/addMonths separately; this is not legal-age advice.
Worked examples
Ten weekday steps
Inputs: Start 2026-11-02; amount 10; Working days
Result: 2026-11-16
The start is excluded; ten eligible weekdays cross one weekend and land on Monday.
Weekend start
Inputs: Start 2026-11-07; amount 1; Working days
Result: 2026-11-09
Saturday is skipped, so Monday is the first counted working day.
Calendar mode
Inputs: Start 2026-11-06; amount 5; Calendar days
Result: 2026-11-11
Saturday and Sunday remain in the calendar-day move, producing Wednesday.
Boundary cases
Weekend start: a one-working-day request from Saturday returns Monday, while calendar mode can return Sunday; the mode changes the consequence.
Start inclusion: a one-working-day request from Monday returns Tuesday. An inclusive policy would produce a different date, so record the convention.
Month or year boundary: calendar mode may land on a weekend; working mode keeps advancing until an eligible weekday.
No holiday selector: a weekend-only result can fall on a public holiday or company closure and must be checked against the applicable calendar.
Duration and timezone are separate: the duration tool uses browser-local date-times, has no IANA selector, and distinguishes calendar components from total seconds. Reject a DST gap; confirm the offset for a repeated fall-back hour.
Common mistakes
Counting the start as day one without checking the source policy.
Assuming this route removes public holidays or all workday exceptions.
Selecting Calendar days when the rule says Working days, or reversing those modes.
Treating a date-only estimate as a business-hours, SLA, employment, statutory, or legal answer.
Using age or duration arithmetic as a substitute for the relevant leap-day, local-time, or timezone policy.
Only in Working days mode. Saturday and Sunday are skipped; Calendar days includes them.
Are public holidays removed?
No. This route is weekend-only. Use the Business Days Calculator or the applicable regional policy to review holidays.
Is the start counted?
No for a positive amount. The engine advances after the entered date, so one working day from Monday ends Tuesday.
Can I use it for a legal deadline?
Only as a preliminary estimate. Legal, employment, filing, and contract rules may define receipt time, holidays, cutoffs, or inclusion differently.
Does it handle timezone-aware deadlines?
No; the deadline input is date-only. For time-of-day conversion, confirm the IANA zone, DST-gap rejection, and offset choice during a repeated fall-back hour.