Maintain an incident register documenting cause, resolution, and follow-up.
- Maintain an incident register documenting cause, resolution, and follow-up1 cited source1 category
Save for later 0
Use × to move an item here. You can restore it when you’re ready.
Your checks and saved items stay in this browser. Nothing is submitted.
Why this matters
Tracking incidents aids transparency, accountability, and continuous improvement in reputation management.
Hypothetical standard operating procedure
Adapt this example to your site, access, tools, and change process. It is our suggested procedure, informed by the sources below.
- Create a centralized repository for incident records accessible to relevant stakeholders.
- Log each incident with date, description, impact assessment, and root cause.
- Document all steps taken to resolve each issue including communications and outcomes.
- Assign responsibility for follow-up actions and track compliance.
- Review the register monthly in reputation management meetings to identify patterns.
Watch for
Lack of documentation leads to inconsistent responses and repeated issues.
Definition of done
All reputation incidents are logged with detailed cause, resolution steps, and assigned follow-up actions.
Sources & attribution
Original checklist wording and example SOP by Best SEO Checklist, using source-grounded AI assistance. Editorial contact: Ted Kubaitis, @tedkubaitis on Teams. Check current source guidance before implementation.