Training & Nutrition · Sep 3, 2026

Your HRV dropped. Should you train today?

One low morning is almost never a reason to skip. What HRV actually measures, the causes worth naming before you touch your program, and a five-case rule for how much of the session to keep.

Short answer

Should you train if your HRV is low? Usually yes, with the intensity lowered rather than the session cancelled. A single low morning — especially the day after a hard session, a short night or a drink — describes what happened to you last night rather than predicting what you can do today. The readings worth acting on are patterns: three or more mornings below your own baseline, particularly alongside a resting heart rate drifting upward.

What counts as a low HRV reading? Only what is low relative to your own baseline. Healthy adults range from the twenties to over a hundred and fifty milliseconds and values fall with age, so there is no universal threshold and no useful comparison to another person. Most systems compare this morning against a rolling week and that week against one to two months, which means a new device needs two to four weeks of your own data before the word low carries any information.

Why did my HRV drop even though I slept well? Sleep is one of several inputs. Alcohol the previous evening, and often the evening before that, is one of the largest single-night effects. A hard session in the last 24 hours, a large or late meal, a hot room, dehydration, travel, altitude and ordinary psychological stress all suppress it. So does an inconsistent measurement: a nap or a mid-afternoon spot check is not comparable to an overnight or on-waking reading.

Does a hard workout lower HRV the next day? Yes, and that is the expected response rather than a warning. The dip reflects the load you deliberately applied, and it typically moves back toward baseline within a day or two without any change to the plan. Backing off training because of it interrupts the block for no reason.

How many days of low HRV should you take seriously? Three or more consecutive mornings below baseline with no cause you can name is the point to cut load by roughly a quarter and look at sleep and food before changing the program. A week or more of suppression is a signal about the training block rather than about any single day, and is better answered with a planned deload than with five separate daily decisions.

Does high HRV mean you should train harder? No. Treat a strong reading as permission to run the plan as written, not as a reason to add volume, extend the session or delay a planned deload. A high reading can also follow a draining day or a large carbohydrate meal rather than indicate unusual freshness, and the plan already accounts for progression in a way a wearable cannot.

The short version, before the explanation

A single low HRV morning, on its own, is almost never a reason to cancel a session. It is a reason to ask why it is low — and the answer is usually available before you open the app. Alcohol, a short night, a genuinely hard session yesterday, a late meal, a warm room, a stressful day. Once you can name the cause, you are no longer looking at a readiness signal. You are looking at a description of last night.

The readings worth acting on are patterns, not days. Three or more mornings sitting below your own baseline, particularly alongside a resting heart rate that is drifting upward, is a different thing from one dip in an otherwise normal week.

And in most cases the useful decision is not train or rest. It is how much of today's session survives.

What the number actually measures

Your heart does not beat like a metronome. The gap between one beat and the next varies by milliseconds, and heart rate variability is a measure of that variation. It reflects how much your parasympathetic nervous system — the rest-and-recover side — is influencing your heart rate at the moment of measurement.

Most wearables report it either as RMSSD in milliseconds, which is a real physiological measure, or as a score out of 100, which is that measure rescaled against your own history. The score is not comparable between people or between brands. Two devices on the same wrist on the same night will not agree on the score, and often will not agree closely on the milliseconds either.

Because HRV tracks the balance between the stress and recovery sides of your nervous system, it responds to anything that loads either one: training, sleep, alcohol, illness, heat, altitude, a difficult week at work. That breadth is exactly what makes it useful, and exactly what makes a single reading ambiguous. It tells you something changed. It does not tell you what changed, and it does not tell you what to do about it.

Your number only means something next to your own number

There is no good HRV. Healthy adults sit anywhere from the twenties to well over a hundred and fifty milliseconds, and values fall with age. Two people can be equally fit, equally recovered, and forty milliseconds apart. Comparing your reading to a friend's, or to a number you saw quoted online, tells you nothing at all.

What means something is your reading against your own recent baseline. Most systems compare this morning against a rolling week, and that week against a longer window of one to two months. A reading is low when it is low for you, this month.

This is why a new device is not useful on the first day. It needs two to four weeks of your own data before the word low has any content in it. Treating day-three readings as guidance is reading noise.

One condition gets ignored more than any other: comparability. The measurement has to be taken the same way each time — overnight, or first thing on waking before you sit up — on the same device. A nap reading, a mid-afternoon spot check, or a morning where you got up to let the dog out first are not the same measurement, and the difference between them is often bigger than the difference you are trying to interpret.

Causes worth naming before you treat it as a training signal

Before a low morning becomes a decision about your program, check whether you can already explain it. Most of the time you can, in about five seconds.

If one of those explains the reading, you have your answer. The number is describing what happened to you, not predicting what you can do.

Alcohol — one of the largest and most repeatable single-night effects there is, and it frequently carries into a second night.
Short or broken sleep, and going to bed much later than usual even when the total hours look fine.
A genuinely hard session in the last 24 hours. This one is the training working, not a warning.
The first hours of an illness, often before you feel anything.
A large or late meal close to bedtime.
Dehydration, a hot room, or a hot day.
Travel, especially crossing time zones or sleeping at altitude.
Ordinary psychological stress — a deadline, a hard conversation, a bad night with a small child.

