Sawe's build was organised around a longer rhythm
Sabastian Sawe's London Marathon preparation is useful because the public detail is structural. The marathons.com feature with Claudio Berardelli documents the kind of information runners and coaches can actually learn from: a 10-day training cycle, high overall volume, frequent doubles, and hill sprints.
That gives us enough to discuss the architecture of the block without pretending we have a full private training diary.
The interesting part is the way those pieces interact. A 10-day cycle changes how often the hard work appears. Doubles change how volume is distributed across the body. Hill sprints add speed and force without turning every neuromuscular stimulus into a full interval session. High volume only works if the whole structure keeps the athlete absorbing the work.
Key takeaways
Sawe's documented build used a 10-day cycle, which spreads key stressors across a longer rhythm than the standard Monday-to-Sunday template.
The source basis documents high volume and doubles, but the publicly available detail is incomplete at daily-session level.
Hill sprints fit well in marathon training when they are treated as a small neuromuscular dose, with enough recovery to keep the main aerobic work intact.
The build appears consistent with a controlled density model: substantial workload, repeated exposure, and enough spacing to prevent every quality stimulus from competing with the next one.
For non-elite runners, the transferable idea is load organisation. Copying the surface detail without matching capacity, recovery, altitude context, and training history carries obvious risk.
What is actually documented
The editorial source basis for this piece is a marathons.com feature involving Sawe's coach, Claudio Berardelli. The documented details available for this draft are:
Sawe's London Marathon preparation used a 10-day cycle.
The build included high training volume.
Doubles were part of the routine.
Hill sprints were included.
Those details are enough to analyse the training logic, with a clear boundary: the public source basis does not give a complete day-by-day diary in the material supplied for this article. There is no safe basis here for inventing exact session prescriptions, weekly kilometre totals, recovery days, or pace progressions.
That boundary matters. Athlete-block writing gets sloppy when race results are used to reverse-engineer training. Sawe's London performance confirms that the preparation produced an elite marathon outcome. It does not reveal the session sequence by itself. The training structure has to come from documented coaching detail.
Why a 10-day cycle changes the block
Most runners organise training in seven-day weeks because life is organised that way. Work schedules, club nights, long runs, school runs, and Sunday logistics all pull training toward the calendar week.
Elite marathon training often has a different problem. The limiting factor is the athlete's ability to absorb repeated high-load stimuli. A seven-day microcycle can be too compressed if the programme includes a long run, a marathon-specific workout, a faster aerobic session, strength or hills, and very high background volume. A 10-day cycle gives the coach more spacing.
That spacing can change the meaning of the same workouts.
A hard long run placed four days after a demanding interval session lands differently from the same long run placed two days later. Hill sprints performed with fresh mechanics create a different stimulus from hill sprints tacked onto a fatigued block. A medium-long aerobic run can support adaptation when it sits between bigger anchors; it can become another stress pile-up when the week already has too much density.
A 10-day rhythm gives more room for sequencing. It can allow the athlete to touch multiple qualities without forcing every meaningful workout into a fixed seven-day box.
For a marathoner like Sawe, that matters because the marathon build has competing demands:
enough volume to support durability and aerobic capacity;
enough marathon-specific running to improve fuel use and pace control;
enough speed or power work to keep mechanics sharp;
enough recovery between anchors to protect the next key session;
enough routine to make the whole thing repeatable.
The 10-day cycle is one way to manage those tradeoffs.
High volume needs distribution, restraint, and context
The marathons.com/Berardelli source basis documents high volume in Sawe's build. That is unsurprising for an athlete operating at the sharp end of the marathon, but the useful detail is the combination with doubles and a longer cycle.
Volume is a blunt number on its own. Two athletes can both run high mileage and receive very different stress. Pace, terrain, altitude, session density, previous training history, and recovery resources all change the cost of the same distance.
For example, 24 kilometres on rolling dirt at altitude with fatigue in the legs can sit closer to a meaningful aerobic stressor than the same distance on flat roads at sea level for a fresh athlete. A short second run can be restorative for a conditioned elite and an injury accelerant for a runner who has only recently moved beyond single runs.
That is the first practical reading of Sawe's build. The volume belongs inside a system.
Doubles are one way to distribute volume. Splitting daily distance can reduce the duration of any single loading bout, make it easier to keep easy running genuinely easy, and allow the athlete to accumulate aerobic work around key sessions. The second run also adds frequency, which can improve routine and mechanical exposure.
There is a cost. Doubles reduce the length of the recovery window between runs. They add more preparation, more fuelling demands, more soft-tissue exposure, and more chances to turn easy mileage into background fatigue. For an athlete with elite durability, coaching support, and years of adaptation, doubles can support a high-volume block. For a recreational runner with work stress and limited sleep, the same structure may simply increase total strain.
The transferable idea is measured distribution. If the training goal is more aerobic load, a second easy run may sometimes be cleaner than stretching a single run beyond what the athlete currently absorbs well. That only works when the extra run stays easy enough and the total week still trends in a recoverable direction.
Hill sprints in a marathon build
Hill sprints are one of the more interesting documented details in Sawe's build because they can look out of place to runners who view marathon training as purely aerobic.
Used well, short hill sprints are a neuromuscular and mechanical stimulus. They can target recruitment, stiffness, coordination, and force application with relatively low total volume. The gradient naturally limits absolute speed, which can make the stimulus safer than flat-out sprinting for some athletes, although hill sprinting still carries high force demands.
The key is dosage.
A small number of short hill sprints with generous recovery can keep the session alactic or near-alactic. The athlete finishes with better recruitment and rhythm, while the main metabolic load of the block remains elsewhere. Extend the reps, compress the recovery, or chase exhaustion, and the session becomes a different workout.
That distinction matters in marathon training. The marathoner already has plenty of fatigue available from long runs, medium-long runs, threshold-style work, and total volume. Hill sprints can add speed and force without requiring a large metabolic bill when programmed carefully.
For Sawe, the documented inclusion of hill sprints suggests that the build preserved some higher-force running alongside marathon-specific endurance. That fits a broader elite pattern: marathoners still need mechanics, reactivity, and the ability to run efficiently at speeds faster than marathon pace. The marathon rewards economy as much as stubbornness.
The likely logic: density without chaos
The documented pieces point toward a block built around controlled density.
A 10-day cycle gives spacing. High volume supplies the aerobic substrate. Doubles distribute the load. Hill sprints preserve mechanical sharpness and force exposure. Together, those details suggest a system where stress is repeated often enough to drive adaptation, with enough structure to stop the work becoming a pile of hard days.
That is interpretation, so it deserves careful language. We cannot say from the supplied source basis exactly how Berardelli sequenced Sawe's long runs, marathon-pace work, threshold sessions, recovery days, gym work, or taper. We can say that the documented architecture is coherent for an elite marathon build.
The coherence comes from the interaction of the parts:
A longer microcycle can reduce unnecessary compression.
Doubles can support high volume while keeping individual runs manageable.
Hill sprints can maintain speed and mechanics with a small time cost.
High volume can be absorbed more reliably when the athlete has enough history and the coach manages density.
For coaches, this is the most useful part of the block. The headline training features only make sense as a system. A 10-day cycle with poor spacing is still poor spacing. Doubles with sloppy intensity control are still a fatigue problem. Hill sprints performed too hard, too long, or too often can interfere with the next meaningful endurance stimulus.
What recreational marathoners can take from it
Sawe's training environment and capacity are far from normal. That does not make the block irrelevant. It means the transferable pieces need translation.
1. Consider stress spacing before copying weekly shape
Many marathon plans stack the same anchors every week: Tuesday workout, Thursday workout, Sunday long run. That can work well. It can also become too dense when the runner is adding volume, carrying life stress, or returning from a hard race.
A 10-day logic can be used inside a normal life. The exact calendar may still be weekly, but the runner can avoid forcing three big stimuli into seven days when adaptation is lagging. Some weeks may carry two meaningful anchors. Other weeks may carry one bigger marathon-specific session plus aerobic support.
The question is simple: does the next key session arrive when the runner can execute it well enough to benefit from it?
2. Use doubles only when they solve a real problem
A second run can be useful when a runner already handles consistent mileage and wants to increase aerobic load without extending every run. It can also help maintain frequency during a busy week.
The second run should have a job. Usually that job is easy aerobic volume. If it becomes another moderate run, the total load may rise faster than the body can absorb.
For many serious recreational runners, the first useful double is modest: 20 to 35 minutes easy, placed far enough from the main run to create some separation, and added only after the single-run week is stable.
3. Keep hill sprints small and clean
Hill sprints work best as a precise dose. Short reps, full recovery, strong mechanics, and a low rep count are enough for many runners. They can sit after an easy run or within a session where the coach wants neuromuscular activation without creating a heavy workout.
The warning sign is sloppy mechanics. If posture collapses, ground contact gets heavy, or the runner starts grinding uphill, the intended stimulus has changed.
4. Track load beyond distance
Sawe's documented build includes high volume, but distance alone is a limited proxy for stress. Pace, elevation, surface, heat, altitude, and cross-training all change the load.
This matters for non-elites because two 100-kilometre weeks can have totally different costs. A week with flat easy running and one controlled workout differs from a week with hills, heat, a hard long run, poor sleep, and an aggressive midweek session. The body responds to the load it experiences, rather than the mileage total written in a spreadsheet.
What the public record leaves open
The public details on Sawe's London build are valuable, but incomplete. The supplied source basis documents the architecture: 10-day cycle, high volume, doubles, hill sprints. It does not provide enough detail here to reconstruct the full block.
Several important questions remain open:
How were marathon-pace sessions distributed across the 10-day cycle?
How often did true long runs appear?
What were the easy-day intensities relative to Sawe's threshold and marathon pace?
How much of the hill work was sprinting, drills, or longer uphill running?
How did the taper change volume and intensity?
How much altitude, terrain, group training, strength work, massage, and recovery support shaped the apparent training load?
Those gaps do not weaken the usefulness of the documented structure. They limit how aggressively anyone should generalise from it.
Elite blocks are most useful when they sharpen our questions. Sawe's build points toward load organisation, session spacing, and neuromuscular maintenance inside marathon preparation. It gives coaches and runners a framework to examine their own training without pretending that a private elite system can be copied from a few public details.
Sources, confidence, and uncertainty
This draft relies on the plan-provided source basis: a marathons.com feature involving Claudio Berardelli, documenting Sawe's 10-day cycle, training volume, doubles, and hill sprints. Sawe's London result should be checked against official London Marathon or World Athletics records before publication.
Confidence is high for the four documented structural elements listed above, because they come from the assigned source basis. Confidence is moderate for the interpretation that the structure reflects controlled density, because that is a coaching analysis built from the documented features. Confidence is low for any exact session reconstruction, so this article avoids exact workouts, weekly kilometre totals, dates, and paces.
Training information from elite athletes is often partial. Coaches may describe the architecture and leave out the details that make the block work: easy pace discipline, terrain, altitude, massage, sleep, illness interruptions, session modifications, and the athlete's long-term training history. Those missing variables matter.
Sawe's build is best read as evidence that a high-performing marathon block can use a longer cycle, high volume, doubles, and hill sprints in a coherent structure. The exact implementation remains private unless the coach publishes more detail.
kaizen is built around the same practical problem at a different scale: turning real training into a load target the runner can actually absorb. The app estimates current fitness, accounts for pace and elevation in training load, translates the underlying target into a weekly distance range, and adapts when life changes the week. If Sawe's block is a reminder of anything, it is that progress comes from calibrated work repeated long enough to matter. kaizen gives that calibration a place to live in your own training.
