Training Quantification Monitoring in Practice: Understanding PMC, TSS, CTL, ATL, and Form—Don't Be Fooled by the Numbers

Coach’s Opening: That Green Line That Keeps Dropping

Every March, the same kind of message pops up in my training group chat: “Coach, my PMC green line keeps dropping — am I about to blow up?” Or the opposite — “Coach, my Form has been positive the whole time, am I training too little?”

In fifteen years of coaching triathletes, from the office worker taking on his first Taitung 51.5 hoping just to finish, to the veteran who eventually flew to Hawaii and earned a Kona slot, I’ve noticed one thing: most people aren’t lacking effort — they just can’t read the numbers behind their effort. They have power meters, heart rate straps, Garmins, TrainingPeaks accounts — data coming out of their ears — yet when it comes to the most critical question, they go by feel: Should I add volume this week or back off? Am I actually progressing, or digging a hole for myself?

In this article, I want to explain PMC (Performance Management Chart) — this quantitative monitoring tool — in plain coaching language. Not by dumping a pile of definitions for you to memorize, but by telling you: what these lines are saying, what a safe rate of change looks like, and the numerical traps that can ruin your training. After reading this, when you open your own chart, you should be able to answer that question yourself: “Should I add or back off right now?”

First, one mindset: numbers are there to support decisions, not to be worshipped. The best data-literate athlete I’ve ever coached was also the one who knew exactly when to take the watch off and go by how his body felt.

---

Conceptual Foundation: What Those Four Letters Actually Mean

To read PMC, you first need to know four core metrics. I’ll explain them in the most down-to-earth way possible — just grasp the “meaning” behind them; the formulas are secondary.

TSS: The “Total Bill” for One Workout

TSS (Training Stress Score) condenses “how hard” a single workout was into one number. It accounts for both duration and intensity. By definition, riding at your FTP (Functional Threshold Power) for one hour equals exactly 100 TSS.

So:

• An easy recovery ride of 1 hour might be only 40–50 TSS
• A serious interval session of 1.5 hours might hit 110–130 TSS
• The bike leg of a 113 half-ironman typically eats 250–320 TSS — that’s normal
• A full standard-distance triathlon (51.5) totals roughly 120–180 TSS, depending on your swim/run split

Key concept: TSS is the bill for a “single” session. By itself, it doesn’t tell you whether you’re improving — only how much you charged today. What’s truly interesting is accumulating those daily bills and looking at the trend — and that’s where the next three metrics come in.

CTL: Your “Fitness Bank Account” (Slow Variable)

CTL (Chronic Training Load) is the exponentially weighted average of your daily TSS over the past 42 days. In TrainingPeaks, it’s labeled “Fitness.”

Think of CTL as a fitness bank account. A CTL of 60 means your body has adapted to handling “roughly 60 TSS per day” on average. This number climbs slowly and falls slowly, because it averages six weeks of data — which is exactly what makes it reliable. Skip a day or two and CTL barely moves; but slack off for three straight weeks and it will slowly shrink, honestly reflecting that your fitness has genuinely declined.

ATL: Your “Current Fatigue” (Fast Variable)

ATL (Acute Training Load) is the exponentially weighted average of your daily TSS over the past 7 days, labeled “Fatigue.” Because it only averages seven days, it’s very sensitive — hit a hard session yesterday and ATL jumps today; rest two days and it drops right back down.

CTL is the slow variable, ATL is the fast variable — this “difference in timescale” is the soul of the whole system. The slow one represents the strength you’ve built long-term; the fast one represents how much fatigue you’re carrying right now. Subtract the two, and you get the most practical number of all.

TSB / Form: How “Fresh” You Are Today

TSB (Training Stress Balance), commonly known as Form, is simply:

TSB = Yesterday’s CTL − Yesterday’s ATL

The meaning is intuitive:

• TSB deeply negative (e.g., −25): You’re buried in fatigue, your fitness bank is far below your current fatigue — “digging deep.” Normal during a heavy block.
• TSB near 0: Fatigue and fitness are roughly balanced — the norm for everyday training.
• TSB strongly positive (e.g., +15): You’re fresh and rested, ready to race — but it could also mean you’re training too little.

Let me plant a seed here: a positive TSB isn’t necessarily good, and a negative one isn’t necessarily bad. That’s the star of the “number traps” section later.

