Should you log your naps?

You wake up on the couch at 3:40, unsure for a second what day it is, and the first honest thought is not about the nap at all — it is about whether the nap is even the kind of thing a log is for. Meetings go in a log. Errands go in a log. A twenty-minute collapse on the couch with your shoes still on feels more like a gap in the day than a part of it, the sort of thing you would leave out even if you were writing everything else down.

A nap does not look like an event

Most of what ends up in a log has some shape to it — it started, something happened, it ended, and the something is what makes it worth a line. A nap does not offer much of that. Nothing happened during it, by definition; the entire point was to be unconscious for a while. So it gets treated the way a stretch of scrolling or a stretch of staring out a window gets treated: real time that passed, but not the kind of thing that seems to belong in a record built around what you did. The trouble is that "what you did" was, in fact, sleep in the middle of the afternoon, and that is not nothing — it is often the most honest fact about how the day was actually going.

The number was never the point

If a nap does get logged anywhere, it usually gets logged as a duration — a sleep app or a smart watch timing it to the minute, the same way it times the night. Twenty-three minutes. Fifty-one minutes. That number answers a narrow question and answers it well, but it is not actually the question worth asking about an afternoon nap, which is closer to why did the day need this than how long did it take. Two naps of the exact same length can mean completely different things — one a deliberate reset between two demanding stretches of work, the other a sign that the morning had already used up more than it should have. A stopwatch cannot tell those apart. It was never built to.

This is where a log does something a timer cannot: it does not ask you to measure the nap at all. There is no field for duration to fill in and nothing to start or stop. A line like "crashed on the couch after lunch, couldn't keep my eyes open" says more about the day than a precise minute count ever would, and it costs nothing to write, because nobody is asking you to time yourself falling asleep.

What one nap tells you, and what it cannot

A single nap on a single afternoon is close to meaningless on its own. Everyone gets tired sometimes, slept badly the night before sometimes, has a heavy lunch sometimes. Reading one entry and trying to draw a conclusion from it is asking a single data point to behave like a pattern, and it will not. What a nap entry is actually for is sitting quietly next to the next one, and the one after that, until a shape starts to show up that no single afternoon could have revealed by itself.

That shape might be ordinary — naps that show up every Sunday after a slow morning, which is just a rhythm, not a problem. Or it might be worth noticing: three unplanned naps in a week that used to have none, all landing in the same stretch that a new project has been running, or all following nights that ran later than usual. None of that is visible from inside any one nap. It only becomes visible once there is a small pile of them to look back across, each one honestly dated instead of remembered as a vague sense that you "haven't had much energy lately."

Write what came before it, not just that it happened

The part of a nap worth keeping is rarely the nap itself — it is the half-sentence of context sitting right next to it. "Didn't plan to, just went out" is a different day from "gave up on the afternoon and napped on purpose." "Woke up groggy, dreaded going back to the desk" is a different nap from "woke up and actually felt reset." None of this needs more than one line, and none of it needs a number attached — the value is entirely in the few words describing why the day made room for it and what state you were in once it was over.

• Skip the clock. "Napped after lunch" is a complete entry. Nobody needs to know it was twenty-three minutes rather than thirty-one for the entry to be worth having.
• Note whether it was planned or not. A deliberate nap and a nap you fell into by accident are different facts about the same afternoon, and the difference is usually the more useful half of the entry.
• Write how you felt after, if it stood out. "Woke up worse than before" is short, honest, and tells a future reader something a duration never could.
• Let an ordinary nap go unremarked. Not every nap needs a line. If it is not telling you anything, skip it — the log loses nothing by staying quiet about a Sunday afternoon that needed no explanation.

About TimeMap

TimeMap has no field for how long a nap lasted, because nothing in it works that way — a moment gets a line, a colour if you want one, and a time it was written, and that is the whole entry. A nap gets treated exactly the same as a meeting or a walk: not measured, just noted, with whatever context actually mattered sitting right there next to it.

A stretch of afternoons that quietly started needing a nap is not something any single Tuesday can tell you. It shows up later, once there is a small run of honestly dated lines to look back across — which only exists for the naps someone bothered to write down, however unremarkable they felt at the time.