How Many Days Are In Three Months

Three months sounds simple until you actually need to count the days.

Try it. Easy. Because of that, that's 92 days. April has 30. May has 31. March has 31. That depends entirely on which months you crossed. But how many days passed? Pick any date — say, March 15 — and add three months. June 15. But if you started in January? January (31), February (28 or 29), March (31) — you're looking at 89, 90, or 91 days depending on the year.

The answer isn't a single number. It's a range. And pretending otherwise causes real problems — missed deadlines, billing errors, contract disputes, even medical miscalculations.

What "Three Months" Actually Means

Most people treat "three months" as a fixed block of time. It's not. It's a calendar concept that shifts based on where you land.

Calendar months vs. rolling 90 days

Here's where confusion starts. April through June. But the day count varies: Q1 is 90 days in a common year, 91 in a leap year. So october through December. Plus, july through September. January through March. Q3 is 92. A calendar quarter — Q1, Q2, Q3, Q4 — is always three calendar months. In practice, q2 is always 91. Q4 is 92.

Now compare that to "90 days from today.That's why " That's a rolling window. It just counts forward 90 sleeps. It doesn't care about month boundaries. The two concepts overlap sometimes but they're fundamentally different.

The February problem

February is the chaos agent. In a leap year, 29. In a common year it contributes 28 days to any three-month span that includes it. That single day shifts everything downstream.

If your three-month window is December through February, you get 31 + 31 + 28 = 90 days (common year) or 91 (leap year). But January through March? 31 + 28/29 + 31 = 90 or 91. November through January? 30 + 31 + 31 = 92. The same "three months" label produces four different totals.

Leap year mechanics

Leap years follow a rule most people half-remember: divisible by 4, except centuries not divisible by 400. So 2000 was a leap year. 2024 was. Day to day, 1900 wasn't. So naturally, 2100 won't be. 2028 will be.

That extra day in February only matters if your three-month window includes February. If you're counting April through June, leap year is irrelevant. But for January-March, February-April, or December-February, it changes the total by one day.

Why the Day Count Matters

You might think a day here or there is trivial. In practice, it's not.

Billing and subscriptions

SaaS companies, gyms, insurance providers — many bill "quarterly" or "every three months." If they define that as 90 days but the calendar says 92, customers get billed slightly more often than expected. Over years, that compounds. Day to day, a customer paying $100 per "quarter" on a 90-day cycle pays 4. 06 times per year instead of 4. That's an extra $6 annually per customer. At scale, it's real money.

Some companies bill calendar quarters (Jan 1, Apr 1, Jul 1, Oct 1). Here's the thing — others bill rolling 90 days from signup. And the difference shows up in proration calculations, refunds, and "why was I charged twice this month? " support tickets.

Legal and contractual deadlines

Contracts love "within three months" or "ninety (90) days.In practice, ninety days later is May 1. A clause saying "notice must be given within three months of the effective date" creates ambiguity if the effective date is January 31. " Those aren't synonyms. Day to day, three calendar months later is April 30. Which controls?

Courts generally interpret "three months" as calendar months unless specified otherwise. Plus, the discrepancy has decided actual cases. But "90 days" means 90 days. If you're drafting or signing something, pick one definition and stick with it.

Pregnancy and medical timing

Obstetrics uses weeks, not months, precisely because months are inconsistent. But patients think in months. "Three months pregnant" means roughly 13 weeks — but the day count varies depending on which months those weeks fall in. Day to day, due date calculations assume 280 days from last menstrual period (40 weeks), not "nine months. " The month-based mental model is off by days to weeks.

Project planning and sprints

Agile teams sometimes plan in "three-month quarters." But a 13-week quarter is 91 days. If you capacity-plan assuming 90 working days but the quarter has 92 calendar days (minus weekends, holidays, PTO), your velocity math drifts. A 12-week quarter is 84. Small errors compound across teams.

Continue exploring with our guides on 43 14 4 5 11 5 23 52 and pete wants to write a business plan for pete's pb.

How to Calculate It Correctly

Don't guess. Use the right method for your situation.

Method 1: Calendar month addition

If you need "same date, three months later," add three to the month number. January (1) + 3 = April (4). Still, august (8) + 3 = November (11). November (11) + 3 = February (2) of next year.

But watch day overflow. January 31 + 3 months = April 31. April doesn't have 31 days. Most systems roll to April 30. Some roll to May 1. Excel's EDATE function returns April 30. Python's dateutil.relativedelta does the same. But not every tool agrees. Test yours.

Method 2: Day counting

If you need exact elapsed days, count them. Don't multiply 30 × 3. That's 90 — wrong for most three-month spans.

Instead: identify the specific start and end dates, then subtract. January 15 to April 15? Count Jan 15-31 (17 days), all of February (28 or 29), all of March (31), April 1-15 (15). Total: 17 + 28/29 + 31 + 15 = 91 or 92.

Or use a date calculator. Or spreadsheet: =END_DATE - START_DATE. Done.

Method 3: Rolling 90/91/92 days

If "three months" means "approximately 90 days" for your purpose, decide which approximation:

90 days: standard business approximation
91 days: average calendar quarter (365.25 ÷ 4)
92 days: most common actual quarter (Q3 and Q4)

Then add that many days to your start date. START_DATE + 90 in Excel. date + timedelta(days=90) in Python. This ignores month boundaries entirely.

Tools that handle this well

Excel/Google Sheets: EDATE(start_date, 3) for calendar months, start_date + 90 for rolling days. DATEDIF or simple subtraction for elapsed days.
Python: `dateutil

relativedelta(months=3)is the gold standard for calendar-based shifts, as it handles month-end overflows gracefully. That's why - **SQL**:DATEADD(month, 3, start_date)in T-SQL orstart_date + INTERVAL '3 months'in PostgreSQL. - **JavaScript**: Libraries likedate-fnsorLuxonare essential, as the nativeDate` object can be notoriously tricky with month increments.

Summary Table: When to Use Which Method

Use Case	Preferred Method	Why?
Legal Contracts	Calendar Month Addition	Provides a fixed, predictable date for renewals or expirations. That said,
Scientific Research	Day Counting	Eliminates ambiguity caused by varying month lengths. That's why
Financial Projections	Rolling Day Counting	Accounts for the actual number of days in a quarter for precise interest or revenue math.
Casual Conversation	Approximation (90 days)	Fast, intuitive, and "close enough" for non-critical communication.

Conclusion

The "three-month" problem is a classic example of how human intuition often clashes with mathematical precision. In everyday conversation, a month is a vague unit of time; in a spreadsheet, a month is a variable length of 28, 29, 30, or 31 days.

The key to avoiding errors is not to find a "perfect" definition of a month—because one doesn't exist—but to choose a definition and apply it consistently. Whether you are a project manager setting milestones, a developer writing date-logic, or a legal professional drafting a term sheet, always clarify whether you mean "the same date in three months" or "exactly 90 days from today." Precision in definition is the only way to ensure precision in results.