Tasks

Closure should mean the outcome is verifiable: the file is uploaded, the email is sent, the approval is recorded, or the waiver is documented with approver and date.

If “done” is subjective, write two lines in the task before starting so reviewers share the same finish line.

Assume someone will ask “how did we decide this?” in six months. Link artefacts rather than pasting sensitive content into the task body when policy discourages duplication.

If work reopens, add a note explaining what changed. Silent reopens destroy audit narratives and confuse downstream owners.

Patterns of sloppy closure are coaching opportunities: unclear owners, missing links, or tasks closed without matching deliverables. Fix the habit, not only the row.