Is time blocking the same as logging your day?

You spend fifteen minutes on Sunday night dragging colored blocks across next week's calendar — deep work from nine to eleven, email at eleven, gym at six. By Wednesday the blocks are still there, sitting exactly where you left them, describing a day that did not happen. Nobody moved them. Nobody deleted them. They just quietly stopped being true, which is a strange thing for a calendar to be.

A block plan is written before the day exists

Time blocking asks you to decide, in advance, what a future stretch of hours will contain. That is a genuinely useful thing to do — it forces a choice about priorities before the day's noise arrives and makes that choice for you by default. But it is also, structurally, a forecast. It is written by a version of you who has not yet met Wednesday, does not know a client will call at ten, and has no way to account for the fact that the deep-work block will get interrupted nineteen minutes in by something that could not have been scheduled around.

None of that makes the plan useless. It makes it a plan, which is a different document from a record, in the same way a weather forecast is a different document from whatever actually happened outside.

A log is written after the day exists

A log runs in the opposite direction. Instead of deciding ahead of time what nine-to-eleven will hold, you write down what nine-to-eleven turned out to hold, once it is already over. There is nothing to protect from Wednesday's interruptions, because the entry is not describing an intention that Wednesday could break — it is describing whatever Wednesday actually did, after the fact, when there is nothing left to guess.

This is why a log does not go stale the way a block calendar does. A block calendar is only accurate at the moment you finish drawing it; every hour after that is a small bet on whether reality will cooperate. A log is accurate at the moment you write it, for the same reason a receipt is accurate — it is not predicting anything, it is naming something that already occurred.

Why the mismatch is easy to miss

The trouble is that a block calendar looks identical whether it is true or not. Nine-to-eleven says "deep work" whether or not deep work happened, and there is no visual difference between a block that was honored and a block that was quietly abandoned by Tuesday. So the plan keeps functioning as a plan long after it has stopped functioning as a description of your week, and the gap between the two only becomes visible if you go looking for it — which most people do not, because the calendar never flags its own inaccuracy.

A log cannot have this problem in quite the same way, because it never claims to describe the future in the first place. There is no block sitting there quietly lying about Wednesday, because nothing was written about Wednesday until Wednesday had already happened.

They answer different questions, not the same one better

It is tempting to treat these as competing systems, where the winner is whichever one you should actually use, but they are not really answering the same question. A block plan answers "what did I intend for this stretch of time to be." A log answers "what did this stretch of time turn out to be." Those can diverge without either document being wrong — the plan was an honest guess when it was made, and the log is an honest account of what actually followed. Only one of the two, though, is still true a week later without anyone having to update it.

About TimeMap

TimeMap is built for the second document, not the first. There is no calendar of blocks to keep current and no schedule to plan against — you write a short line about what you were doing, whenever you happen to think of it, filed to whatever day it was. Nothing is measured against an intention, and nothing needs correcting when the day goes differently than expected, because the entry was never a prediction to begin with.

If you already keep a block calendar for planning, a log like this is not a replacement for it — it is simply the other half, the part that tells you afterward what actually happened instead of what was supposed to.