How do you log a day that didn't go as planned?

The plan was the gym, then the report, then dinner with your sister. What actually happened was a flat tyre on the way out, forty minutes on hold with the insurer, the report finished after midnight, and a reservation given away to someone else. None of it looks anything like what you meant to write down, and that mismatch is usually the reason the day never gets logged at all.

A log was never a copy of the plan

The instinct to skip a derailed day comes from treating the log as if it exists to confirm the plan happened. It doesn't. A plan is a guess made in advance, written by a version of you who had not yet met the flat tyre. A log is written afterward, describing whatever turned out to be true once the guessing was over. Those are two different documents, and only one of them can be wrong. The plan can miss. The log can only be accurate, because it was never predicting anything — it is just naming what occurred, and a flat tyre occurred exactly as factually as a completed workout would have.

Once you see it that way, the derailed day is not a harder case for the log. It is the same case. The log does not need the day to have gone well in order to have something true to say about it.

Why the off-plan day feels unwelcome in the log

Most people did not decide, in so many words, that only successful days deserve an entry. It happens quietly: a good day gives you something you feel like recording, and a day that went sideways gives you something you would rather not think about again, so you close the app instead of opening it. The day does not skip itself. You skip it, on the reasonable but mistaken idea that a log is a place for reporting how the day went, when it is actually just a place for saying what happened.

This is also where a log differs from a to-do list. A list of intentions that didn't happen reads as failure — three unchecked boxes staring back at you. A log has no boxes to leave unchecked. There is no version of "flat tyre, insurer, report at midnight" that fails at being a log entry, because nothing about it was promised to anyone in advance.

Write the chain, not the verdict

The move that actually works is to describe the sequence, plainly, the same way you would describe any other day — not to summarize how it went. There is a real difference between the two.

• Weak: "Bad day, nothing went right."
• Better: "Flat tyre on the way to the gym, forty minutes on hold with the insurer, report done after eleven, missed dinner with Priya."

The first line is a judgment and tells you nothing a year from now — every difficult day looks identical from the outside once it has been compressed into "bad." The second line is a record. It names what actually derailed, in what order, and what it cost, which is exactly the kind of detail memory drops first and a log is good at keeping.

The days that broke from the plan are often the ones worth having later

A log made only of days that went as intended would be a strange, thin thing to read back — a life edited down to its cleanest stretches, with every flat tyre and cancelled dinner quietly missing. The off-plan days are usually the ones that explain something later: the week three things went wrong in a row and you can now see it was one bad week, not a pattern; the reservation you keep meaning to rebook and never do, which the log will remind you of long after memory has let it go. None of that shows up if the derailed days are the ones you decided weren't worth writing down.

TimeMap holds both kinds of day the same way — a short line, a time, a colour, with no field anywhere asking whether the day matched what you meant it to be. A flat tyre costs exactly as much effort to log as a completed workout, which is really the whole point: the record is of what happened, and what happened is never wrong.