Why doesn’t your calendar show what you actually did that day?

You open the calendar to remember last Tuesday and it tells you "2:00 Gym." You did not go to the gym. Something came up, the block just sat there unchanged, and now it is lying to you with total confidence. This is not a bug. A calendar was never built to record what happened — it was built to hold what you intended, and it keeps holding that even after the day has proven it wrong.

A calendar is written before the fact

Almost every entry in a calendar is created before the event it describes takes place. That single fact decides everything else about what a calendar can and cannot tell you later. It is a forecast, made with the information you had on Sunday night, about a Tuesday afternoon you had not lived yet.

Forecasts are useful for exactly one thing: knowing where to be next. They are not evidence of where you actually were, because nothing forces the calendar to check itself against reality once the time has passed. The block just sits there, unattended, saying the same thing it said a week ago.

What happens when the day doesn't match the plan

Most days do not go as planned, at least a little. A call runs forty minutes over. A meeting gets cancelled and you use the hour for something else entirely. You meant to work on the proposal at ten and actually started at half past two, after a conversation that was not on the calendar at all and turned out to matter more than anything that was.

None of that gets written down anywhere, because there is nowhere on a calendar to write it. The interface only has one move: place a block at a time. It has no second move for "this is what actually happened instead," so the original block simply stays, technically present and quietly false.

Edited and deleted events leave no trace

It gets worse the moment you touch anything. Drag a meeting from 2pm to 4pm and most calendars just move it — nothing marks that it was ever at 2pm, or that the move happened, or why. Delete a cancelled event and it is not marked cancelled, it is simply gone, as if that hour had never had a plan at all. A calendar edited over a busy week ends up looking exactly like a calendar that went perfectly, because the software has no memory of its own history, only its current state.

Ask it in November what your Tuesdays looked like in March and it will answer with whatever the boxes say today — after every reschedule, every cancellation, every plan quietly replaced by something else — not with what a Tuesday in March actually contained.

What a calendar was never designed to hold

Even a perfectly accurate, never-edited calendar would still be missing most of a day, because most of a day was never scheduled in the first place. The calendar has a block called "Lunch," but nothing about who you sat with or what they told you. It has no block at all for the conversation in the hallway that changed your afternoon, the hour you spent stuck on a problem, the walk you took because you needed one. Those things were not intentions that got kept or broken — they simply were not plans, so a tool built entirely out of plans has no slot to put them in.

The difference between a schedule and a record

A schedule answers "what is supposed to happen." A record answers "what did happen." They look similar — both are a list of things attached to times — which is exactly why it is easy to assume one is quietly doing the other's job. It is not. A schedule is written in advance and left alone; a record has to be written during or after, by someone actually paying attention to what took place instead of what was hoped for.

This is the same gap that shows up between planning your week and journaling about it — a plan and an account of what actually happened are never the same document, even when they are about the same hours.

Nobody sets out to lose track of their own months this way. It happens by default, because the only tool most people already have for "things and times" is a calendar, and a calendar quietly volunteers for a job it was never built to do.

About TimeMap

TimeMap is built for the other half of that job. Instead of blocks placed in advance, you write a short line for what is actually happening, whenever it happens, and give it a colour. Nothing needs to be moved or deleted when a plan changes, because nothing was ever a plan to begin with — every line was written about something that had already occurred. The calendar view fills in the way an ordinary calendar never can: with what the day actually was, not what someone hoped it would be.

You do not need to replace your calendar to fix this. Keep it exactly as it is, for exactly what it is good at — knowing where to be next. Just stop expecting it to also tell you, months later, what actually happened once you got there. That is a different job, and it needs a different kind of entry: one written looking backward, not forward.