PLAN VERSUS PERFORMANCE
See what was planned and what actually happened.
A practical guide to comparing planned and completed training without false scores, hidden matching, or rewritten history.
Current statusAutomatic activity import, matching, correction, and weekly reporting are planned closed-beta capabilities and are not yet available as a complete public product flow.
Keep both sides of the comparison
A completed activity does not explain the original intention by itself. A planned session does not prove what the athlete was able to do. Pitwall is designed to preserve both records, then show the relationship between them.
That means a shorter easy run can still be the right decision, while a longer ride can create useful context for the next day. The comparison should inform a choice, not hand out a moral grade.
Match carefully and allow correction
The intended matching flow uses sport, timing, duration, distance, and surrounding context to suggest which completed activity belongs to which planned session. A confident automatic match can save work, but athletes still need a manual correction path.
- Do not duplicate an activity when a provider retries delivery.
- Do not force an unplanned activity into an unrelated target.
- Show when a match was suggested, corrected, or left unresolved.
Use measurements that explain something
Duration and distance can be compared directly when both records contain them. Effort and purpose need more care. Pitwall is intended to show measurable differences and plain-language context without claiming that a single adherence score proves fitness, readiness, or training quality.
The useful output is a better review of the week and a clearer next decision. The athlete remains responsible for accepting changes to the plan.
TRAIN. PLAN. PERFORM.