How do you log a day you spent mostly running errands?

The package finally got returned, the form that had been sitting in a drawer for three weeks finally got dropped off, the dentist appointment you kept rescheduling finally happened, and you picked up the one ingredient the recipe actually needed instead of the two substitutes you'd been making do with. None of it, on its own, seems worth a line. By evening the whole day compresses into a single word — "errands" — and that word feels like it says everything and nothing at the same time.

An errand day doesn't have a shape, it has a list

Most days organize themselves around one or two things big enough to name — a job, a trip, a person you spent the afternoon with. An errand day refuses that. It's built from a dozen small closed loops, each one finished the moment it starts: stand in line, hand over the package, done; sit in the waiting room, get the cleaning, done. Nothing in the list is large enough to be the day's headline, so the day ends up with no headline at all, just a category that describes the shape of the hours without describing anything that actually happened inside them.

"Ran errands" is true of every errand day and useful about none of them

Write "ran errands" often enough and the phrase stops carrying any information at all — it is exactly as true of the day you finally sorted out a broken lease clause as it is of the day you bought stamps and picked up dry cleaning. Both were errand days. Neither reads back as anything, because the word describes the category, not the content. A month of entries that all say the same three words about a Saturday tells you that Saturdays exist for errands and nothing else, which you already knew before you opened the log.

The friction is usually the actual story

What makes one errand day different from another is almost never the errands themselves — it's what got in the way of them. The office that was closed when the sign said it wouldn't be. The form that bounced back because of a signature on the wrong line. The thing you'd been putting off for a specific reason, and what that reason turned out to be once you actually showed up. That's the part worth a line, because it's the part a bare list of tasks erases completely:

• Whatever took longer or went worse than expected, and what actually happened — a website that wouldn't accept the payment, a queue that ran forty minutes past what it should have.
• The one item on the list you'd been avoiding, if there was one, and what it turned out to feel like once it was actually done.
• Anything you learned in the process that changes how you'd do it next time — a better time of day to go, a form you now know to bring two copies of.
• How the day felt once the list was empty — relieved, still behind, or oddly flat considering how much technically got finished.

Most errand days produce one or two lines like that, not twelve. The other ten errands can stay folded into the category and lose nothing worth keeping.

A duration would only tell you how long you were out of the house

A tool built to measure elapsed time has exactly one thing to offer an errand day: how many hours it swallowed. That number confirms what you already suspected walking back in the door — a lot of the day is gone — without explaining anything about where it went or why it felt worse than the same number of hours spent almost any other way. The reason a form bounced back, the reason you'd been avoiding one specific call, the small relief of finally not having to think about the thing anymore — none of that is a duration, because none of it is about how long anything took. It's about what actually happened while you were out.

The guilt an errand day carries doesn't belong in the log

Errand days tend to arrive with a quiet verdict attached — a sense that nothing "real" got done, even on a day that closed out a list of things that had been unresolved for weeks. That verdict isn't information, and it doesn't need a line of its own. A log isn't scoring the day against some idea of what a productive one should have contained. It only needs what actually happened, and a returned package or a rescheduled appointment finally kept is exactly as legitimate an entry as anything else the day could have held.

What a string of errand days actually shows you

One errand day rarely tells you anything. A handful of them, read back together over a few months, tend to show something a single day can't: whether the same task keeps reappearing because it never actually gets resolved, whether errands cluster on the days you're already most stretched thin, or whether a specific kind of task — anything involving a phone call, say — is the one that keeps getting pushed to the bottom of every list. None of that is visible from inside any single Saturday. It only shows up once there are enough of them, filed with real dates, to be set next to each other.

TimeMap treats an errand day the same way it treats any other one — filed under whatever category it actually was, with no clock that needs starting the moment you walk out the door and no penalty for a day that produces nothing more than a list of small closed loops. The friction, if there was any worth remembering, goes in as its own line. The rest of the list is allowed to just be the category it already is.

An errand day rarely deserves more than a sentence, and some deserve none at all beyond the category itself. But the sentence that is worth writing — what actually got in the way, what you'd been avoiding and why, how it felt once the list was finally empty — is easy to skip precisely because "ran errands" already feels like it closed the subject, when it's really just the label on a day whose actual contents never made it onto the page.