How to write troubleshooting notes that others can replay

Updated Feb 2026 • Writing / Docs

The replayable format

  1. Symptom: what is failing and how you observed it
  2. Environment: version, node names, network zone, time
  3. Hypotheses: top 3 likely causes
  4. Tests: ordered steps with expected result
  5. Observed: what actually happened
  6. Root cause: confirmed, not guessed
  7. Fix: exact change made
  8. Verification: proof the fix works
  9. Prevention: what to do next time

One rule

If a future engineer cannot repeat it, it is not done.