One Table to Understand the Four Brothers

Metric	Common Chinese Term	Time Window	Personality	What You Should Care About
TSS	Training Stress Score	Single session	Bill	How much this session charged
CTL	Fitness	42 days	Slow, steady	Long-term fitness bank
ATL	Fatigue	7 days	Fast, sensitive	How much fatigue you’re carrying now
TSB	Form	CTL−ATL	The difference	How fresh you are today, whether you can race

---

Reading the PMC Chart: A Conversation Between Three Lines

A PMC chart typically shows three lines (TrainingPeaks default colors):

• Blue line = CTL (Fitness): The one climbing steadily — the fruit of your six weeks of work.
• Red line = ATL (Fatigue): The one jumping around most violently — reflects the last few days.
• Green line = TSB (Form): The one swinging above and below zero — the difference between blue and red.

Learning to read the chart is learning to read “what story the relationship between these three lines is telling.”

Scenario One: A Healthy Build Phase

The blue line climbs steadily to the upper right, the red line bounces above the blue, and the green line mostly sits between −10 and −25. This is the ideal “making progress while handling the load” look. Your legs feel heavy — but not the kind of heavy that breaks you. This is what I want most athletes to live in during the 8–12 weeks before race season.

Scenario Two: Tapering

In the 1–2 weeks before a race, we deliberately cut training volume. You’ll see the red line drop fast (fatigue dissipates quickly), the blue line dip only slightly (fitness fades slowly), and so the green line swings rapidly from negative to positive, shooting upward.

That’s the magic of the taper: trading “a tiny bit of fitness” for “shedding a huge amount of fatigue,” so you’re fresh on the starting line. I usually want my athletes to have a TSB between +5 and +20 on race day — the sweet spot most research and coaching communities agree on for endurance performance. Too negative means you haven’t tapered enough; too positive (e.g., +30 or above) means you’ve cut back too much and your legs have gone “hollow.”

Scenario Three: Dangerous Over-Stacking

The red line stays far above the blue for a long stretch, the green line stays pinned below −30 or even −40 and won’t come back up, and at the same time you subjectively feel sleep is poor, HRV (heart rate variability) is dropping, morning resting heart rate is inexplicably elevated, and you have no motivation to train — this isn’t “being dedicated,” this is the precursor to Non-Functional Overreaching, and the next step is overtraining. At this point, the answer isn’t to add volume — it’s to hit the brakes.

---

The Core of the Core: Ramp Rate

If you can only remember one thing from this article, let it be this: Ramp Rate (weekly CTL increase) predicts injury risk better than the absolute CTL value.

Ramp rate is simply how many points your CTL rises each week. If CTL goes from 50 to 55, that week’s ramp rate is 5. Why is it more important than CTL itself? Because the body’s adaptation speed has an upper limit, and the cardiorespiratory system adapts quickly, while tendons and ligaments adapt slowly. Your engine (cardio) might handle a sudden spike in training load, but your drivetrain (tendons, ligaments, bones) can’t keep up—that’s why people who ramp up their running or cycling volume too fast often see problems in the “structure” first—Achilles tendon, IT band (ITBS), shins—rather than running out of breath.

How to Find the Safe Zone

Based on consensus across multiple coaching communities (including Joe Friel and official TrainingPeaks articles), here’s a practical reference table I’ve put together:

Weekly CTL Increase	Classification	Suitable For	Coach’s Notes
3–5 pts/week	Conservative, sustainable long-term	Most amateur athletes, those returning from a break, short training history	Safest option; aim for this when building over 8+ weeks
5–7 pts/week	Aggressive but manageable	Athletes with solid training history and good recovery habits	Only for short-term pushes; don’t string together multiple weeks
Over 8 pts/week	High-risk zone	Almost no one should stay here long-term	Significantly higher chance of illness, injury, or burnout

For the office workers I coach from first triathlon to Olympic distance, I almost always keep ramp rate in the 3–5 range. They work during the day, may need to look after kids at night, and life stress itself is an invisible training load (the PMC chart won’t factor in your boss’s relentless calls). For this group, climbing slowly and climbing long is far more cost-effective than going hard for a month and then ending up sick.

