Watch Data Analysis: Build a 12-Week Training Plan

Purpose

Use APOPT Watch Analysis to turn FIT, GPX, TCX, Final Surge, Strava, or Zepp activity history into a coach-reviewed 12-week plan grounded in the athlete’s current preparation, target event, schedule, and recovery capacity.

What the tool does

The dashboard combines weekly mileage and load, selected-workout detail, pace and heart-rate zones, aerobic efficiency, decoupling, best efforts, pace curves, intensity distribution, race predictions, limiter evidence, and AI-ready exports. Profile fields can add age, event history, current and target performance, available days, other sports, and race-execution context.

An anonymized example report illustrates several important coaching checks. A nearly complete training history can still show a misleading headline when the latest week is incomplete. A single long run may dominate the week. Intensity shares may show strong aerobic volume but interrupted threshold or speed exposure. Limiter labels and predictions become useful only after the coach checks race execution, recent health, training intent, and whether the underlying files are representative.

Deriving actionable insight

Do not copy the dashboard into a plan. Ask what the athlete is ready to absorb.

• Confirm data coverage and exclude non-running or corrupted activities.

• Use the last 3–4 complete weeks—not a partial week—as the initial volume anchor.

• Check whether the long run or one unusual session dominates total load.

• Compare easy, threshold, VO₂/speed, and unclassified shares with the athlete’s phase.

• Use efficiency and decoupling as trends, not verdicts from one run.

• Treat predictions and limiter labels as hypotheses that must agree with athlete history and race execution.

• Build recovery weeks and at least one reassessment checkpoint into the plan.

For youth runners, use the age- and readiness-based guidance at Roadrunner Middle-School Distance and Roadrunner High-School Distance. Plans should match recent training, healthy adaptation, available days, other sports, sleep, school stress, and weather—not the mileage the athlete hopes to reach someday.

90–120 minute assignment

0–15 minutes — Frame the decision. State the athlete’s target event, date, current-performance anchor, recent weekly training, available days, other sports, and one constraint. Use your own data or authorized de-identified athlete data.

15–35 minutes — Build the dashboard. Upload the available files. Record the usable date range, missing periods, excluded files, and whether the latest week is complete.

35–55 minutes — Find the planning signals. Capture five items: recent complete-week volume, intensity distribution, long-run share, one aerobic trend, and the most plausible limiter or race-execution issue. Add one reason each signal could be misleading.

55–95 minutes — Draft 12 weeks. Create a week-by-week table with total volume or duration, one or two quality themes, long-run or sport-specific endurance work, recovery, strength/cross-training, and a purpose for each week. Use 2–3 build weeks followed by a recovery week when appropriate. Make the final 7–10 days event-appropriate rather than adding last-minute fitness work.

95–120 minutes — Athlete message and audit. Write a 150–250 word explanation of the plan for the athlete. Identify the first reassessment date and the evidence that would lead you to maintain, reduce, or progress training.

Questions to answer

1. Which complete weeks best represent current training tolerance, and why?

2. What evidence supports the plan’s primary focus?

3. Which dashboard output did you choose not to use directly?

4. Where does recovery appear in the plan?

5. What athlete feedback could change the plan immediately?

Generative AI knowledge check

Use only de-identified information.

Prompt 1: “Act as a skeptical endurance coach. I will provide a de-identified APOPT Watch summary and a proposed 12-week plan. Identify three places where the plan overreaches the evidence, three missing context questions, and one conservative revision. Do not diagnose or guarantee performance.”

Prompt 2: “Using the supplied complete-week volume, intensity distribution, long-run share, event date, available days, and athlete constraints, explain why each week in this plan exists. Flag any abrupt progression, stacked hard days, or missing recovery week.”

Prompt 3: “Create five oral-exam questions that test whether I understand aerobic efficiency, decoupling, intensity distribution, limiter evidence, incomplete-week bias, and prediction uncertainty. Ask one question at a time and critique my answer.”

Deliverable

Submit the de-identified dashboard summary, the 12-week table, the athlete-facing explanation, and a one-paragraph AI critique/reflection. The plan is a coach-editable guide, not a guarantee or medical prescription.