How do you log a day you spent mostly commuting?

The train was delayed twice, you finally finished a chapter you had been stuck on for two weeks, and a stranger's phone rang through an entire podcast episode two seats over — and by the time you were home, none of it felt worth writing down, because none of it happened anywhere you would call a place. A commute does not look like an activity from the inside. It looks like the gap between two activities that actually count, and gaps are exactly the kind of thing a daily log is tempted to leave blank.

A commute is not "work" and it is not "personal"

Almost every other hour of the day sorts itself into a category on its own — you were at work, or with your kid, or making dinner, and the entry all but writes itself because the activity already told you what it was. A commute refuses that sorting. It is not the job, even though it exists entirely because of the job, and it is not free time either, since you did not choose it and rarely get to spend it the way you would spend an evening. It sits between categories, doing neither one's work, which is a large part of why it gets no entry at all: there is no obvious bucket to file forty minutes on a train into, so the whole stretch gets quietly skipped rather than mis-filed.

"Commuted" describes the container, not what was in it

Even on the days someone does write the word down, it describes the shape of the hour and almost nothing about what filled it. Forty minutes on a delayed train spent reading a book is a different forty minutes from the same train spent rehearsing an argument you are dreading having once you get home, and both are different again from forty minutes spent staring out the window with your mind genuinely empty for once. "Commuted" is equally true of all three. Writing it down settles nothing about which one actually happened, which means a string of days that all say "commuted" ends up telling you less about that stretch of your life than almost any other word could.

You are not being judged on how the ride went

There is a specific guilt that attaches to commuting time, more than to most other gaps in a day — a sense that this hour was owed to something more useful and instead got spent staring at a phone. That guilt is not a reason to skip the entry. If anything it is a reason the entry matters, because a log is one of the few places a commute gets to be neutral instead of judged. Nothing about what belongs in the line requires the hour to have been used well. It only asks what was actually in it.

• A thought that arrived unprompted while you were not trying to think about anything — the ones that surface on a familiar route are often the only unsupervised thinking a day gives you.
• Something that happened around you, even briefly — an overheard conversation, a delay, a stranger's small kindness or small rudeness.
• What you actually did with the time, if it was different from usual — finished a book, finally called someone you had been putting off, sat with nothing on for once.
• How your body felt getting off, if it was notably different from getting on — wired, drained, oddly calm.

Most days that produces nothing longer than half a line, and half a line is the correct amount. A commute does not owe you an insight every time.

A tracker would only ever hand you the delay

A tool built around duration has exactly one thing to say about a commute: how long it took, and maybe whether that was longer than usual. That number is not nothing — a commute that has quietly crept from thirty-five minutes to fifty over a year is worth knowing about. But it is the least interesting thing a commute could tell you, and it happens to be the only thing a stopwatch is built to notice. The chapter that finally clicked, the argument rehearsed and then never actually had, the stranger's small kindness — none of that shows up in a duration, because none of it is a duration. It is what happened, not how long it took to happen.

What a month of commutes actually shows you

A single ride, read back later, rarely says much. A month of them, lined up, tends to say something no single day can: whether the commute has quietly become the only part of the day that hands you any silence, whether a new route changed more about your mood than the new job at the other end of it did, or whether the days you dreaded a particular train were always the days something specific was waiting for you at either end of it. None of that is visible from inside any one ride. It only becomes visible once there are enough of them, each filed with an actual date, to be set against one another.

TimeMap treats a commute the same way it treats every other hour — one line, one colour, filed under whatever it actually was rather than forced into "work" or "personal" because neither one fits. There is no clock running on the ride, and nothing that needs starting the moment you step onto the platform. If a delayed train hands you an unexpected forty minutes and a stray thought worth keeping, it goes in exactly the way a good conversation would. A rushed transfer where nothing happened is allowed to leave no trace at all.

A commute rarely deserves a full paragraph, and most days it deserves nothing. But the days it does — the stray thought, the delay that turned into something, the ride home that felt different from the ride in — are easy to lose precisely because "commuted" is such an easy word to write instead, and such a complete-feeling nothing once it is sitting on the page.