Why Month Length Changes the Answer

The 30-day assumption and where it fails

Treating a month as 30 days is convenient and wrong in eleven months out of twelve. Seven months have 31 days, four have 30, and February has 28 or 29. The assumption is exactly right in April, June, September and November and nowhere else.

Over a single month the error is small. Over a year of month-by-month arithmetic it accumulates to about five days, which is why a 30-day-month model and a calendar model give visibly different answers for anything measured in months over a long span.

Use this guide with the right tool: Open the Date Difference Calculator for calendar difference in years months days and total days. If the question shifts, compare it with the Months Between Dates Calculator or the Days Between Dates Calculator.

Borrowing, and why it goes wrong

Manual age calculation usually works column by column: subtract days, subtract months, subtract years, borrowing when a column goes negative. The borrow step is where the month length enters, and where people default to thirty.

The correct borrow takes the actual length of the month preceding the reference date. Borrowing from a February gives 28 or 29; from a March, 31. Using thirty in either case shifts the days field by up to three, which is enough to cross an assessment band or a policy boundary.

End-of-month arithmetic

Adding a month to 31 January has no exact answer, because February has no 31st. The two standard responses are to clamp to the last day of the target month, or to roll forward into the next. Both appear in real systems, and they differ by up to three days.

This matters most for anything recurring monthly from a date near the end of a month — subscriptions, medication schedules, contractual milestones. Whichever convention applies, the important thing is that it does not change between calculations, because a sequence built on two conventions cannot be reconstructed.

When to abandon months entirely

If what you actually need is a duration rather than a calendar structure, days are cleaner. Total elapsed days is unambiguous, needs no convention, and handles leap years automatically because every day in the span is simply counted.

Use months when the question is calendar-shaped — anniversaries, monthly cycles, age in a form that asks for months. Use days when the question is about quantity. Problems arise when a days answer is reported as months, or the reverse, without saying so.

Worked example

The shape of the calculation stays the same with your own figures. What changes is the source of the rule, so check that before treating the number as settled.

Common mistakes to avoid

• Assuming a month is 30 days. It is only true four months of the year. The error accumulates to about five days annually.
• Borrowing a flat thirty in the days column. Borrow the real length of the preceding month, or the days field is off by up to three.
• Switching end-of-month conventions between calculations. Clamping and rolling both exist. Inconsistency makes a sequence irreproducible.

Use the right calculator

Start with whichever matches the information you already hold. The other two are there for when the question shifts.

Date LabDate Difference Calculatorcalendar difference in years months days and total days

Date LabMonths Between Dates Calculatorcomplete calendar months and residual days between dates

Date LabDays Between Dates Calculatorelapsed calendar days between two dates

Frequently asked questions