Most training plans are written in weeks: week 1 is the base phase, week 8 is peak load, week 12 is the race. The problem is that "week 1" doesn't mean anything on a calendar — it's relative. If you start a 16-week marathon plan on March 10, you need to track which calendar week corresponds to which training week, or you end up confused about whether this week is supposed to be hard or easy.

Using ISO week numbers solves this. Each week of the year has a fixed number (1 through 52 or 53), so you can map your training weeks directly onto the calendar from the start. Week 15 of your plan corresponds to ISO week 15 of the year — and you can always check the current week number to see exactly where you are.

How to Build a Training Plan Around Week Numbers

The process is straightforward:

Step 1: Find your event date's week number. If your race or event is on a specific date, find its ISO week number. A marathon on April 26 falls in ISO week 17 of 2026. That's your target week.

Step 2: Count backward from event week. If your plan is 16 weeks, subtract 16 from the event week: 17 − 16 = week 1 starts in ISO week 2 (early January). Adjust if you need a taper — if the final week before the race is a taper week, count that as part of the 16 weeks.

Step 3: Map each training phase to a week range. Label the week numbers for each phase in your plan:

• Base phase: weeks 2–6
• Build phase: weeks 7–11
• Peak phase: weeks 12–15
• Taper and race: weeks 16–17

Now every weekly training decision can be anchored to a week number you can check at a glance.

Deload Weeks and Recovery Scheduling

Most structured training plans include deload weeks — periods of reduced volume designed to let the body absorb training stress and recover before the next loading block. Common deload patterns:

• Every 4th week: weeks 1–3 hard, week 4 easy, weeks 5–7 hard, week 8 easy, etc.
• Every 3rd week: more aggressive recovery schedule, useful for athletes who accumulate fatigue quickly
• Planned mid-cycle: a single deload in the middle of a longer training block

When you map these onto ISO week numbers from the start, you always know which type of week this is. If deload weeks are 5, 9, 13, and 17 in your plan, and you're currently in ISO week 9 of your training calendar, you know immediately that this is a recovery week — even if you haven't looked at the plan document recently.

This is especially useful for multi-sport athletes managing multiple training loads simultaneously. A runner who also cycles and lifts weights can align deload weeks across all three activities to the same calendar week, rather than having each sport on a different recovery cycle.

Race Season Planning With Week Numbers

Week numbers are useful for mapping a full season of events, not just a single race.

Say you have three target events:

• Spring 10K: ISO week 18
• Summer half marathon: ISO week 28
• Fall marathon: ISO week 42

With these fixed points, you can work backward from each event to define training blocks and recovery periods:

• Post-10K recovery: weeks 19–20
• Half marathon build: weeks 21–27 (plus taper)
• Post-half recovery: weeks 29–31
• Marathon build: weeks 32–41 (plus taper)
• Off-season: weeks 43–52

Laying this out at the start of the year gives you a full season view and helps you spot problems early — like a training block that's too compressed, or a recovery period that's being squeezed by the next event starting too soon.

Tracking Weekly Training Load Over Time

Training load tracking — monitoring how much work you're doing week over week to manage fatigue and fitness — is much cleaner when keyed to week numbers.

Instead of tracking by date (which creates variable-length periods if weeks don't start on Monday), training load calculations use a consistent 7-day window from Monday to Sunday. ISO weeks are exactly this: Monday to Sunday, every week, with a sequential number.

Key training load metrics athletes track by week:

Weekly volume: Total miles/kilometers, hours, or sessions. Tracking by ISO week makes it easy to compare week 8 to week 12 without worrying about calendar alignment.

Acute:Chronic Workload Ratio (ACWR): A formula that compares recent training load (the past 1–2 weeks) to longer-term average load (the past 4–6 weeks). Used to manage injury risk. Calculating ACWR requires consistent weekly data, which week numbering provides.

Week-over-week increase: The general rule is not to increase weekly training volume by more than 10% week-over-week. Tracking by ISO week makes this calculation immediate: week 9 volume ÷ week 8 volume − 1.

Syncing Training Plans With Team or Coach Schedules

If you train with a coach or as part of a club, week numbers create a common reference language. Instead of saying "in the third week of March," you say "in week 12" — and everyone is working from the same reference point regardless of when they started their individual training plan.

Group training plans distributed to multiple athletes at the start of a season typically use ISO week numbers for exactly this reason. The coach publishes "week 8 workouts" and everyone knows which calendar week that is.

Check the current week number to orient yourself whenever you're reviewing a training plan that uses week numbers.

A Practical Example: 12-Week Running Plan

Here's what a 12-week base-to-race plan looks like mapped to ISO weeks, assuming a race in ISO week 20:

Mapping your plan to ISO weeks this way means you always know exactly how many weeks until the race, how many weeks into the current phase you are, and whether this is supposed to be a high or low load week — without consulting the plan document every time.