# Post-Incident

After the incident is resolved, effective communication remains essential to maintain trust, provide transparency, and support continuous improvement. This chapter outlines how to communicate with stakeholders once the immediate crisis is over.

## Share Root Cause & Next Steps

Once services are restored, communicate the outcome of the incident to all relevant stakeholders. Your message should be clear, factual, and tailored for the intended audience (internal teams, customers, partners, regulators, etc.).

### What to include:

* **Summary of the incident**: What happened, which services were affected, and for how long.
* **Root cause**: Explain (in plain language) what led to the incident. Avoid technical jargon for external audiences.
* **Resolution**: Describe the steps taken to restore service.
* **Next steps**: Outline actions being taken to prevent recurrence (e.g., process changes, system improvements, further investigation).
* **Further updates**: If the root cause analysis or remediation is ongoing, set expectations for when more information will be shared.
* **Support contacts**: Provide information on how stakeholders can reach out if they continue to experience issues or have concerns.

Tip: Tailor the level of detail for each stakeholder group. Internal teams may need a more technical breakdown; external audiences require concise, empathetic, and non-technical explanations.

## 2. Feedback & Communication Review

Invite stakeholders to provide feedback on the incident communication process. This helps identify areas for improvement and ensures future communications better meet stakeholder needs.

### How to gather feedback:

* Include a feedback link or contact in your communications.
* Proactively reach out to key stakeholders (e.g., VIP customers, internal teams) for their impressions.
* Review any questions or concerns raised during the incident for recurring themes.

## 3. Documentation & Accessibility

Ensure all incident communications—acknowledgments, updates, resolutions, and root cause summaries—are archived and accessible for future reference.

### Best practices:

* Store communications in a centralized, searchable repository (e.g., internal wiki, incident management tool).
* Document any changes made to communication templates or processes as a result of lessons learned.

## 4. Proactive Trust-Building

After a major incident, proactive communication helps rebuild trust and demonstrates a commitment to reliability and transparency.

### What to communicate:

* Improvements or preventive measures being implemented.
* Appreciation for stakeholder patience and cooperation.
* Assurance of ongoing monitoring and readiness to respond to future incidents.

Optional: Consider publishing a public-facing summary or blog post if the incident had broad impact.

## Checklist: Post-Incident Communication Tasks

* Send tailored root cause & next steps communication to all relevant stakeholders
* Invite and gather feedback on the communication process
* Archive all incident communications for future reference
* Communicate improvements and preventive measures
* Review and update documentation, templates, and processes as needed

By following these steps, your organization can ensure post-incident communications are clear, comprehensive, and contribute to a culture of continuous improvement.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.statuspal.io/old-2-incident-communication-handbook/post-incident.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.