Adding days without creating deadline confusion
“In 30 days” sounds simple, but a useful result needs a definite starting point. Today works for personal planning; following up an earlier agreement needs the date of that event instead.
Fix the starting point
Adding 1 day moves to the next date. Adding 0 keeps the same date. If instructions call the starting date “day 1”, that is a different, inclusive counting convention and needs to be stated before calculating.
“Today” changes over time and can differ between locations near midnight. When sharing a plan, write the starting date rather than relying only on “two weeks from today”.
A day count is not a month count
Adding 30 days is not always the same as adding a month. Months have different lengths, and leap years change February. Use the unit specified by the original instruction rather than silently replacing a month with 30 days.
Calendar-day addition includes weekends. “Business days” requires a definition of weekends and holidays, not just a different number.
References: US Naval Observatory — Leap years
A calculated date does not interpret a deadline
The result cannot tell you whether submission closes at midnight or at a particular business hour, or whether a holiday moves the deadline. Obtain those conditions from the relevant organisation.
For periods measured in hours, retain the starting time and time zone. A daylight-saving transition can separate one calendar day from 24 elapsed hours.
References: MDN — Date.setDate and daylight-saving transitions
Worked example: a follow-up in 45 days
Starting on the illustrative date 2026-09-29, adding 45 calendar days gives 2026-11-13. Check it in parts: 1 day to 30 September, another 31 to 31 October, and 13 more to 13 November.
For a different boundary example, 30 days after 2026-01-31 is 2026-03-02, not the end of February. If the actual instruction says “one month”, do not silently replace it with that calculation.