Protocol
Show the delta when a requirement changes
Change communication should reveal the change.
When it fits
- A thread says 'updated requirement' but readers must compare old and new text manually.
When to avoid it
- Keep formal change-control rules where required; a readable delta does not replace approvals or traceability.
Why it matters
State the previous rule, the new rule and why the change matters. For structured data, highlight changed fields rather than resending an unmarked full artifact. Name effective timing and whether previous work must be revised.
Steps
- A reader can identify what changed without diffing two long documents.
An example
'Delivery block: blank → ZM for scope X; effective for Monday load; regenerate batch file only.'
Check your result
A reader can identify what changed without diffing two long documents.
Keep this limit in mind
- Keep formal change-control rules where required; a readable delta does not replace approvals or traceability.
Evidence and sources
CDC clear-communication guidance recommends one obvious main message, placing it early and including a clear action for the audience.
Complex work can require several actions, but the communication still benefits from a dominant purpose.
Description and Examples of Index Items · Core items 1, 2 and 5
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