The ATP Manager: plans and templates across athletes

The ATP Manager

Manage plans across athletes from the ATP Manager at /coach/atp/ (linked from the coach dashboard). It lists every athlete ATP you own and every team template, with their status (active / archived) and quick actions.

From the manager you can:

• Open the ATP Builder for any athlete (or standalone) to build or edit a plan. See Macrocycle plans: the basics.
• Activate or archive a plan. Each athlete has at most one active ATP at a time; archiving removes it as the active overlay, and you can re-activate an archived one later.
• Deploy a team template to a roster — every athlete gets their own derived plan, with each one's starting load personalised from their real training history. See Deploying a macrocycle.

You still build and edit an individual athlete's plan in the Annual Training Plan page (/athlete/<public_id>/year/), which opens the ATP Builder linked to that athlete.

Lower-level access

• Django admin at /admin/core/macrocycleplan/ lists every plan with filters for team, athlete, status, is_template and is_stale.
• JSON API at /api/macrocycle-plans/ is the same listing in programmatic form.

Stale derived plans

A derived plan is stale when its parent team template was edited after the last deploy. In the admin list filter by is_stale=Yes to surface them, open the template, make sure it is current, and re-run the deploy.

From plan to calendar

An ATP stores weekly load targets and phases (the bars on the annual view); it does not by itself put workouts on the calendar. To create real sessions, use Push to calendar (one athlete, a static plan you can unapply) or Push to dynamic plan (a shared multi-season calendar) from the builder — see Macrocycle plans: the basics and Dynamic plans.