The Garmin Fitness and Fatigue Chart, Explained

You opened Garmin Connect looking for the chart. The one with a slow blue fitness line, a spiky pink fatigue line, and a form line that dips when you are buried and rises when you taper. You saw it in a screenshot on a forum, you know it exists somewhere, and you cannot find it in your own account.

It is not there. Garmin has never shipped that chart.

What Garmin ships instead is the same underlying idea, broken into four separate readouts that live on different screens and never get drawn on top of each other: Acute Load, Load Ratio, Training Status, and Training Readiness. Each one is a partial view of fitness versus fatigue. None of them is the whole picture, and Garmin never assembles them for you.

This guide explains what each one is actually measuring, where Garmin's model differs from the classic fitness and fatigue curve, and how to read the four together so you get the same decision the chart would have given you.

The model everyone is looking for

The chart you are picturing is a Performance Management Chart, and the idea behind it is old. Banister and colleagues proposed the impulse-response model in 1975: every training session delivers a stimulus that produces two effects at once, a slow-building fitness effect and a fast-decaying fatigue effect. Performance at any moment is the difference between them.

Modern software implements that with two exponentially weighted moving averages of daily training load:

• Fitness, usually called CTL or Chronic Training Load, uses a 42-day time constant. It climbs slowly and falls slowly. It represents what you have banked.
• Fatigue, usually called ATL or Acute Training Load, uses a 7-day time constant. It spikes within days of a hard block and drains almost as fast.
• Form, or Training Stress Balance, is fitness minus fatigue. Negative means you are carrying more fatigue than your fitness base absorbs. Positive means you are fresh.

The reason athletes want this specific view is that it makes one decision obvious: whether the hole you are in is a productive one. Fitness rising while form sits at minus 15 is a healthy build. Fitness flat while form sits at minus 25 is just digging. You can read both in one glance, which is what makes the chart addictive. Our guide to Training Stress Score covers how the daily load numbers that feed this model are calculated in the first place.

Garmin measures training load too. It just does not express it this way.

What Garmin actually gives you

Garmin's performance metrics run on Firstbeat Analytics, the Finnish physiology company Garmin acquired in 2020. Firstbeat's model is built around EPOC, the excess post-exercise oxygen consumption a session produces, which is why Garmin's training load is in arbitrary units rather than TSS.

Here is the map from Garmin's language to the model above.

Acute Load

This is your fatigue line. Acute Load is an exponentially weighted sum of the training load from roughly your last 7 days, with recent sessions weighted more heavily than sessions from six days ago. Garmin displays it against a shaded optimal range rather than as a bare number.

Conceptually this is ATL under a different name and a different unit. It moves fast, it spikes after a hard weekend, and it falls within days of backing off.

Load Ratio

This is Garmin's substitute for the form line. On newer devices Garmin shows a Load Ratio: your acute load compared against a chronic load calculated over roughly 28 days.

This is the acute:chronic workload ratio, popularised for injury-risk monitoring by Tim Gabbett, whose 2016 paper in the British Journal of Sports Medicine framed the training-injury prevention paradox around it. The common reading is that a ratio between about 0.8 and 1.3 is a comfortable place to live, and that risk climbs meaningfully above about 1.5.

Two honest caveats before you treat that band as gospel. First, the ratio has been criticised hard in the literature. Impellizzeri and colleagues published a detailed critique in 2020 arguing that several of the ratio's conceptual and statistical foundations do not hold up, and that much of its apparent predictive power comes from acute load alone rather than from the ratio. Second, the ratio is genuinely noisy for athletes training fewer than about four days a week, because a single extra session moves the acute side sharply while the chronic side barely notices. Williams and colleagues proposed an exponentially weighted version in 2017 partly to reduce exactly that sensitivity.

So: useful as a spike detector, weak as a target.

Training Status

This is a label, not a measurement. Training Status is the output of the other metrics, not an independent signal. Garmin combines your acute load, your load ratio, your HRV Status and the direction of your VO2 max estimate, then picks one word.

The labels you will see, depending on device:

• Productive. Load is being maintained or built and your VO2 max estimate is trending up. This is the one you want during a build.
• Maintaining. Load is steady, fitness is holding. Correct during a maintenance phase, disappointing during a build.
• Peaking. Load has come down while fitness held. This is what a taper is supposed to produce.
• Recovery. Load has dropped substantially. Appropriate after a race or during a deload, concerning if you did not choose it.
• Unproductive. Load is being held or raised while VO2 max is flat or falling. Work going in, fitness not coming out.
• Overreaching. Acute load is well above your established chronic baseline. Fine for a planned overload week, a warning if it was accidental.
• Strained. Overreaching plus a recovery signal that has gone bad. Treat this as a stop sign.
• Detraining. You have been away long enough that the model expects fitness loss.

The single most useful thing to understand about Training Status is that a flip is never new information. It is a summary of things you could already see. When it goes Unproductive, the interesting question is which input caused it, and the answer is almost always in HRV Status or in a VO2 max estimate that a single bad-data run dragged down.

Training Readiness

This is a morning score, not a load metric. Training Readiness blends sleep from last night, sleep history over recent days, recovery time remaining, HRV Status, acute load and stress into a 0 to 100 number.

