What happens when you forget to stop a timer?

You start a timer for one task, get pulled into something else — a call, a knock at the door, lunch that runs long — and forget about it completely. Hours later you glance at the app and it says four hours and twenty minutes on a task that actually took about thirty. The number is not slightly generous. It is not even really a measurement anymore. It is a record of how long a piece of software sat there counting while you were somewhere else entirely.

A timer cannot tell the difference between working and forgetting it is on

This is not a bug, or at least not one that can be fixed without changing what a timer fundamentally is. A timer counts elapsed seconds from the moment you press start until the moment you press stop, and it has no way of knowing what happened in between. It cannot see that you left your desk. It cannot see that the "quick call" became a forty-minute one, or that you closed the laptop and went to make dinner. All it knows is that no one told it to stop, so it kept going, faithfully and uselessly, turning a real thirty minutes of work into a fictional four and a half hours.

The absurd part is that this happens to careful people too. Forgetting to stop a timer is not a sign of poor discipline. It is what happens whenever a task's natural ending does not coincide with a decision to press a button — which is most of the time, because most tasks do not end with a click. They end with a phone ringing, or someone walking in, or your attention simply sliding somewhere else without asking permission first.

The fix is worse than the problem

Once you notice the runaway number, there is no way back to the truth — only a guess dressed up as a correction. You try to reconstruct when you actually stopped: was it closer to twenty minutes or forty? You round to something that feels plausible, type it in, and move on, quietly aware that the figure you just replaced a wrong number with is also not a real one — just a more socially acceptable fiction. Do this often enough and the whole log stops being a record of what happened and becomes a record of what you were willing to type in after the fact to make the totals look reasonable. The tool that exists specifically to protect precise numbers ends up full of numbers nobody actually measured.

Nothing warns you while it is happening

The cruelest part of the design is that a runaway timer gives you no signal. There is no gentle buzz an hour in asking whether you are still at it. The little running clock in the corner of the screen looks exactly the same at minute five as it does at minute two hundred, so unless you happen to glance at it — which you will not, because you are the person who just forgot it was running — it simply accumulates in silence until something else reminds you it exists. Idle-detection features exist precisely because this failure is common enough that an entire feature category was built to catch it after the fact, which is itself a quiet admission that the basic design invites the mistake.

A log has no clock to leave running

This entire failure mode depends on one thing existing: a timer that keeps counting whether or not you are paying attention to it. Remove that, and the mistake has nowhere to happen. A log does not start counting when you write an entry and does not need to be told to stop, because nothing was ever running — you write a line about what you did, whenever you get around to writing it, and the line does not accrue error the longer you take. Coming back three hours later and writing "on a call, then lost the afternoon to it" costs you nothing. There is no number silently inflating in the background while you are not looking, because there was never a number ticking in the first place.

That is not the same as saying a log is more accurate about duration — it is not trying to be. It simply cannot be wrong about duration in this specific, embarrassing way, because it never claimed a duration to begin with. What it records is what you were doing, and that stays true whether you write it down the instant it happens or remember it at the end of the day.

If you do need real durations

None of this means duration never matters — billable work, a paced workout, anything someone else is going to hold you to a number on genuinely needs a real clock, and a runaway timer there is a real problem worth solving with reminders, idle detection, or simply checking the running total more often than feels natural. But most of a day is not billed to anyone. For that part, the safer instrument is the one that was never counting in the first place.

TimeMap is built on that second kind of instrument. There is no timer anywhere in it, running or otherwise — you write a line about what you are doing, attach a colour, and that entry is complete the moment you save it, with nothing left ticking in the background to forget about later.

The next time a timer app hands you back an afternoon that clearly did not take four hours, it is worth asking what exactly you were trying to learn from that number in the first place. Often the honest answer is that you just wanted to remember what the afternoon held — and a running clock was never the tool for that.