How do you log a day you spent mostly sick in bed?

The day is a blur of the same four walls, a thermometer you keep rechecking out of boredom more than need, and a couch dent that gets deeper by the hour. Nothing on the to-do list moved. Nobody would call it a day worth remembering. So the log stays closed, on the reasonable-sounding theory that a day like this has nothing in it worth writing down — which turns out to be exactly backwards.

"Nothing happened" and "I was sick" are not the same claim

A day spent sick in bed did not happen to you the way an empty afternoon does. Something specific was going on: a fever that peaked at a particular hour, a stomach that would not hold anything down until evening, a headache that finally let up after the second dose of something. None of that is dramatic, but all of it is information, and none of it will still be sitting in your memory in six months the way it is sitting there right now. "I was sick that week" is the sentence memory keeps. It drops the actual shape of the illness — how bad, how long, what helped — the same way it drops most specifics that were not attached to anything a story needed.

Sick days are where the guilt reflex is strongest

Of all the days that make people close the app instead of opening it, a sick day is the worst offender, because it arrives paired with a second feeling on top of the illness itself: the sense that the day was wasted, that it should not count, that writing it down would just be confirming a failure. That reflex is worth noticing rather than obeying. A log is not a ledger of output, and a day your body spent fighting something off was not idle — it was doing the one job that mattered that day. Writing "fever, mostly slept, cancelled the two calls" is not an admission of failure. It is simply what happened, stated as plainly as any other line in the log.

What is actually worth a line

You do not need a symptom-by-symptom account, and nobody is asking for one. A few honest fragments do more work than a complete medical history:

• What it actually was, in plain words: a cold, a stomach bug, a migraine, nothing you could name.
• Roughly how bad, and when it turned — worse in the morning, better by evening, a fever that broke overnight.
• What you did about it: the medicine, the soup someone brought over, the doctor you finally called.
• What got cancelled or moved, if it matters to you later that it did.
• Anything small that made the day survivable — a show you half-watched, a person who checked in.

That is a handful of lines, not an essay, and it takes less time to write than it took to read this paragraph.

What one sick day cannot tell you, and what a year of them can

A single entry like this will not feel useful the day you write it — it is one flat afternoon, filed away with no obvious reader. Its value shows up later, and it shows up twice. The small version: the next time something similar hits, you can look back at what actually helped last time instead of relearning it from scratch. The larger version only appears once there are enough entries to compare — whether it is always the same season, whether it tends to follow the same stretch of overwork, whether "sick" has quietly gotten more frequent this year than last. None of that is visible from inside any single bad day. It only becomes visible once there is a real record of more than one of them, sitting side by side instead of scattered across a memory that keeps none of the specifics.

TimeMap does not need the day to have gone well before it is worth a line — a fever and a cancelled afternoon get the same one-line, one-colour entry as anything else, saved with its date and left alone. Lay a sick week next to an ordinary one later and you are looking at what your body was actually doing then, not a gap where a real day used to be.