How should I interpret TrainingPeaks and WKO dashboards?

Training dashboards can feel like a cockpit. The goal isn’t to watch every dial—it’s to know which ones matter, when to look, and how to act. Here’s a clear way to read TrainingPeaks and WKO so your metrics drive better training, pacing, and recovery.

Get the inputs right (so the outputs mean something)

Dashboards are only as good as the data you feed them. Take 10 minutes to lock these in:

• Set accurate thresholds: Update FTP and threshold heart rate as they change. In WKO, confirm modeled FTP (mFTP) aligns with your recent bests; small wiggles (<2%) may be noise.
• Use consistent zones: Choose a system (Coggan classic, iLevels in WKO, or your coach’s) and keep it consistent across devices and software.
• Calibrate devices: Zero-offset your power meter, keep firmware current, and avoid mixing estimated power (virtual) with direct-measured files in the same block of analysis.
• Clean the data: Trim warm-up/cool-down if needed for interval analysis. Exclude corrupted files. Tag rides (endurance, threshold, VO2, race) so filters work.
• Weigh-ins and equipment: Update body mass and bike setup if they change—watts/kg, CdA estimates, and climbing velocities depend on it.

Good setup beats fancy charts. Fix thresholds, zones, and data quality before you chase trends.

Read the performance management chart: load, fatigue, and freshness

The Performance Management Chart (PMC) in TrainingPeaks and WKO summarizes how much work you’ve done and how fresh you are:

• CTL (chronic training load): Rolling average of daily TSS over weeks. Think of it as your aerobic capacity to do work. It trends slowly.
• ATL (acute training load): Short-term load. It moves quickly and reflects current fatigue.
• TSB (training stress balance): Freshness = CTL − ATL. Positive is fresher; negative is more fatigued.

Typical patterns for ambitious amateurs:

• Build phases: CTL rising gradually (3–8 CTL/week) with frequent negative TSB (−5 to −25). If you sit < −25 for weeks, expect burnout or stagnation.
• Taper: Slight ATL reduction lets TSB drift positive. Many riders feel sharp at TSB +5 to +25, but context matters—don’t force the number over how your legs feel.
• Maintenance/off-season: Lower, steadier CTL with minimal swings, more strength work, and skills.

Quick weekly check

• Trend: Is CTL climbing at a sustainable rate? If it spikes, you may be overreaching; if flat for months, plan a new stimulus.
• Balance: Are hard weeks (low TSB) followed by genuine recovery (TSB returning toward zero)?
• Consistency: Is TSS distributed across the week, or are you cramming it into one big day?

TSS ≈ (Duration in hours) × (Normalized Power/FTP)^2 × 100
TSB (today) = CTL (yesterday) − ATL (yesterday)

Caveats:

• TSS quality depends on FTP accuracy. If you bump FTP, expect CTL to dip; don’t panic—that’s the model re-scaling intensity.
• CTL is capacity, not speed. Use performance metrics (below) to confirm you’re actually getting faster.

Are you getting faster? Track the right performance markers

Use WKO’s power-duration (PD) model and TrainingPeaks charts to see whether the work is turning into speed and durability.

Power-duration curve and key WKO metrics

• mFTP: Modeled FTP from your recent bests. Upward drift with stable or longer TTE suggests real improvement.
• TTE (time to exhaustion): How long you can sustain mFTP. Building TTE from ~35–45 min toward 50–70+ min improves threshold durability.
• FRC (functional reserve capacity): Anaerobic work capacity (kJ) above FTP. Useful for punchy races and repeated surges.
• Pmax: Neuromuscular peak. Track sprint freshness and top-end maintenance.
• Stamina/curve shape: A flatter tail indicates better endurance across long durations.

Endurance efficiency and pacing

• Pw:Hr decoupling: On steady Z2 rides, aim for <5% drift. Improving decoupling at the same power suggests better aerobic economy.
• EF (efficiency factor = NP/HR): On similar terrain and conditions, a rising EF indicates more watts per heartbeat.
• VI (variability index = NP/AP): Closer to 1.00 means steadier pacing; high VI can hide extra fatigue for the same TSS.

Time-in-zone and intensity distribution

• Base/endurance blocks: 70–90% of time in Z1–Z2, with small doses of tempo/threshold.
• Build/race prep: Keep a strong low-intensity foundation while adding focused blocks at tempo/threshold/VO2 to match goals.
• Quality beats quantity: Hit target watts, repeatability, and minimal fade across intervals.

Interval quality checks

• Target adherence: Within ±3–5% of prescribed watts, not just the first rep.
• Repeatability: Minimal drop from first to last set (unless the goal is maximal efforts).
• Recovery cost: HR and RPE return between sets; if not, reduce set count or extend recovery.

Small, steady improvements across the curve plus better durability beat a single big PR.

Taper and race week sanity checks

• TSB: Let it drift positive while keeping a touch of intensity. Don’t chase a specific number at the expense of how you feel.
• Specific power: Hit a few short efforts at race power to confirm “open legs,” not to make fitness in race week.

Turn charts into decisions

• If CTL is rising but PD curve is flat: You’re getting better at doing work, not necessarily faster. Add race-specific intensity and progress interval duration.
• If mFTP rose and TTE dropped: Keep the new ceiling; now extend it with longer steady efforts (e.g., 2×20–30 min, then 1×40–60 min).
• If FRC improved but threshold sagged: Rebalance with tempo/threshold to hold speed after surges.
• If decoupling is high on long rides: Improve fueling (60–90 g carbs/h), hydration, and extend Z2 duration gradually.
• If VI is high in steady events: Practice pacing, refine gear choice, and preview course demands.

Common pitfalls

• Chasing CTL: Big numbers look good but can mask fatigue and stagnation.
• Stale FTP: Out-of-date thresholds distort every chart.
• Apples vs oranges: Compare similar terrain, temperature, and equipment when judging trends.
• Ignoring feel: RPE and sleep/recovery notes make the data actionable.

Use your dashboards like a coach: confirm the plan, spot issues early, and adjust one lever at a time. You’ll spend less time staring at charts and more time turning watts into results.