Protocol
Preserve the sequence when chronology explains the failure
Some problems are state machines disguised as email threads.
When it fits
- A handoff lists facts but loses the order in which state changed.
When to avoid it
- Timestamps can create false precision if clocks or systems differ; note source and timezone where material.
Why it matters
When sequence matters, use a compact timeline with timestamps or ordered states. Include only transitions relevant to the issue and mark the first divergence from expected behavior.
Steps
- A reader can locate the first unexpected transition without reconstructing the thread.
An example
'10:10 In Development → To Be Tested: success. 10:40 To Be Tested → Successful Tested: No change in development system.'
Check your result
A reader can locate the first unexpected transition without reconstructing the thread.
Keep this limit in mind
- Timestamps can create false precision if clocks or systems differ; note source and timezone where material.
Connected ideas
Useful withReset a long thread with a current-state block
Evidence and sources
Supports
CDC guidance recommends lists, chunks and descriptive headings to make information easier to scan and organize.
Very short messages may not need headings; structure should match complexity.
Description and Examples of Index Items · Core items 8 through 10