1. PaceRunner
  2. Guides

Is my training plan safe? Four checks for any running plan

Check four things: no week grows more than about 15% on the biggest of the three weeks before it; no two hard or long days back to back; the long run isn't too big a share of its week (about 40% of a five-run week); and after 10 days or more off, the first week back is no more than about three-quarters of your last full week. These are common coaching guidelines, the same ones PaceRunner checks every plan against. They catch the usual mistakes, not every risk.

Measure in time, not distance

Count each week's running in minutes. Time treats a slow runner and a fast one fairly, and a hilly 10 km and a flat one alike. Add up each run's planned time, warm-up and cool-down included. A plan in kilometers or miles converts easily at your easy pace; the free mileage increase calculator helps.

Check 1: the weekly ramp

Compare each week with the biggest of the three weeks before it. Using the biggest recent week, not just last week, means a planned cutback week doesn't make the following normal week look like a jump.

  • Rule of thumb: no more than about 15% over that peak, or 20 minutes, whichever is more. (The classic "10% rule" is stricter; many published plans rise faster than 10% and work.)
  • Week 1 counts too. Compare it with what you've actually been running, not with nothing. A plan that opens at 50 km a week for someone running 25 fails on day one.
Weeks 1–3PeakWeek 4 limitWeek 4 plannedVerdict
180, 200, 170 min200 min230 min (15%)220 minFine
180, 200, 170 min200 min230 min250 minToo big a jump
90, 100, 80 min100 min120 min (20 min is more than 15%)115 minFine

Check 2: hard days back to back

A hard day is a session with real work at half marathon pace or faster: intervals, tempo, threshold, races, time trials. Five minutes of strides doesn't count. A long day is a run of 75 minutes or more that's the week's longest. No two of these should fall on consecutive days, including across the end of one week and the start of the next.

PatternVerdictFix
Tue intervals, Wed tempoBack to backMove the tempo to Thursday
Sat 90 min long run, Sun intervalsBack to backIntervals on Tuesday instead
Sun long run, Mon threshold (next week)Back to back across the weekEasy Monday, threshold Tuesday
Tue intervals, Thu tempo, Sun long runFine

Back-to-back hard days are the most common slip in AI-written plans, especially after you ask for changes: "move the long run to Saturday" can land it the day before Sunday's intervals.

Check 3: the long run's share

A long run that's most of the week's running piles stress into one day. Common caps, as a share of the week's time:

A race on race day isn't the long run, so race week isn't flagged for it.
Runs that weekLong run at mostExample weekLong run allowed
3 or fewerNot checked (it's naturally a big share)
445%200 min90 min
540%250 min100 min
6 or more35%300 min105 min

If a marathon plan's long run breaks the cap, the usual fix is a little more easy running on other days, not a shorter long run.

Check 4: coming back after a gap

After 10 days or more without running, fitness and tissue tolerance have dropped further than it feels. The first week back should be no more than about 75% of your last full week before the break. Last full week 200 minutes, two weeks off: the first week back is at most 150 minutes, then build from there with Check 1. After a longer break, an illness, or an injury, start lower; see returning to running.

Other things worth a look

  • Most running easy. Many plans aim for roughly 80% of time at easy effort. See 80/20 running.
  • Easy pace actually easy. Easy runs written too fast are common in any plan. Check yours: easy run pace.
  • Cutback weeks every third or fourth week.
  • A taper of two to three weeks before a marathon. See the marathon taper.

How PaceRunner checks a plan

PaceRunner runs the first four checks in code on your whole calendar, whichever plan a session came from, using each workout's estimated time. On a plan's page, back-to-back hard days show on the second day's row, and the other findings under their week. When PaceRunner writes or rewrites a plan, the draft is checked and revised before you see it, and week 1 is held to about 15% over what you said you run. When a missed run is re-planned, only days that break no new limit are used. When you move a session yourself, the move happens and you're told what it newly breaks.

These checks catch the usual planning mistakes. They can't see how your body is responding: soreness that doesn't fade, poor sleep, a niggle. Those are reasons to ease off whatever the plan says.

Questions

How much should weekly running increase?
A common guide is no more than about 15% on the biggest of the last three weeks, or 20 minutes for low-volume runners. The classic 10% rule is stricter. See weekly mileage increase.
Can I do two hard runs in a row?
Generally not: put at least one easy day or rest day between hard sessions and between a long run and a workout.
How big should my long run be?
About 40–45% of the week's running time at most with four or five runs; less with six or more.
Are AI training plans safe?
They can be sensible, but they follow your lead and have no enforced limits. Run these four checks on any plan, AI-written or not, and see a professional for any pain.

Checked November 18, 2026