It is a genuinely useful score, and it is also the one people most often mistake for a competitor product's recovery score. It is not the same thing. Readiness already knows what you did yesterday, because acute load and recovery time are inputs. A recovery score built primarily from overnight physiology is closer to a pure readout of how your body responded. Neither is better. They answer different questions, and our WHOOP, Oura and Garmin comparison goes through where each one wins.

HRV Status

This is the recovery input the others depend on. Garmin measures heart rate variability overnight and compares your 7-day average against a personal baseline range it builds over about three weeks. The output is Balanced, Unbalanced, Low, or Poor.

This is the metric worth watching most closely, because it is the one that flips first. A build that is going wrong usually shows Unbalanced HRV a few days before Training Status admits anything is wrong. The mechanics of training off that signal are covered in our HRV-guided training guide.

Where Garmin and the classic chart disagree

The two models are not the same thing in different clothes. They disagree in three ways that matter.

Different time constants. Garmin's chronic window is about 28 days. The classic fitness line uses a 42-day constant. A 42-day fitness curve is deliberately sluggish, because the thing it is trying to model is a slow physiological adaptation. A 28-day chronic load reacts faster, which makes it better at catching a spike and worse at describing a season.

Different units. Garmin's load is EPOC-derived. TSS is threshold-derived, anchored so that one hour at your threshold equals 100. You cannot convert between them, and a number that looks alarming in one system may be unremarkable in the other.

Different memory. This is the big one. Garmin's model is built around what is happening now, so it does not keep much history. Training Status needs recent data to hold a label and typically resets after roughly two weeks without a synced activity, and Garmin's API exposes only about the last 30 days of history to any connected platform. That is a deliberate product decision, and it makes a native season-long fitness curve impossible.

That last constraint is worth sitting with, because it explains why almost everyone who wants a real fitness and fatigue chart ends up feeding Garmin data into something else. The watch is an excellent sensor. It is not an archive.

How to read the four together

Here is the practical translation. When you want the answer the chart would have given you, read the metrics in this order.

Start with the direction of your chronic load, not your acute load. Acute load is supposed to move around. What matters is whether your 28-day baseline is drifting up, flat, or falling over a month. Up during a build is correct. Flat during a build means you are training hard without training more, which is the most common way to plateau.

Then read the ratio as a spike detector only. If acute load has jumped well above the band, ask whether you chose that. A planned overload week producing Overreaching is the system working. An unplanned one is a scheduling problem.

Then check HRV Status as the veto. This is the input that tells you whether the load is being absorbed. Rising chronic load plus Balanced HRV is a build that is working. Rising chronic load plus Unbalanced HRV for more than a few days is a build that is about to cost you. The other signs of overtraining tend to show up in the same window.

Read Training Status last. It is a summary of the three you just read. If it says something you did not expect after reading them, the surprise is usually a VO2 max artifact rather than a physiological event.

Ignore single days entirely. Every one of these metrics is a rolling average with a long enough window that a single day cannot move it meaningfully. If a number changed overnight and you cannot name the session that did it, it is noise.

Filling the gap Garmin leaves

Garmin gives you a live snapshot with about a month of memory. The fitness and fatigue chart is a story that needs a season. That gap is the whole reason third-party platforms exist in this space.

AthleteData reads your Garmin activities, sleep, HRV, Body Battery and daily summaries over Garmin's official connection and keeps the history Garmin does not, then computes the classic model on top of it: a 42-day fitness constant, a 7-day fatigue constant, and form as the difference. It also runs the acute:chronic ratio in parallel, using the exponentially weighted variant for athletes who train fewer than four days a week, because the plain rolling-mean version is unreliable for them.

The part that matters more than the chart is what happens next. A number on a screen still leaves you to decide what to do about it. An AI coach that can see a chronic load flattening, an HRV baseline drifting down, and a race eight weeks out can say the specific thing: this week is the one to cut, and here is what to cut. If your training is spread across a Garmin watch, a gym app and a sleep tracker, that combined view is the thing no single device can build. Our Garmin AI coaching guide covers what the coach does with the data once it has it.

Putting it together: a Garmin fitness and fatigue protocol

1. Once a week, open Performance Stats and note your acute load and where it sits against the optimal range. Write it down, or let a platform store it. One number a week is enough.
2. Track the direction of your chronic load over a rolling month, not day to day. Up, flat, or down is the only resolution you need.
3. Aim to raise chronic load gradually. In TSS terms the common guideline is no more than about 5 to 7 points of fitness per week sustained. Garmin's units differ, so watch the shape of the curve rather than the absolute step.
4. Check HRV Status every morning. Treat two or more consecutive Unbalanced days during a build as a real signal, not noise.
5. When Training Status flips, do not react to the label. Find the input that moved it, then react to that.
6. Before a race, look for load coming down while fitness holds. Peaking is Garmin's way of saying your form line went positive.
7. If Training Status has been Unproductive for more than about two weeks with recovery signals intact, the problem is usually intensity distribution rather than volume. That is a deload decision or a plan restructure, not a "train harder" one.
8. Export or sync your history somewhere permanent. Anything you want to look at next season will be gone from Garmin by then.

Garmin already knows whether you are building fitness or burying yourself. It just tells you in four places at once, and never draws the line between them. Once you know which readout is the fitness line and which is the fatigue line, the chart is there. You are drawing it in your head.

Ready to see the full curve instead of a rolling 30-day window? Start a 7-day free trial and connect your Garmin in about a minute.