Week 1 and week 2: which counting method is being used

Someone writes "second week of the month" in a recurring meeting invite. Half the attendees show up on the 8th, the rest on the 15th. Or a supplier quotes delivery in W15 and the receiving team reads it one week off. Or a payroll sheet says week 3 and the calendar app on the desk says week 2.

None of this is a mistake in arithmetic. Weeks get numbered by at least three different methods, only one of them is defined by a published standard, and everyday language uses the same words for all three. Sorting out which method is in play takes about five minutes, and it is the difference between a shared schedule that holds and one that generates a thread of clarifying emails every month.

Three different things are called week 1

The first method is the year running number. Weeks are counted from the start of the year, so a date in April lands somewhere near week 15. Manufacturing, logistics, and a lot of European business correspondence use this instead of dates.

The second method is the month running number. Weeks are counted inside a single month, which is what most people mean by "the second week." School timetables, community schedules, and internal office documents use this.

The third method is the ordinal weekday. "Second Tuesday" counts occurrences of a weekday within the month, not weeks. Recurring meetings and municipal collection schedules use this.

Only the first method has a fixed definition. The second is genuinely ambiguous. The third is unambiguous but counts something different from the other two, which is why converting between them by hand produces errors.

The confusion comes from the fact that all three can be written as "week 2." "The second Tuesday" is clear. "Tuesday of the second week" is not, because the answer depends on where the second week starts. That single phrase is responsible for most of the misfires in shared calendars.

February 2026 shows the gap plainly. The 1st falls on a Sunday. Counting with weeks starting Sunday, the first week of February is one day long. Counting with weeks starting Monday, January 26 through February 1 belongs to January, and February's first week starts on the 2nd. Under one reading, Monday of the second week is February 2. Under the other, it is February 9.

The year numbering is defined, and the definition is short

For the year running number there is nothing to argue about. The iCalendar specification, which is the format calendar apps use to exchange events, states it directly.

Week number one of the calendar year is the first week that contains at least four (4) days in that calendar year.

That sentence appears in RFC 5545, the same document that defines how recurring events are written. With weeks starting on Monday, the rule is equivalent to "the week containing the first Thursday."

The consequence at year boundaries surprises people. Week 1 of 2026 runs from Monday, December 29, 2025 through Sunday, January 4, 2026. December 29 to 31 are dated 2025 but numbered as the first week of 2026. Any staffing sheet that spans the new year has to decide how to label those three days, and the decision is easier to make once rather than every December.

The same specification allows week numbers from 1 to 53, and it notes the exact condition for a 53rd week. With a Monday week start, week 53 happens only when January 1 falls on a Thursday, or in a leap year when it falls on a Wednesday. January 1, 2026 is a Thursday, so 2026 has a week 53, running December 28 through January 3, 2027. Any planning template built on the assumption that a year has 52 weeks overflows this year.

One more setting sits underneath all of it. The specification has a separate field for the day the week starts, and changing it moves dates between weeks and shifts the numbers. Agreeing on a week number without agreeing on the start day settles nothing.

The month has no agreed definition of week 1

Nothing equivalent to the standard above exists for numbering weeks inside a month. Three conventions are in active use.

Convention Week 1 is Behaves badly when
Containing week The week that contains the 1st The 1st falls late in the week, making week 1 one or two days long
First full week The first week entirely inside the month Skips days at the start of the month entirely
Fixed date blocks Days 1 to 7, then 8 to 14 Blocks stop lining up with weekdays

The third convention breaks the link between a week and its weekdays, which sounds unusable until it turns up in timesheet and revenue systems, where it is common.

Since no convention is authoritative, the practical move is to publish one. A single line in the margin of the schedule, stating that week 1 is the week containing the 1st and that weeks start Monday, ends the ambiguity for everyone who reads it. A notice saying "stock count in week 3" without that line will, in some months, gather people a week late.

The trap that survives longest is the pay period. When a workplace closes its timesheets "at the end of week 4," the containing-week convention and the first-full-week convention produce cutoff dates a week apart, and months that begin on a Friday or Saturday show the largest gap. Deadlines that involve money are better written as dates. Week labels are safe for cleaning rotas and duty rosters, where being a week off costs nothing.

Ordinal weekdays remove the ambiguity and add a gap

Switching to "second Tuesday" makes the reference exact. It also introduces a different problem: some months have four occurrences of a given weekday and some have five.

In 2026, February has Tuesdays on the 3rd, 10th, 17th, and 24th, which is four. March has them on the 3rd, 10th, 17th, 24th, and 31st, which is five. A meeting set to the fifth Tuesday simply does not occur in February. Quarterly reviews pinned to a fifth weekday quietly skip months.