A decision rule you can run in thirty seconds

Five situations cover almost every low morning. The response is different in each, and only one of them ends with not training.

One low morning, the day after a hard session

Train as planned. A dip following real work is the expected response to that work — the same physiological signal that eventually produces the adaptation you trained for. It typically returns toward baseline within a day or two on its own. Backing off here interrupts the block for no reason.

One low morning with an obvious cause

Train, but lower the ceiling. Keep the session, the exercises and the slot in the week; take out the heaviest work. Cap effort somewhere around an RPE of 7 — every set stopped with two good reps still in reserve — and drop the top set entirely. You keep the movement, the skill and the habit, and most of the training stimulus, for a fraction of the recovery cost.

Two or three low mornings with no obvious cause

Keep training, cut the load by roughly a quarter, and look at your inputs before you look at your program. Multi-day suppression in people who are not full-time athletes is far more often accumulated sleep debt or simply eating too little than it is overtraining. Fixing sleep and food resolves more of these than any programming change will.

Low HRV alongside a rising resting heart rate and symptoms

This is the one case worth obeying outright. Illness tends to announce itself in this combination — HRV down, resting heart rate up, sleep worse, sore throat or heaviness in the limbs — sometimes a day before you would otherwise notice. Training hard through it does not just produce a poor session; it reliably extends the whole thing. Rest, and treat the next day as a fresh reading rather than a plan.

A week or more below baseline

This has stopped being a today question. Suppression that persists across one to two weeks is a signal about the block you are in, not about Tuesday. That is a deload conversation — a planned week at reduced volume and intensity — rather than five separate daily decisions made under a cloud.

When you keep the session, change the ceiling and not the shape

The common instinct on a bad-recovery morning is to swap the session for something gentler: a walk instead of squats, a class instead of the lifting day. That is usually the wrong edit, and it is worth understanding why.

Intensity is what costs recovery. Doing the movement is what preserves the skill, the habit and the structure of the week. So the edit that gives back the most recovery for the least loss is to keep the shape of the session and lower its ceiling — not to replace it with something unrelated.

Concretely: same warm-up, same lifts, same slot in the week. Drop the top set. Hold every working set at a weight you could manage two more reps with. Cut the last accessory block if you are still flat by then. A session at seventy percent, finished, is worth considerably more over a training block than a perfect session skipped.

This is also the honest reason we push back on skipping. The cost of a missed session is rarely the missed session. It is that the week loses its shape, and the next one starts from a worse place.

The mistake in the other direction

A high reading is not a green light to add work. It is common to see someone take a strong HRV morning as permission to extend the session, add a fourth hard day, or push a planned deload back a week — and then find the following fortnight harder than it should be.

A very high reading can also follow a genuinely draining day, or a large carbohydrate meal the night before, rather than indicating unusual freshness. Treat a good number as permission to run the plan as written. The plan already accounts for progression; the watch does not know what the plan is.

What HRV cannot tell you

The limits here are not a caveat at the end. They are the reason the number needs a plan around it to be useful at all.

Which is why a recovery score belongs among the inputs to a decision, and not in the seat where the decision gets made.

It cannot separate stress from training from stress from everything else in your life.
It cannot tell you which session to change, or by how much.
It does not measure fitness, and it does not go up because you trained well.
It says nothing about whether you are injured, which is the signal that should actually stop a session.
It does not know what week of your block this is, or what the plan is building towards.

How CoachArc treats a low reading

A recovery signal is one input, weighed against what you actually completed in the last two weeks, what the current block is building towards, and how close the next planned deload is. A single low morning in an otherwise consistent fortnight moves very little. The same reading in the third hard week of a block, after two sessions you finished early, means something quite different.

Any change to the plan is proposed and shown to you before it applies. You see what is being cut and why, and nothing moves in your week until you say yes. A coaching system that quietly rewrites your Tuesday because a wearable had an opinion is not coaching; it is guessing on your behalf.

Where this stops being a training question

HRV on a consumer wearable is a wellness metric, not a diagnostic one. It is not validated to detect or rule out anything, and neither we nor your watch can interpret it clinically.

Persistent unexplained suppression, a resting heart rate well above your normal without a reason, palpitations, chest pain, breathlessness, fainting, or feeling unwell in a way that does not resolve — those are conversations to have with a doctor, and they are worth having promptly. They are not training questions, and no amount of adjusting your sets and reps is the right response to them.

Everything above is about the training lever a signal points at. What the signal means for your health is your provider's call, not an app's.

How CoachArc uses this idea

CoachArc is built around practical, adaptive coaching: what to do today, what changed, and how to keep momentum without turning a missed day or imperfect meal into a restart.

It connects today's plan, food guidance, progress, and Hey Coach so you review a recommendation and apply it only when it makes sense. It reads the health data you choose to share — body-composition scans, blood panels, and wearable recovery — and proposes the change it wants to make.

See everything CoachArc does, how it compares to trackers and generic AI, or what it costs.