You audit a training year like a coach by reviewing the data you kept (races, field tests, training logs and adherence) against the goals you set, then asking what drove your gains, what wasted time, and what to change next season. A structured season review is how athletes stop repeating the same mistakes and compound their improvement year on year.
Why bother reviewing a whole season?
Because without a review you carry the same blind spots into next year and pay for them again. When we built THETA BLUEPRINT, the philosophy was borrowed directly from good product work: you cannot improve a system you do not measure and interrogate. A season is a large dataset, with dozens of sessions, a handful of races and months of field tests, and buried in it are the patterns that explain why you got faster in one block and stalled in another. Skip the review and those patterns stay invisible, so you keep making the same programming errors. Spend a few hours auditing it honestly and you turn a year of raw experience into a sharper plan for the next.
What data should you actually look at?
Pull together everything that shows what you did and what it produced. Your race results and station splits show outcomes. Your field-test history, covering 5K times, pace-at-heart-rate and station benchmarks, shows whether the engine actually grew and when. Your training log shows what you planned versus what you completed, which is often the most revealing layer. And your notes on illness, injury, sleep and life stress explain the gaps. Laid side by side, these let you connect cause and effect: which blocks moved your markers, which coincided with plateaus, and whether the stalls were programming failures or simply weeks you did not complete.
| Data source | What it reveals | Question it answers |
|---|---|---|
| Race splits | Where time was won and lost | Which stations or runs to target |
| Field-test history | When fitness actually moved | Which blocks worked |
| Training log adherence | Planned vs completed | Was it the plan or the execution? |
| Illness/injury notes | Disruptions and their causes | What to prevent next season |
How do you run the review step by step?
Work through it in order so you draw conclusions from evidence, not memory.
- Restate the goals you set at the start of the season.
- Lay out race results and field tests on a timeline.
- Mark which blocks moved your markers and which did not.
- Overlay adherence: did the flat blocks coincide with missed sessions?
- Identify your two biggest limiters and one recurring pattern to fix.
"A season review is a retrospective, the same discipline I ran on every product I built: what did we ship, what actually moved the numbers, what do we stop doing. Applied to training it's blunt and useful: the log usually tells you whether it was the plan that failed or the fact you only did half of it," says Michael Snook, CTO, THETA.
How do you separate a bad plan from bad execution?
Overlay your adherence data on your results, because the two failures look identical until you do. A block that produced no improvement might have been poorly designed, or you might have completed only half of it. These need opposite fixes: change the programming in one case, remove the barriers to consistency in the other. In practice, incomplete execution is the more common culprit for amateurs, which is why the training log is the most valuable document in the review. If your flat periods line up with missed sessions, illness or chaotic weeks, the plan was probably fine and the real project is building consistency into next season.
A worked case makes the distinction concrete. Suppose two of your four blocks last year moved your pace-at-heart-rate and two did not. Lay the log underneath. If the flat blocks show eight of twelve key sessions completed, riddled with a work trip and a bug, the plan was sound and the fix is scheduling and recovery, not a new programme. But if the flat blocks show near-perfect adherence and still no movement, the stimulus itself had stopped working and the fix is to change it. Athletes routinely misdiagnose this, tearing up a good plan after a poorly executed block, then repeating the same consistency failure against a shinier template. The log settles the argument before you waste a season on the wrong repair.
What should the review actually change?
It should produce a short, specific list of decisions for next season, not a vague sense of doing better. That might mean prioritising a limiter the data exposed, say compromised running or a weak sled push, restructuring blocks that consistently failed to move your markers, or protecting recovery in the months where life predictably disrupts training. The value of a review is only realised if it changes the plan, so force yourself to name concrete changes: fewer but better-recovered hard days, an earlier deload, a specific station emphasis, a maintenance block booked into a known-busy period. A review that ends in resolutions rather than decisions has not done its job. If a once-a-year audit feels too coarse, this is essentially the loop THETA BLUEPRINT runs continuously: it reads where your fitness sits from a 2-minute assessment, selects your stations weakness-first, and adapts each block off what the last one produced, so the "what worked, what to change" question gets answered block by block rather than being saved up for the end of the season.
When should you do a season review?
At the natural end of a competitive cycle, after your last key race and before you plan the next season's first block. This timing matters: review while the season is fresh enough to remember but complete enough to judge, and use the conclusions to shape the base block that follows. Many athletes also run a lighter mid-season check-in after a major race, which catches problems early rather than waiting a whole year. Either way, anchor the review to a transition point in your calendar so its output flows directly into your next block of planning, rather than becoming an interesting document you never act on.
Common questions
What is a training season review?
A season review is a structured audit of a year's training (races, field tests, logs and adherence) against the goals you set. It identifies what drove your gains, what wasted time, and what to change next season.
What data do I need for a season review?
Race splits, field-test history, your training log and notes on illness, injury and life stress. Together they let you connect what you did to what it produced.
How do I tell if my plan or my execution failed?
Overlay your adherence data on your results. Flat blocks that coincide with missed sessions point to execution, while flat blocks you fully completed point to the plan. For amateurs, incomplete execution is the more common culprit.
When should I review my training year?
At the end of a competitive cycle, after your last key race and before planning the next season's first block. A lighter mid-season check-in after a major race also helps catch problems early.
How long should a season review take?
A few focused hours is usually enough to lay out the data, spot the patterns and name your changes. The value is in the honesty and specificity, not the length.
Sources
- HYROX official race format and public results (hyrox.com)
- THETA's analysis of publicly logged elite training (Strava, race splits, published programs), 2023-2026
- THETA coaching data, 2024-2026
- Established principles of periodisation, performance analysis and retrospective review