Listing and managing macrocycle plans across athletes

Where this lives today

The Hub does not yet ship a dedicated frontend macrocycle dashboard. Plan management currently happens in two surfaces:

• Django admin at /admin/core/macrocycleplan/. List view shows every plan you have access to (team templates and individual derived plans), filterable by team, athlete, status, is_template, and is_stale.
• JSON API at /api/macrocycle-plans/. Same listing in programmatic form, used by the in-progress frontend planner.

A dedicated coach-side dashboard for plan management is on the roadmap.

What to look for in the admin listing

• is_template=True rows are team-level master plans.
• Rows with a parent_template link are derived individual plans that came from a template.
• is_stale=True rows are derived plans whose parent template was edited after the last deploy. These need a re-deploy. See Deploying a macrocycle.
• status=archived rows are previous plans kept for history but no longer active.

Filtering for stale plans

In the admin list, filter by is_stale=Yes to surface plans that need re-deploy. Then open the template they derive from, make sure it is current, and re-run the deploy.

Why adherence is not yet here

You will not find an adherence metric (planned vs actual volume) in the listing today. That comparison happens activity by activity on individual athlete dashboards. A roster-wide adherence report is on the roadmap.