Quarter of the Year Calculator

How the Quarter of the Year Calculator works

Calendar quarters never move: Q1 is always January through March, Q2 April through June, and so on, regardless of any organization's own fiscal calendar. Fiscal quarters instead count three-month blocks starting from whatever month you designate as the fiscal year's first month, wrapping around the December/January boundary as needed — set that start month to April and "Q2" becomes July–September; set it to October and "Q4" becomes July–September of the following fiscal year instead.

Three fiscal-year-start conventions come up constantly in practice and are worth naming directly: April 1 (the UK government's and India's fiscal year, and Japan's), July 1 (Australia's fiscal year), and October 1 (the US federal government's fiscal year, one calendar quarter offset from the US federal government's own October start relative to the calendar). A US-based multinational reporting to a UK parent company, or a contractor billing against a US federal fiscal year, routinely needs to translate between two of these conventions on the same date — which is exactly the side-by-side comparison this tool exists to make painless.

Once a quarter (calendar or fiscal) is identified for your date, the tool reports its exact start and end civil dates, the ISO-8601 week numbers those two boundary dates fall in (useful since a quarter's boundary essentially never lands on a clean week boundary), the total number of days the quarter spans, and how many of those days have elapsed as of your chosen date versus how many remain — day counts that shift by exactly one whenever a leap February falls inside the reported quarter.

Worked example

Take July 12, 2026. On the plain calendar, that's squarely inside Q3 (July–September): calendarQuarter = 3, with the quarter running July 1 through September 30, 2026 — 92 days total (31 + 31 + 30), of which 12 have elapsed and 80 remain. Those two boundary dates fall in ISO week 27 (July 1) and ISO week 40 (September 30) of 2026.

Now compare fiscal readings of that identical date. With a fiscal year starting April 1 (the UK/India convention), July 12, 2026 falls in fiscal Q2, because the block of months three past the April start is July–September — the same three-month window as the calendar Q3 above, just labeled Q2 under that fiscal convention. With a fiscal year starting October 1 (the US federal convention), the same date falls in fiscal Q4 of federal fiscal year 2026, since FY2026 runs October 1, 2025 through September 30, 2026, and July–September is the fourth three-month block inside that span. Three different quarter labels — Q3, Q2, Q4 — for the exact same July 12, 2026, depending purely on which fiscal-year-start convention is being asked about.

Edge cases this tool handles correctly

Leap-year Q1 is one day longer

Q1 (January–March) runs 90 days in a non-leap year (31 + 28 + 31) and 91 days in a leap year (31 + 29 + 31) — the only quarter whose total length changes from year to year, since February is the only month with a variable day count and it always falls inside Q1.

Fiscal year straddling two calendar years

For any fiscal-year-start month other than January, roughly half the fiscal year's quarters fall partly or entirely in the calendar year before the fiscal year's own number — a US federal FY2026 Q1 (October–December 2025) is entirely inside calendar year 2025, which trips up anyone assuming a fiscal year's number always matches the calendar year its months belong to.

Quarter boundaries rarely align with ISO week boundaries

Because ISO-8601 weeks run Monday to Sunday and a quarter's first day can fall on any weekday, a quarter's start or end date is almost never itself the first or last day of its own ISO week — the reported ISO week number marks which week contains that boundary date, not a week that begins or ends exactly with the quarter.

A fiscal-year-start month equal to January

Setting the fiscal-year-start month to 1 makes every fiscal-quarter figure identical to the plain calendar-quarter figure — there's no separate fiscal convention to apply, so the tool's two outputs simply agree in that specific configuration, which is the expected default behavior rather than a special case needing extra logic.

Days elapsed and days remaining always sum to the total

daysElapsed counts from the quarter's first day through your chosen date inclusive of both ends, and daysRemaining counts the days strictly after your date through the quarter's last day — the two figures always add up to exactly the quarter's total day count, a useful sanity check when comparing across different quarters or fiscal conventions.

A date on the very last day of a quarter

Entering the final calendar day of any quarter reports daysRemaining as zero and daysElapsed equal to the full quarter length — there's no special-case handling needed since the same elapsed/remaining arithmetic applies uniformly across every day in the quarter, including its first and last.

Frequently asked questions