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.
| Detail | Value |
|---|
| Sprint | Start date | End date | ISO Week(s) | Duration |
|---|
| ISO Week | Mon start | Sun end | Month |
|---|
How to use the Calendar Week Number
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.
| Feature | ISO 8601 (global) | US Standard (North America) |
|---|---|---|
| Week starts on | Monday | Sunday |
| Week 1 definition | First week with a Thursday | Week containing 1 January |
| Year can have | 52 or 53 weeks | 52 or 53 weeks |
| Used in | Europe, Asia, ERP, manufacturing, ISO standards | US, 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.
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.
| Sprint | Start date | End date | ISO weeks |
|---|---|---|---|
| Sprint 1 | 5 Jan 2026 | 18 Jan 2026 | W02–W03 (2026) |
| Sprint 2 | 19 Jan 2026 | 1 Feb 2026 | W04–W05 (2026) |
| Sprint 3 | 2 Feb 2026 | 15 Feb 2026 | W06–W07 (2026) |
| Sprint 4 | 16 Feb 2026 | 1 Mar 2026 | W08–W09 (2026) |
| Sprint 5 | 2 Mar 2026 | 15 Mar 2026 | W10–W11 (2026) |
| Sprint 6 | 16 Mar 2026 | 29 Mar 2026 | W12–W13 (2026) |
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
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.
→