Your Garmin Knows You're Dehydrated. It Just Can't Tell You.

You wake up. Check your watch. Recovery score: poor. HRV tanked overnight. Resting heart rate up 6 beats from your baseline.

You didn’t drink last night. You slept eight hours. You took a rest day. So what happened?

Scroll through r/Garmin or r/whoop on any given week and you’ll find this exact post. Sometimes it’s titled “Why is my Body Battery so low?” Sometimes it’s “HRV crashed for no reason.” The comments are always a mix of speculation. Stress? Overtraining? Coming down with something?

And then, buried in the replies, someone asks: “How much water did you drink yesterday?”

That’s usually it. That’s the whole mystery.

The physiology is not subtle

Dehydration does specific, measurable things to your cardiovascular system. This is not fringe science. It’s exercise physiology 101, backed by decades of research.

When you lose roughly 2% of your body mass through fluid loss (that’s about 1.5 litres for an 80kg athlete), your blood plasma volume drops. Less plasma means less blood volume per heartbeat. Your heart compensates by beating faster to maintain the same cardiac output. Resting heart rate climbs 5 to 8 bpm. Sometimes more.

At the same time, your autonomic nervous system shifts. The sympathetic branch (your fight or flight system) ramps up to manage the reduced blood volume. The parasympathetic branch (rest and digest) pulls back. The result? Heart rate variability drops. Typically 10 to 15%, but in moderate dehydration it can fall further.

Your watch captures every single one of these changes. It tracks your resting heart rate to the beat. It measures HRV down to the millisecond. It logs skin temperature, respiratory rate, and sleep quality. All of these shift with dehydration.

And then it tells you: “Your recovery is low.”

No context. No cause. Just a colour on a screen.

Reddit figured this out years ago

There’s a post on r/whoop from an endurance runner who noticed a pattern over several months. Every time their WHOOP recovery dropped below 40% without an obvious reason (no alcohol, no bad sleep, no illness) they went back through their day and found the same thing. They’d been busy at work, skipped their water bottle, and only had coffee.

Another poster on r/Garmin tracked their Body Battery alongside a simple hydration log for six weeks. The correlation was, in their words, “almost creepy.” Low water days consistently preceded low Body Battery mornings, even when sleep and activity were normal.

These aren’t isolated anecdotes. Search “dehydration HRV” on any fitness subreddit and you’ll find dozens of similar stories. Athletes connecting dots that their $500 wearable refuses to connect.

One r/Garmin user put it perfectly: “My watch knows more about my body than my doctor does. But it can’t tell me to drink water.”

Why wearables won’t do this

It’s not a sensor problem. Your watch already has everything it needs.

The issue is that consumer wearables are built around single metric reporting. Garmin shows you Body Battery. WHOOP shows you Recovery. Oura shows you Readiness. Each of these is a composite score derived from multiple inputs, but the output is always one number, one colour, one vague verdict.

What none of them do is pattern recognition across metrics over time. They don’t say “your resting heart rate has been elevated for two days while your HRV is suppressed and your skin temperature is slightly up, which is consistent with mild dehydration.” They can’t, because their software isn’t built to synthesise signals into causes. It’s built to report signals as scores.

There’s also a liability angle. The moment a consumer device starts saying “you’re dehydrated,” it crosses from wellness tracking into something that looks like medical advice. That’s a regulatory minefield. So instead, you get traffic light colours and motivational nudges. Safe. Useless for anyone trying to actually optimise.

The cost of not knowing

Here’s where it gets expensive in performance terms.

A 2% fluid deficit doesn’t just mess with your watch metrics. It degrades endurance performance by 10 to 20%. That’s not a marginal difference. For a runner doing a half marathon at 1:45 pace, that’s the difference between hitting their target and blowing up at kilometre 15.

Reaction time suffers. Cognitive function drops. Perceived exertion goes up, meaning the same workout feels significantly harder than it should. You push through it because your watch says you slept well and your training load is fine. But you’re grinding through a session your body isn’t equipped to handle because you’re down a litre of fluid.

And the cruel part? Most athletes don’t feel thirsty until they’re already at that 2% deficit. Thirst is a lagging indicator. By the time you want water, the damage to your session is already baked in.

This is exactly the kind of thing a wearable should catch. Not after the fact, but before your morning workout. “Based on your overnight metrics, you may be under-hydrated. Consider increasing fluid intake before training.”

No wearable does this.

The pattern is obvious once you see it

Here’s what dehydration looks like in your data, laid out plainly:

Resting heart rate: Elevated 5 to 8 bpm above your personal baseline, persisting through sleep.

HRV: Suppressed 10 to 15% below baseline, particularly the RMSSD metric that reflects parasympathetic activity.

Skin temperature: Slightly elevated (your body is worse at thermoregulation when dehydrated).

Sleep quality: Fragmented. Dehydration increases overnight cortisol, which disrupts deep sleep phases.

Recovery score: Low, with no corresponding training load explanation.

Each of these alone could mean a dozen things. Together, in combination, they point strongly in one direction.

But “together, in combination” is the part that requires synthesis. And synthesis is exactly what current wearables don’t do.

What athletes actually want

Talk to serious athletes (or just read their forums) and the frustration is consistent. They don’t want more data. They have plenty of data. What they want is someone, or something, to look at all of it and tell them what it means.

Not “your recovery is 43%.” Tell me why it’s 43%. Is it because I trained too hard yesterday? Is it because I had two beers? Is it because I sat in a conference room for 9 hours and drank nothing but coffee?

The answer matters because the response is completely different. If you’re under-recovered from training, you back off. If you’re dehydrated, you drink a litre of water and electrolytes and you’re fine to train. Same recovery score, opposite action required.

This is the gap. Not in data collection (wearables are excellent at that) but in data interpretation. The synthesis layer between raw metrics and actionable insight.

Where P247 fits

This is the problem P247 is built to solve.

Not by adding more sensors or inventing new metrics, but by connecting the signals that already exist. Your resting heart rate, HRV, sleep architecture, training load, and recovery trends all tell a story when you read them together. Dehydration is one chapter. Overtraining is another. Accumulated fatigue, illness onset, nutritional deficits: they all have signatures in the data your watch already collects.

The value isn’t in the data. It’s in the layer that reads it.

Your Garmin knows you’re dehydrated. P247 is building the system that can actually tell you.