Only for veterans with 5+ years of training history, solid sleep and nutrition, and relatively simple lives do I briefly push to 6–7 during a specific build block—and I watch closely, pulling back immediately at the first sign of fatigue.

A Realistic Ramp-Up Example

Take an Olympic-distance triathlete starting with a CTL of 40, aiming to reach CTL 65 after 12 weeks, using a gentle ramp of roughly +4 per week with a recovery week inserted every three weeks (CTL dips slightly):

Week	Week Type	Weekly TSS Target	Weekend CTL	Weekly Ramp
1	Build	300	42	+2
2	Build	340	46	+4
3	Build	360	50	+4
4	Recovery	230	48	−2
5	Build	380	52	+4
6	Build	400	56	+4
7	Build	410	59	+3
8	Recovery	260	57	−2
9	Build	420	61	+4
10	Build	430	64	+3
11	Build	430	66	+2
12	Taper	280	64	−2

Note two things: First, a negative ramp during recovery weeks is normal and necessary—a slight CTL dip doesn’t mean regression; it’s the body truly “digesting” the stimulus from previous weeks into fitness. Second, the closer you get to the end and the higher CTL climbs, the smaller the ramp naturally becomes, because maintaining the same ramp rate requires racking up more and more TSS—which isn’t realistic in an amateur life with limited time. Forcing it is how you break down.

---

The Traps in the Numbers: Pitfalls That Break Smart People

This is the chapter I most wanted to write. Reading the charts is just the entry level—seeing through the lies in the numbers is the advanced course.

Trap One: Does a Positive TSB Mean You’re in Good Form?

No. A positive TSB only means “fatigue is lower than fitness.” It can’t distinguish between “tapered clean, ready to fire” and “not training at all.”

I once had an athlete who took a long break over the Lunar New Year, and his TSB shot up to +35. He excitedly sent me a screenshot saying, “Coach, I’m in amazing form.” I replied: that’s not good form—your fitness bank is draining; the green line just looks nice because fatigue is even lower. Sure enough, at the first interval session after the break, his power dropped noticeably. A chronically high TSB is an alarm for fitness loss, not a badge of honor.

Trap Two: Is Higher CTL Always Stronger?

CTL measures the quantity of training load, not the quality of performance. Two people with a CTL of 70—one built it with mindless long Zone 2 rides, the other with structured intervals, threshold work, and race-pace sessions—the latter will crush the former on race day. CTL only answers “how much have you swallowed,” not “whether that volume is effective training.” Don’t pad your blue line with junk miles that serve no training purpose.

Trap Three: TSS Itself Can Be Fake

TSS calculations depend heavily on whether your FTP (power) or threshold heart rate settings are accurate. If FTP is set too low, the same ride will produce an inflated TSS, and your CTL and ATL get watered up along with it—the charts look booming, but it’s a mirage. I require athletes to retest FTP at least every 6–8 weeks, or whenever they feel noticeably stronger. Garbage in, garbage out—if the input parameters are wrong, all the fancy charts afterward are illusions.

Runners using heart-rate-based TSS (hrTSS) need extra caution: Taiwan’s summers are hot and humid. At the same pace, heart rate gets artificially elevated by the heat, inflating hrTSS. Training along Taipei’s riverside in July or August, your heart rate data will read higher than at the same intensity in winter—don’t let the inflated TSS scare you into thinking you’re overtraining.

Trap Four: PMC Doesn’t Know Your “Life Stress”

PMC only consumes the training data you upload. It doesn’t know you stayed up late finishing a report, doesn’t know you have a cold this week, doesn’t know you’ve been eating out and missing proper nutrition. True total stress = training stress + life stress, but the chart only shows the former. So a green line of −15 might be easy for a retired person with a regular routine, but for a new dad burning the candle at both ends, it might already be the limit. Always use subjective feelings (sleep, appetite, mood, morning HRV) to calibrate the objective numbers.

Trap Five: Treating a CTL Drop During Recovery Week as Regression

Mentioned earlier but worth repeating: CTL dropping during recovery weeks and taper periods is by design, not a sign you’re getting weaker. The body gets stronger through “supercompensation”—stimulus, fatigue, then growing higher fitness during rest. Panicking at a slight blue-line dip and adding more training is like constantly interrupting the body’s renovation project.

