Guide
What a training streak actually measures
Streaks are the most motivating number on a training dashboard and the least informative. Knowing exactly what one counts tells you when to trust it — and when the calendar underneath it is telling you something the streak is hiding.
How the streak is counted
In Hevy Analyzer a streak is measured in weeks, not days. A week counts if it contains at least one workout, and the run is counted from the last completed week — so the week you are currently in never breaks it. Monday of a rest week is not a failure yet.
That is a deliberate choice. A daily streak punishes rest days, which are part of training, and it turns a deload week into a broken record. A weekly streak asks the only question that matters at this resolution: did you show up at all?
What it hides
Everything about the size of the week. One session every seven days keeps a streak alive indefinitely, and so does five. The number that separates them is sessions per week, averaged over a real window — 90 days is long enough to survive a holiday and short enough to reflect your current life.
- Two sessions a week for a year beats five sessions a week for six weeks and then nothing. The chart makes this obvious in a way memory does not.
- Distribution matters more than the total. Twelve sessions spread across four weeks is a program; twelve sessions in one week and none in three is an incident.
The calendar's honest edge
The heatmap covers up to 53 weeks, but it never starts before your oldest imported workout. Only the most recent 150 workouts are imported, so for a high-volume logger the window can be much shorter than a year — and if the grid started a year back regardless, every week before the import cap would be painted as "never trained". Blank because nothing was imported and blank because nothing happened are not the same fact, and a calendar that conflates them is worse than no calendar.
Using it
- Set a floor, not an optimum. "Two sessions, every week" survives a bad month. "Five sessions" does not, and the week it breaks is usually the week people stop entirely.
- Read the gaps, not the streak. The interesting part of the heatmap is where it goes empty and what was happening then — travel, injury, work. Those repeat, and they can be planned around.
- Check attendance before rewriting a program. Most stalled training is not a programming problem. Before you change anything, count the sessions you actually did against the sessions the program asked for — the gap is usually the whole story. See telling a plateau from noise.