How do you log a day you spent mostly waiting on other people?
A delayed flight. A doctor's office running two hours behind. A contractor who said morning and showed up at four. A phone held to your ear on hold, a kid who is not ready yet, a friend running late to something you both cared about. None of these are things you did. They are things you sat through while someone else's timing decided what your day was going to be. When it comes time to write a line about the day, the instinct is to write nothing at all, because it does not feel like it was yours to describe.
Waiting does not feel like an entry because it does not feel like an action
Most days give you something to write because most days you did something — a meeting, a walk, a meal, a task finished or abandoned. A day of waiting does not hand you a verb that easily. "Waited for the plumber" is technically true and says almost nothing, and it says nothing on purpose, because the day genuinely did not have much content that was yours to generate. The hours belonged to someone else's schedule, and a log built around what you did runs low on material when what you mostly did was sit somewhere and let time pass around a delay you did not cause.
So the day gets skipped, or gets one flat line that reads like an apology for having nothing better to report. Neither response is really about laziness. It is that waiting sits outside the shape a log entry usually has, and nobody hands you a template for describing time that was not, strictly speaking, spent on anything.
The day still happened, even if the day did not belong to you
This is the part worth pushing back on. A day spent waiting is not a blank — it is a day with a very particular texture, and that texture is exactly the kind of thing a log is good at holding onto, precisely because nothing else is going to. You will not remember, a year from now, the general fact that a certain appointment ran late. You might remember, if you wrote it down, that you reread half a chapter you had abandoned months earlier, or that you and the person waiting next to you ended up talking about something neither of you would have brought up on purpose, or that you spent forty minutes doing nothing but watching a parking lot and it was, unexpectedly, kind of restful. None of that shows up if the entry is "waited at the clinic." It shows up if the entry is about what the waiting was actually like.
Write what filled the gap, not just the fact of the gap
The useful version of this line is rarely about the delay itself. It is about the small, specific thing that happened inside it: the book, the conversation, the podcast episode you finally finished, the argument you had with yourself about whether to say something to the person at the desk, the view out the window you had never had reason to look at that long before. A day of waiting almost always contains a handful of these fragments, and they are the part actually worth keeping — the delay is just the frame that happened to hold them.
If genuinely nothing filled the gap — if it really was forty minutes of staring at a wall — that is also fine to write exactly as it was. "Sat in the waiting room, didn't really do anything, just tired" is a true sentence about a real hour, and a log that only records eventful hours is not actually a log of your life, it is a highlight reel with all the connective tissue removed.
You do not need a category called "waiting"
It can be tempting to invent a special colour or category just for these stretches, as if waiting were its own separate kind of activity that deserves its own bucket. It usually is not worth it. The waiting is not the category — it is the container the actual moment happened inside of. If you were reading during the wait, log it under reading. If you were talking to someone, log it under whatever you would call that conversation any other time. The delay is context you can mention in the line itself if it matters, not a label the whole entry needs to be filed under.
What this is actually worth, later
A month from now, one delayed appointment will not matter on its own. But a log that includes these entries, instead of quietly skipping every day that felt like it was not really yours, ends up with something a memory-only account of the month never gets: an honest sense of how much of your time is actually spent on someone else's schedule, not your own. Some people find that number is much smaller than they assumed. Some find it is much larger, and that itself is worth knowing — not as a complaint, just as an accurate fact about a life that other people's timing keeps quietly borrowing from.
TimeMap does not need the day to have been productive, or even yours, for a line about it to count. You write what you were doing — reading in a waiting room, on hold with the airline, sitting with a friend who was running late — give it a colour, and it sits in the record next to every other kind of day, exactly as valid as a day that went entirely to plan.
The next time a day gets swallowed by somebody else's schedule, it is worth writing one line about what actually filled the waiting, rather than skipping the day for having nothing to report. There was almost always something in there. It just was not the thing you were waiting for.