Deploying a macrocycle template to a team roster

What deploy means

The macrocycle deploy is the action that cascades a team template down to every athlete on that team. It takes a plan with is_template=True attached to a team and produces (or updates) an individual plan for each athlete, with the template's config_json carried down and a parent_template link pointing back.

URL: /admin/macrocycle-deploy/<plan_id>/.

Who can deploy

Only head coaches of the team (the Main Coach) and admin tier users. Assistant coaches are blocked because deploying affects the whole team's plans, which is a head-coach decision.

What deploy does

• For each athlete on the team, looks up the existing derived plan (one whose parent_template is this template).
• If the athlete has no derived plan, creates one with the current template config.
• If the athlete already has one, updates it from the template.

A plan is marked is_stale=True if the parent template was updated after the athlete's derived plan was last deployed, which surfaces in the macrocycle dashboard so you can see who is out of sync.

What deploy does NOT do

• Touch athletes who are not on the team.
• Touch individual plans that were created from scratch (no parent template link).
• Modify the athlete's race calendar, wellness logs, equipment, or any other data outside the macrocycle plan record.

Individual plans

You can also create an individual MacrocyclePlan for one athlete without a parent template (athlete set, team blank). For those plans there is no separate "deploy" cascade; the plan takes effect when its status is set to active and its date window covers the current week.

When to redeploy

• You updated the team template (added or removed a race, changed weekly volumes, changed phasing).
• New athletes joined the team and you want them populated with the team plan.
• You want to push a corrected template down to refresh stale derived plans.

Redeploy is safe: athletes whose derived plans already match the template are left untouched.