If you use TrainingPeaks, you’ve probably seen your TSB hit +20 on a Tuesday and had no race until October.
That’s the specific problem this article is about. Not a data problem. Not a coaching problem. A competitive calendar problem — the gap between a well-built training picture and the competitive structure that gives the picture a reason to exist.
The short version:
- TrainingPeaks and URX have no functional overlap — they address completely different phases of athletic life
- Use TrainingPeaks for coaching infrastructure: PMC, periodization, TSS-based load management
- Use URX for competitive race seasons: verified results, age-group standings, regular events to train toward
- Together: TP structures the preparation; URX provides the race to prepare for
What TrainingPeaks Actually Is
Most running platforms are built for runners who want to track their activity. TrainingPeaks is built for athletes who want to engineer their performance.
The distinction matters. TrainingPeaks assumes the user already knows why their training should be periodized, why taper timing affects performance, and why the relationship between fitness and fatigue — not just fitness alone — determines whether race day goes well. It was built for coaches and the athletes they work with. The vocabulary is specific: TSS, ATL, CTL, TSB. The platform doesn’t explain these; it uses them.
The 2025-2026 Athlete Home redesign has made the PMC more readable for self-coached athletes, adding simplified visualizations of Training Readiness and Ramp Rates, and allowing athletes to layer peak performance data points onto their fitness curve. This is a meaningful update — it brings the platform’s power closer to athletes who don’t have a coach translating the chart. But the underlying model is unchanged: TrainingPeaks remains a precision tool for people who take periodization seriously.
What the PMC Tells You — and What It Can’t
The Performance Management Chart is the core of TrainingPeaks. Understanding it precisely is the prerequisite for understanding the gap it leaves.
The chart tracks three derived metrics:
CTL (Chronic Training Load, “Fitness”) — an exponentially weighted 42-day average of daily Training Stress Score. It rises as training load accumulates over weeks and months. A CTL of 80 means you’ve averaged about 80 TSS/day over the past six weeks. For context: 80 TSS is roughly a moderately hard hour of running, or 90 minutes at easy effort. A CTL of 80 represents a real base.
ATL (Acute Training Load, “Fatigue”) — a 7-day exponentially weighted average. It responds quickly to recent training. A hard training week drives ATL up fast; a rest week drops it quickly.
TSB (Training Stress Balance, “Form”) — CTL minus ATL. When you’re in heavy training, ATL exceeds CTL and TSB is negative — you’re tired. When you taper, ATL falls faster than CTL (because fatigue clears faster than fitness), and TSB rises. Most coaches target a TSB of +15 to +25 on race day. Below -30 indicates strain that requires recovery before further loading.
What the PMC tells you: how much fitness you’ve built, how tired you currently are, and how ready you are to perform on a given date.
What the PMC cannot tell you: how that fitness compares to other runners at your level. It has no competitive reference. CTL of 90 is a meaningful number relative to your own history. It says nothing about whether 90 is strong, average, or modest for runners racing your target distance in your age group.
The PMC answers “am I ready?” It doesn’t answer “ready for what, and against whom?”
The Peak-With-No-Race Problem
There’s a specific failure mode that TP users who race infrequently know from experience, even if they haven’t named it.
A standard road running periodization block runs somewhere between 16 and 24 weeks. CTL builds at a sustainable 5–7 TSS points per week. You reach peak fitness — CTL 85, 90, 95 — and execute a taper. TSB rises into the optimal window. Everything the PMC promised is visible in the chart.
If there’s a race that week, the preparation cashes out. The structure justified itself.
If the next A-race is four months away, the peak dissolves. You can’t sustain CTL 95 indefinitely. The fitness you built over five months has a shelf life measured in weeks. By the time the race arrives, you’re building again from a lower base, with the memory of a PMC that looked perfect and nothing to show for it.
This is not a training design failure. It’s a competitive calendar problem. The periodization worked. The race opportunities didn’t match the frequency of fitness peaks the training produced.
Serious athletes in traditional competitive sports don’t have this problem because competition is built into the season. A track athlete races every few weeks. A road racer has an event calendar they built their block around. The PMC has multiple deployment points per year.
A recreational runner using TrainingPeaks for precision periodization but racing a single marathon in the fall has built a Formula 1 engine for a car that goes to the track once a year.
Why Serious Runners Need More Competitive Exposure, Not Less
There’s a performance argument for frequent competition that goes beyond motivation.
Racing produces physiological and psychological adaptations that training alone doesn’t fully replicate. Pacing under genuine competitive pressure, the ability to push past perceived limits with a field around you, executing a taper correctly and knowing what it feels like to perform fresh — these develop through competition, not through optimal training load management.
This is why coaches in serious endurance programs build in “B races” and “C races” alongside the target A-race: not just as tune-up events, but as training experiences that develop race execution skills. The PMC can model fitness. It can’t model the specific competence that comes from racing regularly.
A URX virtual race season provides exactly what B and C races provide in a traditional calendar: structured competitive events, verified results, and standings that give each performance meaning — without requiring travel, entry fees, or race-specific logistics that make B races difficult for recreational athletes to fit into their schedules.
The Two Platforms in Practice
TrainingPeaks and URX occupy adjacent but non-overlapping functions.
TrainingPeaks: receives activity data from your watch or app, calculates TSS, tracks CTL/ATL/TSB trends, provides the coach-athlete communication layer, structures the training prescription. It operates on the training side of athletic life.
URX: provides race windows, collects verified results, generates age-group standings and season rankings. It operates on the competition side.
The two tools need to communicate nothing. TrainingPeaks doesn’t need to know a URX race is happening. URX doesn’t need to see your PMC. What connects them is the underlying activity: a run that is simultaneously a training event (logged in TP as a workout with a TSS) and a race result (submitted to URX as a verified competitive performance).
The 2025-2026 Athlete Home update allows athletes to overlay peak performance data points onto the PMC — best pace or power at key durations. A submitted URX race result is exactly the kind of peak performance data that makes this feature meaningful: it shows whether the CTL built over a training block actually translated into competitive output on race day.
A Practical Example
To make the integration concrete: here’s what a periodization block looks like when paired with a URX season.
Say you’re building toward a goal half-marathon. Your A-race is in 16 weeks. CTL is currently 60; target is 80–85 at peak.
A standard periodized plan has hard weeks, recovery weeks, and a 2-3 week taper. Weeks 4, 8, and 12 might be good moments to test fitness — traditionally a “time trial” or a local race.
With a URX season running in parallel: week 4’s test run becomes an actual race result — submitted, verified, ranked against a field. The performance doesn’t just show up as a data point on your PMC; it shows where that CTL-60 fitness places you in your age group right now. Week 8’s test run shows whether the CTL 70 build translated into competitive improvement. Race week, with TSB at +20, produces a result that closes the loop on everything the training predicted.
The PMC chart and the competitive standing tell different stories about the same preparation — and both stories are more informative together than either is alone.
Frequently Asked Questions
Does URX work with TrainingPeaks? The two platforms don’t connect directly, and they don’t need to. TrainingPeaks manages training; URX manages competition. You run the activity as your training plan prescribes, the result logs to TrainingPeaks as a workout, and if the activity falls within a URX race window, you take a screenshot and submit it separately. No integration is needed.
What does a URX race result mean for my PMC? A race result is the external validation of what the PMC modeled. If your TSB is at +20 and you run a verified race that week, the result tells you whether your fitness at CTL 85 is competitive in your age group. That’s information the PMC can’t provide on its own.
Can I use TrainingPeaks and URX without a coach? Yes, to both. TrainingPeaks’s 2025-2026 Athlete Home redesign has made the PMC more accessible for self-coached athletes. URX doesn’t require a coached training program — you submit whatever activity you ran.
Which URX events make sense alongside TrainingPeaks periodization? URX race seasons are typically structured around standard distances (5K, 10K, half-marathon). For a TP user building toward a goal race, monthly 5K or 10K events fit naturally as B-race equivalents — performance tests that fall within your training block without requiring special taper management or travel.
Does URX require a specific training platform? No. URX accepts results from any tracking app or device that records a completed GPS running activity. You don’t need TrainingPeaks, Garmin, or Strava specifically. Any app that shows distance, time, and date on a completed activity is sufficient.
