How week numbers work: the ISO system explained

In the ISO week system — the one businesses, payroll and diaries use — a week runs Monday to Sunday, and week 1 is whichever week contains the year’s first Thursday. Two odd consequences fall out of that single rule: most years have 52 weeks, but some have 53, and a date sitting near New Year can belong to a week count that names a different year from the one on the calendar.

The rule

The mechanism is simpler than it sounds once you fix the anchor point. Take Thursday as the marker day, find whichever Monday-to-Sunday week contains it, and that’s week 1. An equivalent and often easier test: week 1 is always the week containing 4 January, because 4 January can never fall more than three days from the year’s first Thursday. If your date falls in the same Monday-to-Sunday span as 4 January, you’re in week 1, whatever the calendar date looks like.

This is why the system starts weeks on Monday rather than Sunday: the whole scheme is built around finding a stable midpoint for a seven-day block, and Thursday, sitting fourth in a Monday-start week, is that midpoint. Change the start day and the anchor logic collapses.

The 53-week year

Because a year has 365 or 366 days — not an exact multiple of seven — the weeks don’t divide evenly, and the leftover days occasionally add a whole extra week rather than a partial one. A year gets a 53rd week when 1 January itself falls on a Thursday, or when it falls on a Wednesday and the year is a leap year (the extra day in February shifts the following January’s weekday far enough to matter). 2026 is one of these: it is a 53-week year in the ISO system.

For everyone else, the year ends cleanly on week 52 and the next year’s week 1 picks up right after. For a 53-week year, that extra week has to come from somewhere, and it comes at the edges — which is exactly where the next problem shows up.

Dates that defect

Because week 1 is defined by where 4 January falls, not by the calendar page, the days right around New Year regularly belong to a different year’s week count than their date suggests. Two examples fix the idea: 1 January 2027 belongs to week 53 of 2026, not week 1 of 2027, and 30 December 2024 belongs to week 1 of 2025, three days before the calendar year has even ended.

This isn’t a quirk to shrug off if you run payroll, shift rosters or project plans on week numbers. A system that labels timesheets or delivery schedules by ISO week can silently attribute the last days of December to the wrong year’s totals, or the first days of January to the year that’s just finished, unless it applies the same first-Thursday test consistently. Reconciling a “week 1” invoice against calendar-year accounts is a common place this bites: the week and the year it’s filed under can legitimately disagree.

Checking any date

Working out which ISO week a specific date falls into by hand means locating the nearest Thursday and counting forward — manageable, but easy to get wrong right at the December-January boundary where the defections happen. The date calculator’s week mode applies the first-Thursday test directly to any date you enter, returning the correct week number and its associated ISO year without the manual counting, which is exactly where errors tend to creep in.

The same logic explains why ISO 8601, the international standard that defines this week-numbering scheme alongside its date formats, treats the week-year as a distinct field from the calendar year in the first place: it’s the only way to make week numbers behave consistently across the boundary where most ad hoc systems break.