A program is a reusable training plan. Its saved versions contain the schedule structure. Enrollment records a member's participation in a program.
Program structure
A program version can contain mesocycles. Each mesocycle contains microcycles, and each microcycle contains days. Days can be rest days or training days with workouts and other supported scheduled items.
A microcycle is a planning unit. Use the schedule's actual days and the tool's definition of a week instead of assuming every block contains exactly seven days.
Program, version, enrollment
| Concept | Meaning |
|---|---|
| Program | The named training plan and its identity. |
| Version | A saved structure belonging to a program. |
| Enrollment | A member's participation, with a start and an optional completion. |
| Session | Training the member actually logged. |
A program identifier, a version identifier, and an enrollment identifier are not interchangeable. Ask which program or version is intended when multiple candidates match.
Changes and progress
Inspect the current plan and enrollment before proposing a change. Do not assume a new version is automatically applied to every member or that a template edit rewrites logged history.
Progress can mean position in the schedule, elapsed time, sessions completed, or another defined metric. State which measure the tool returned. Do not turn missing server data into an adherence score.
The mobile device may hold changes that have not reached the server yet. A server-side result describes server data at the time of the request.
Assigning a program
Program assignment is a distinct operation from reviewing program progress. The external public connector cannot assign programs. Use the coaching dashboard's authorized workflow, and do not invent an assignment tool if the current agent session does not expose one.
See assign a program.