Why is it easier to log what you did than what you're about to do?

Ask someone to write one line about what they did an hour ago and they will do it without much thought. Ask the same person to write one line declaring what they are about to do for the next hour, and something changes — a pause, a flicker of resistance, sometimes a decision to skip it entirely. The two sentences look almost identical on the page. What is asked of the person writing them is not identical at all.

A fact and a forecast are different kinds of sentence

"I spent the last forty minutes replying to email" is a report. It describes something that already happened and cannot un-happen; the only job left is to get the wording roughly right. "I am about to spend the next forty minutes on email" is a different kind of claim. It is a prediction about a future you do not fully control — a call might come in, a more urgent task might surface, forty minutes might turn into fifteen or into two hours. Writing it down does not just describe your intention, it exposes that intention to being wrong in front of yourself, on the record, before it has even happened.

Nobody enjoys signing up for that in writing. A fact carries no risk of being contradicted later, because the moment it describes is already settled. A forecast carries exactly that risk, every single time.

Starting something is a promise you have not earned yet

This is most of what a "start" button is actually asking for. Press it and you are not just marking a moment — you are committing to a category and a duration you cannot yet know, on the assumption that the next block of time will unfold the way you picture it right now. Most blocks of time do not. You get interrupted, or the task turns out to be shorter or longer than expected, or you switch to something else halfway through and now the running timer is quietly measuring the wrong thing. None of that is a failure of willpower. It is what happens whenever a method requires a prediction the future is under no obligation to honor.

A record made after the fact is never in that position. It waits until the outcome exists, then describes the outcome. There is no promise sitting inside it that reality can later break.

The past does not need to be defended

There is a second reason writing about what already happened feels easier, and it has nothing to do with prediction. A finished moment cannot be argued with. You do not have to justify why you spent forty minutes on email, the way you might feel you have to justify committing to spend the next forty minutes on it — the decision is already made, already lived, and writing it down is just naming it, not defending it. A log of what happened is closer to a photograph than a plan. A plan invites second-guessing before it has even started. A photograph just sits there being true.

This is also why retroactive entries do not need to be exact

Because a finished moment is not a promise, it does not have to be predicted correctly, only described honestly — and honest description tolerates far more looseness than a forecast does. "Around four, I think," or "sometime after lunch," is a perfectly good entry about something that already happened, because there is nothing left riding on the number. Try to write "at four I will start doing this for exactly this long" with that same looseness and the sentence stops doing its job. Forecasts want precision they cannot actually earn. Records can afford to be approximate, because approximate is still true.

About TimeMap

TimeMap only ever asks for the sentence that is easy to write. There is nothing to start and nothing to promise — you write a line about something once it has already happened, whether that is a minute later or that evening, give it a colour, and move on. Looking back, those lines line up as a calendar, a summary of your most-used words, two stretches of days set side by side, or a sphere of your own tags to wander through. None of it required you to predict your day correctly. It only required you to notice it once it had already gone by.

If a method keeps asking you to declare what you are about to do, and you keep finding reasons to skip that step, the reluctance is not a discipline problem. It is a sign the method is asking for the wrong kind of sentence. The one you already know how to write — the one about what actually happened — was there the whole time.