A steady rebuild for a former runner returning after a year or more away.

This example is for someone who used to run regularly — perhaps five kilometres a few times a week, or the occasional half marathon — and has been away from structured running for around a year or longer. The old fitness memory is strong; the current tissue and aerobic base are not what they were. Earned Pace Progression is used here to rebuild from what is actually there today, not from what used to be, while quietly recording the old PB for context.

A former runner in athletic vest lacing fresh trainers at the edge of a park path in golden late-afternoon light before an easy return jog.

The runner

Runner
Former regular runner, approximately one year away from structured training. No current 5K time — the old PB is more than a year out of date. Generally well and reasonably active in daily life.
Current ability
Can jog 10–15 minutes at very easy effort without stopping. Aerobic capacity clearly reduced from previous baseline.
Schedule
Three running days per week, with a rest day between each.
Goal
Rebuild to a comfortable continuous 30-minute run and a controlled easy 5K, without triggering the old-pace trap that ended their previous training block.

What makes this training situation hard

  • Anchoring to old threshold or race paces that no longer represent current fitness.
  • Expecting a fast return because 'I used to do this all the time'.
  • Aerobic fitness returning noticeably faster than tissue tolerance (tendons, calves, feet).
  • Overdoing early quality sessions that used to be routine.
  • Comparing every session to a previous version of themselves rather than to last week.

Why Earned Pace Progression fits

For a returning runner, EPP is essentially memory-wiping in the useful sense: it decides the next session from what was completed in the last one, not from what used to be completed a year ago. The old PB is recorded as history and shown for context — it is never used as a current target. Duration and easy running come first; quality is reintroduced gradually and only after a genuine base has been rebuilt from evidence.

Starting assessment

The first two weeks are a deliberate assessment at very easy effort — 3 × 30 min conversational jogs. Runallo records completed pace at a fixed HR ceiling and uses that as the current baseline, entirely independent of the previous PB. If the runner asks to skip the assessment, Runallo declines: the whole plan depends on a real current baseline rather than a remembered one.

A typical week

DaySessionNote
MondayRest or strength
TuesdayEasy run · 30 minRecovery pillar. Effort hold. No pace target.
WednesdayRest or mobility
ThursdayEasy run · 30–35 minSame as Tuesday, longer duration if week is clean.
FridayRest
SaturdayLong run · 40–60 min by timeEndurance pillar. Duration hold. Pace as insight only.
SundayOptional walk

Week-by-week progression

WeekFocusTargetOutcome / decision
1Assessment3 × 30 min easy runs at conversational effortAll three completed. Current easy-pace baseline recorded, old PB stored as history only.
2Repeat week 1Same as week 1Consistency week; no changes.
3Extend long runSaturday 30 → 40 minCompleted. Drift ≤6 bpm — endurance base holding.
4Extend mid-weekThursday 30 → 35 minCompleted cleanly. Only one variable moved this week.
5Disrupted weekTwo runs, no long runCalf tightness — Runallo drops Saturday, holds the following week's target.
6RebuildReturn to week 4 templateThree completed cleanly, no tightness.
7Extend long runSaturday 40 → 50 minCompleted with clean HR.
8Introduce short stridesAdd 4 × 20 s relaxed strides on TuesdayFirst quality touch. No work-average target.
9HoldRepeat week 8Consistency week before any real quality.
10Extend long runSaturday 50 → 60 minFirst hour on feet since returning — completed with clean HR.

Example sessions

Tuesday · Recovery · 30 min easy

Recovery

Conversational effort. HR ceiling from the current assessment, not from the previous training block. No pace target and no expectation that the pace should match what it used to be.

Saturday · Endurance · 50 min by time

Endurance

Duration hold. HR ceiling. Pace on the long run is treated as an insight — a slowly improving pace at the same HR across weeks is proof the aerobic base is returning. Pace is never the target on this session.

Optional Thursday strides

Quality

From week 8 onward, four 20-second relaxed strides slot into the middle of Thursday's easy run. Not sprints. Relaxed effort, full recovery between. Progression is only offered once HR has recovered fully between strides across two consecutive weeks.

Historical PB reference

Race

Runallo records the old PB for context in the runner's profile and displays it on the progress page, but never applies it as a current target. Future race attempts will pace from the current earned evidence, not the historical result.

How Runallo decides week to week

  • Runner types in their old threshold pace and asks for a session at that pace

    Runallo declines to schedule the session. The current earned pace is defined by completed evidence in the current block; a session at the old pace is not offered until it has been held cleanly at least once in a controlled test.

  • Two clean weeks at the same template

    One variable moves — usually long-run duration by 5–10 minutes. Mid-week runs stay unchanged.

  • Calf tightness after Saturday's long run

    Runallo drops the following long run to the previous owned duration and prompts a soft signal — no additional volume until the tightness clears across two runs.

  • Runner books a Parkrun in week 4

    Runallo advises against a hard effort in the current base block. If the runner opts in, the result is recorded but is not used as evidence for future pace targets unless the surrounding weeks were also consistent.

  • Aerobic pace at the same HR drops noticeably across three weeks

    Runallo surfaces this as a positive insight — evidence the aerobic base is returning — but does not immediately introduce a pace target. Owning a pace still requires two consecutive weeks at that pace in a completed session.

