Social and Community Content

Crisis Social Update

Prepare a concise, time-stamped social update containing confirmed facts, immediate guidance, acknowledged unknowns, source ownership, and the next update.

Free editable Markdown · Crisis communications teams, social media managers, and incident leaders · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Incident control

Incident ID and name: [Internal reference]
Severity and communication level: [Approved classification]
Incident lead: [Name or role]
Fact source: [System, team, or official authority]
Communication owner: [Name or role]
Affected service, place, or audience: [Confirmed scope]
Known start: [Date, time, and zone]
Current phase: [Investigating, responding, monitoring, or resolved]
Restricted details: [Security, privacy, safety, or another]

Public update

As-of timestamp: [Date, time, and zone]
Opening status: [What is confirmed now]
Who is affected: [Known scope and uncertainty]
Immediate action: [What people should do or avoid]
Organization action: [What responders are doing]
Known impact: [Verified effect]
Unknowns: [What is not yet confirmed]
Help route: [Accessible, staffed destination]
Canonical update page: [Stable route]
Next update: [Specific time or condition]

Verification and release

Statement-to-source check: [Owner for each material fact]
Safety review: [Reviewer and result]
Privacy or security review: [Reviewer and result]
Translation status: [Locales and reviewer]
Accessibility check: [Text, links, media, and low-bandwidth route]
Final account preview: [Evidence]
Approver: [Name, role, and time]

Cause and resolution are not stated beyond confirmed evidence.
The timestamp and time zone appear in the published message.
Advice does not exceed organizational authority or qualified expertise.

Sequence and aftercare

Previous update: [Reference and timestamp]
What changed: [New, corrected, or unchanged]
Rumor or misunderstanding to address: [Verified response]
Correction required: [Exact change and destinations]
Monitoring owner: [Channels and hours]
Closure authority: [Role]
Final public state: [Resolved, restored, continuing risk, or another]
Post-incident record: [Archive and review owner]

How to use this template

Confirm incident authority, affected scope, known start, current status, public actions, support routes, unknowns, and prohibited details.
Draft the time-stamped update in priority order: status, affected audience, immediate guidance, organizational action, unknowns, and next update.
Verify every sentence with its named source and obtain the defined incident, safety, legal, or executive approval for the risk level.
Test the final post, links, media, captions, alternative text, translation, account identity, and consistency with the canonical status page.
Publish, monitor interpretation and new evidence, issue versioned corrections, and continue until an authorized closure update transfers ownership.

Establish a single confirmed fact stream

Name the incident lead and factual source before drafting. Capture what is happening, who or which service is affected, when it began, what geographic or system boundary is known, and what the organization is doing now. Label each item confirmed, unconfirmed, superseded, or restricted. Give every update an “as of” time and version. A screenshot in a team chat is not a source unless its owner and context are clear. Separate observed impact from suspected cause, and avoid estimates that the incident team has not approved.

Put useful public action before narrative

Readers in a crisis need to know whether they are affected, what they should do or avoid, where to obtain help, and when reliable information will return. Open with the current status and action. Use short sentences, direct headings, descriptive links, captions, alternative text, translations, and a low-bandwidth text route where needed. Repeat critical instructions rather than asking people to reconstruct them from a thread. Do not use reassuring language that conflicts with uncertainty, promote unrelated products, or send everyone to a support channel unable to handle the volume.

Maintain continuity and corrections

Treat each post as one entry in a versioned sequence. Link to a canonical status page when available, but keep the social update accurate on its own. State what changed since the previous message. Give a next update time even when the likely message is “no material change,” then meet it or explain the delay. Monitor questions, harmful rumors, exposed personal data, impersonation, and accessibility failures. If a fact is wrong, correct it visibly and update dependent languages and platforms. After closure, publish the current state, continuing actions, and where a fuller review will appear.

See the fields in context

Fictional example: community booking outage

Larkspur Rooms, its booking service, and every incident detail are invented.

As of: 14:20 UTC on 12 August, the fictional room-booking website cannot complete new reservations; existing confirmed reservations remain visible.
Guidance: Users are asked not to repeat payment attempts and are given a staffed telephone route for same-day accessibility needs.
Unknown: The team is investigating the cause and does not claim a restoration time.
Next update: A new message is promised by 15:00 UTC even if there is no material change.
Correction control: If existing reservations are later found to be affected, all posts, translations, the status page, and the support script will be updated together.

Frequently asked questions

Should a team wait until it knows the cause?

No, when people need confirmed status or guidance. Publish what is known, identify what remains unknown, and give the next update. Do not fill the gap with a suspected cause.

How often should social updates appear?

Set a cadence based on risk, audience need, and operational capacity. State the next time and meet it. Frequent repetition without new value can obscure important instructions, while silence can create unsafe uncertainty.

Can an old post simply be edited?

Editing may help current readers, but material corrections need visible acknowledgment according to the platform and policy. Preserve a version record and update replies, translations, pinned posts, and linked pages that repeat the error.

What belongs in the closure update?

State the current service or safety condition, the confirmed restoration or continuing limitation, any action users still need, support routes, and where a fuller incident review will appear. Avoid declaring closure before the incident authority does.