The Mathematics of Duration: Why "3 Months" Is Not Always 90 Days

⏱ 5 min read · Time & Planning

"Payment due in 3 months." Simple, right? Except 3 months from January 15 is April 15 (90 days). 3 months from February 15 is May 15 (89 days in non-leap years, 90 in leap years). 3 months from March 15 is June 15 (92 days). Same duration, different number of days.

This is the mathematics of duration problem: months are not uniform units. And this creates ambiguity in contracts, deadlines, and planning.

The Variable Month Problem

Months range from 28 to 31 days. February has 28 or 29 days. April, June, September, and November have 30 days. The rest have 31 days. This means "1 month" can be anywhere from 28 to 31 days depending on which month you're counting.

When you say "3 months from now," do you mean 3 calendar months (March 15 to June 15) or 90 days (March 15 to June 13)? The difference is 2 days, which might not matter for casual planning but matters a lot for legal contracts.

Months are convenient for humans but terrible for precise calculations.

The End-of-Month Edge Case

What's 1 month from January 31? Is it February 31 (which doesn't exist), February 28/29 (the last day of February), or March 3 (31 days later)? Different systems handle this differently.

Most date calculators use "same day next month" logic: 1 month from January 31 is February 28 (or 29 in leap years). But some financial systems use "30 days" or "31 days" as the definition of a month, giving different results.

This ambiguity creates disputes. A loan payment "due 1 month from January 31" might be interpreted as February 28 by the borrower and March 3 by the lender. Both interpretations are defensible.

The Leap Year Complication

Leap years add an extra day to February, which affects all duration calculations that span February. "90 days from January 1" is March 31 in non-leap years and March 30 in leap years.

This is why financial contracts specify "calendar months" or "days" explicitly, not just "months." "Payment due in 90 days" is unambiguous. "Payment due in 3 months" depends on which months are included and whether it's a leap year.

The Business Month Convention

Some industries use a "business month" convention where all months are treated as 30 days. This simplifies calculations but creates a mismatch with calendar reality.

Under this convention, "3 months" is always 90 days, regardless of which calendar months are involved. This works for financial modeling but creates confusion when you try to map it back to actual calendar dates.

A "30-day month" system says February 1 to March 1 is 30 days (even though it's actually 28 or 29). This is mathematically convenient but factually wrong.

The Quarter Ambiguity

A quarter is 3 months. But Q1 (January-March) has 90 days in non-leap years and 91 in leap years. Q2 (April-June) has 91 days. Q3 (July-September) has 92 days. Q4 (October-December) has 92 days.

So "one quarter" can be anywhere from 90 to 92 days depending on which quarter you're in. This matters for quarterly reports, quarterly payments, and quarterly planning.

Some financial systems define a quarter as exactly 91.25 days (365.25 ÷ 4) to avoid this ambiguity. But this creates a mismatch with actual calendar quarters.

Why Days Are More Reliable

For precise calculations, days are better than months. "90 days from now" is unambiguous. "3 months from now" depends on which months are involved.

This is why legal contracts often specify durations in days, not months. "Payment due within 30 days" is clear. "Payment due within 1 month" is ambiguous.

The trade-off is that days are harder for humans to think about. "90 days" requires mental math to convert to "about 3 months." "3 months" is immediately intuitive.

The Practical Solution

For casual planning, months are fine. For legal contracts, financial calculations, or anything where precision matters, use days or specify exact calendar dates.

Instead of "deliver in 3 months," say "deliver by June 15" or "deliver within 90 days." This eliminates ambiguity about month lengths, leap years, and end-of-month edge cases.

And if you must use months, specify how edge cases are handled: "1 month from January 31 is February 28 (or 29 in leap years)." Make the convention explicit.