You finished the sportive. You sat in the car park eating a flapjack, legs buzzing, half-delirious. You posted a photo of your Garmin screen to Instagram with "what a day" and maybe a mountain emoji. Your mates commented. You moved on.
Three months later, you are lining up for the next one. You have a vague memory that you went too hard on the first climb. Or was it the second? You think you ate something at the 60 km feed station but you cannot remember if your stomach was already turning by then or if that started later. You know you faded in the last hour but you cannot remember exactly when the wheels came off.
This is the problem. Your memory of a race rewrites itself within days. The emotional high of finishing — or the frustration of blowing up — overrides the specific, useful details. The bits that would actually help you next time are gone, replaced by a general narrative that is mostly feelings and not much data.
Here's the thing nobody tells you: the difference between riders who get faster from event to event and riders who repeat the same mistakes is not always fitness. It is often information. The fast improvers write things down. Not war stories for social media — actual debriefs that feed directly into their next training block.
The 48-Hour Window
Write your report within 48 hours of finishing. Not a week later. Not "when I get around to it." Forty-eight hours.
Your recall of specific moments — the exact point where your legs started to feel heavy, what your heart rate was doing on the third climb, whether that second gel sat well or sat badly — degrades fast. After three days, you are already editing the memory. After a week, you are telling a story, not recording what happened.
Download your head unit data the same evening. Plug in the Garmin, sync the Wahoo, whatever your process is — do it while your kit is still damp. The subjective notes need to be written while the ride is still in your body, not just your head. You can tidy the analysis later, but the raw observations have a shelf life.
The Five-Section Structure
The most useful race reports I have seen — and I have read hundreds from riders in the Roadman community — all follow roughly the same structure. Five sections. Nothing complicated. You could write this on the back of an envelope if you had to, though a notes app is probably easier.
- Pre-race decisions
- Execution data
- What went right
- What went wrong
- The one change
That is it. No epic narrative required. No literary ambition. Just five headings and honest answers under each one.
Section 1: Pre-Race Decisions
This is the section most people skip, and it is the most revealing one. Before the gun went off (or before you rolled through the timing mat), you made a set of decisions. Write them down.
What was your goal? A finishing time? A power target? Survival? "Just enjoy it" is a valid goal, but be honest — were you actually racing the clock?
What was your pacing plan? If you had power targets for different sections of the course, write them here. If your plan was "go by feel," write that too. The point is to record what you intended so you can compare it to what actually happened.
What was your nutrition plan? What did you eat for breakfast, and when? What did you carry on the bike? What was your plan for the feed stations? How many grams of carbohydrate per hour were you targeting?
What kit choices did you make? Tyre pressure, gearing, clothing layers, bottles versus a hydration pack. These details seem trivial until you realise three months later that you cannot remember why you were cold on the descent or why your hands were numb by the finish.
Recording your pre-race decisions is not about proving you were clever. It is about creating a baseline. When you compare your plan to your execution, the gaps tell you everything.
Section 2: The Data
This is the backbone. Open your power file (or heart rate file, or whatever you have) and compare it to your plan.
If you said you would hold 200 watts on the flat sections, what did you actually hold? If you planned to climb at 250 watts, what does the file show? The numbers do not lie, and the gaps between planned and actual power are where the interesting information lives.
Here is what to look for specifically:
First 30 minutes. Did you go out too hard? This is the single most common mistake in sportives and the data will show it clearly. If your normalised power for the first 30 minutes is 15 per cent above your normalised power for the whole event, you went out too hot. Full stop.
Climbing versus flat. How did your power distribute? Some riders are consistent across terrain. Others spike on climbs and recover too much on flats. The ratio tells you something about your pacing discipline.
The final quarter. How did your power hold up in the last 25 per cent of the event? If there is a significant drop-off — more than 10 to 15 per cent below your average — you either paced poorly, fuelled poorly, or your endurance base was not deep enough for the distance.
Heart rate decoupling. If your power stayed steady but your heart rate drifted upward through the event, that is cardiac drift. It usually points to dehydration, heat stress, or insufficient aerobic base. Dr Stephen Seiler talks about this as one of the clearest signals of where your fitness ceiling sits versus where the event demanded you perform.
If you do not have a power meter, heart rate and RPE still give you useful data. Where did your heart rate spike? Where did perceived effort feel disproportionate to the terrain? Those patterns are worth recording even without watts.
Section 3: What Went Right
Be specific. "Felt good" is not useful. "Pacing on the first two climbs was within 5 watts of plan, legs felt controlled, breathing was manageable" — that is useful.
What moments went well, and why? Was it because of something you did deliberately? A pacing decision, a positioning choice in the bunch, a nutrition strategy that worked?
Examples of specific positives worth recording:
- "Ate a gel at 45 minutes and another at 90 minutes, stomach was fine both times"
- "Sat in the group on the A-road section and kept power under 180 watts, which saved legs for the climb"
- "New chamois cream worked — no saddle issues for the full distance"
- "Drank a bottle per hour, never felt thirsty, no cramps"
These details sound boring on paper. They are gold when you are planning the next event, because they tell you what to keep doing.
Section 4: What Went Wrong
This is where honesty matters. The version of the race you tell your mates in the pub afterwards is not the version you need here. You need the uncomfortable truth.
Be specific and be data-backed where possible. Not "I blew up on the last climb." Instead: "Power dropped from 240 watts to 180 watts on the final climb at 95 km. Heart rate was already at 172 on the approach, suggesting I was in the red before the gradient started. I had not eaten anything since the 75 km feed station — a 40-minute gap in fuelling."
That version tells you three things: the power drop was real and measurable, the heart rate suggested accumulated fatigue, and the fuelling gap probably contributed. You can work with all three of those. "I blew up" tells you nothing you can fix.
Common patterns that show up in the "what went wrong" section across hundreds of reports:
- Went out 15 to 20 watts above plan in the first 30 minutes
- Missed a feed window — too caught up in the group to eat
- Stomach issues from a new product not tested in training
- Kit problem that was minor at 20 km but significant at 120 km (hot spots, chafing, numbness)
- Positioning error in a bunch that cost energy chasing back on
Section 5: The One-Change Rule
This is the most important section in the entire report. Read everything you have written above and ask yourself one question: if I could change only one thing for the next event, what would it be?
Not five things. One.
The temptation is to write a shopping list — train more, eat better, pace smarter, buy a lighter bike, lose 3 kg. That list is paralysing. None of it gets done because all of it feels urgent.
Pick the single biggest limiter. The one factor that cost you the most time, the most comfort, or the most enjoyment. Make that the focus of your next 8 to 12 weeks of training.
If you blew up because you went out too hard, the one change is pacing discipline. Practise it in training rides. Set a power ceiling for the first 30 minutes and do not break it, no matter how good you feel.
If your nutrition failed, the one change is gut training. Practise your race-day fuelling plan on training rides until your stomach handles the volume without complaint.
If you faded because your endurance was not deep enough, the one change is more time at lower intensity. Build the aerobic base that supports the distance you are racing.
One thing. Fix it. Race again. Reassess. This is how you get faster year on year.
Nutrition Logging: The Section Most Riders Skip
Nutrition is the invisible variable. Your power file shows what your legs did. It does not show what your gut was doing. And gut problems are behind more blown-up sportives than fitness deficits.
Record this in your report:
- Pre-race meal: What, when, and how much. "Porridge with banana and honey at 6:30 am, two hours before start" — that level of detail.
- On-bike fuelling: Every gel, every bar, every drink mix. What you consumed and at what time or kilometre mark. "Gel at 45 km, gel at 85 km, half a banana at the 100 km feed station."
- Stomach status at each feed point: Fine, slightly off, bloated, nauseous. If you felt nothing, record that. It is just as useful.
- Hydration: How many bottles did you finish? Did you feel thirsty at any point? Any signs of dehydration — headache, confusion, cramps?
I have spoken to enough sports nutritionists on the podcast — people like Alan Murchison and Hannah Grant — to know that most amateur fuelling failures are not about the wrong product. They are about timing, volume, and practise. Your race report is where you find the pattern. Three reports showing stomach issues at the 90-minute mark tells you something. One vague memory of "feeling a bit off" tells you nothing.
The Mental Debrief
Your brain raced too. Record what it was doing.
Where did you feel strong mentally? Where did you want to quit? Was there a specific moment where you made a decision — to push through, to sit up, to follow a wheel, to let a group go?
Mental patterns repeat. If you always fade psychologically at roughly 70 per cent of the total distance, that is a pattern worth knowing about. It might be a fuelling issue (low blood sugar affects mood and motivation before it affects power). It might be a pacing issue (you have already buried yourself and your brain is pulling the handbrake). Or it might be a real mental challenge that you can train with targeted long rides and deliberate suffering.
The point is: you cannot train what you have not identified. And you cannot identify a pattern from one data point. Write it down every time.
Private Reports Versus Shared Reports
Your race report is a training document. It is not a social media post. Write the version for yourself first — honest, specific, with all the uncomfortable bits included. The version where you admit you panicked in the bunch, or that you ate crisps at the feed station because you had not packed enough gels, or that you sat up with 10 km to go because you were mentally done.
That version is valuable precisely because it is uncomfortable. Nobody else needs to see it.
If you want to share a version — with a coach, a training partner, or a community — brilliant. That is immensely useful because other riders spot patterns you miss. They have made the same mistakes. They will see the pacing error or the fuelling gap instantly because they have lived it themselves. But edit the shared version for comfort if you need to. The private one is the one that matters.
Using the Report to Set Your Next Training Block
Read your report a week later, when the post-race emotions have settled. Look at Section 5 — your one change. Ask yourself: what does my training need to look like for the next 8 to 12 weeks to fix this specific thing?
If pacing was the problem, build pacing discipline into your long rides. Set a power cap for the first hour and hold it regardless of how your legs feel. Practise negative splitting — starting conservative and building.
If fuelling was the limiter, spend the next training block practising your race-day nutrition plan on every long ride. Train your gut to handle the carbohydrate volume you need. Test every product you plan to use in the event.
If fitness was the issue — you simply did not have the engine for the distance or intensity — then the training block is straightforward. More volume at lower intensity to build the aerobic base, or more threshold work to raise the ceiling, depending on where the gap was.
The race report is the bridge between events. Without it, each event is isolated — a thing that happened. With it, each event feeds the next. You carry forward what worked, you fix what did not, and you arrive at the start line with a plan that is built on evidence, not hope.
Start Writing
You do not need a special template. A notes app, a Google Doc, a page in a training diary — anything works. The format matters far less than the habit. Five sections, honest answers, written within 48 hours.
The riders who improve year on year are not always the ones with the most talent or the most time to train. They are the ones who pay attention. Who record what happened, figure out why, and fix the one thing that matters most before the next event.
That is the whole system. Write it down. Be honest. Change one thing. Race again.
If you want a group of riders who actually share their reports and help each other spot the patterns — pacing mistakes, fuelling gaps, training errors that are obvious to everyone except the person making them — the Roadman Cycling community on Skool is where those conversations happen. Drop in. Post your report. Someone there has already made the exact mistake you are trying to fix.