What Is ISO Week Numbering?

The Standard Behind the Number

ISO week numbering is the global standard used in logistics, manufacturing, finance, and software analytics. It is defined by ISO-8601, the same specification that standardizes date and time representations across international systems. The goal is to give every week of the year an unambiguous label that teams in different countries and cultures can use without confusion.

Before this standard became widely adopted, organizations invented their own week-numbering schemes. Some started weeks on Sunday, some on Monday. Some counted the week that contained January 1 as week 1 regardless of what day it fell on. The inconsistency created reporting headaches whenever data crossed organizational or national borders.

The Two Core Rules

ISO week numbering rests on exactly two rules. First, weeks always start on Monday. Second, week 1 is the week that contains the first Thursday of the year.

The Thursday rule has a mathematically equivalent form: week 1 is the week that contains January 4. Since January 4 always falls in the first "real" week of the year under ISO logic, this is just another way to state the same definition. Both formulations produce identical results.

The practical consequence is that some days in late December belong to ISO week 1 of the following year, and some days in early January belong to the last ISO week of the previous year. This surprises people who encounter it for the first time, but it is entirely intentional — the goal is consistent whole weeks, not alignment with calendar months.

Year-Boundary Examples

December 31 in a non-Thursday year

If December 31 falls on a Tuesday, then the Monday of that week is December 29 and the Thursday is January 1 of the next calendar year. Under ISO rules, that Thursday is in the new year, so the whole week — including December 29, 30, and 31 — is week 1 of the next ISO year, not a final week of the current one.

Early January belonging to the prior ISO year

Conversely, if January 1 falls on a Friday, then the Thursday of that week falls on December 28 of the previous calendar year. That means the entire week belongs to the ISO year that just ended, not the new one. January 1, 2, and 3 all carry an ISO year label one less than their calendar year.

Why This Matters for Analytics and Reporting

If your dashboards use week labels, a mismatch between calendar-year logic and ISO-year logic will show up as broken trends at year boundaries. A metric that looks perfectly steady through December may appear to drop sharply in the last week purely because one system labels it as week 53 of the old year and another labels it as week 1 of the new year.

The safest practice is to always store both the full calendar date and the ISO year-week label (for example, 2025-W52) in your data. When you need to aggregate by week, filter on the ISO year-week field rather than deriving it at query time from the calendar date, since different query engines may apply different week-numbering conventions by default.

SQL databases are a common source of confusion here. MySQL's WEEK() function has a mode parameter that controls the week-numbering convention. PostgreSQL's date_part('week', date) follows ISO-8601. If you switch databases or combine data from multiple sources, audit the week definitions before trusting aggregated reports.

ISO Week Numbers in Spreadsheets

Excel does not have a native ISO week number function in all versions. The most portable formula is =ISOWEEKNUM(date), available in Excel 2013 and later. For older versions, a commonly cited workaround uses INT((date - WEEKDAY(date, 3) - DATE(YEAR(date + 4 - WEEKDAY(date, 3)), 1, -3)) / 7).

Google Sheets supports ISOWEEKNUM directly. Both applications treat the result as a simple number, not a composite year-week label. When late December dates return week 1, you need to derive the ISO year separately — it is not always the same as the calendar year.

Verifying Edge Cases

The most reliable way to verify unusual boundary dates is to use a dedicated week-number calculator rather than reasoning through the ISO rules manually. Enter December 28–31 and January 1–4 for the years you care about and confirm the week numbers before finalizing any report logic. A small verification step here prevents a class of reporting bugs that are notoriously hard to diagnose later because the data looks superficially correct.