Trap Six: Chasing the “Perfect Chart” While Ignoring Real Performance

This is the easiest pitfall for seasoned data nerds. Some athletes take PMC to the extreme, adjusting their schedule daily just to make the curves “pretty”—ramp precisely locked at 5.0, the green line as smooth as if drawn with a ruler. But a pretty chart doesn’t equal running fast. What truly tests whether training works is always on-field performance: Has your FTP improved? Can you hold race pace longer? At the same CTL, do you recover faster from a long ride than before? These “performance markers” are the goal; PMC is just the dashboard of the process. I’ve seen people who keep their charts perfect yet their PBs stagnate all season—the problem is usually “volume is right, but intensity distribution or recovery quality is off”—and PMC won’t tell you a single word about that. Don’t fall in love with the dashboard; fall in love with the finish-line time.

---

Practical Application: How to Use This in a Taiwanese Daily Life

Now that we’ve covered the concepts and pitfalls, here’s something you can use directly.

Three Questions for Your Weekly Chart Review

Every Sunday evening, I have athletes open PMC and ask themselves three questions:

1. How many points did CTL rise this week? Did it fall within my ramp target range (3–5 for most people)? If it exceeded, back off next week; if too little, make up for it next week.
2. Where is the green line now? A TSB between −10 and −25 is healthy; if it has been stuck below −30 for two or three consecutive weeks and won’t recover, force a recovery block.
3. Are objective and subjective signals conflicting? The chart looks great but I feel exhausted → trust the body, back off. The chart looks rough but I actually feel energetic → you can push a bit more.

Sample Weekly Schedule (Sprint Triathlon Base Period, ~400 TSS/week)

Using the example of a working professional sprint triathlete who can train 8–10 hours per week:

Day	Workout Content	Estimated TSS
Mon	Rest or swim technique session (low intensity)	30
Tue	Trainer intervals: 4×8 min @ threshold	90
Wed	40-min tempo run + core work	60
Thu	Main swim set (with pace groups) + easy ride	55
Fri	Rest (important! Let the body digest)	0
Sat	Long ride 2.5–3 hrs Zone 2–3	130
Sun	Long run 70–80 min + race-pace finish	65

The week totals about 430 TSS, with hard sessions (Tue, Sat) separated by low-intensity work or rest. This is called hard-easy alternation, the fundamental skill for keeping ATL from spiraling out of control. That zero on Friday isn’t laziness—it’s strategy.

Connecting the Whole Season: PMC in Periodization

A weekly schedule is just a brick; the real house is “season-long periodization.” I typically break a season into four phases, each presenting a distinct picture on PMC:

Phase	Duration	CTL Trend	Typical Green Line (TSB)	What’s Happening
Base	6–12 weeks	Steady gradual rise, ramp 3–5	−5 to −20	Building aerobic foundation, lots of Zone 2, tendons and bones gradually adapting
Build	4–8 weeks	Continued rise, ramp can be slightly higher	−15 to −28	Adding race-intensity intervals, converting “volume” into “quality”
Peak/Taper	1–2 weeks	Slight decline	Crosses from negative to +5 to +20	Shedding fatigue, preserving fitness, peaking for race day
Transition	1–3 weeks	Clear decline	Mostly positive	Post-race physical and mental recovery, active rest—don’t fear the CTL drop

Many people get stuck at “impatience in the base period.” They see the blue line climbing slowly and get anxious, skip the foundation work and jump straight to intervals—then the build phase dumps high-intensity work on unprepared tendons, and ITBS, plantar fasciitis, and friends all show up. The base period is boring, but it determines how much stimulus your build phase can absorb. The deeper the foundation, the taller the building you can erect.

Another key is the “transition period.” In Taiwan, races often stack back-to-back (Challenge Taiwan in spring, city triathlons across the island in summer, and a pile of marathons in fall/winter), and many people never give themselves a proper off-season. On PMC, that shows up as the green line pinned in negative territory year-round and CTL held up by sheer stubbornness. This “always in race prep” state often ends, two or three years later, in a major injury or a whole season of burnout. Letting CTL drop in the transition period is a hallmark of a mature athlete, not a step backward.

A Full Walkthrough of a Real Scenario

