Your Watch Knows You're a Woman. It Just Doesn't Know What to Do About It.

Your watch knows exactly what sex you are. You told it on day one, during setup, right between your age, height, and weight. The problem isn't ignorance. The problem is that it knows, and it has no idea what to do with that knowledge.

What the score can't see

Open your readiness app and look for a place to tell it your hormonal status. Your cycle phase, perimenopause, the contraceptive pill, pregnancy, the months afterwards when everything is recalibrating week by week.

It isn't there. Your sex sits in the settings as a fixed label, and underneath, the algorithm quietly assumes a hormonally steady human — the same baseline logic applied every single day of the month.

I don't say this to dismiss the score. Learning your personal baseline — your normal, not a generic chart's — is genuinely useful, especially somewhere between 35 and 55, when temperature and resting heart rate start moving for reasons nobody explained to you. A number that knows your normal beats any population average. The problem is only that "your normal" isn't one thing across the month, and the score doesn't know that.

What a normal luteal phase looks like to your score

After ovulation, progesterone does a set of entirely ordinary things: your resting heart rate rises a few beats per minute, your basal temperature ticks up, your breathing quickens slightly, and your HRV — heart rate variability, the tiny variations between heartbeats that reflect how recovered your nervous system is — dips by 10 to 20 percent compared to your follicular baseline.

None of this is dysfunction. It's your body doing exactly what the second half of the cycle is supposed to do.

But the score knows only one story for "heart rate up, HRV down, temperature up," and that story is: take it easy today. It isn't wrong about the numbers. It's just missing the context that would change what the numbers mean — the way a sentence changes meaning when you finally hear the tone it was said in.

It's not the sensors — it's the interpretation

The sensors deserve credit here. They pick up shifts of a fraction of a degree while you sleep; the measurement side of this industry is remarkable. What's missing is the reading of the measurement — interpretation that includes your hormonal reality as a matter of course, not as an edge case.

This is the same gap Eric Topol, the cardiologist, pointed at recently: the data behind wearable scores is impressive, yet nobody has shown that following the score actually makes people healthier. I suspect part of the reason is this — a score can't refine your judgment about something it can't see. And right now, it can't see the hormonal half of your physiology.

Where I land

I keep coming back to the same middle ground I found when writing about this before. Listening to yourself is a skill worth having, with or without a device — most of us spent years overriding what we felt because a plan or an app said otherwise. And the numbers are genuinely good at catching what feelings miss: the slow drift, the pattern across weeks, the fatigue you talked yourself out of noticing.

Neither replaces the other. The morning decision gets better when the check-in and the data are read together, in plain language — with hormonal context treated as a first-class input, not an afterthought. That's the gap I'm building Pace & Phase around: not more sensors, but interpretation that knows what your hormones are doing.

A number becomes truly useful when it's read with context, and hormonal context is the part we're still waiting for.