Your running app highlights the biggest week, and it is easy to treat this as the main evidence of your marathon preparation. Yet the maximum remembers only one week. What do the mean, median, surrounding weeks and a check for missing uploads reveal alongside it? Using our own eight-week example, we build a summary that also shows the whole process.
The maximum remembers only one week
The peak week is the greatest weekly volume within the selected period. That is a clear definition, but surprisingly little information. It does not tell you how many similar weeks there were, how you reached it or what followed. A seventy-kilometre maximum may form part of a longer, consistent series, or stand out from a period of otherwise much lower volume. The record is the same; the background differs.
Even selecting the period can change the answer. The maximum in the last eight weeks is not necessarily the same as the biggest week of the entire six months. Are you including the race, or only the training completed beforehand? Without a fixed framework, it is easy to keep choosing whichever view looks more favourable. The first thing alongside the peak value should therefore be the date range examined.
The record celebrated by the app can be a useful memory, but it is not a certificate of readiness. For a marathon, the longer process matters, with the highlighted week as only one data point. The aim is not to devalue a week you are proud of. Rather, preserve alongside it the weeks that were less striking but still made up much of the preparation actually completed.
Two fictional eight-week series with the same mean
Series A in our example, in kilometres, is 40, 42, 38, 44, 40, 70, 20, 26. Series B is 38, 40, 42, 40, 40, 40, 42, 38. Each totals 320 kilometres, giving an average of forty over eight weeks. The middle value, or median, is also forty in both cases. The maximum, however, is seventy for A and forty-two for B. Ranking them by the record alone would therefore give a very different impression.
The numbers alone do not tell us why A’s final weeks became smaller. There may have been a planned reduction, lack of time, travel or another reason; we attach no story to them in this example. That is precisely the lesson: a dataset does not automatically contain its explanation. Seventy does not establish better readiness, and twenty cannot be used to diagnose injury or a poor decision without knowing more.
Together, the mean, median and maximum raise more questions. Which week resembles what you completed regularly? Which stood apart, and for what purpose? How did the rhythm change? Series B looks more even, but that still does not mean every workout had the same intensity or duration, or was appropriate for that runner. The kilometre series is the beginning of the analysis, not the whole training diary.
| Metric | Series A | Series B |
|---|---|---|
| Eight-week total | 320 km | 320 km |
| Weekly mean | 40 km | 40 km |
| Weekly median | 40 km | 40 km |
| Maximum | 70 km | 42 km |
Enlarge imageOpen the two pages before and after the peak too
Examine the weeks around the highlighted one separately. Previous weeks show which volume it followed, while subsequent weeks show how the programme continued. It is worth adding the number and duration of sessions too. The same weekly increase may come from more short runs, a longer weekend session or partly different recording. These are separate events in the calendar.
Preserve the week’s purpose alongside its volume. Was it a deliberately emphasised period, did annual leave allow more time, or did an event add the bigger number? This helps distinguish a planned peak from an incidental one in later assessment. You do not need to invent a neat explanation afterwards for every difference: saying the week looked that way because your work schedule changed is also an accurate entry.
Do not immediately judge the reduction afterwards either. A reduction recorded in advance is different from planned sessions unexpectedly being missed one after another. A table of weekly distance does not distinguish these on its own. A brief note preserves the difference and prevents you trying to reconstruct definite causes from the shape of the graph months later.
A missing upload is not a day without running
Clarify data quality first. If a workout did not synchronise, the empty box in the calendar does not prove you did not run. If the same session arrived from two devices, the total may be doubled. Check particularly where a manually recorded run meets a watch file that arrives later. Sometimes an upload problem creates a record, rather than an extraordinary training week.
For a session started and then shortened, record what was actually completed. Ten kilometres in the plan do not become ten kilometres covered if you finished at six. This is not merely strict bookkeeping: assessing preparation requires seeing what happened. You can keep the plan separately and add a brief reason beside the difference. Both the number and the story then stay accurate.
Use three simple data states: verified completion, known omission and data needing clarification. Do not automatically treat the last as zero. If the week in question would matter in a comparison, first look for the original file or your own note. If you cannot find it, keep the uncertainty visible. A maximum from an incomplete diary should not be called a millimetre-precise basis for planning.
Large databases examine a process too
The research analysing app data on marathon preparation examined the weeks before the races of several thousand finishers. The authors had to filter raw data and interpreted training patterns within a longer window. Greater volume in faster groups does not mean a simple ranking of single exceptional weeks. How the data was processed forms part of what the findings can tell us.
The study following Boston Marathon participants compared training characteristics and their changes across two longer pre-race periods with results. This allowed the relationship between habitual training history and more recent preparation to be examined together. The research did not ask who produced the single biggest week, and does not prove that a new record week improves finishing time on its own.
For your own diary, this suggests a useful question: what was typical for me, and what changed from that? The answer does not necessarily require complex statistics. A few checked weekly totals, the time associated with the volume and notes on significant events already help distinguish a sustained pattern from an outlier. Research broadens the perspective; it does not fill in the missing details of your personal calendar for you.
Do not merge volume, intensity and time
The week with the most kilometres was not necessarily the biggest in every other respect. Another week may have involved more running time, more climbing or more targeted fast sections. If using the peak week as a planning baseline, specify which variable’s maximum you mean. A single weekly distance record cannot stand for every different characteristic of the workload.
Make three separate lists side by side: weekly distance, weekly running time and a brief description of the tasks in the sessions. You do not need to turn each into another competition. They help you notice during assessment that the kilometre-maximum week may have contained more comfortable movement, while a lower-volume week placed key sessions closer together. Without sequence and content, the numbers can easily mislead.
Mark strength work or other activity separately rather than trying to convert it arbitrarily into running kilometres. Cycling kilometres and running kilometres are different quantities; adding them can create a misleading record. Both can have a place in the diary, provided the label is precise. You also preserve what happened alongside running without an artificial common unit obscuring the distinction.
Enlarge imageDo not choose a taper baseline afterwards to fit a favourable graph
Percentage reductions soon come up when discussing the pre-race taper. First, however, you need to name what you are comparing with. An exceptional record week and a usual preparation week provide different baselines. The ratio alone does not explain which you used. If the reference point appears only once the result is known, assessment can easily turn into retrospective storytelling.
The research analysing recreational marathon runners’ tapers distinguished patterns from changes in distance during the pre-race weeks. More consistently decreasing volume was associated with better results in certain comparisons. This is observational data and does not mean a ratio calculated from one personal record week overrides every other circumstance. The pattern of the process mattered in the analysis too.
In your own plan, record in advance which period you regard as the comparison baseline and why. You can preserve an exceptional week as a separate data point without automatically making it the denominator for every later calculation. Naming the baseline precisely helps coach and runner discuss the same reduction and compare the weeks actually completed using the same method.
How to make an honest preparation summary
Choose a meaningful time window in advance and check the data within it. Calculate total distance, weekly mean, median and maximum, then place them back into the weeks’ original sequence. Add the relevant week’s purpose and a brief note beside the maximum. This does not give you a ready-made training plan, but it produces a summary that can support a meaningful discussion.
Choose a specific question for further assessment. Did the usual weeks fit well, or was the plan on paper achievable only during annual leave? Was the continuation after the highlighted week planned in advance, or did several unexpected gaps follow? Different answers may call for different changes. Simply repeating the record does not answer every organisational or preparation problem.
The peak week then keeps its place: a memorable, precisely defined data point in a process. Marathon preparation, however, is characterised jointly by repeated weeks, the content of sessions and what was actually completed. There is no need to make a successful big week look artificially smaller, nor to pull the entire story up to its level afterwards. An accurate diary makes quieter work visible alongside the striking days.
Sources
- Zrenner and colleagues: marathon training patterns from app data.
- DeJong Lempke and colleagues: habitual training and changes before the Boston Marathon.
- Smyth and Lawlor: marathon taper patterns and race results.
How Futószív articles are prepared: our editorial guidelines.


