Training streaks and consistency: how to count them without lying to yourself
Streaks motivate until they mislead. This guide gives a definition that counts what you actually planned and did, explains why today without a session yet should not break a run, and shows how Method computes activity, partial sessions, and streaks.
GuideUpdated 3 min readMarkdown version
Why most streaks mislead
A streak counter that ticks for any app open, or breaks the moment midnight passes without a workout, teaches the wrong lesson. It rewards logging over training and punishes sleep. Worse, it cannot tell a rest day from a skipped day, so a well-planned week with three sessions reads as four "misses".
A streak is only informative if three things are true. It counts something real, it respects the plan you actually had, and it does not break on a technicality.
A definition that holds up
Training day. A calendar day in your timezone with at least one completed session.
Streak. Consecutive training days. The current streak counts back from today. If today has no session yet, it does not break a streak that ran through yesterday; the day is still open. The longest streak is the longest run of training days in the window.
Day status. Each day is one of completed, partial, missed, or rest.
- Completed. At least one session finished as prescribed.
- Partial. A session was completed but an exercise fell short of its prescription. Cardio-only sessions are never partial.
- Missed. A session was planned for that day and none was completed. Only planned days can be missed.
- Rest. Nothing planned, nothing done.
When a day has more than one status, completed wins over partial, which wins over missed.
What "planned" means here
Missed depends on the plan. That is why a tracker needs the plan stored separately from the log; see planned vs completed. In Method, a session scheduled to a date is the plan. A day with no scheduled session is a rest day by definition, even if you usually train on that weekday. An ad hoc workout on a rest day is a training day, counted toward the streak, and never read as something you were supposed to do.
Window and weeks
Method's activity view covers the last 26 weeks. Weeks run Monday to Sunday in your timezone. The week view shows sessions per week; the day view is the heatmap of statuses above.
Workouts imported from Apple Health that you never opened Method to record, for example a walk from your watch, are in history but are not counted as app activity. That keeps the activity view about the training you logged against your plan.
Using it without being used by it
A streak is a description of the recent past. It says you trained on these days in a row. It does not say the training was good, and a streak that ends is not a failure; a planned deload week with two sessions is a good week with a short streak. Method shows the counts and the statuses and stops there. It does not send you a notification to keep a streak alive, and it does not score you.
Common questions
- How does Method define a streak?
- Consecutive training days. A training day is a calendar day in your timezone with at least one completed session. The current streak counts back from today, and a today with no session yet does not break a run that ended yesterday.
- Is a rest day a missed day?
- No. Missed applies only to days you actually planned a session and did not complete one. A day with nothing planned is a rest day, and it is never shown as missed.
- Does a partial session count?
- It counts as a training day. It is shown as partial, not completed, when an exercise fell short of its prescription. Cardio-only sessions are always complete.
- What window does Method show?
- Activity covers the last 26 weeks, in Monday-first weeks in your timezone, with a day-level view showing completed, partial, missed, and rest.
Try Method
Write your program on the web, log every set on iPhone, and keep the whole history in one place. Free to start.
Related reading
Planned vs completed training: why a tracker should never overwrite the plan with the log
A plan is an intention. A log is a fact. Trackers that overwrite one with the other lose the ability to tell you where you deviated. Method stores the prescription with every completed workout and keeps the two apart in history, analytics, and counts.
Muscle coverage with effective sets: how to count which muscles your training reached
Counting sets per muscle is only useful if the rule is stated. This guide gives the effective sets rule, explains why secondary muscles count half and why warm-ups count nothing, and shows how Method keeps every number decomposable.
How to program workouts in advance and log against the plan
Programming in advance means deciding the work before the day arrives so the gym is execution, not decision-making. This guide covers what to write down, how far ahead to plan, and how Method keeps the plan and the log connected.
Deload weeks: what they are, how to write one, and how they show up in your log
A deload is a planned easy week, not a missed week. This guide covers the common ways to write one, how to build it in a few edits in Method, and why a deload looks different from a skipped week in your history.
Method writes and maintains this page. Every statement about Method is checked against the shipped product. If something here is out of date, email contact@methodapp.net. For general references, link to the Method homepage.