Explain the refund plan in the event cancellation notice

When an event is canceled, tell guests what has changed, what will happen to their order, and when they can expect the next update. Put that answer on one current event page and use it as the reference for your direct communications. If a refund decision is still pending, state what your team is resolving and give a date for the update.

Nonprofit event cancellation communication is an operating task that connects the public announcement to the people handling orders. A clear message cannot substitute for reviewing your platform's requirements and your organization's policy.

Confirm the decision your message will describe

Assign one event owner to confirm whether the event is canceled or postponed. If a new date is unconfirmed, do not advertise it as settled. Record the decision time and the person authorized to answer questions about it.

Before drafting, have the appropriate team review the purchase terms, ticket provider's rules, and any applicable obligations. This article does not establish legal refund rights or recommend overriding them. It explains how to communicate the decision your organization is authorized to implement.

Ticket Tailor's cancellation guidance recommends notifying buyers, explaining expected refunds or vouchers where applicable, and closing sales with a canceled status. Check the supported sequence for your own provider rather than assuming every platform handles canceled orders alike.

Write one complete answer

Give the message enough detail for a ticket buyer to understand their next step. Include:

• The event name and date that are affected.
• Whether the event is canceled or moved to a confirmed new date.
• What your approved decision means for tickets and payments.
• Whether the buyer must take any action and by when.
• The next update date and a contact for unresolved questions.

Describe timing precisely. “We plan to submit refunds by Friday” concerns your team's action. “The money will appear on Friday” promises a result outside that action. Use the timing supported by your provider and distinguish submission from completion.

If orders contain optional donations, multiple tickets, or other components, have the order owner check what the decision covers. Do not casually announce that “everything is refunded” while the staff workflow returns only admission charges.

Reach buyers and the people planning to attend

The ticket purchaser may need payment information while each named guest needs to know not to travel to the venue. Use the buyer and attendee distinction to identify both audiences without assuming the purchase email reaches every person who intended to come.

Coordinate the venue, volunteers, speakers, and partners through their own event handoffs. Remove the event from active schedules and update the ticket page, registration links, reminder content, and shared event listings your team controls.

Keep the current explanation visible at the original public URL when possible. Someone opening an old link should be able to find the cancellation and next step, rather than land on an unexplained missing page.

Verify the communication and order work separately

Check which direct messages were delivered and which contacts need another supported route. Keep the exception list restricted to the staff who need it. A drafted or queued message is not evidence that the buyer received the notice.

Separately inspect refund or cancellation status for the affected orders. Your payment-status check explains why the actual payment state matters before money movement; apply your provider's ticket-specific process to these orders.

If a refund fails, assign a person to resolve it and communicate an accurate update. Record order identifiers, current state, and next action. Avoid copying full payment credentials into the cancellation log.

The announcement owner and the order owner should compare their unresolved lists. A guest waiting for information and a buyer waiting for money may be connected to the same order, but they are different completion checks.

Give pending questions a real update date

If you cannot settle every detail immediately, publish what is confirmed and what remains open. Set a time your team can meet for the next update, even if the update will report continued work. Do not leave guests wondering whether silence means the event might still happen.

Before releasing the announcement, ask a colleague to read it with the original ticket confirmation. They should be able to identify the affected event, the payment plan, and the next action without calling the venue. Resolve any mismatch before the message goes out.