Adaptive training plans: how a running plan should change when life happens
An adaptive training plan changes when your training does. In PaceRunner that means three things: a missed hard session or long run is moved to a free day in the next week, within safety limits (easy runs aren't made up); when weeks have gone off track, Rewrite from here rewrites the rest of the plan from where you are now; and a 5K time trial or new race time updates your paces and every session to come, with big changes waiting for your OK. Every change is listed and can be undone.
What "adaptive" should mean
A plan on paper assumes every week goes to plan. Real weeks don't: a work trip, a cold, a hard session that took two days to recover from. A plan that adapts should do what a sensible coach would: not cram missed work into the next few days, not let one bad week wreck the rest, and update paces when you're fitter, without making changes behind your back that you can't see or reverse.
1. Missed runs: the week rearranges
If you share your Garmin activities with PaceRunner, it knows when a planned session had no run. It waits a grace day first, so a Tuesday session counts as missed from Thursday, leaving all of Wednesday for a late sync. Then:
| The missed session | What happens |
|---|---|
| An easy run | Left out. Easy runs aren't made up |
| A hard session or long run | Moved to the earliest free day in the next 7 days where it breaks no safety limit the plan didn't already break |
| No such day, or already moved once for a miss | Left out |
| Anything near race day | Nothing moves onto or past the race |
A moved session goes to your Garmin calendar on its new day and is checked like any send. Missed sessions don't count as training load in the safety limits. You can also settle a past session yourself: I skipped it adjusts the plan now, and I ran it without my watch marks it run and changes nothing. If the run syncs late after all, the session goes back to its day and the change reads "Reversed: the run for that day came in."
2. Off track: Rewrite from here
Sometimes moving a session isn't enough: a fortnight of illness, or a plan that's turned out too hard or too easy. Rewrite from here rewrites the rest of the plan, from next Monday to race day. It's at the foot of every plan with weeks left, and offered at the top once two sessions have been missed in two weeks.
- Say what's changed: I've missed some training, it's been too hard, it's been too easy (any or none). Confirm how much you're running now and your week's rhythm.
- PaceRunner writes the remaining weeks, keeping the plan's shape and key sessions where they still fit, and starting from where you are now. If you've agreed to it, it also uses how your last three weeks went: sessions run against planned, time against planned, pace targets hit.
- The draft is checked against the safety limits and revised up to twice before you see it. It's drawn week by week over a dashed outline of the old plan.
- Choose Replace the rest of my plan or Keep my plan as it is. Replaced sessions on Garmin come off and the new ones go on. Undo puts the old plan back.
There's no free-text box: runners would type injuries into it, and health details aren't sent to the model. The model writes sessions as efforts (easy, threshold, 5K pace); code turns them into workouts at your paces, so paces are never the model's guess.
3. Getting fitter: paces follow
Paces come from a race time through the Daniels–Gilbert equations. As you get fitter, they should move with you:
| Source | Applied |
|---|---|
| A 5K time trial in the plan (offered every fourth week, in place of that week's first hard session) | At once if under 2% faster; a change of 2% or more, or any slower result, waits for your OK |
| A time trial result you type in | Same as above |
| A new race time or changed paces on your profile | At once, to upcoming sessions (you can untick it) |
| Hard sessions that keep missing their pace range over about two weeks | Only offered, never applied on its own |
A 2.6% faster time trial, for example, reads "Paces 2.6% faster: Threshold 4:47 → 4:40/km" with Use the new paces and Keep my paces. When applied, every session from today on that hasn't been run is updated, and the ones on Garmin are re-sent and checked. Paces you set by hand move by the same percentage and stay yours; paces written out in a plan stay as written. The latest change can be undone.
- 15 min easy
- 5 km as fast as you can hold evenly, no target
- 10 min easy
What stays fixed: the safety limits
Every automatic change, and every rewritten plan, is held to the same four rules in code: no hard days back to back, weekly time up no more than about 15% on the biggest of the three weeks before, the long run capped as a share of its week, and a gentler first week back after a gap of 10 days or more. A model can't override them. When you move something yourself, the move happens (it's your plan) and you're told what it newly breaks. The rules in full: is my training plan safe.
Every change is visible
- The plan page lists each adjustment under Changes, with its reason and Undo. A session left out has Make it up on… to place it on a day you choose.
- Pace changes are listed on your profile under Pace changes.
- In ChatGPT or Claude, with PaceRunner connected, the calendar shows which sessions were missed and where moved ones came from, so the assistant can talk about the week with you.
Questions
- What happens if I miss a run?
- An easy run is left out. A hard session or long run moves to the earliest free day in the next 7 days that breaks no safety limit; if there's none, it's left out. You can undo any move.
- Will it change my plan without asking?
- Moves after a missed run happen on their own, listed with Undo. Rewriting the rest of a plan, and pace changes of 2% or more, always wait for your OK.
- Does it work with a plan I imported?
- Yes. Imported plans, plans from ChatGPT or Claude, and plans PaceRunner wrote all adapt the same way.
- How does it know I missed a run?
- From your Garmin activities, if you share them with PaceRunner. It waits a grace day for late syncs before treating a session as missed.
Checked November 18, 2026