Should you log your day in bullet points or full sentences?
You open a blank entry and there is a small decision before you have written a single word: type a fragment, or write it as a real sentence with a subject and a verb. It looks like a style preference, the kind of thing you settle once and stop thinking about. It is actually a decision about how much of the day survives being written down, and it is worth making on purpose rather than by accident.
The bullet-point instinct
Most people default to fragments without deciding to. "Coffee with Dana." "Fixed the login bug." "Long call, rescheduled dinner." No subject, no verb tense to choose, no punctuation to get right. A bullet takes about as long to write as it takes to think of it, which is exactly why it survives days when nothing else would: a rushed morning, a bad mood, a moment stolen between two other things. The lower the cost of an entry, the more likely it actually gets written, and an entry that gets written beats a beautifully composed one that does not.
What a bullet point quietly drops
The cost of that speed shows up later, not now. A fragment records the noun and throws away everything attached to it. "Call with Raj" does not say whether the call ran long because a client was upset, or short because everything had already been fixed the day before, or whether you hung up relieved or drained. Read that fragment in eight months and you will remember that a call happened. You will not remember what it was like to be in it. The label survives; the texture does not, and texture is usually the entire reason a specific day is worth having a record of at all.
The full-sentence instinct
The opposite habit — writing in complete grammar, with cause and consequence spelled out — fixes exactly that problem. "Raj's call ran forty minutes over because the client found a second bug right as we thought we were done, so I pushed the deploy to tomorrow" is a sentence you could hand to a stranger and have them understand your afternoon. It carries the story, not just the topic. Reread a year later, it puts you back in the moment in a way a two-word label never will.
What a full sentence costs you
It also costs more to produce, and the extra effort is not evenly distributed across your days — it lands hardest on exactly the days you can least afford it. On an easy afternoon, composing a proper sentence is no trouble at all. On the day the deadline moved, the kid was sick, and dinner burned, sitting down to write a grammatical account of any of it is the first thing that gets skipped. That is the trap: the format that captures the most also breaks first on the days most worth capturing, and a log that goes silent under pressure teaches you, slowly, to stop trusting it to be there.
What actually survives being reread
In practice, the entries people are glad they kept are rarely full grammar and rarely bare labels either. They sit in between: a short phrase with one piece of cause or feeling attached, the kind of thing you would say out loud if a friend asked "how was today" and you only had one breath to answer. "Deadline day, skipped lunch, Priya covered the call I missed" is not a sentence in the grammatical sense — no verb doing the connecting work a textbook would want — but it has a subject, an obstacle, and a person in it, and that is enough to reconstruct the day from months away. A bare bullet like "deadline day" would not do that. A full paragraph would not have gotten written at all.
A few things that tend to separate a rereadable entry from a forgettable one, regardless of grammar:
- One cause or consequence, not zero. "Late again" tells you nothing a year later. "Late again, train was cancelled" tells you something, and costs almost nothing extra to add.
- A name over a category, when one is available. "Dinner with Sam" survives rereading better than "dinner," because a name is a hook memory can actually catch on.
- Write it the way you would say it, not the way you would file it. A filed label is written for a system. A said-out-loud line is written for the person who will read it back.
None of this needs to be decided consciously every time. Most people land on a rhythm — closer to phrase than sentence, closer to a fact plus a feeling than a bare label — after a couple of weeks of just writing whatever comes out and noticing which entries they are glad to find later.
TimeMap does not enforce either style. An entry is one line and a category color, nothing about grammar checked or required, so the choice stays yours rather than the app's. What tends to happen, once the pressure to be either terse or correct is gone, is that people settle into something closer to how they would actually describe the day to someone who asked.
The format is not really the question worth spending time on. The real question, whichever way you write it, is whether the line would mean anything to you if you found it again in a year with no other context. If it would, the grammar around it was never the point.