Event postponement emails: templates for keeping ticket buyers informed

Your event postponement email should say that the original date is off, explain what happens to existing tickets, and give buyers a clear next step. If you haven't confirmed a new date, say so and tell them exactly when you'll update them again. You can be honest about the uncertainty without leaving everyone guessing.

So you've got an event to move. You're dealing with the venue, the programme, suppliers, and the money you've already spent. Meanwhile, someone who bought a ticket is wondering whether to cancel their train. They don't need the whole story of your afternoon. They need enough information to make their own decision.

That's what we're going to write. Below you'll find templates for a confirmed replacement date, a date you're still working on, a follow-up when there's no answer yet, and the questions that arrive afterwards. We'll also cover who needs each message and how to keep old reminders from sending people to the wrong place.

First, work out what you can actually tell buyers

Before you open the email builder, get the confirmed facts together. You don't need a long meeting. You do need someone who can make a decision about tickets and someone who knows what has been agreed with the venue.

Start with the original date and what you're asking people to do about it. Is the event definitely not happening that day? If yes, say that plainly. "We're reviewing our schedule" leaves room for a buyer to think they should still show up.

Then check the replacement date. A venue holding a slot for you isn't the same as a confirmed booking. If the date depends on an artist, licence, or supplier who hasn't agreed yet, don't put it in the announcement as a fact. You can explain that you're arranging a replacement without promising the weekend you hope to get.

Next, settle what happens to the ticket. Can someone use the same ticket at the replacement event? Will they receive a new one? Do they need to accept the change? Those are different instructions. Your email should contain the instruction your team has actually checked, including how it works for reserved seats and add-ons.

The refund paragraph needs the same care. Your published policy, the ticket terms, and the rules that apply where you operate all matter. Don't paste a "no refunds" line into a postponement announcement because it appears in your normal checkout terms. A change to what you sold can raise different questions.

For example, the Australian Competition and Consumer Commission explains that refund rights when an event changes depend on the circumstances. Its guidance distinguishes changes made by the organizer from changes caused only by others, and says consumers are entitled to a refund when the organizer makes a major change. That's Australian guidance, not a worldwide rule. Check the requirements relevant to your event before you promise, limit, or refuse a remedy.

Have that decision reviewed by whoever owns your terms and customer obligations. Then give the communications team approved wording they can use consistently. Our guide to writing an event refund policy is useful preparation, but a policy page doesn't settle every postponement situation by itself.

Finally, choose the next update time and the person responsible for sending it. "We'll be in touch soon" sounds harmless when you're writing it. It becomes frustrating when you're the person refreshing your inbox.

Tell people early enough to change their plans

Once you know the original event won't happen, buyers need that information even if the replacement plan is unfinished. Waiting for a nicer announcement can leave them booking accommodation or arranging childcare for a date you've already ruled out.

Give them the confirmed part first. You can follow with the missing details later. That doesn't mean sending every rumour from your planning chat. It means separating a decision you've made from a decision you're still making.

If the event is close, email may need help. Update the event page, pin a notice on the channels people use to find you, and contact the venue so its team gives the same answer. Use another permitted contact method where you have one and the situation warrants it. Don't assume a social post reaches everyone who paid.

Check the places where the old date can keep appearing. Your scheduled reminders, paid adverts, promoter messages, calendar invitations, and ticket instructions may each have their own copy. Pause or change those messages as part of the postponement work. Otherwise you can send a careful update in the morning and an automated "see you tomorrow" in the evening.

You also need to think about the people who bought together. The order buyer might be the only person whose email you hold, while several friends have tickets in that order. Ask the buyer to share the update with their group. If your system holds attendee contact details, check which people you can reach directly and which ticket holders rely on the buyer.

Don't claim everyone has been informed because your campaign says "sent." Some addresses may be wrong or undeliverable. A public notice gives those people somewhere to check, and your support team can help with individual orders. Keep that page easy to find from the event listing.

Build the email around the buyer's questions

The most useful layout is usually a plain email with a clear heading and short paragraphs. You don't need a dramatic graphic to explain that a date has changed.

Put the event name and "postponed" in the subject. Use the preview text to explain whether the replacement date is confirmed. The sender should be recognizable, and the reply address should lead somewhere your team checks.

In the opening paragraph, name the event and original date. Then state the replacement date or say you haven't confirmed it. You can apologise in the same paragraph. "We're sorry for the disruption to your plans" is enough to get started. Save the detail for the sentences that help someone act.

Give a short, accurate reason if you can. "The venue cannot open on the original date" tells people more than "unforeseen circumstances." If you're dealing with a private medical matter, you don't have to disclose it. Say what you can confirm without inventing a reason that sounds less awkward.

