Your training load can change without a new workout

Editorial analysis · Manufacturer documentation checked November 17, 2026

You did not train today. Your training-load number moved anyway. Before treating that as a failed sync, a sudden loss of fitness or an instruction to squeeze in a workout, ask a less dramatic question: what aged out of the calculation?

A rolling training-load number is partly a description of the calendar. It depends on which sessions still count, how much weight they receive and what history the app uses for comparison. Time can change all three without a new workout arriving.

That does not make training load useless. It makes the definition indispensable. The trouble begins when an app compresses a history-dependent estimate into a number that looks as direct as a stopwatch reading.

We checked current Apple, Garmin and Polar documentation and built two transparent numerical examples. We did not conduct a device experiment, reproduce a proprietary algorithm or test whether any load target prevents injury. The examples explain arithmetic; they do not prescribe training.

“Seven days” does not identify one calculation

Documentation-based field reference, checked November 17, 2026. These are not interchangeable units.
System and fieldDocumented basisTime contextLimit to keep visible
Apple Watch training load, watchOS 27 guideWorkout intensity and durationLast seven days compared with previous 28 daysDo not infer the complete weighting formula from this guide
Garmin acute load, current technology descriptionEstimated EPOC-based exercise loadActivity influence fades over ten days; total normalized to a seven-day windowOlder devices used a different seven-day total
Polar Strain and ToleranceDaily Cardio Load, expressed as TRIMPSeven-day and 28-day daily averagesCurrent status feedback uses more than their ratio alone

Sources: Apple's watchOS 27 guide, Garmin's training-load description, and Polar's Training Load Pro documentation. Availability and behavior depend on the device and software; this is not a compatibility list.

Garmin's distinction is particularly useful. Its current description says a new activity contributes fully, then its influence expires gradually over ten days. It contrasts this with older devices that simply combined the past seven days. Reading “weekly load” as “add up seven visible rows” can therefore produce a discrepancy before a single sensor error enters the picture.

A 40% drop with no deleted workout

Here is a deliberately simple model, not an Apple, Garmin or Polar output. We invent eight consecutive days with arbitrary load units: 100, 0, 50, 0, 50, 0, 50, 0. Each value is the total assigned to that day. The zeros mean known zero activity in this illustration, not missing observations.

Displayed daySeven-day windowSumDaily average
Day 7Days 1 through 7250 units35.71 units/day
Day 8Days 2 through 8150 units21.43 units/day

The rolling sum fell by 100, or 40%, because day 1 left the window and a zero entered. Every workout is still in the underlying history. The apparent collapse says nothing by itself about an overnight change in the person's body. It is exactly what this model was built to do.

A weighted system can make the same general phenomenon smoother: an older activity contributes less as it ages instead of disappearing at one boundary. That is a mathematical possibility, not our reconstruction of a vendor's undisclosed weights. We publish the simple model precisely because every step can be inspected.

The comparison can rise while today's load is zero

A relative value has a second moving part: its denominator. In a second hypothetical 29-day history, day 1 has 100 units, days 2 through 21 have zero, day 22 has zero, days 23 through 28 each have 50, and day 29 has zero.

On day 28, the seven-day total is 300 and the 28-day total is 400. Their daily averages are 42.857 and 14.286; the short-to-long average ratio is 3. On day 29, the short total stays 300, but the long total falls to 300 as the original 100-unit day leaves. The ratio rises to 4.

No new load was added. The recent window stayed constant. The comparison changed because the longer reference window lost a large day. These numbers are intentionally exaggerated to make the mechanism visible. They are not real training records, risk thresholds or a reason to increase or decrease exercise.

In both examples, interpreting the headline alone hides the cause. Keep the numerator, denominator and date range beside the ratio. If the longer average is zero, the ratio is undefined; a spreadsheet should not quietly replace it with zero or a comforting category.

Sometimes the label changes because the software did

Polar documents another complication: updated Cardio Load Status feedback considers absolute Strain and Tolerance and the preceding 14 days of status, rather than only their ratio. Some older watches still use the previous calculation, so their feedback can differ from current Flow feedback. Polar lists Flow 6.25.0 or later for iOS/Android and 7.25.0 or later for Huawei for the update.

That is a documented reason to record the app surface and version before comparing screenshots. A disagreement between a watch and a phone does not establish missing data. Conversely, a software explanation should not become an excuse to ignore an actually absent workout. Check the underlying record first.

Apple's guide also lets people filter training load by workout type and edit a workout's effort rating. Before comparing two views, confirm that they cover the same activities and that the inputs have not been edited. A comparison is only useful when its scope is stable.

An audit that starts with the history

Our proposed audit has four questions. Which field is displayed? Which dates and activity filters does it include? Did a workout arrive late or change? Did the app or device calculation change? Record the answers before deciding the chart is broken.

The distinction between a true zero and a missing session matters here. Our synthetic examples have complete histories. A real log may not. If a device was unworn or an activity failed to sync, you cannot assume its empty day means no exercise. Equally, finding the activity in the history does not prove it contributes to every derived metric.

A load chart should help you understand your record. It should not turn a declining line into a daily obligation to earn points. Whether to train depends on more than the arithmetic shown here; this article makes no individualized recommendation.

Inspect the definitions and reproduce the examples

Download the field dictionary, sourced JSON reference and complete synthetic daily records. The records include rolling totals, averages and ratios wherever a complete window exists. Blank means the full window is unavailable or the ratio is undefined, not zero.

For another metric whose definition travels badly, see why HRV numbers are not interchangeable. Vora's existing proactive AI brings wearable information together with nutrition and workouts for ongoing context. That does not make differently defined training-load scores convertible. Our product guides explain supported workflows without changing the definitions above.

Frequently Asked Questions

Why can training load fall on a rest day?

In rolling or weighted systems, older workouts can leave the window or lose influence. A decline can therefore occur without a deleted workout or a new training session.

Is Garmin acute load just the last seven days added together?

The current Garmin technology description says activity influence expires over ten days and the total is normalized to a seven-day window. It distinguishes this from older devices that used a simple seven-day total.

Why can Polar watch and Flow status feedback disagree?

Polar documents updated Flow feedback that considers absolute values and recent status history as well as the strain-to-tolerance ratio. Some older watches retain the previous calculation. Check the device and software version.

Are the downloadable load examples measured workouts?

No. They are invented daily values in arbitrary units, designed to isolate moving-window arithmetic. They do not reproduce vendor outputs or establish training or injury-risk thresholds.

Sources & References

  1. Apple. Training load, watchOS 27 guide
  2. Garmin. Current acute-load weighting description
  3. Polar. Training Load Pro and updated Flow feedback

All research discussed in this article is summarized in our own words. We link to original sources for full access. This content is for informational purposes and does not constitute medical advice.

Training loadGarminApple WatchPolarEditorial

Experience it yourself

AI-powered workouts, photo nutrition logging, HRV recovery tracking, voice coaching, and more - all free to start.

Related Articles

Wearables

Why your sleep trackers disagree about the same night

An 85 is not the same across Apple, Oura, WHOOP and Garmin. Compare what the scores mean, separate missing data from different definitions, and use a downloadable log to investigate your own nights.

Read more
Wearable Data

We analyze one million steps to find the best device.

1,024,917 manually counted steps across 293 public reports. Explore the device counts, walking rankings and every original test.

Read more
Health Data

An Export button does not prove you can move your health history

Apple, Garmin and Oura offer different export routes. This dated reference separates summaries, archives and untested migration claims, with an audit worksheet.

Read more