TimeMap

TimeMap / Guides

Should you log how many hours you slept?

You open the log first thing in the morning, ready to write the day's first line, and the number arrives before anything else does: seven and a half hours, or five, or some rough guess based on when you remember the room going dark. It feels like it belongs at the top of the day, the way a weather report belongs at the top of the news. But a log built around short lines about what you were doing does not obviously have a place for a span of time you spent unconscious, and the question of whether to write the number down at all turns out to be less obvious than it looks.

Sleep is the one thing in your day that is actually a duration

Almost everything else worth logging is a moment: you sat down to write, someone called, you left for the gym. Even a long stretch of work gets logged as an event — started the proposal — not as a count of minutes. Sleep does not work that way. Nobody experiences eleven consecutive hours of unconsciousness as a moment; the only honest way to describe it after the fact is as a span, measured from one clock reading to another. That makes it the single entry in a day most naturally suited to a number, in a log that is otherwise not built around numbers at all. The friction you feel writing it down is not a flaw in you — it is one real duration trying to fit into a format built for instants.

What the number actually buys you

Write "7.5 hours" every morning for a month and reread it later, and it reads less like a memory and more like a spreadsheet column you forgot to graph. A string of numbers does not tell you why one night was short or what the short night did to the day that followed — it just tells you that a number went down. If you are already wearing something that tracks sleep automatically, that number exists somewhere more accurate than your morning guess anyway, and a log competing with a wearable to store the same figure is a log doing a job something else already does better.

What a log is actually good at instead

What a log can capture that a sleep graph cannot is everything around the number: up twice for the dog, back asleep fast both times, or couldn't switch off after the argument, gave up and read until 2, or best night in weeks, woke up before the alarm for once. None of those lines require you to know the exact hour count, and all of them are more useful to reread in six months than a column of decimals would be, because they say what actually happened rather than how long it took. A bad night with a reason attached is a more useful entry than a good number with none.

When the number is worth keeping anyway

None of this means never write a number down. If a night was rough enough that the hour count is the point — up until 4, brutal — including it makes the line more specific, not less, in the same way naming a place or a person does. The difference is between a number that shows up occasionally, attached to a night worth remarking on, and a number that shows up every single morning as a category you feel obligated to fill in whether or not last night had anything worth saying about it. One is a detail. The other is a metric you have quietly agreed to keep, and a log was never meant to collect metrics.

Treat waking up like any other moment

The simplest way through this is to stop treating sleep as a special category that needs its own rule, and log it the way you would log anything else: only when there is something worth a line. Most mornings that means skipping it entirely and writing about whatever comes next instead. Some mornings it means one sentence about how you woke up and why. Either way, the log stays a record of what your days were actually like, not a running tally of how many hours you managed to close your eyes.

About TimeMap

TimeMap does not have a sleep category with a target to hit or a total to watch — there is no running number anywhere in it, because duration is not something the app tracks for anything you log, sleep included. It is built for the line you write after you wake up, whatever that line happens to be: a note about how the night went, a colour, a moment stamped to when you wrote it. If a wearable already gives you the hour count, the log is free to do the part the wearable cannot, which is remembering why the night was worth mentioning at all.

If you have been skipping mornings in your log because you were not sure whether the sleep number counted as something worth writing, it is worth remembering that a log was never about the number. It was about the sentence you would actually want to reread.