LazyTools Header
Calendar Week Number — ISO 8601, Sprint Planner & Full Year Weeks | LazyTools
Date & Time Tool

Calendar Week Number — ISO 8601 Week Lookup, Sprint Planner & Full Year

Find the ISO 8601 week number for any date — with the week's Monday start and Sunday end dates shown alongside. Furthermore, the Sprint Planner is unique to LazyTools: enter a sprint start date and sprint length (1–4 weeks) and it auto-generates the full sprint calendar with ISO week numbers for every sprint in the sequence — essential for agile teams reporting by week number.

ISO 8601 & US standardSprint planner modeFull year week listDay-of-year & quarterEdge cases handled

How to use the Calendar Week Number

1
Enter a date in the Week Lookup tab
Click the date field and select any date. Additionally, choose your preferred standard from the dropdown — ISO 8601 (Monday start, used globally and in most ERP systems) or US Standard (Sunday start, common in North American spreadsheets and consumer calendars).
2
Click Find Week Number
The stat strip shows the ISO week number, ISO week year, US week number and calendar quarter simultaneously. Furthermore, the breakdown table shows the full Monday-to-Sunday range of that week, the day of year and a flag if the ISO week year differs from the calendar year.
3
Use Sprint Planner for agile team scheduling
Click the Sprint Planner tab. Enter your sprint start date, select the sprint length (1–4 weeks) and choose how many sprints to generate. Furthermore, clicking Generate Sprint Calendar produces a full table of sprints — each with its start date, end date and ISO week number(s) — ready to copy and paste into your project management tool.
4
View the full year week calendar
Click the Full Year Weeks tab and enter any year. The complete list of ISO weeks for that year appears with Monday start and Sunday end dates for every week. Furthermore, the current week highlights automatically for quick reference.
5
Copy the sprint plan as text
Click Copy as text in the Sprint Planner output to copy the entire sprint table as tab-separated text. Additionally, this format pastes directly into Excel, Google Sheets, Jira or Confluence without reformatting.

ISO 8601 versus US week numbering

Two different week numbering systems are in common use worldwide. ISO 8601 — used in Europe, most of Asia and internationally in business — starts each week on Monday. Furthermore, Week 1 always contains the year's first Thursday and at least 4 January days.

FeatureISO 8601 (global)US Standard (North America)
Week starts onMondaySunday
Week 1 definitionFirst week with a ThursdayWeek containing 1 January
Year can have52 or 53 weeks52 or 53 weeks
Used inEurope, Asia, ERP, manufacturing, ISO standardsUS, Canada, consumer apps, spreadsheets
Excel function=ISOWEEKNUM(date)=WEEKNUM(date,1)

The ISO week year edge case

The ISO week year can differ from the calendar year for dates near the year boundary. For example, 31 December 2025 is ISO Week 1 of 2026 — its Thursday is 1 January 2026. Furthermore, 29 December 2024 falls in ISO Week 1 of 2025 for the same reason. The tool flags this when it occurs, showing a warning alongside the ISO year.

How ISO week numbers are calculated

The ISO 8601 week number algorithm uses Thursday as the anchor day. Any week that contains a Thursday belongs to the year that Thursday falls in. Furthermore, Week 1 is always the week containing the year's first Thursday — equivalently, the week containing 4 January.

ISO week = ceil( (Day of year adjusted to Thursday + 3) ÷ 7 )
Adjustment = shift date to the Thursday of its week before dividing
Year start = 1 January of the ISO week year (which may differ from calendar year)
53-week years = occur when 1 Jan falls on Thursday, or Wednesday in a leap year
Recent 53-week years = 2015, 2020, 2026, 2032

Why 2026 has 53 ISO weeks

A year gets 53 ISO weeks when 1 January is Thursday, or Wednesday in a leap year. Furthermore, 2026 has 53 weeks — ISO Week 1 starts 29 December 2025 and Week 53 ends 31 December 2026. The tool correctly handles 53-week years in the full year calendar view and in sprint planning.

Worked example: sprint planning for Q1 2026

An agile development team starts their Q1 2026 sprint cycle on Monday 5 January 2026. They run two-week sprints. The Sprint Planner generates the following calendar.

SprintStart dateEnd dateISO weeks
Sprint 15 Jan 202618 Jan 2026W02–W03 (2026)
Sprint 219 Jan 20261 Feb 2026W04–W05 (2026)
Sprint 32 Feb 202615 Feb 2026W06–W07 (2026)
Sprint 416 Feb 20261 Mar 2026W08–W09 (2026)
Sprint 52 Mar 202615 Mar 2026W10–W11 (2026)
Sprint 616 Mar 202629 Mar 2026W12–W13 (2026)
Six two-week sprints cover the full Q1 2026 period — from Week 2 through Week 13. The sprint table copies directly into Jira, Notion or any project management tool, eliminating the manual work of calculating sprint boundaries across a quarter.

Using ISO week numbers in reporting

Teams that report velocity by sprint often use ISO week numbers as identifiers — "W14 velocity was 42 points". Furthermore, ISO week numbers keep sprint reports consistent across years — every week runs Monday to Sunday regardless of national holidays.

What is a calendar week number?

A calendar week number assigns a sequential number — 1 through 52 or 53 — to each year week. Furthermore, ISO 8601 defines the global standard for week numbering: weeks start on Monday, and Week 1 is the first week containing the year's first Thursday.

