Key takeaways
- Prepare the page, roles, approvals, access, templates, fallback hosting, and update rhythm before an incident.
- Separate confirmed facts, what remains unknown, actions people should take, and the time of the next update.
- Use one source-of-record URL and synchronize derivative channels back to it.
- Correct visibly and preserve the reason instead of silently editing a material claim.
01
Silence does not create an information vacuum; it fills one with somebody else
Customers, employees, partners, journalists, and searchers will look for an answer before the organization has a complete one. The useful first update is not a confident reconstruction. It states what is confirmed, what the team is checking, what people should do now, and when they can expect another update.
CDC’s Crisis and Emergency Risk Communication framework emphasizes being first, right, and credible while expressing empathy, promoting action, and showing respect. “Right” does not require pretending uncertainty is gone. It requires verifying what can be verified and labeling the rest honestly.
Swipe to compare every column
| Block | Include | Avoid |
|---|---|---|
| Status | Confirmed event and affected scope | Speculation presented as cause |
| Action | Specific step, audience, deadline, support route | Generic reassurance without help |
| Unknowns | Questions under investigation | Silence that implies certainty |
| Next update | Time or condition for another statement | “We will update soon” with no owner |
02
Build a source-of-record route that works under pressure
Pre-create a fast, accessible incident template with a stable URL pattern, lightweight assets, status, timestamps with time zones, update log, contact, and subscription or support route. Define who can publish if the normal website team is unavailable and how the page will operate when traffic spikes or a primary system fails.
Use ordinary, crawlable HTML for the essential update. Keep social, email, support macros, and partner messages aligned to the source page. Do not make a person watch a livestream or open a PDF to learn whether their service, account, or safety is affected.
03
Verify in parallel, approve by risk
Assign owners for incident facts, customer impact, legal and regulatory review, operational action, employee communication, translation, accessibility, and publication. Use a short approval path for low-risk status facts and a named escalation for claims about cause, responsibility, numbers affected, or resolution.
Record the source and time behind each material fact. Publish a visible correction when a fact changes. Silent edits may be appropriate for a typo; they are poor practice when the number affected, recommended action, or explanation changes.
04
Recover the information system after the incident
When the incident closes, publish the final status and link a fuller review if appropriate. Keep the incident URL available, remove urgent actions that no longer apply, and make the historical state clear. Ask search engines to recrawl only after the source page itself is accurate and internally linked.
Review time to first verified update, update cadence, correction rate, page availability, support deflection, accessibility, translation lag, repeated questions, harmful misunderstanding, and trust feedback. Do not turn a crisis scorecard into a contest for the fastest unverified sentence.
Primary sources and further reading
Use the source material to validate details against your own context and current platform configuration.
- CDC: Crisis and Emergency Risk Communication manual
- CDC: Crisis communication plans
- Google Search Central: Ask Google to recrawl URLs
This field note follows the XenGrowth editorial policy: primary sources where available, visible limitations, material review dates, and no invented first-hand experience.
Stay with the problem
