Three common week starts
"What day does the week start?" looks like a settled question until you compare a wall calendar in Berlin, a phone calendar in New York, and an Excel sheet from a payroll team in the Gulf. There are three first-day conventions you will see in practice:
- Monday-start. The default in most of Europe, in most international business systems, and the rule defined by ISO 8601. Used wherever a "work week" framing is implied.
- Sunday-start. Common in the United States, Canada, parts of Latin America, much of East Asia, and in many consumer calendar apps. Useful for "weekend into next week" framings and for liturgical and academic schedules.
- Saturday-start. Common across much of the Middle East and North Africa, where the working week typically runs Sunday through Thursday and the weekend falls on Friday and Saturday.
None of these is wrong. They are calibrated to different working weeks and different cultural rhythms. The trouble starts when one team labels a week using its convention and another team reads that label using a different one.
How a different start day changes the week number
The week-start setting controls which days fall into the same numbered block. If a year begins on a Wednesday, then under a Monday-start system the first calendar week holds Wed–Sun; under a Sunday-start system it holds only Wed–Sat (the prior Sunday already started "week 1" in some implementations); under a Saturday-start system the first full week may not begin until the following Saturday. Two people looking at the same Tuesday can disagree about whether it lives in week 1 or week 2.
ISO 8601 sidesteps this by being explicit. It pins week 1 to the week containing January 4 and starts the week on Monday. That gives a single, deterministic answer no matter where you are. If you want to understand the underlying rules — the Thursday test, week 53 years, and how the ISO week year can drift from the calendar year — see the ISO 8601 week number guide.
Where each convention shows up
Monday-start (ISO 8601)
Used by most European national calendars, by international logistics and manufacturing, by most enterprise resource planning systems, by GitHub and many developer tools, and by the standard week functions in most server-side date libraries. If a system asks for "ISO week," that is Monday-start.
Sunday-start
Used in many US-focused consumer calendar apps, in retail planning calendars, and in the default of spreadsheet functions like WEEKNUM when no type is specified. Several major operating systems also default to Sunday-start in their built-in calendar widgets when the locale is set to a Sunday-start region.
Saturday-start
Used in countries where the customary working week runs Sunday through Thursday. Locale settings in operating systems and office software respect this when the region is set accordingly, so a date picker in those locales begins the week on Saturday.
Why the working week is the real driver
Week-start conventions are not chosen at random. Each convention puts the weekend at the right edge of the week so that the working block is visually contiguous:
- Monday-start places the weekend (Sat–Sun) at the end of the row.
- Sunday-start places the weekend (Sat) at the end and the rest day (Sun) at the start, mirroring the cultural week.
- Saturday-start places the weekend (Fri–Sat) split around the row to put the working week in the middle.
Once you see this, the apparent disagreement is really about which calendar best describes how local life is organized, not about which is mathematically correct.
Worked example: a year that begins on Wednesday
Imagine a year whose January 1 is a Wednesday. The week containing Jan 1 has these seven days: Mon Dec 30, Tue Dec 31, Wed Jan 1, Thu Jan 2, Fri Jan 3, Sat Jan 4, Sun Jan 5.
- ISO 8601 (Monday-start, Thursday rule). The Thursday of this week is Jan 2, which sits in the new year, so this is week 1 of the new ISO week year. Jan 1 belongs to week 1.
- US-style Sunday-start "week 1 = the week containing Jan 1." The Sunday-start week containing Jan 1 begins on Sun Dec 29 and ends Sat Jan 4. That becomes week 1, but it is "week 1" by a different definition than the ISO one.
- Saturday-start. The Saturday-start week containing Jan 1 begins on Sat Dec 28 and ends Fri Jan 3. By the same "first week containing Jan 1" rule, this is week 1 in that system.
The same Tuesday, Jan 7, lands in week 2 in all three systems — but only because the example year cooperates. Switch to a year that starts on a Friday and the three systems will disagree on Jan 7 because they pick different starting Saturdays / Sundays / Mondays. That is exactly the situation where "what week is it?" becomes a multi-answer question.
Converting between systems
The reliable way to convert is to anchor on the date, not the week number. Two patterns are enough for almost any conversion:
- Date in, week out. Start with a calendar date. Apply the rule for the target system to get the week number. The ISO converter on this site does that for ISO 8601; spreadsheet functions like WEEKNUM with the appropriate return type cover Sunday- and Saturday-start systems.
- Week label out, date back. When you receive "week 14" from a colleague, ask which system they are using and convert their week 14 back into a concrete Monday–Sunday range. Compare that range to your own week 14 to find the offset. Carrying the date range alongside the week number makes the conversation unambiguous.
For ISO 8601 specifically, the safest written form is the ISO week code, such as 2026-W19. It carries the year, the week, and an implicit Monday-start convention all in one short string.
Common mistakes
- Mixing "week 1 contains Jan 1" with ISO. ISO does not say "week 1 is the week of Jan 1." It says "week 1 contains Jan 4." Those are different rules and will produce different answers around New Year.
- Assuming Sunday-start equals US. Several US enterprise systems are configured to ISO 8601 Monday-start because they integrate with European partners. Always confirm before assuming.
- Trusting locale alone. Two devices in the same country can show different week starts because one was set up by a user who picked a different regional preference. Locale is a default, not a guarantee.
- Using "week N" without a year. "Week 1" alone is meaningless once you cross New Year. Always pair the week with an ISO year, or include the date range.
- Toggling the calendar app halfway through a project. Switching from Sunday-start to Monday-start mid-quarter renumbers everything visually and makes old notes look wrong. Pick one and stay with it.
A practical recommendation
For anything that crosses regions or that needs to remain stable for years — payroll cycles, sprint logs, contract milestones, audit trails — use ISO 8601 Monday-start and write the full ISO week code. Reserve Sunday- or Saturday-start systems for visual presentation in places where readers expect that local format. Two layers (a stable internal label, a localized display) avoid almost every disagreement.
If you need a pre-built planning surface that already uses Monday-start, the printable year-in-weeks calendar is set up that way by default. For the live current value, the current ISO week number today page shows it next to the full week range so there is no room for confusion.