What Runallo will not do

  • Using the old PB as a current target.
  • Progressing pace on the long run.
  • Introducing quality intervals in the first four weeks.
  • Assuming rapid return of fitness because of prior training history.
  • Stacking a missed long run into the following week.

Why the old PB is history, not a target

For a returning runner, the historical PB is the loudest number in their head — and, for the first several weeks at least, the most misleading. A PB from a year ago is evidence of what the runner used to be able to do, under a base they no longer have. Using it as a current target is the fastest way to sabotage a return. EPP records the PB in the runner's profile for context and displays it on the progress page, but the plan itself only uses evidence from the current block. Every earned pace, every duration progression and every quality target is derived from sessions completed in the current return, not from the previous training life.

Why the aerobic system returns first — and why that is dangerous

The pattern almost every returning runner sees is the same: within three or four weeks of easy running, the cardiovascular system starts to feel like it did before. Breathing feels controlled at paces that felt hard in week one. That signal is real, but it lags the tissue side of the equation by several more weeks. Tendons, calves and feet take longer to rebuild the specific durability required for sustained running. If the runner increases pace or intensity in response to the aerobic signal alone, the tissue side pushes back — usually as a niggle in a calf, an Achilles complaint or shin discomfort. EPP is designed against this exact trap. Duration comes first, quality is deferred, and the plan will not progress pace off a single strong week.

How duration-first rebuilding actually works

In the first block of a long-break return, the only variables that meaningfully move are duration on the long run, duration on the mid-week runs, and consistency of the weekly pattern. Pace is watched as an insight — a slowly improving pace at the same HR across weeks is exactly what a returning aerobic system is expected to produce — but pace is not a target. Once the runner is consistently completing three runs a week with a long run of 50–60 minutes at conversational effort, the base is genuinely reset and Runallo can begin to explore a small amount of quality. That transition usually lands somewhere around weeks 8–12, not earlier.

How quality is reintroduced without breaking the return

The first quality session in a long-break return is deliberately small — four 20-second relaxed strides inside an otherwise easy run. This is essentially a diagnostic session. It gives Runallo a look at how HR recovers between short efforts and whether the tissue tolerates a brief change of pace. If that first session lands cleanly and repeats the following week, Runallo grows the strides into short pieces (60–90 seconds) at controlled effort — still with no work-average target that references the historical PB. Only after several clean weeks of small quality does a proper work-average session appear, and that first work-average target is derived from the returning runner's current comfortable pace, not from what they used to hold.

How Runallo handles a Parkrun temptation

The single most common request in the first month of a long-break return is 'can I do a Parkrun this weekend?' — the answer from Runallo is nuanced. During the first block, Runallo advises against a hard effort because the base does not yet support one; if the runner opts in anyway, the result is recorded but is not used as evidence for any future pace target unless the surrounding weeks were also consistent. Once the base is genuinely rebuilt, a Parkrun becomes a useful fitness marker. Until then, it is a temptation the plan will politely discourage.

What a successful long-break return looks like at 3 months

For most returning runners, a successful 12-week block looks quiet from the outside. Three consistent runs a week. A long run that has grown from 30 minutes to an hour. An easy pace that has drifted noticeably faster at the same heart rate. A few small strides on Thursdays. No PB attempts, no big weekend races, and no dramatic weeks. That is exactly what the plan is designed to produce — a base that supports actual training in month four and beyond, rather than a fast few weeks followed by a setback. The old PB stays on the profile page as history; the current earned pace is what the plan actually works from.

Frequently asked questions

  • Why won't Runallo use my old threshold pace?

    Because it is not a current pace. It is a memory of what your fitness was a year ago. Using it as a current target is one of the most reliable ways to trigger a setback during a return-to-run block.

  • How quickly will my fitness come back?

    Faster than a complete beginner, slower than most returning runners expect. A common trajectory is 8–12 weeks to a solid easy base and several more weeks before controlled quality returns. Runallo lets the completed evidence set the pace.

  • Can I include strength training?

    Yes, and it usually helps a returning runner — particularly for calf, ankle and hip resilience. Runallo works alongside a strength routine but does not prescribe the exercises.

  • When can I run a hard 5K again?

    Usually once a comfortable continuous 30-minute run has been held cleanly for several weeks and small quality sessions have been reintroduced. Runallo will suggest a controlled attempt when the evidence supports it, not before.

  • Do I need a GPS watch even for an easy return?

    Yes — the plan depends on completed pace and heart-rate data at conversational effort. See the running watches guide for compatible options.

Related examples

Get your own version of this plan

Runallo builds one for your goal, your schedule and your last few runs — free to start.