Workplace communication
Crisis Communication Plan: Prepare a Postponement Update Pack
A crisis communication plan needs a way to verify facts, decide who may approve a message and keep affected audiences updated while answers remain incomplete. This practice pack uses a fictional conference postponement caused by a booking conflict. It is a communication exercise, with no emergency-response instructions.
Establish the verified facts and unknowns
At 09:00 on 15 October, the fictional Cedar Forum event lead confirms that the 20 October conference cannot use its booked venue because of a scheduling conflict. The event is postponed. A replacement date and venue are not confirmed. The booking team is checking existing registration arrangements.
No injury, hazard or emergency is part of this scenario. No refund decision, replacement booking or travel reimbursement has been approved. The ASPR TRACIE resource summary identifies audiences and appropriate messages as planning elements; the facts and update pack here are original.
Assign verification, approval and audience ownership
Original responsibility record
Fact owner: event lead confirms event status and any replacement arrangements.
Registration owner: booking coordinator checks affected registrations and collects individual questions.
Message approver: event director signs off verified public updates.
Publisher: communications coordinator updates the event page and sends the approved attendee message.
Audiences: registered attendees, speakers, exhibitors and public enquirers; each receives the relevant approved status and contact route.
Issue a first message that carries uncertainty accurately
The message gives a concrete consequence for the old date without promising an unapproved solution. It does not say registrations transfer automatically or that refunds will occur. Those are separate decisions requiring verified facts and the appropriate owner.
Original first update, approved at 09:30
“Cedar Forum update — 15 October 2026, 09:30. The conference planned for 20 October is postponed because of a venue scheduling conflict. A new date and location are not yet confirmed. Please do not travel to the original venue for this event on 20 October. We are reviewing existing registrations and will publish the next update on our event notice by 14:00 today, even if replacement details remain unconfirmed. Registered attendees may reply to their registration message with booking questions. The event notice is the current public status record.”
Make the next update even if the answer is incomplete
At 13:30 suppose the director confirms that no replacement date is approved. The promised 14:00 update should report that status and a new realistic checkpoint rather than disappear until there is good news.
This fictional commitment assumes an owner is available to meet it. Choose an achievable time before publication. A promise to update is itself information that recipients can rely on for when to check again.
Original second update, 14:00
“Cedar Forum update — 15 October 2026, 14:00. The conference remains postponed. A replacement date and venue are still unconfirmed. The booking coordinator has received attendee questions; no change to registration arrangements is announced in this update. The next public status update will be posted by 12:00 on 16 October. Earlier event listings should link to this current notice.”
Keep channel versions and question status aligned
Record message version, approval, publication time and which audiences were contacted. Mark old event-date listings as superseded and direct them to the current notice. A sent email alone does not establish that a speaker’s old listing was corrected.
Keep individual booking details in the appropriate private record, separate from the public status summary. Review recurring questions for missing public information, but verify answers before adding them. This pack manages uncertainty and ownership; it does not guarantee trust, prevent reputational harm or determine any attendee’s contractual entitlement.
Questions, answered
Should the first update wait until every detail is known?
In this fixture, the confirmed postponement affects attendance now. The message states that fact while clearly separating unresolved arrangements.
What if no replacement is confirmed by the promised update?
Publish the verified current status at the promised checkpoint and state the next owned update time.
Sources and examples
ResumizeAI team. Examples are fictional teaching material, not customer results. Replace sample details with your own facts.
Your experience. A complete resume.
Build in Resumize with ATS-friendly templates, guided editing and a live preview. Start free, then upgrade when you need more.
Free account required. Free-plan PDF exports include a watermark.