
Prevent recurrence
Document the cause, fix, and relevant dependencies. Replace unsupported components or change the update process when needed. Agree whether the evidence supports keeping, changing, or stopping the approach.
Collect error messages and the update or edit that preceded the issue. Check logs and reproduce the problem before applying multiple changes. Keep enough history to separate a planned test from an unrelated change.
- A written brief
- Named responsibilities
- Agreed review points




