Week numbers look like the simplest idea in scheduling: number the weeks 1 to 52 and everyone stays in sync. In practice, "week 29" on a European production plan and "week 29" in an American diary can be different weeks. To see why, you need the two rules that define the international standard, and the one habit that breaks it.
The two rules of ISO 8601
The international standard for dates and times, ISO 8601, defines week numbering with two rules:
- Weeks start on Monday. Every ISO week runs Monday through Sunday, with no exceptions and no partial weeks.
- Week 1 is the week containing the first Thursday of January. Equivalently, it is the first week with a majority of its days (at least four) in the new year.
The second rule is the surprising one. Week 1 is not simply the week containing 1 January. It is the first week that mostly belongs to the new year, and Thursday, as the middle day of a Monday-start week, is the tiebreaker.
Consequence one: 1 January can belong to last year
If 1 January falls on a Friday, Saturday, or Sunday, its week has a majority of days in the old year, so ISO assigns the whole week to the old year. The standard even has a separate name for the year a week belongs to, the week-year, because it can differ from the calendar year of a given date.
A concrete case: 1 January 2016 belongs to ISO week 53 of 2015. Anyone labelling that Friday "week 1" on a spreadsheet was a full week out of step with every ISO-compliant system for days.
Consequence two: some years have 53 weeks
Fifty-two weeks is only 364 days, so the leftover day or two has to accumulate somewhere. Under ISO rules, most years get 52 numbered weeks, but some get 53. 2026 is one of them: it is a 53-week year, so planners who built a 52-row schedule for 2026 are one week short.
If your organisation plans in week numbers, it pays to check the week count for the year before locking in recurring schedules, because "week 1 of next year" arrives one week later than a 52-week template assumes.
The American convention, and the off-by-one problem
Many US calendars and planners use a different scheme: weeks start on Sunday, and week 1 is simply the week containing 1 January, however few of its days fall in the new year. Both choices are reasonable on their own, but together they produce numbering that frequently disagrees with ISO by one.
For much of a typical year, a date sits one week number higher in the US scheme than in the ISO scheme, and around New Year the two can even disagree about which year a week belongs to. So when a supplier in Germany quotes delivery in "week 29" and a partner in the US reads that against a Sunday-start planner, the two sides can be planning around different weeks without either noticing.
Checking a real date
Take 18 July 2026. Under ISO 8601 it falls in ISO week 29. Whether your wall calendar agrees depends entirely on which convention it was printed with. That is the whole problem in one sentence: a week number is meaningless without knowing the rule that produced it.
The practical fix is to anchor week numbers to dates. When someone gives you a week number, ask for the Monday date of that week, or look it up yourself with the week number calculator, which follows the ISO 8601 rules described here. And if you need to know what day of the week a particular date lands on before you translate it into a week, the day of the week calculator answers that instantly.
Week numbers are genuinely useful shorthand once everyone is using the same definition. Until you have confirmed that, treat any bare week number as a question, not an answer.