Non-Destructive Overlays

Every modification to your plan, including vacations, injuries, manual edits, and redistribution, is applied as a layer on top of the original plan. The base plan data in the database is never modified. Layers are re-applied each time your plan loads.

This means you can always "undo" any modification by removing the overlay, and your original plan is restored exactly as it was.

Moving workouts around (a swap, or a reflow after you change your training days) is saved against the original plan, never against the adjusted version you see on screen. If an injury, vacation or workout edit is reshaping a week, the mobile app won't save moved workouts in that week, so the adjusted versions never become your plan by accident.

Layer Application Order

Layers are applied in a specific order, with later layers taking precedence:

  1. Vacations: reduce or zero out workouts during time off
  2. Injury: apply severity-based distance reductions
  3. User Edits: manual overrides to workout type, distance, or load
  4. Redistribution: spread removed miles across future easy runs
  5. Automatic adjustments: trim a week's easy runs when an active auto-replan cut applies
  6. Weather: add heat and humidity pace guidance to upcoming runs, when weather adjustment is on

Redistribution runs after vacations, injuries, and user edits so it can see vacation/injury reductions and user overrides. Automatic adjustments run after redistribution so they see the redistributed distances, and they skip any run already shaped by a vacation, injury, manual edit, a workout you added, or a day off you kept as a shorter easy run. The weather overlay comes last and changes pace guidance, not distance.

How Each Layer Works

  • Vacation layer: applies the vacation's load percentage (0% for full rest, or a custom percentage for light mode) to each affected workout
  • Injury layer: skips workouts already modified by vacation; applies severity-based reductions to future workouts only
  • User edit layer: replaces planned values with your manual overrides and tracks the delta miles for redistribution. Changing the type gives the workout that type's pace zone and effort, so a tempo turned into an easy run is paced as an easy run, and drops the warm-up and cool-down unless the new type is another quality session. Switching to a non-run type (or zero distance) clears run-only fields like pace zone, warm-up, and cool-down.
  • Day off: taking a day off is a special user edit: it creates an override (with the DayOff modifier) that either zeros the workout out or, if you set the load slider above 0% (up to 80%), keeps it as an easy run at that share of the planned distance, shown as "Day Off — Light". It also queues a matching redistribution so the missed miles can be picked up across future easy runs.


Plan layers run inside the Pheidi app, sign in to use them.


Research & evidence

Science behind this feature from pheidi.training.


See also

  • How Schedule Flexibility Works How Pheidi adapts your training plan when life gets in the way: day blocking, workout swapping, and automatic reflow that preserves the overall training load.
  • How Vacation Scheduling Works What happens to your training plan when you schedule time off: date-range blocking, load redistribution, and graduated return to normal volume.
  • 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.