Should you log the things you didn't finish?

There is a quiet rule most people apply to their own log without ever deciding to: write it down once it is done. The report gets filed, the call ends, the errand gets crossed off, and only then does it seem worth a line. Everything still in progress waits its turn. The trouble is that most of a day is still in progress. If closure is the ticket to get into the log, the log ends up holding a small, tidy fraction of what actually happened.

A finished thing is the exception, not the rule

Look honestly at an ordinary day and count what actually resolved by the time you went to bed. One or two things, maybe. The rest is a draft left open in a tab, a conversation that trailed off because someone had to go, a project you meant to start and didn't, a book you read forty pages of and put down. None of that is a failure — it is just what a day is mostly made of. Waiting for an ending before you write anything down means the log only ever sees the small minority of your time that happened to wrap up cleanly.

Over a few months this adds up to a strange kind of record: a life that looks like a series of completions, stitched together with nothing in between. That is not what living it felt like, and it is not what you will want to read back.

An unfinished line still tells you something later

Say you write, on a Tuesday in February, "started trying to learn guitar again." Nothing follows for three weeks. Then, in March, "picked it up again, thirty minutes, fingers hurt less than last time." That pair of lines is more useful than either a completed-tasks list or nothing at all. It shows you when something actually started, how long it sat untouched, and that you came back to it — none of which you would remember accurately on your own six months later. An attempt you gave up on is still information. So is one you circled back to twice before it stuck.

None of this requires the entry to resolve anything. You are not opening a ticket that needs closing. You are noting that something happened — including the fact that it stalled — and moving on.

The difference between logging and tracking a task

A to-do list exists to be emptied. An item on it that never gets checked off reads as unfinished business, and the list itself starts to feel like an accusation. A log is not that. It has no open items, because it was never a list of things owed — it is a record of what actually occurred, and "gave up on this for now" is a perfectly complete thing to have occurred. The moment a log starts behaving like a task list — carrying things forward, expecting them to eventually close — it inherits all the guilt a task list produces, which is exactly the feeling a log is supposed to be free of.

Writing down an interruption is not admitting a failure to write down a completion. It is describing the day accurately, on a day when accuracy meant something didn't get finished.

What this looks like in practice

You do not need a special format for it. The same line you would write for anything else works: what you were doing, roughly when. "Back on the proposal, third sitting this week, still not sent." "Gave up on cleaning the garage after twenty minutes, too hot." "Two chapters into the book, might not finish it." Each of these is a complete entry. None of them needs a follow-up to be worth keeping, and if a follow-up does happen later, it becomes its own line rather than a correction to this one.

TimeMap treats every entry this way by default, because it never asks an entry to resolve into anything — a line, a time and a category colour, nothing more is required. There is nowhere to mark something as done and nothing that stays open, so writing "stopped halfway" costs exactly as little as writing "finished it."

What you get back later is not a record of your successes. It is a record of what you actually spent your attention on, including the parts that trailed off — which, on reflection, is most of what a real day is.