Event postponement communication sequence and stakeholder checklist

Approve one source of confirmed facts

Download the editable postponement communication ledger (Markdown, English)

Record the event and original date, the decision owner and time, whether the new date is confirmed, what happens to ticket sales and the next reliable update point. Get ticket validity, refund or travel language reviewed against actual terms before any message. If details are unknown, say so plainly instead of making a provisional date sound final.[2][3]

Identify dependencies, then notify without avoidable delay

Tell the internal response team and operational parties whose actions affect the announcement: venue, ticketing provider, speakers, suppliers and support staff. Confirm who can pause sales, amend venue commitments and answer questions. Some calls can happen in parallel; do not wait for every supplier negotiation before warning ticket holders of a confirmed postponement. Give each audience its own action owner and channel.[2]

Send a direct ticket-holder notice

Address registered attendees through the platform or contact route actually used for registration. State the original event details, confirmed postponed status, new date only if approved, current ticket position if known, the contact for questions and when or where the next update will appear. Review accessibility and language versions. Verify the reply path and delivery report; sending does not prove everyone received or read it.[1][3]

Align public surfaces and keep a send ledger

Update the event page, ticketing status, calendar/listings, social profiles and on-site signs from the same approved fact sheet. Keep the original event page as a stable answer and reconcile conflicting dates and checkout links. Log the approved text, audience, channel, sender, send time, delivery evidence and next owner. When details change, issue a dated correction and recheck every surface.[1][3]