The fix is to use "last Tuesday" rather than "fifth Tuesday" when the intent is end of month. Every month has a last Tuesday. Calendar apps expose the ordinal and the "last" option as separate choices in the repeat settings, so the distinction is available without any workaround.

Converting an existing series is where the count changes. A meeting described as "Tuesday of the second week" under the containing-week convention is not always the second Tuesday. When the 1st falls on a Wednesday, the first week holds no Tuesday at all, so the second week's Tuesday is the first Tuesday of the month. Rewriting a batch of recurring events from week language to ordinal weekdays therefore needs a check month by month for the first quarter, not a blanket find and replace.

Recurring series also have a ceiling. Google Calendar's help states that a recurring event can be set to repeat up to 730 times. A daily series reaches that in roughly two years. A rota built as an open ended recurrence stops producing entries at some point in the future, without an error, which is worth knowing before a duty schedule is handed to a team.

Spreadsheets and calendars number weeks differently

Week numbers calculated in a spreadsheet often disagree with the ones displayed in a calendar app, and the cause is usually a default argument.

Google's documentation for the WEEKNUM function says the type argument defaults to 1, which treats Sunday as the first day of the week, and describes system 1 as treating the week containing January 1 as the first week of the year and numbering it 1. Type 2 starts weeks on Monday, and the documentation identifies it as the method specified in ISO 8601, also known as the European week numbering system.

So the default is not the standard. Because it makes the week containing January 1 into week 1 unconditionally, it can report a number one higher than the standard method in years when January 1 lands late in the week. That single off-by-one accounts for a large share of "the spreadsheet says week 3, the calendar says week 2" reports.

There is a related hazard in month week numbers. No built in function returns them, so teams write their own formula, usually dividing the day number by seven or offsetting from the weekday of the 1st. Two years later nobody can say which convention the formula implements. Writing the convention into a cell note next to the formula saves the next person from reverse engineering it.

Turning week numbers on in macOS

Once the method is settled, it helps to see it on screen rather than compute it. The Calendar app included with macOS has a setting for exactly this. Apple's user guide lists Show week numbers among the Advanced settings, described as showing week numbers in Week, Month, or Year view. It is reached from the Calendar menu, then Settings, then the Advanced tab.

The week start day lives elsewhere. The same guide describes the General settings, which include how many days per week to show, either 5 or 7, and "Start week on," the day on which to start the week in Week, Month, and Year view. Enabling week numbers while leaving the start day on Sunday produces numbers that do not match the standard, so both settings need to be set together.

Two habits keep the display honest once it is on. First, check the number shown for the first week of January against the four day rule, because that is the only week of the year where an incorrect start day is obvious at a glance. Second, when a schedule is printed or exported for someone outside the team, include dates alongside any week label, since the reader's app may be configured differently and will renumber the same days without warning.

Google Calendar on the desktop keeps the start day under Settings, then View options, where the help page describes choosing the day the week starts on, setting a custom view, and using an alternate calendar. The available views are day, week, month, year, schedule, and 4 days. A week number display is not among the options described on that settings page, so a desktop app that draws the numbers directly is the shorter route for anyone who needs them visible all day. A side by side look at what different Mac calendars expose is collected in Compared with other calendars.

What to change first

Pick one convention and write it down where the schedule is read: weeks start Monday, and the year numbering follows the four day rule. Then rewrite any recurring event that says "week of" as an ordinal weekday, using "last" instead of "fifth" for anything meant to land at month end. If the calendar on the Mac still hides week numbers after that, turn them on in the Advanced settings, and check how a desktop calendar handles repeats and travel before adding another tool: Caltimate documents both.

Frequently asked questions

Which week numbering should a team standardise on?

The one defined in the iCalendar specification: week 1 is the first week containing at least four days of the new year, with weeks starting Monday. It matches what calendar apps display and what European suppliers mean by a week number, so nothing has to be translated later.

Is week 1 of the month the week containing the 1st, or the first full week?

Both are in use and neither is wrong, because no standard defines month week numbers. Rather than looking for a correct answer, state the convention in the document itself. One line saying weeks start Monday and week 1 contains the 1st removes the question for every reader.

Why does a fifth Tuesday meeting sometimes not happen?

Because some months only have four Tuesdays. February 2026 has four, March 2026 has five. For anything meant to fall at the end of the month, use the "last" option in the repeat settings instead of the fifth ordinal, since every month has a last Tuesday.

Why does a spreadsheet report a different week number from the calendar app?

Usually the function default. WEEKNUM defaults to Sunday start and treats the week containing January 1 as week 1, which is not the standard method. Passing the Monday start type, or using the ISO variant of the function, brings the two into agreement.

Back to all posts