Then explain the ticket status, the options available, and how to get help. If someone must take action, give them the link and the relevant deadline. If they don't need to do anything, say that too. A missing instruction creates work because buyers have to ask whether they've missed something.

Keep the detailed FAQ on one current page, with the essentials in the email itself. A person should understand whether to attend, whether their ticket works, and where to get help without opening several links.

The GOV.UK guidance on writing for user interfaces recommends accounting for people who won't read everything in detail. The same practical idea applies here. Someone checking your message between meetings should be able to spot the changed date and the action they need to take.

Template when the replacement date is confirmed

Use this version when the venue and programme arrangements are confirmed enough for you to announce the new event. Replace every bracketed field. The ticket and refund paragraphs must reflect the options you've approved, rather than whichever wording is easiest to send.

Subject: [Event name] postponed to [new date]

Preview text: Your ticket arrangements and options for the new date.

Hi [first name],

[Event name] will no longer take place on [original date]. The event will now take place on [new date] at [venue], with doors opening at [time and time zone].

We're sorry for the disruption to your plans. We've moved the event because [short confirmed explanation].

[Confirmed ticket instruction. For example, if verified: Your existing ticket remains valid for the new date. You don't need to buy another ticket or contact us to keep your booking.]

If the new date doesn't work for you, [approved options and how to use them]. You can find the full details at [buyer information link], including [applicable deadline, if any].

[Any confirmed changes to venue, programme, reserved seats, access arrangements, or purchased add-ons. Delete this paragraph if nothing relevant has changed.]

Please update your calendar and share this message with anyone whose ticket you purchased.

If you have a question about your order, reply to this email with your order reference. Our team will [confirmed response expectation].

Thank you,

[Name] [Event team]

Notice that the template doesn't say "we can't wait to see everyone there." You can be warm, but you don't know yet whether everyone can make the replacement date. A buyer with a shift booked that evening needs to see their options without feeling pushed to keep the ticket.

If there are significant programme changes, include them near the new date. Someone who bought for a particular speaker or performer shouldn't have to read a long FAQ to discover that person is no longer appearing.

Be equally specific about location. "Same venue" is useful only if the event really remains in the same building and room. When the address changes, give the new address and check transport, parking, and accessibility information before reusing the old instructions.

Template when you haven't confirmed a new date

This is the message people tend to put off because it feels incomplete. Send it when the original date is definitely off. Buyers can adjust their immediate plans while you work on the replacement.

Subject: [Event name] is postponed: please don't attend on [original date]

Preview text: We're arranging a new date and will update you by [date and time].

Hi [first name],

[Event name] will not take place on [original date] at [venue]. Please don't travel to the venue for the original event.

We're sorry for the change. [Short confirmed explanation.]

We haven't confirmed a replacement date yet. We're currently [specific work you can accurately describe], and we'll email you again by [date, time, and time zone], even if the new date is still being arranged.

Your booking is currently [confirmed status]. [Explain what buyers should do with their ticket now, without promising that it will work for an unconfirmed replacement.]

Your current options are [approved options and the process for using them]. Details are available at [buyer information link].

If you need help with your order, reply with your order reference or contact [support address]. Our team will [confirmed response expectation].

Please share this update with anyone whose ticket you purchased. We'll keep the latest information at [event update page].

Thank you,

[Name] [Event team]

The next update deadline is a promise about communication. You control sending that email even when you don't control the venue's answer. Choose a time you can meet, put it in the team's calendar, and assign someone to cover it if the usual owner is busy.

Don't write that refunds will become available only when you announce the date unless that position has been checked against the applicable terms and rights. The absence of a replacement date doesn't automatically justify making someone wait indefinitely.

Template when the promised update arrives and you're still waiting

Nobody enjoys writing a second email that says the date is still unresolved. But if you promised an update, send it. The buyer should learn what's happening from you before they have to chase.

Subject: Update on the postponed [event name]

Preview text: The new date is still being arranged. Here's what we can confirm.

Hi [first name],

We promised to update you by [previous update deadline] about [event name]. We haven't confirmed the replacement date yet.

We're waiting for [specific confirmed outstanding decision]. [Explain any progress that materially affects buyers, if there is any.]

The event will not take place on the original date of [original date]. Your booking remains [confirmed current status], and your current options are [approved options]. You can use [link or contact route] if you want help with your booking now.

We'll send the next update by [new date, time, and time zone]. If we confirm the replacement before then, we'll let you know sooner.

We're sorry you're still waiting for a firm date. Please reply with your order reference if you have a question we haven't covered.

[Name] [Event team]

Make the progress paragraph earn its place. "We're working hard behind the scenes" doesn't tell someone whether they should change a booking. "The venue has confirmed availability, and we're waiting for the revised programme agreement" gives a clearer account if that's really where you stand.

After repeated delays, review the event decision itself. A better email can't make an unworkable replacement plan work. Your team may need to offer a different remedy or cancel the event, depending on the situation. When it becomes a cancellation, use clear cancellation wording and the appropriate options. Our event cancellation email templates cover that change in message.

Template for confirming the date after a pending announcement

Use this when buyers already received the notice that the event was postponed without a replacement date. Refer back to that notice so they understand what has changed. You don't need to make them read the whole story again.

Subject: New date confirmed for [event name]

Preview text: Your postponed event will take place on [new date].

Hi [first name],

Following our postponement announcement, we can now confirm that [event name] will take place on [new date] at [venue]. Doors open at [time and time zone].

Thank you for waiting while we arranged the replacement. We're sorry for the disruption to your original plans.

Your booking is [confirmed current status]. [Give the verified instruction for using the existing ticket, receiving a replacement, or confirming attendance.]

If you can't attend, [approved options, request route, and any applicable deadline]. The details are at [buyer information link].

[State any other confirmed changes that affect what the buyer purchased.]

We'll send your arrival information by [confirmed update date]. If you need help before then, reply with your order reference or contact [support address]. Please share this update with your group.

[Name] [Event team]

Send this to the current affected ticket holders, with wording that fits their current bookings. Someone who received a refund while you were arranging the date shouldn't receive instructions suggesting their refunded ticket is still valid.

Before sending, update the public event notice too. A buyer may open the email, follow the link, and see the earlier pending-date announcement. Put the confirmed date at the top so the page supports the email they just received.

Template for a buyer who can't attend the new date

This reply should help your team handle the request consistently without treating the customer as a problem. They bought the event you originally offered. Their diary may not fit the event you can now deliver.

Subject: Your booking for [event name]

Hi [first name],

Thanks for getting in touch. I'm sorry the new date doesn't work for you.

For your order [order reference], the options available are [confirmed options that apply to this order].

To choose [option], please [specific instruction]. [Include a deadline only if it applies and has been checked.]

[If a refund has already been approved: We've approved a refund of [amount and currency] for [items covered]. It will go to [verified payment destination]. We expect [confirmed processing information], and we'll contact you if there's a problem.]

If your circumstances aren't covered by the information above, reply here and we'll review your request.

[Name] [Event team]

Use the approval paragraph only after you have actually approved the refund. If you're reviewing the request, say you're reviewing it and give a realistic reply time. "Your refund is being processed" means something different to "we've received your request."

Don't ask buyers to send full payment card details by email. Use your established order and payment process. If you need more information to locate the booking, explain what you need and provide the appropriate route.

Also check what the order includes. Admission, reserved seating, merchandise, parking, and another separately supplied service may need different handling. Explain the actual amount and items in an individual confirmation so the buyer doesn't have to guess whether something is missing.

Make the ticket options easy to compare

Where buyers have a choice, list the choices in the same order everywhere. Explain who each option is for, what someone needs to do, and what happens afterwards. Avoid giving the preferred commercial outcome a huge button while hiding the other available options in small print.

For example, a replacement-date email might offer keeping the booking and requesting a refund. Another event may have an approved transfer option. Only describe an option you can fulfil, and don't present a credit as though it's interchangeable with a refund where a refund is required.

Keep deadlines precise. "Respond by Friday" can be read later in a forwarded message, or by someone in another time zone. Write the full date and the time zone when a cutoff matters. If different orders have different rules, direct each buyer to the information relevant to their booking.

Ask your support team to test the process before the message goes out. Can they open the link without an organizer login? Does the form recognize a valid order? Does the confirmation explain what happens next? A beautifully written email with a broken request form creates a queue of frustrated replies.

Keep the postponement update separate from promotions

A postponement email goes to people who need information about something they've already bought. Adding an offer for your next event can change the nature of the message and distract from the information they came to read.

The UK's Information Commissioner's Office explains that service messages contain information rather than promotion. Its guidance warns that adding promotional content means the message is no longer simply a service message. Keep the postponement notice focused on the booking.

In the US, the Federal Trade Commission's CAN-SPAM guidance on transactional and commercial email says the primary purpose of the message matters and treats transactional categories narrowly. These are different legal frameworks, so don't copy one jurisdiction's rule into another. The useful writing decision is straightforward. Put the event change and the buyer's options first, and send promotions through the appropriate marketing process.

This is where connected ticketing and email can help. Loopyah's attendee email tools distinguish updates about an event someone has paid for from offers, and handle recipient selection accordingly. You write the update; the product helps direct it to the relevant people. You still need to provide accurate event details, approved buyer options, and a working support route.

Don't turn that capability into a claim that every person has read the email or that a template guarantees compliance. You need to review the actual message and follow up on delivery problems. Keep the current event notice available outside the inbox too.

Give buyers the details in readable text

Your event brand can stay in the message. Just don't make an image carry all the information. Some buyers won't load images, and others use tools that read the email aloud. The original date, new date, ticket status, and action link should remain readable text.

The World Wide Web Consortium's guidance on informative images explains that text alternatives should communicate the information an image conveys. For a postponement email, the easiest approach is often to write the essential information directly in the message and use graphics sparingly.

Give your links descriptive names. "View your ticket options" tells someone more than "click here." If you use a button, make sure the surrounding paragraph explains the action and any deadline. Check the message on a phone before sending. That's often where someone will decide whether they need to reply.

For translated messages, have a competent reviewer check the action wording as well as the announcement. A correct translation of the reason won't help if the ticket instructions are ambiguous. Date formats deserve attention too. Writing out the month can avoid confusion between day-first and month-first formats.

Keep the current update page accessible without requiring a social account. If buyers have to sign in somewhere, explain why and test that journey with a buyer account. Your organizer view can hide problems that only appear on the customer side.

Check the audience before you send

Select the people affected by this specific event and date. If you run several nights under one event brand, the postponement may affect only one performance. Sending it to every past buyer creates unnecessary questions and can make people think another booking has changed.

For an event with several ticket types, check whether the core instruction is the same. General admission buyers might keep their tickets while reserved-seat buyers need a separate explanation. Use a shared announcement where the facts are shared, then provide the relevant detail for the orders that need it.

Check transfers and refunded orders as well. The person holding a ticket now may differ from the original purchaser. Someone whose order was already fully refunded may need different wording from a person whose booking is active. Confirm what your ticketing system records before you decide who gets which message.

Keep a copy of what you sent and when you sent it, with the audience selected and the approved options. Your support team can then answer from the actual announcement rather than remembering a planning discussion. If you discover a mistake, record the correction and tell the affected people clearly.

Send the revised reminder when the event is ready

Once the replacement event is confirmed, the reminder needs fresh information. Don't reuse the original message with a date swap and assume the rest still works. Doors, transport, programme, access arrangements, and ticket delivery may have changed while you were reorganizing.

Our event reminder email guide can help with the final attendance message. For a postponed event, begin by identifying the confirmed replacement date so someone who remembers the earlier notice can see which arrangement is current.

If an old ticket is still valid, repeat that verified instruction. If a new ticket replaces it, explain which one to use and where to find it. Tell buyers how to get help before doors open, particularly if the ticket delivery method changed.

You can also remind the order buyer to share the arrival details with their group. Keep that request friendly and specific. They may have forwarded the first announcement weeks ago, and the rest of the group may never have seen the replacement-date email.

If you need to correct something after sending, name the correction in the subject and repeat the accurate instruction in the first paragraph. Don't quietly edit the event page and assume everyone will notice. Someone may have forwarded the original email to friends or saved a screenshot of it.

For example, if you gave the wrong door time, say which time was wrong and which time now applies. Keep the explanation brief. If the correction affects only one ticket type, reach those buyers directly rather than sending unrelated customers another announcement.

Have the support team use the corrected wording immediately. Check any scheduled follow-ups too, so the same mistake doesn't appear again in the replacement reminder. Save both announcements with their send times for future support reference.

Review the email with someone who bought a ticket in mind

Before sending, ask a colleague to read the message as a buyer who hasn't been in your planning conversations. Can they tell whether to attend on the original date? Do they know what happens to their ticket? Can they find an option if the new date doesn't suit them?

Have them follow each link and reply to the test email. Check the subject, preview text, and sender together. If the subject says "new date confirmed" while the body says you're still arranging it, fix the subject before anyone sees it.

Also check that the support team knows which requests it can resolve and which need a manager, so buyers receive an answer without unnecessary handoffs.

Read the apology aloud. If it sounds like a statement from a company trying to avoid a difficult conversation, rewrite it. You can acknowledge the inconvenience without making promises about costs, compensation, or timing that your team hasn't approved.

The same goes for the close. Buyers don't need pressure to "support the event community" when they're trying to recover the cost of an evening they can no longer attend. Explain their available options, answer their questions, and let them decide.

A good postponement email leaves someone knowing what changed and what they can do next. Send the confirmed facts promptly, keep the ticket instructions accurate, and make the next update a promise your team will keep. That's how you make a difficult change easier for the people who paid to be there.