ISO Week Numbers vs US Week Numbers

The problem is not the week number. It is the rule behind it.

Ask two systems for the week number of the same date and you can get two correct answers. Friday, January 1, 2021 was 2020-W53-5 in the ISO week-date system. In a common US-style Sunday-first system, the same date was in Week 1 of 2021. On Sunday, January 3, 2021, many US calendars had already moved to Week 2, while ISO was still in Week 53 of 2020.

That sounds like a bug until you see the hidden assumption. Week numbers are not just labels. A week-numbering system must answer three questions: which day starts the week, which week counts as Week 1, and whether dates near New Year belong to the old week-year or the new one.

ISO 8601 answers those questions one way. Many US tools answer them another way. Programming libraries add another wrinkle with week 00. If you exchange reports, payroll cutoffs, school plans, factory schedules, retail comparisons, or analytics dashboards across countries, the difference is not academic.

The short comparison

The visual reason they diverge

What ISO 8601 actually says

The ISO week-date system is built around complete weeks. Monday is day 1, Tuesday is day 2, and Sunday is day 7. A week-year has either 52 or 53 full weeks. Week 1 is the week that contains the first Thursday of the Gregorian year. The same rule is often expressed as “the week containing January 4,” because January 4 is always inside ISO Week 1.

The practical consequence is that the ISO week-year is not always the same as the calendar year printed in the date. Sunday, January 1, 1995 was 1994-W52-7. Tuesday, December 31, 1996 was 1997-W01-2. The calendar dates look like 1995 and 1996; the ISO week dates belong to different week-years.

That behavior is intentional. It keeps every ISO week as a Monday-Sunday block and keeps most of each numbered week inside the year named by that week. This is useful when people compare weekly production, weekly revenue, weekly staffing, or weekly deliveries.

What “US week number” usually means

There is no single universal “US week number” standard in the same sense as ISO 8601. The phrase usually means a Sunday-first calendar where the week containing January 1 is Week 1. Microsoft Excel’s WEEKNUM function describes this as System 1. With the default return type, Excel starts weeks on Sunday and makes the week containing January 1 Week 1.

That is why US-style week numbers often feel more intuitive to people reading a January calendar. January 1 is in Week 1 because it is January 1. The tradeoff is that Week 1 may be a partial week, and the first Sunday can move the count to Week 2 after only one or two January days.

This is not “wrong.” It answers a different business question: which numbered week inside this calendar year contains this date? ISO answers: which complete Monday-Sunday week-year does this date belong to?

Concrete examples

The software trap: %U, %W, %V, and Excel

Developers and spreadsheet users often assume a function called “week number” must mean one thing. It does not. In Python-style date formatting, %U is a Sunday-first week number where days before the first Sunday are in week 00. %W is similar but Monday-first, with days before the first Monday in week 00. %V is the ISO week number, and it belongs with %G, the ISO week-year, not ordinary %Y.

Excel has a different interface. WEEKNUM(date) defaults to System 1, where the week containing January 1 is Week 1. WEEKNUM(date, 21) uses System 2, the ISO method. Newer Excel versions also have ISOWEEKNUM(date). If you mix WEEKNUM and ISOWEEKNUM in the same workbook, dates around New Year are where the mismatch becomes visible.

The safest rule is simple: never store only year and week unless you also store the week system. Store isoYear, isoWeek, and a date range, or store a clearly named value such as usSundayWeek.

Locale settings are not the same as ISO

Unicode CLDR, the locale data used by many platforms, stores regional week preferences such as first day of week, weekend days, and the minimum number of days required in Week 1. For the United States, current browser/ICU data typically gives Sunday as the first day and one minimal day in Week 1. For the United Kingdom, Spain, France, Germany, and the Netherlands, it typically gives Monday as the first day and four minimal days, matching ISO-style week-of-year behavior.

That explains why changing an app’s region can move the leftmost day in the calendar grid. It also explains why a week number can change when data moves from a US-configured dashboard to a European-configured one. The date did not change. The locale rule did.

Practical rules for international teams

• Write ISO week when you mean ISO: for example, 2026-W01, not just “week 1.”
• Add the date range for deadlines: “ISO Week 1, 2025-12-29 to 2026-01-04.”
• Do not mix YYYY with ISO week numbers. Use ISO week-year notation such as 2026-W01.
• In spreadsheets, choose either ISOWEEKNUM or WEEKNUM deliberately. Do not rely on defaults in shared workbooks.
• For US-European reporting, define whether weeks run Sunday-Saturday or Monday-Sunday before comparing weekly totals.

The bottom line

ISO week numbers are best when weeks are operational units: production weeks, school weeks, logistics weeks, payroll periods, and international reporting. US-style week numbers are common when the calendar year is the primary frame and Sunday-first calendars are expected. Both are legitimate. The mistake is sending a bare number like “Week 1” and assuming everyone’s software will infer the same rule.

Sources and further reading

• ISO/WD 8601-1 draft hosted by the Library of Congress
• Python documentation: datetime.date.isocalendar() and date format codes
• Microsoft Support: Excel WEEKNUM function
• Unicode LDML / CLDR date and week data documentation