I Started Logging When I Actually Fell Asleep, Not When I Got Into Bed
There's a version of the sleep problem invisible in most tracking: not when you tried to sleep — when you actually did. I measured it for 30 days with a notepad. What I found was stranger than I expected.
In this article5 sections
The sleep app on my phone said “bedtime: 10:45 PM.” That’s what I’d been tracking for three years — the time I plugged in my phone, turned off the lamp, and declared the day over. The app rendered it as a bar chart. The chart looked fine.
The problem: I was in bed at 10:45 and asleep sometime around midnight. This gap had been real for most of my adult life and I’d never measured it.
A colleague in behavioral research mentioned, almost as an aside, that “bed time” and “sleep onset time” are two completely different variables, and that most consumer sleep apps conflate them. “Your app knows when you stopped scrolling,” she said. “It doesn’t know when you stopped being awake.”
She was right. I’d been tracking the wrong thing.
The Setup
For 30 days, starting on a random Tuesday in November, I kept a small paper notebook on my nightstand. One column: last remembered time. Every morning, before doing anything else, I wrote down the last clock time I remembered checking the previous night — not how I felt, not a score, just the time.
The method has real limits. Memory encoding for time isn’t reliable when you’re drowsy. It’s a proxy, not a measurement. But for revealing patterns across 30 nights, it’s directionally accurate and costs nothing.
What I expected: a 15–20 minute gap most nights, with occasional outliers on stressed evenings.
What I found: my average gap was 43 minutes.
Week One: The Size of the Gap
On six of the first nine nights, the gap exceeded 40 minutes. On two nights it was over an hour.
My first instinct was to pathologize this — sleep onset over 30 minutes is one marker sleep researchers use for insomnia screening. But it’s a probabilistic flag, not a diagnosis. High sleep onset latency is also associated with anxious personality traits entirely separate from sleep disorders. And it’s associated with a brain still running active processes from the day — something almost anyone would recognize.
What stopped me cold wasn’t the number itself. It was how surprised I was by it. Three years of tracking had produced a narrative about my sleep that had no 43-minute lying-awake phase in it. The narrative was wrong, and the app hadn’t contradicted it because the app was measuring something else.
Week Two: The Pattern Inside the Number
By the second week I’d noticed that the gap wasn’t random. It tracked something more specific than how tired I felt.
The shortest gaps — under 20 minutes — consistently followed evenings with physical activity and dinner before 7 PM. The longest gaps — over 50 minutes — were almost always preceded by the same combination: a late meal and a cognitively demanding task in the two hours before bed.
This has a name. Morin, Stone, Trinkle, Mercer, and Remsberg (1993, Journal of Consulting and Clinical Psychology) documented the relationship between pre-sleep cognitive arousal and sleep onset latency across both insomniac and non-insomniac populations. Active problem-solving, worry, and goal-directed thinking while lying in bed produce sympathetic nervous system activation that conflicts with the arousal threshold drop required for sleep onset. The finding has been replicated extensively.
What I found wasn’t new science. It was confirmation that a well-documented phenomenon was operating in my specific life on specific nights — information my sleep score was actively hiding by averaging over it.
Week Three: An Accidental Reduction
On day 18, partly out of curiosity, I tried a technique called a cognitive shuffle — developed by Luc Beaulieu-Prévost at the Université du Québec à Montréal as a pre-sleep imagery exercise for disrupting ruminative thought chains.
The method: choose a random word, visualize a disconnected image for each letter, then move to another random word. The goal is to occupy the brain’s default mode with something sufficiently meaningless to prevent it from chaining back to real problems. Trivial enough that it can’t sustain goal-directed thought, structured enough that attention doesn’t snap back immediately.
On the seven nights I used it in the final 12 days, my average gap was 19 minutes. On the five nights I didn’t, 47 minutes.
I can’t call this a controlled experiment. I probably used the technique on calmer nights. The sample is small and placebo effects in cognitive sleep interventions are a genuine confound. I noted all of this in the notebook.
What I can say: the signal was strong enough that I continued the technique two months past the end of the 30-day window, and the notebook data shows sustained shorter gaps on nights I use it.
What Changed
I no longer log my sleep score. I log the gap.
The gap tells me something the score doesn’t: whether I was actually asleep or just horizontal in the dark, performing the rituals of sleep without arriving at it. A 7.5-hour bar on a chart covers both. The gap reveals the difference.
More practically: the gap led me to identify a specific behavior — cognitively demanding late-evening work — that I now treat as a direct tradeoff. I understood intellectually that “winding down before bed is good.” I didn’t feel the cost clearly enough to act on it until I watched it appear 30 times in a handwritten column.
The app wasn’t tracking the thing that mattered. I had to track it myself, with a $2 notebook, to find out.
There’s no product I’d recommend here. If you’re routinely exhausted despite what looks like adequate sleep and you want a structured set of explanations to work through, this FAQ covers the most common causes — high and unnoticed sleep onset latency is one of them.
See also: Sleep latency explained · What sleep trackers genuinely cannot tell you