Single-Session Spike Guard

A run that goes well past your recent longest is a strong injury risk, so Pheidi watches a 110% threshold in two places:

  • When it moves miles. If you take a day off or a vacation and choose to redistribute the miles, no run is given extra miles that would take it past 110% of the longest run of the same kind in the preceding 4 plan weeks. Miles that don't fit go to other runs with room, and the preview marks any week where the guard held a run back.
  • On the day. If an upcoming run is longer than 110% of your longest completed run in the past 30 days, the day view shows a spike warning so you can shorten it or split it into two sessions.

The guard doesn't trim your planned long-run build. That follows the progression rules, with recovery weeks built in.

Research: BJSM 2025 (n=5,200) found single-session spikes to be the strongest predictor of running injuries.

Acute:Chronic Workload Ratio (ACWR)

Pheidi continuously monitors your training load ratio by comparing your last 7 days (acute) against your last 28 days (chronic, averaged per week). A minimum of 3 weeks of completed workout data is required before the ratio becomes available.

ACWR RangeRisk ZoneGuidance
< 0.8● Under-trainingYou can safely increase load
0.8 to 1.3● GreenSweet spot, building fitness safely
> 1.3 and ≤ 1.5● YellowCaution, training load is ramping quickly
> 1.5● RedHigh injury risk, dial it back


Safety guards run inside the Pheidi app, sign in to see your risk score.


Research & evidence

Science behind this feature from pheidi.training.


See also

  • How Adaptive Progression Works How Pheidi increases your training volume safely: volume-aware increase rates, 3-up-1-down recovery weeks, and protection against rapid mileage spikes.
  • How Load Redistribution Works What happens to the miles you remove from your plan, and how Pheidi safely reallocates load across future easy runs without breaching ACWR thresholds.
  • How Injury Management Works How Pheidi adjusts your training plan when you report an injury: severity-based volume reductions, graduated return-to-running, and pain-based progression gates.