A note can be long and still fail its reader. Streams of copied messages, unexplained abbreviations, and meeting transcripts preserve words but hide decisions. When the task returns days later, you still need to reconstruct what changed and where to restart.
Useful task notes are written for a future reader with partial context. They capture the current state, key evidence, decisions and reasons, unresolved questions, and the next action. This creates continuity without turning every task into a formal report.
Lead with the current state
Start with a dated sentence explaining where the task stands: revised quote received; freight still excluded, or client approved option B subject to colour sample. This gives the reader orientation before details. Update the state when material facts change rather than endlessly appending without summary.
Distinguish fact, assumption, and interpretation. Write supplier confirmed delivery August 18 rather than delivery should be fine. If you infer a consequence, label it: likely schedule impact is two days if approval arrives after Friday. Clear language protects later decisions.
Record decisions and their reasons
Capture what was decided, by whom, when, and the reason that may matter later. The reason can be short: option A rejected because it exceeds the approved weight limit. This prevents the team from reopening settled choices after the original context fades.
Include conditions and expiration points. A decision may remain valid only if pricing holds or testing passes. Recording the condition helps future readers know whether they can rely on the choice or must verify it again.
Link evidence instead of duplicating it
Point to the authoritative drawing, email, photo, estimate, or file and describe why it matters. Avoid copying large bodies of content that may become outdated or expose unnecessary information. A useful link has a label such as approved sketch dated August 7, not file here.
If the source may move or disappear, store it in the approved project location and link from the task. Respect access boundaries: do not place sensitive personal, financial, or contractual information in notes visible to people who do not need it.
End with unresolved questions and restart
List the few questions that still block progress and name who can answer them. Then write the exact next action. The combination tells a future reader what remains uncertain and how to move without rereading the entire history.
Clean notes when the task becomes cluttered. Replace outdated summaries, close answered questions, and keep the essential history. Preserve important decisions, but remove navigation noise. The note should become easier to use as work advances, not progressively harder.
Rewrite one messy note
- Add a dated one-sentence summary of the task’s current state.
- Extract the key decision, decision owner, reason, and any condition.
- Replace duplicated source material with clearly labelled links.
- Finish with unresolved questions and one exact restart action.
Common questions
How long should a task note be?
Use the shortest length that preserves material state, decisions, evidence, and restart context. A simple task may need three lines. Complex work may need sections, but each section should remain scannable and purposeful.
Should I delete old information?
Remove obsolete navigation details and superseded summaries, but preserve decisions or evidence with ongoing significance. When audit history matters, use dated entries or versioned files rather than silently rewriting material facts.