Let me walk through the entire process using one athlete’s situation (pseudonym A-Jhe). A-Jhe, 38, works in tech, targeting a fall 113 half-ironman with a goal of finishing under 6 hours. His CTL at the start of the year was only 35 (he slacked off over the winter).

Here’s how I set him up:

• Weeks 1–10 (Base): Ramp held around 4, CTL pushed from 35 to 63. His most common complaint during this stretch was “why are we always riding slow,” but I told him to hold the line. A recovery week every third week brought the green line back near 0 to let him catch his breath.
• Weeks 11–16 (Build): Added 113 race-pace long brick sessions (ride then run), ramp nudged up to 5, CTL pushed to 72. The green line sat around −22 during this phase, and he started feeling “legs are heavy but they keep pushing”—exactly the signal I was looking for.
• Week 15 had a hiccup: His company hit a project crunch, he pulled all-nighters, and one Monday his morning heart rate was 8 bpm higher than usual with HRV dropping. The PMC chart looked fine that day (green line only −18), but I told him to swap the day’s intervals for an easy ride. That’s “subjective + physiological data correcting the objective chart” in practice—the chart gave no alarm, but the body did.
• Weeks 17–18 (Taper): Training volume cut to 50–60% of normal, the red line dropped sharply while the blue line only dipped slightly, and the green line reached +12 on race day. CTL eased from 72 down to 66.

The result? A-Jhe finished in 5:47, hitting his goal. Note: his race-day CTL was 66, not the peak of 72. That’s completely normal—you don’t race on “peak fitness”; you race on “fitness retained after fatigue is shed.” That’s why obsessing over CTL’s absolute value is pointless; what matters is always the dynamic gap between CTL and ATL.

Practical Considerations for Taiwan

• Working backward from race goals: For a solid Challenge Taiwan (Taitung) sprint triathlon finish, aim to push CTL above 50 pre-race; for a comfortable 113 half-ironman finish, a CTL of 65–80 gives you a solid buffer. For classic cycling challenges like the one-day Taipei–Kaohsiung or Wuling (that climb on Provincial Highway 14A that makes you question life), the higher your CTL, the safer you are.
• Climate adjustments: Taiwan’s summers are hot and humid, so heart rate and TSS at the same effort run higher. If your taper happens to land in midsummer, don’t let inflated numbers scare you into adding extra work. In winter, the northeast monsoon blows hard—headwind rides along the river may show great power but slow speeds, so watch power, not average speed.
• Eating out and nutrition: Eating out in Taiwan is convenient, but refined carbs are plentiful and protein often falls short. As training volume climbs (ramp increases), recovery demands rise in tandem. A daily protein intake of 1.6–2.0 g per kg of body weight is a common recommendation for endurance athletes. Convenience-store tea eggs, unsweetened soy milk, and chicken breast are your friends. If nutrition doesn’t keep up, even a beautiful PMC is a castle in the air.

---

Actionable Advice for Athletes at Different Levels

First-Timers / Just Starting with Power and Heart Rate

• Don’t worry about whether the green line is positive or negative yet—just keep your ramp rate between 3 and 5. Your biggest enemy at this stage isn’t training too little; it’s training too hard, getting injured, and dropping out.
• Get your FTP / threshold heart rate measured accurately—it’s the foundation for every number that follows.
• Trust subjective feel over the charts. Your body is more honest than the software right now.

Sprint Triathlon / Advanced Triathletes

• Start learning to use “recovery weeks that let CTL dip slightly” to buy a higher long-term ceiling—don’t fear the blue line dropping.
• Taper goal: aim for a race-day TSB of +5 to +20. The exact number varies by individual, so use a few practice races before your A-race to find your own sweet spot.
• Retest FTP every 6–8 weeks to keep TSS from being inflated or deflated.

Long-Distance / Veterans Chasing Results or Even Kona Slots

• You can push ramp to 6–7 short-term, but you must use HRV, morning heart rate, sleep, and subjective fatigue as a multi-layered brake—the moment any alarm sounds, back off immediately.
• Learn to distinguish “functional overreaching (supercompensation makes you stronger)” from “non-functional overreaching (you get weaker the more you train)”—the difference shows in whether performance bounces back after a recovery week.
• Treat PMC as a long-term strategic map, making decisions on “multi-week trends” rather than “single-day numbers.” No matter how ugly a single day’s green line looks, it should never make you scrap the whole season’s plan that same day.