Week numbers reduce scheduling complexity in organisations that operate on recurring weekly cycles. A manufacturing facility schedules production runs by week number — "Week 28 target" — without ambiguity. Furthermore, all partners use the same shared reference. Moreover, agile teams track sprint velocity by week number. This keeps reports consistent across quarters and years.

Where ISO week numbers appear in practice

Manufacturing and supply chain systems use week numbers for production schedules, delivery slots and inventory cycles. ERP systems including SAP and Oracle use ISO week numbering internally. Furthermore, this makes ISO weeks the de-facto standard for enterprise scheduling. Furthermore, broadcast and media industries use a broadcast calendar based on week numbers for ad scheduling, rights windows and ratings periods.

European institutions reference week numbers for payment deadlines and submission windows. Furthermore, this convention saves time compared to specifying full date ranges. Moreover, agriculture uses ISO week numbers for planting and harvest schedules in Northern Europe. Agile software development teams adopted week numbers as a universal sprint reference across distributed teams.

Years with 53 ISO weeks

Most years have 52 ISO weeks. Approximately 71 years out of every 400 have 53 ISO weeks. Furthermore, a year has 53 weeks when 1 January falls on a Thursday or on a Wednesday in a leap year. Recent 53-week years include 2015, 2020 and 2026. Financial and supply chain systems that rely on week-based reporting need to handle these years specially, since a 53-week year has one extra reporting period compared to a standard 52-week year.

Why calendar week numbers matter in business

Week numbers eliminate date ambiguity in recurring operational schedules. Saying "shipment arrives Week 24" communicates the same window to teams in different countries without requiring timezone or date format conversion. Furthermore, ERP systems synchronise production schedules, purchase orders and delivery bookings using week numbers as the primary scheduling unit across supply chains.

Agile teams that plan and report by sprint consistently use ISO week numbers as sprint identifiers. The ISO system guarantees every sprint week starts on Monday — creating natural alignment with most office schedules. Moreover, sprint retrospectives that reference "W26 velocity" create a permanent, unambiguous record that remains readable years later without needing to know what dates Week 26 covered that year.

How the sprint planner saves planning time

Manually calculating sprint boundaries across a quarter takes 10 to 15 minutes. Furthermore, every boundary must be verified to prevent errors propagating through the sprint plan. The Sprint Planner generates a full quarter of sprints in under two seconds. Additionally, the output copies directly into project management tools without reformatting. Moreover, it handles ISO week year edge cases automatically — including sprints that span a year boundary.

Frequently asked questions

ISO 8601 is the international standard for date and time representation. Under this standard, each week starts on Monday and Week 1 is defined as the first week containing the year's first Thursday. Furthermore, this means Week 1 always contains at least 4 days of the new year. The standard is used in most of Europe, in business and manufacturing systems globally, and in ERP platforms including SAP and Oracle.
The ISO week year differs from the calendar year for dates very close to 31 December or 1 January. For example, 31 December 2025 is in ISO Week 1 of 2026, because that week's Thursday is 1 January 2026. Furthermore, this is correct behaviour — the ISO system defines the week year by which year Thursday falls in, not the calendar year of the date itself. The tool flags this with a warning in the result.
The Sprint Planner calculates start and end dates numerically, regardless of year boundaries. A sprint starting on 22 December and running 14 days correctly ends on 4 January of the following year. Furthermore, the ISO week numbers shown for that sprint reflect the correct ISO week years for each week — for example "W52 (2025) – W01 (2026)" for a sprint that crosses year-end.
A 53-week ISO year contains 53 complete Monday-to-Sunday weeks instead of the usual 52. This occurs when 1 January falls on a Thursday, or on a Wednesday in a leap year. Furthermore, 2026 is a 53-week year. Sprint plans that cover the full year in a 53-week year will generate one extra sprint compared to a 52-week year if the sprint length is exactly one week — the Sprint Planner handles this correctly automatically.
Excel has two week number functions. Use =ISOWEEKNUM(date) to get the ISO 8601 week number — this matches the result from this tool for the ISO standard. For US week numbers, use =WEEKNUM(date,1) for Sunday-start or =WEEKNUM(date,2) for Monday-start. Furthermore, avoid =WEEKNUM(date) without a second argument — it defaults to a non-ISO Monday-start that does not match either standard consistently across year boundaries.

Related Date & Time tools

Every tool on LazyTools runs in your browser. Nothing is uploaded or stored.

Business Days Calculator

Count working days in any period with UAE and US holiday support. Furthermore, add N business days to any start date.

Date Difference Calculator

Exact gap between two dates in every unit. Additionally, milestone markers show every 100th and 1000th day.

Workweek Calculator

Find all dates in any given ISO workweek. Furthermore, compare ISO, US and Gulf working week formats side by side.

Days Left in Year

Full-year day grid showing days elapsed and remaining. Additionally, a quarter breakdown shows Q1–Q4 days separately.

Recurring Date Generator

Generate date sequences for any recurrence pattern. Furthermore, add multiple patterns simultaneously and export as CSV.

Calendar Generator

Generate a printable monthly or yearly calendar. Additionally, add named events directly into the calendar grid.

Rate this tool

4.0
out of 5
195 ratings
5 ★
57%
4 ★
17%
3 ★
9%
2 ★
3%
1 ★
14%
How useful was this tool?