Adherence metrics become misleading when the denominator is unclear. A client who completes three sessions out of three assigned sessions is different from someone who logs three sessions against an undefined plan. Define what counts as assigned, completed, skipped and rescheduled before comparing percentages.
The contract to define first
Keep the planned schedule version and the logged activity distinct. Decide how late logs, partial sessions and approved schedule changes affect the reporting window. Display missing information separately from noncompletion. A coach should be able to trace a summary back to the underlying sessions rather than relying on a score whose rules change invisibly.
A worked scenario
In a synthetic week, one of four planned sessions is rescheduled into the next week by the coach. The report should follow the documented denominator policy and identify the change. It should not silently improve or penalize the client’s apparent adherence after the reporting period closes.
An implementation and review sequence
- Define the reporting denominator and completion criteria
- Track schedule revisions and late logs
- Provide a path from totals to session evidence
Failure cases worth testing
| Condition or input | Expected behavior |
|---|---|
| A session is partially completed | Apply the stated completion rule |
| Coach reschedules an assignment | The denominator follows the documented policy |
| A late log arrives | The report shows the resulting revision |
Download the illustrative acceptance checklist (JSON)
Tradeoffs and limits
Simple percentages are easy to read but can hide context. Pair the summary with counts and a clear policy, then use richer detail only where it helps a coach make a decision.
Use the result to make a decision
The practical output is straightforward: define completion denominators and late logging rules. Keep the assumptions with the artifact so a product owner, implementer or prospective partner can review the same decision. A useful handoff states the supported scope, the evidence collected and the remaining dependency instead of treating a successful demonstration as proof of every operating condition.
Continue with related implementation detail
Related guide: Building UltraFit360: the app, coach portal and shared backend
Coach client access after reassignment
Workout substitutions by equipment
References and current platform requirements
Android: health and fitness app design
The linked references provide platform or process context. The worked scenario and acceptance matrix are original examples; adapt them to the actual product, supported environment and documented responsibilities.
Discuss the workflow
Map one coach-to-client workflow with AptixLabs before expanding the feature list.
Explore the relevant AptixLabs service
What is the denominator for training adherence?
Adherence metrics become misleading when the denominator is unclear. Simple percentages are easy to read but can hide context.
Which failure cases should be included in the review?
Include these explicit cases: A session is partially completed: apply the stated completion rule; Coach reschedules an assignment: the denominator follows the documented policy; A late log arrives: the report shows the resulting revision.