FAQ

Q: I don’t have a power meter, only a heart rate strap. Does this still work?

Yes. Switch to hrTSS (calculated based on threshold heart rate). Accuracy is slightly lower than power-based TSS, and as mentioned earlier, it’s heavily affected by heat and dehydration, but the trends are still useful. The key point remains the same: “Look at trends, don’t obsess over a single number.”

Q: How high does CTL actually need to be?

There’s no standard answer; it depends on your target race distance. Instead of chasing an absolute number, ask yourself, “Given the demands of my target race, has my CTL grown steadily enough to handle it comfortably?” A person with a CTL of 55 but solid structure may perform better than someone with a CTL of 75 built entirely on junk miles.

Q: The green line goes up and down every day. Which day should I look at?

Look at the trend, not the single day. A single day’s green line is heavily influenced by the previous one or two days of training and isn’t very meaningful. What’s truly valuable is “which direction this line has been heading over the past two to three weeks.” Only the TSB on race day needs to be looked at precisely.

Q: Can I decide whether to train based solely on PMC?

Not recommended. PMC is just one input into the decision; the other two are subjective feeling and morning physiological data (HRV, resting heart rate). Look at all three together, and when they conflict, lean toward being conservative. In fifteen years of coaching, I’ve never seen an athlete get worse from resting too much, but I’ve seen plenty who “crashed from doing one extra workout.”

Q: How do I combine TSS across the three triathlon disciplines (swim, bike, run)?

Most platforms sum the TSS calculated for each discipline (swimTSS, bikeTSS, runTSS) and feed them into the same CTL/ATL. This is convenient for monitoring “total load,” but remember: running impacts your structure far more than swimming or cycling. For the same 60 TSS, a long run does far more damage to tendons and bones than a session on the indoor trainer. So don’t just watch the total TSS ramp rate—also keep a separate eye on the rate of increase in “run volume.” Be especially conservative with running.

Q: I was sick this week and didn’t train, so my CTL dropped a chunk. Should I make it up?

Don’t rush to make it up. Your body is already weakened after illness, and aggressively spiking the ramp rate to “earn back” the lost CTL is the classic script for relapse plus injury. The right approach is to treat the first week after illness as a gentle restart, easing back into rhythm with lower-than-usual volume and letting CTL recover naturally. Those few points of fitness are far easier to regain than a major illness or a training injury.

---

Conclusion: Let the numbers be your co-pilot, don’t let them grab the wheel

Back to that anxiety about “the green line keeps dropping” from the opening. Now you know: during the base phase, the green line is supposed to be negative. That’s not an alarm—it’s you banking fitness. What should actually trigger caution is when it drops too deep and won’t recover, combined with fatigue signals from your body.

The PMC, TSS, CTL, ATL, and TSB toolkit is powerful, but it’s ultimately the co-pilot—it helps you read the dashboard, warns you not to spike the ramp rate, and tells you whether your pre-race taper is clean enough. The wheel belongs in your hands, because only you know how well you slept last night, how much work stress you’re under, and whether your legs feel “heavy in a good way” or “heavy in a bad way.”

Learn to read the numbers, then use them to serve your body—don’t let them hold you hostage. That’s the real value of quantified training. Next Sunday night, open your PMC and ask yourself those three questions—you’ll find you no longer need to ask your coach in the group chat.

This article is educational content and does not replace individual assessment by a physician, physical therapist, or nutritionist.

---

References

• A Coach’s Guide to ATL, CTL & TSB — TrainingPeaks
• Why Ramp Rate is an Important Training Metric — TrainingPeaks
• The CTL Ramp Rate — Joe Friel
• CTL, ATL & TSB Explained — Paincave
• How to Read Your Training Data: TSS, CTL, ATL, TSB Explained — Roadman Cycling

Related Reading

• How to Read the PMC Chart: How ATL, CTL, and TSB Guide Your Training Cycles
• Training Peaks Fully Explained: TSS, ATL, CTL, and Race Preparation Adjustments
• CTL, ATL, and TSB Fitness-State Models: Tracking Training Status with Data
• Power Meter Training for Beginners: A Complete Guide to FTP Testing and Five-Zone Workout Design