It is 6:40 a.m. in a hotel room in Lisbon. You have been awake, on and off, since roughly 3. You lay very still in the dark, doing the arithmetic of how many hours remain until the meeting. Then you pick up your phone, and the app tells you that you slept seven hours and eleven minutes. Sleep score: 78. "Good."

You do not feel good. You feel like someone has replaced your head with wet sand. And now there is a second, quieter problem on top of the first: the number says you are fine, so maybe the exhaustion is a personal failing.

It isn't. The tracker is not lying out of malice. It is answering a different question from the one your body is asking.

What your wrist can and can't see

Most consumer wearables estimate sleep from two things: movement and heart rate, sometimes with skin temperature and blood oxygen added. From those signals, an algorithm guesses when you were asleep and what stage you were in.

The research on this is fairly consistent in outline. Devices of this kind are decent at detecting that you are asleep versus awake across a whole night, and noticeably weaker at sorting light, deep and REM sleep. They also tend to be better at recognizing sleep than recognizing wakefulness. Someone lying motionless and awake can look, to a movement-based algorithm, a lot like someone asleep.

Now think about what jet lag does to a night. The classic pattern is not thrashing around. It is lying quietly, eyes closed or half open, mind running, for long stretches, which is exactly the behavior these devices are most likely to over-count as sleep.

So the tracker's seven hours may include a long stretch of still, awake, resentful lying-in-bed. The device has no way of knowing that your brain was not doing the thing the rest of your body appeared to be doing.

The deeper problem: it measures the night, not the clock

Jet lag is not mainly a shortage of sleep. It is a mismatch of timing. Your internal circadian clock, driven by a cluster of neurons in the hypothalamus, is still running on the schedule of the city you left. Light is the main signal that resets it, and it resets slowly, on the order of an hour or so per day depending on direction and exposure.

A tracker scores the hours it labels as sleep inside a window. It does not know that, to your clock, 2 a.m. in Lisbon is still evening in New York. Your body's alertness rhythm, your core temperature rhythm and your melatonin rhythm are all pointing the wrong way, and a sleep score has no column for that.

This is why you can post a respectable score and still feel the signature symptoms: the midmorning crash, the 3 p.m. fog, the strange wired feeling at midnight. Sleep duration and circadian alignment are separate things, and the app mostly reports the first. (If that distinction is new to you, it is the same one behind feeling tired even after a long sleep: sleep pressure and clock timing are two different dials.)

Why your readiness score tanks anyway

There's an opposite failure too. Plenty of people notice that their recovery or readiness score collapses after a trip, even on a night the sleep graph looks fine.

Many of these scores lean on resting heart rate and heart rate variability (HRV), compared against your personal baseline. Both of these are known to follow circadian patterns, and both are sensitive to things travel piles on at once: disrupted sleep timing, dehydration, alcohol, a heavy late meal, cabin conditions, stress, cramped sitting for hours. When several of those land together, your overnight heart rate can run higher and your HRV lower than usual, and the score drops.

That drop may be a real physiological signal, or it may simply be the algorithm noticing that you are off your normal pattern. The honest reading is: it reflects strain, but it is not a precise measure of how impaired you are, and it is not a verdict on you.

The hidden trap: the baseline is wrong

A tracker learns what "normal" looks like for you from your recent weeks. In a new time zone, your normal is temporarily meaningless.

Three things commonly go wrong:

  • The device's clock lags your location. If the phone or watch hasn't updated its time zone cleanly, sleep windows and daily summaries can be cut at the wrong hour, splitting one night into two odd fragments.
  • Auto-detected sleep misses your new schedule. Algorithms often look for sleep in a habitual window. A 4 a.m. to noon sleep can get chopped, or a daytime nap can be filed as the main sleep.
  • Comparisons are against home. Your "average bedtime" is suddenly eight hours off, so every trend line looks like a crisis.

None of this means the hardware is broken. It means the interpretation layer was built for people whose clocks stay put.

Use the tracker for timing, not for the grade

Here is the more useful way to read your wearable while your clock is moving: stop looking at the score and look at the timing.

Overnight heart rate tends to dip to its lowest point in the second half of a normal sleep period, and that low sits fairly close to the low point of your core body temperature rhythm. So when your lowest heart rate of the night lands, compared with your usual, gives you a rough, imperfect hint about where your clock currently is. If your lowest reading is happening at what feels like the middle of the afternoon in your new time zone, your clock is still largely on home time.

Treat that as a clue rather than a measurement. It is nowhere near as precise as lab methods for finding circadian phase. But it is a lot more informative than a single number out of 100, and it turns a gadget that was making you feel worse into one that tells you whether the plan is working.

Your next moves

  • Fix the time zone first. On arrival, make sure your phone, watch and app have all switched to local time. Then check that last night's sleep wasn't cut into odd pieces.
  • Ignore the sleep score for the first three days. Write down two things yourself each morning: roughly when you fell asleep and how alert you felt at 10 a.m. and 3 p.m. Those are closer to what jet lag actually changes.
  • Look for your lowest heart rate time. Note when your overnight low occurs each day. Over several days you should see it creep toward your local night. Stalling means you probably need more morning or evening light timed correctly for your direction of travel.
  • Distrust "still, so asleep." If you lay awake for a stretch, mentally subtract it from the tracker's total. Tell yourself the real figure is lower, and plan your caffeine and nap decisions around how you feel rather than the figure.
  • Hold off on judging recovery metrics until the baseline resets. Give it roughly a day per time zone crossed, then compare. Don't change your whole routine because of one bad readiness number.

Where a plan beats a graph

A tracker looks backward. It tells you, with some error, what your last night looked like. Jet lag is a forward-looking problem: when to seek light, when to avoid it, when to take a small dose of melatonin, when the last coffee should be. That's the part Meridian is built around. It builds a personalized light, melatonin, caffeine and meal schedule for your specific trip, and it works fully offline, so it still functions on the plane or somewhere with no signal. Use your wearable if it helps you notice patterns, and let the plan do the steering. If you'd like to try it, it's at meridian.lumenlabs.works.