Skip to main content

Training Load

What it is. Accumulated training stress, following the published load models. It rises with hard sessions and decays with rest. How to read it. The number alone means little; the shape over weeks means a lot. A load climbing steadily is training. A load spiking is a week you may pay for. What it needs. Recorded sessions with heart rate.

Activity Units

What it is. Effort, normalised so that different activities compare sensibly. A hard swim and a hard run should produce similar Activity Units even though the raw numbers look nothing alike. Why it exists. Because “minutes of exercise” treats a gentle walk and a hill sprint as equals, and calories flatter whoever is heaviest. Activity Units try to measure the thing you actually did. This is one of the four engines we are still tuning. If yours produces something that feels obviously wrong for a session, that is a genuinely useful thing to report.

Steps

What it is. Steps, from whichever source you nominated as Primary. One thing to know. If you carry a phone and wear a watch, both count. Which one the app uses depends on your Primary source — see several wearables through one hub. If your step count looks wrong, that is the usual reason.

Active Calories

What it is. Calories burned by moving, above what your body would have used anyway. A caveat. Every wearable estimates this, and they disagree substantially. Read your own trend; do not compare with a friend’s watch.

Calories Goal

What it is. How much you should be eating, given your body and your activity. And this one changes character depending on what you give it:
This is the card that rewards logging most. Without nutrition it is a textbook formula describing a statistical average — not wrong, but not about you. With a few weeks of food logged it becomes genuinely personal.See What each number needs.