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 statusManual activity entry, FIT and Garmin ZIP import, suggested matching, manual correction, GPS route playback, progress totals, and personal-record eligibility controls are live in the controlled closed beta. Temporary Garmin activity synchronization is available to approved athletes.

01

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.

02

Match carefully and allow correction

The matching flow uses sport, timing, duration, distance, and surrounding context to suggest which completed activity belongs to which planned session. Athletes can accept the suggestion, choose a different target, or leave completed work unlinked.

  • 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.
03

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.

Closed beta first. Open beta after validation.

Read beta status