How to Calculate Age, Date Differences and Time Spans Correctly

Date arithmetic looks trivial until a result is challenged. Is a person born on 29 February one year older on 28 February or 1 March? Does "three days from Monday" include Monday? Does a meeting across a daylight-saving change last one hour or two? The answers depend on conventions, and the conventions need to be stated.

Age: completed years, not calendar years

Age is normally counted in completed years. Subtract the birth year from the current year, then subtract one more if the birthday has not yet occurred this year. That rule handles most cases, but two edge cases deserve attention:

• 29 February birthdays. In non-leap years, different jurisdictions treat the birthday as 28 February or 1 March. For legal purposes, follow the rule that applies where you are, not the calculator's default.
• Time zones. Someone born late in the day in one country may already be a day ahead elsewhere. For age thresholds such as eligibility dates, use the local date at the place the rule refers to.

If a form asks for age in months, for example for an infant, use completed months with the same logic. Do not convert years to months by multiplying by twelve; the day-of-month offset matters.

Counting days: inclusive versus exclusive

If an event runs from the 3rd to the 7th, does it last four days or five? Both are used. Hotel nights are usually exclusive of the checkout day; a conference programme is usually inclusive of both the first and last day. Before you quote a duration, decide which convention the audience expects, and state it if there is any chance of confusion.

Project and contract deadlines add another wrinkle. "Within seven days" may mean seven calendar days or seven working days. Working-day calculations must skip weekends and public holidays, and public holidays differ by country and year, so a simple arithmetic result can be off by several days.

Leap years and month lengths

A year is a leap year if it is divisible by four, except centuries that are not divisible by 400. So 2000 was a leap year, while 1900 was not. This matters when adding a year to 29 February: the target date does not exist in a common year.

Month arithmetic is also uneven. Adding one month to 31 January can produce 28 February, 29 February or 3 March depending on the implementation. If the exact end date matters, calculate from a fixed day of the month or specify the rule in advance.

Time spans, time zones and daylight saving

A duration measured in wall-clock time is not the same as elapsed time. When clocks move forward, a two-hour meeting that spans the change may have an elapsed time of one hour; when they move back, it may be three. Systems that store timestamps in UTC avoid this by measuring absolute elapsed time, then converting for display.

For international scheduling, always state the time zone with the time, and check whether the zone observes daylight saving. A recurring meeting set in local time can shift by an hour for participants in another country even though nobody changed the invitation.

Checking a date result

1. Write down the start date, the end date and the convention you intended.
2. Count the days in the first and last month by hand as a spot check.
3. Confirm that leap years inside the range were handled.
4. For deadlines, confirm whether working days or calendar days were meant.
5. If times are involved, confirm the time zone used for each input.

A calculator is a tool for arithmetic, not for interpreting policy. Where a deadline or an eligibility rule has consequences, read the rule itself and use the calculator to apply it, not to replace it.