Editing a macrocycle plan after deploy

Two scopes of edit

A macrocycle plan exists at two possible scopes (see Macrocycle plan basics):

• The team template (is_template=True, team set).
• The individual derived plan (athlete set, often with a parent_template link pointing back to a team template).

Edits at each scope have different consequences. Decide which you want to change before you start editing.

Editing the team template

Edit the team template when the change should apply to every athlete on the team. Examples:

• Volume targets for the next mesocycle are wrong for the whole squad.
• A team-wide A race is moved.
• Phasing for the season needs a structural change.

How to edit:

1. Open the template in Django admin (/admin/core/macrocycleplan/<id>/change/).
2. Edit config_json (or any other field).
3. Save.
4. Re-deploy the template to cascade the change to derived plans. See Deploying a macrocycle.

After save (before re-deploy), derived plans get marked is_stale=True to flag that the parent template moved.

Editing one athlete's derived plan

Edit a derived plan when the change is specific to that athlete and should not be pushed back to the template. Examples:

• The athlete missed 10 days of training; ease this and next week's targets.
• This athlete has a different A race from the rest of the team.
• You want to lower volume for an injured athlete temporarily.

How to edit:

1. Open the individual plan in Django admin (filter by athlete).
2. Edit the config_json directly.
3. Save.

The change applies immediately to that athlete only. The team template is untouched, and other derived plans are untouched.

When to re-plan from scratch

Replace the plan entirely when:

• The athlete moves to a different season block.
• The athlete's goals change materially (a different A race).
• Threshold metrics shifted enough that the prescription is meaningless.

To replace, create a new MacrocyclePlan record and archive the old one (set status to archived). The old plan stays in history.

Editing from the ATP Builder (and re-pushing)

You don't have to touch Django admin. Open the ATP Builder for the athlete (from their Annual / ATP page), adjust the plan, and use the two buttons at the bottom:

• 📅 Save as this athlete's ATP — writes the plan so it shows on the Annual / ATP page and can be reloaded into the builder later.
• Push to calendar — lays the dated sessions onto the calendar. This now also saves the ATP first, so a pushed plan is always editable afterward (reopen the builder → Load it into the form → change → push again). Re-pushing replaces the previous push: its still-planned sessions are cleared, completed ones are kept.

Two conveniences in the builder's race picker: it lists only the athlete's upcoming races (a past race can't anchor a forward plan), and picking the A-race auto-fills the training-block End date to the day after race day — edit it if you want a different boundary.