How do you communicate an event policy change after selling tickets?

So you've sold tickets, your event is going ahead, and the venue tells you a rule has to change. Maybe people can no longer leave and come back. Maybe an included service has disappeared. You can update the event page in a few minutes, but the people who already paid are still planning around the original promise.

Tell those buyers exactly what changed, how it affects their booking, and what they can do about it. Before sending the announcement, agree the practical arrangements and check their rights. A well-written email won't help someone who arrives with a perfectly reasonable expectation that your entrance team has been told to refuse.

The first thing you want to do is compare the new rule with what you actually sold. Then decide whether you can preserve the original arrangement, provide a suitable alternative, or offer the refunds or other options the situation requires. Explain that decision directly, with a working contact route for people whose circumstances need attention.

This guide covers policy changes while the event itself remains scheduled. We'll work through a fictional re-entry change, write the buyer message, and follow it through support, ticket records and the entrance briefing. The aim is to make a difficult change understandable and workable, without pretending that a notice gives you permission to rewrite every purchase.

Start with the promise the buyer received

Before anybody drafts the announcement, collect the information that was available when tickets were purchased. Read the event page, ticket description, confirmation and relevant terms. Check messages your team sent in response to individual questions too. A public page might say one thing while a buyer has an email giving a more specific assurance.

Save the versions you can establish, with their dates. Keep the original evidence rather than replacing it with today's corrected page. If a buyer later asks why they were refused something they paid for, you need to understand their purchase, not just repeat the wording currently online.

Write the old arrangement and proposed arrangement in ordinary language. For example, "Ticket holders could leave and return until 9pm" and "The venue now proposes no re-entry after admission." That comparison shows the actual change. "We're updating our admission procedures" tells your colleagues very little and your customers even less.

Then establish whether this is a new requirement, a correction to inaccurate information, or a clarification of an existing rule. Those descriptions have consequences. If your original wording permitted re-entry and you're removing it, calling the announcement a reminder is misleading. If the venue always prohibited re-entry but your page promised otherwise, the buyer still received the promise your business published.

Include every authorised seller and partner whose description may differ. A change approved by the promoter won't necessarily update the venue's page, an affiliate's listing or a confirmation already sitting in someone's inbox. Give one person responsibility for gathering those versions and coordinating corrections.

This record doesn't have to be elaborate. It needs to show what buyers were told, which sales were affected, the proposed change, and who is deciding what happens next. You'll use it to brief the team and resolve individual cases consistently.

Decide how much the change affects attendance

A policy can sound minor inside an event business and make the booking unusable for a customer. Re-entry might be an administrative detail to your team. To someone who arranged to leave for a caring responsibility and return for the main performance, it may determine whether they can attend at all.

Ask what the new arrangement requires the buyer to do differently. Does it change what they can bring, when they must arrive, whether they can access the activity, or what is included in their price? Does complying require more money, different transport or a personal arrangement they cannot reasonably change?

Consider the effect on different ticket types. Removing an included lounge affects someone who bought that benefit differently from a general-admission customer. A restriction that applies only to one room may still affect everyone whose programme includes it. Don't choose the email audience until you've worked through those connections.

You also need to check whether people bought before or after the new information became available. The event date alone won't identify the relevant bookings. A later buyer might have purchased through an old partner page, while an earlier buyer may already have agreed a specific alternative. Use the sales records and the information each route supplied.

Bring your access lead into the discussion when a rule affects disability-related needs. Don't assume that publishing the same instruction for everyone produces a usable arrangement for everyone. Ask the responsible people to review the proposed policy and its exceptions under the requirements that apply to your event.

Where the issue concerns a new bag restriction, our guide to writing an event bag policy covers the practical decisions about essential belongings, storage and checks. Here, your additional job is dealing with people who bought under the earlier arrangements.

Check what you can change before deciding what to say

Your team may have a sound operational reason to change a rule. You still need to establish what that means for the sale you've already made. Keep those questions together during the decision, rather than approving the restriction first and asking customer support to defend it afterwards.

For UK consumer contracts, the Competition and Markets Authority's guidance on fair customer contracts explains that a change clause is unlikely to be fair if it gives a business unrestricted power to impose higher costs, new requirements or reduced benefits. It also discusses advance warning and a genuine ability to leave without penalty. A broad sentence reserving the right to change things should therefore prompt review, rather than end the conversation.

For Australian events, the ACCC's guidance on selling event tickets says consumers are entitled to refunds where the organizer chooses to make a major change. It distinguishes changes caused solely by third-party actions and notes that other rights can apply. The cause and significance matter; don't translate this into a worldwide promise about every policy adjustment.

Have the person responsible for your terms and consumer obligations assess the actual change in your jurisdiction. Give them the original descriptions and the proposed response. Ask a specific question about affected purchasers, required refunds or other remedies, suitable notice and any conditions you intend to impose.

Avoid writing "no refunds" while that assessment is unresolved. Equally, don't announce a universal refund arrangement before finance and the ticket seller have confirmed how it will work. You can tell buyers what is known and when the remaining answer will arrive, provided the uncertainty is real and somebody is responsible for resolving it.

An organizer's refund policy is one part of the assessment. Our event refund policy guide can help you review that wider arrangement, but the question here starts with a change made after purchase. A customer's ordinary change of mind and your decision to alter the delivered event deserve separate consideration.

Agree an arrangement your team can actually deliver

Start by asking whether the original promise can safely and lawfully remain available to existing purchasers. Sometimes the proposed restriction is a preference, and retaining the earlier arrangement for affected bookings is feasible. Sometimes the venue, licensing conditions or safety assessment prevents that. Get a definite answer from the responsible lead.

Don't promise an exception that security has not approved. If a restriction is necessary for safety, customer-service staff cannot solve the problem by privately telling selected buyers to ignore it. The alternative may need a different operating arrangement, another performance or an appropriate refund. Confirm what is possible before giving people a choice.

If you propose a substitute, explain what it actually offers. A voucher for another date may be useful to one person and useless to someone who travelled for this event. An alternative service on the other side of town might add cost and time. Describe those differences instead of treating the original benefit and the substitute as automatically equivalent.

Decide who pays any extra charge created by the replacement. If an included service becomes a paid external service, you haven't preserved the promise merely by finding a supplier. Review the total effect on the purchaser and confirm the approved financial response before linking to that supplier.

Where a refund or cancellation option applies, specify the eligible booking, covered amount, process and payment destination. Check fees, bundled extras and partially refunded orders individually where necessary. The choice between credit and money should reflect the customer's applicable rights and your approved offer, rather than whichever is easier for your cash flow.

Name the person who can decide unusual cases. Support staff need the authority to apply the agreed arrangement and a clear route for anything outside it. An inbox full of requests awaiting an unnamed manager is not a functioning option, however reassuring the email sounded.

Work through a re-entry change from sale to announcement

Consider a fictional paid evening event called Harbour Sessions at the Foundry Hall. Its published information allowed ticket holders to leave and return until 9pm. The event is on Saturday 15 May 2027, with doors at 6pm and the final performance ending at 11pm. All times in this example are local venue time.

On Monday 10 May, the venue confirms that its revised security arrangements will not permit public re-entry for this event. The organizer checks the decision with the venue and security leads. They confirm that retaining the original re-entry promise for earlier buyers is not an approved option. The date, programme and ordinary first admission remain unchanged.

The organizer now has a customer problem to resolve. Some buyers may have planned to leave for food, collect something or attend to a personal responsibility. Asking them to discover the restriction at the exit would deny them the chance to make another plan while they still can.

For this fictional example, assume the organizer has completed the relevant obligations review and approved a clear offer. Purchasers affected by the revised rule can cancel their affected unused tickets for a refund of the amount they paid for those tickets, including associated mandatory booking fees. The team can also consider cancellation of selected unused tickets within a group order.

These are invented arrangements for explaining the workflow, not terms to copy without checking your own event. The organizer confirms funding, seller responsibilities and how previously issued refunds will be accounted for. It also agrees how the ticket status will change so a refunded ticket cannot remain available for admission.

The support team asks customers to contact it by noon on Friday 14 May where possible, so cases can be handled before doors. That is a planning request in this example, not a statement that applicable rights expire at noon. Later cases still have a monitored route, and the message makes that clear.

Before sending, the organizer checks the remaining practical questions. Where can people buy food inside? Are essential-item and access arrangements still usable? Who answers a purchaser who bought for someone else? If the change exposes another barrier, the team has to address it rather than hide it behind a narrow re-entry explanation.

Write the email in the order the buyer needs it

Your subject should identify the change and the event. "Harbour Sessions: re-entry has changed" is more useful than "Important information from our team." The person should understand why this message matters before opening it, particularly if they have already read an earlier arrival guide.

In the opening, state the old and new arrangement. Explain whether the event is still going ahead and name anything that remains unchanged only where it resolves a likely concern. Buyers don't need a long inventory of unaffected details. They do need to know whether the new restriction changes the plan they made.

Give the reason briefly, using facts the responsible lead has confirmed. "The venue has revised its security arrangements" may be enough when it accurately describes the decision. Don't add unverified claims about legislation or disclose sensitive security information to make the explanation sound more convincing.

Next, explain the effect and the available choice. Use direct language about leaving, returning, requesting help or cancelling affected tickets. If the buyer must take action, name that action and the route. If no action is required to keep a usable booking, say so without implying that silence waives any rights.

Finish with the support contact and any genuinely necessary follow-up. A person reading on a phone should be able to answer what changed, whether they can still use their ticket, and what to do if they can't. Your explanation can be calm and considerate without making the reader search through your apology for those answers.

Put the essential information in readable text, with useful headings and descriptive links. The W3C's accessible writing guidance recommends clear instructions and link wording that describes the destination. A graphic saying "policy update" cannot carry the only explanation of a restriction somebody needs to follow.

Example email for the confirmed re-entry change

The message below uses the fictional arrangements above. Replace the event details, reason and buyer options with approved facts. The contact instructions describe a reply to the real sender; your own message needs a monitored reply address and staff ready to answer it.

Subject: Harbour Sessions on 15 May: re-entry has changed

Preview: Once you leave, you won't be able to return. Here's what to do if this affects your booking.

Hi Sam,

We're writing about your Harbour Sessions tickets for Saturday 15 May at the Foundry Hall. The event is going ahead, with doors at 6pm and the programme ending at 11pm.

When you bought, our information said you could leave and return until 9pm. This has changed. Once you've entered and then left the event, you won't be able to come back in.

The venue has confirmed this restriction following a revision to its security arrangements. We're sorry this changes the plans you may have made around our original information.

If you can attend under the revised arrangement, your existing unused tickets remain valid. You don't need to exchange them or reply just to confirm you're coming. First admission is still available under the event's published arrival arrangements.

If the change means you cannot use your booking as planned, reply to this email with your order number and tell us which unused tickets are affected. We've approved cancellation and a refund of the amount paid for those tickets, including their mandatory booking fees. You can ask about selected tickets within a group order.

Please contact us by noon on Friday 14 May where possible so we can help before the event. This is a planning request and does not limit your applicable rights. If you contact us later, our support team will still review your case, including during admission on Saturday.

We will confirm the affected tickets and refund amount with you. We will also explain the payment status and expected timing for your payment method. This email is a notice of the change; it is not confirmation that a refund has already been submitted.

Please share the re-entry information with anyone attending on your booking. Share the public update rather than private order links or ticket barcodes.

Reply here if you need help planning around the restriction or discussing an access requirement. Our booking team is monitoring replies and will answer within one working day. On Saturday, the team will monitor this inbox from noon until 11pm for event-day questions.

We're sorry we couldn't keep the original re-entry arrangement.

Alex, Harbour Sessions booking team

The useful part of this email is the sequence. It admits that the original information was different, describes the practical consequence, and gives the purchaser a usable route. It also separates the event-wide notice from an individual refund confirmation. You should only promise its response times if your staffing can support them.

If the full response isn't ready, say what is known

Sometimes you need to warn buyers before every alternative has been confirmed. People may be booking travel or preparing something the new rule affects. Waiting for a perfect email can leave them making decisions from information you already know is wrong.

Separate a confirmed restriction from a possible one. If the venue is still assessing a proposal, don't describe it as a final rule. If the restriction is confirmed but your response for affected buyers remains unresolved, explain both facts without implying that the unresolved part has been settled against them.

For example, an initial notice might say, "The venue has confirmed that public re-entry will not be permitted at Harbour Sessions. Our earlier information allowed re-entry until 9pm. We are confirming the arrangements for purchasers whose plans are affected and will email you by 5pm on Tuesday 11 May, local venue time. Please reply now if this affects an urgent travel or access decision."

That wording gives people a factual warning and names the answer still owed. It should not become your final response. Assign the follow-up to a person with access to the venue decision, the terms review and the seller's payment process. Set the update time according to what the team can genuinely establish.

If the promised time arrives and something remains unresolved, send the update anyway. Explain the specific issue, what you're doing about it and the next time buyers will hear. Don't restart the clock with another vague "more information soon" message while people continue spending money on plans you cannot confirm.

For a change close to doors, confirm whether it is responsible to keep selling tickets while essential information or a workable arrangement is missing. The decision belongs with the accountable event team. A disclaimer at checkout is not a substitute for an offer you can describe accurately and deliver.

Keep the policy update separate from selling

This message concerns a booking somebody has already paid for. Send it to the affected booking audience, including the relevant holders who never joined your newsletter. Don't use your ordinary promotional audience as a shortcut and assume every purchaser will be there.

The UK's ICO distinguishes administrative service messages from direct marketing. Its guidance explains that adding promotional content can make a service message count as marketing. For this kind of update, keep the content about the existing booking and the change. A discount for next month's show can go in a separate, appropriately addressed campaign.

With Loopyah's attendee email tools, event updates and promotions are handled as different kinds of messages. The product connects contacts to ticket purchases and provides a test send, so you can prepare the update around the paid event and check it before sending. Your team still has to approve the rule, buyer options and actual wording.

Check the selected event and relevant ticket holders before release. If only a premium benefit has changed, an event-wide message can confuse people who never bought that benefit. You may still need a general explanation where the change affects shared facilities, but keep private payment information with the correct purchaser.

Our broader event email marketing strategy explains how promotions and booking updates fit together over an event campaign. Here, success means people receive and understand a usable change notice. A sales result is not the right test for whether you've dealt properly with existing purchasers.

Don't describe a sent message as proof that everybody knows. Bad addresses, spam filtering and group bookings can interrupt the route. Keep an appropriate public version of the update available, and plan how to help people who first learn about the change through another channel.

Account for group bookings and transferred tickets

The person who paid may not be the person arriving. A purchaser can buy tickets for colleagues, friends or family and pass on only the practical arrival details. If those details change, the other attendees may never see the message sent to the original buyer.

Use the current booking and attendee information your business legitimately holds. Ask purchasers to share the public update with their group, while also using appropriate direct attendee contact routes where available. Give them a short explanation that can be forwarded without exposing a payment history or a private order-management link.

Keep decisions about money with the authorised person and the actual payment record. An attendee's request to cancel their place does not automatically establish where a refund belongs. The seller needs to verify the order, the affected ticket and the applicable process before moving money or cancelling admission rights.

Transferred and resold tickets need particular attention because the buyer and holder can have changed. Confirm the supported route with the seller handling that transaction. Avoid promising that money will go directly to the person who writes to support when your system or agreement sends it elsewhere.

In a group order, ask exactly which tickets the purchaser wants the team to review. If only one person cannot attend under the revised arrangement, cancelling the whole order can create another avoidable problem. Confirm the proposed action before submitting it, and make sure the remaining tickets stay usable under the approved process.

Complimentary guests also need relevant admission information, although they have no paid ticket amount to return. Staff, performers and exhibitors may use different entry arrangements. Give each group the instruction that actually applies to them, rather than forwarding a public notice and assuming it covers every working entrance.

Update the places that will keep repeating the old rule

Sending the email is one part of the work. Buyers will still read the event page, a saved arrival guide or a partner's listing. Your support team may reply from an old template. If those versions disagree, people have to choose which one to trust.

Choose one maintained public page for the current explanation. Show the date of the relevant update and describe what changed for existing purchasers. Don't silently replace the earlier promise and then tell customers they should have checked the page. A dated explanation lets them distinguish the correction from information they already read.

Update the ticket description, checkout information and scheduled booking messages where the supported system allows it. Review queued emails rather than assuming edits to the event page will rewrite them. A reminder prepared before the change can otherwise send the old instruction after your correction.

Check active advertising and partner copy too. Stop promoting an included benefit you cannot provide. Brief the venue and authorised sellers with the approved wording, the buyer response and the person handling questions. Ask each owner to confirm that its relevant page or message has been corrected.

Keep historical records separately from the public correction. You need evidence of what was sold, but customers need a clear statement of today's approved arrangements. Preserving the original information for review doesn't require leaving misleading purchase instructions active.

A useful internal record can be short. Name the location of the old wording, who owns it, the correction required and whether that owner has verified the change. Include the public page, sales descriptions, automated messages, support replies, staff instructions and physical signs that actually apply to this event.

Prepare the entrance team for someone who hasn't seen the email

Assume at least some buyers will arrive relying on the earlier information. Prepare a response that works in that situation. "We emailed everyone" doesn't tell the steward what to do with a person who has already travelled and cannot follow the new rule.

Give staff the confirmed rule, the earlier promise and the approved response for affected purchasers. Explain which person can make decisions beyond ordinary admission and how to reach them during the whole arrival period. Use a deputy where the main contact will be occupied elsewhere.

Staff need to distinguish an exception request from an argument about the policy. Somebody may need help with an access requirement or a specific arrangement your support team confirmed. The entrance conversation should reach the right responsible person without requiring the visitor to explain private circumstances repeatedly in the queue.

Britain's Health and Safety Executive says security searches must not create an overcrowding risk, and its crowd-control guidance discusses safe queue arrangements. When your policy affects admission, agree where questions can be handled with the venue and security leads. Don't solve a customer-service delay by creating unsafe congestion.

For the fictional re-entry change, an ordinary steward explains the restriction and refers an affected buyer to the booking supervisor. The steward cannot promise re-entry that the security lead has ruled out. The supervisor can check the booking and apply the approved response, including a cancellation request where appropriate.

Brief the exit team as well as the entrance team. A person who asks to leave briefly needs to understand the consequence before leaving. Put the clear instruction where it can be read before that decision, and make sure the wording matches the update. Don't let a customer pass the exit and only then explain that their return is prohibited.

Handle the reply without making the customer prove your mistake

When someone replies, begin with the booking and the practical difficulty. If your own published information promised the earlier arrangement, acknowledge it. Asking the customer to send repeated screenshots of a promise you've already verified adds effort without helping you decide anything.

Ask only for information needed to locate the order and understand the requested action. An order number and the affected tickets may be enough for an ordinary cancellation request. Use your approved identity checks where needed. Keep payment credentials and unnecessary personal details out of the email conversation.

Then explain the next step precisely. "We can review cancellation of the two unused tickets you identified" is different from "Your refund is complete." Before confirming an amount, inspect what the purchaser paid and what has already been returned. Before cancelling tickets, establish which ones they mean and what happens to the rest of the order.

A useful reply in the fictional case might say, "We've found your order and the two unused tickets you want to cancel because of the re-entry change. The total paid for those tickets, including their mandatory booking fees, was $104. Please confirm that these are the two tickets you want us to cancel. Your other ticket will remain valid. Once we've completed the action, we'll send the payment status and timing."

That amount is an invented example, assuming two tickets cost $50 each plus $2 in mandatory fees each. It describes the amount actually paid in that example. Your team must use the real order, including discounts and any previous refunds, rather than copying the current advertised price.

If the customer raises a loss beyond the ticket payment, record it and refer it to the person authorised to assess the claim. Don't dismiss it automatically or promise reimbursement before review. The answer depends on the circumstances and applicable obligations, which an entrance steward or a generic email template cannot determine.

Budget for the refund and support work

You need to know whether the approved response can be funded and staffed. That financial check helps you deliver what you owe; it doesn't decide whether a customer has a right simply because the event budget is tight. Keep mandatory obligations separate from optional gestures when modelling the cost.

Here's a hypothetical calculation using USD, not an industry benchmark or a forecast. Suppose the event has 240 paid tickets at $50 each, plus a $2 mandatory booking fee per ticket. The approved cancellation response returns the full $52 paid for each affected unused ticket.

If 18 tickets are cancelled under that arrangement, the payments returned total $936. If 30 are cancelled, the total is $1,560. Those are scenarios for cash planning, not estimates of how many people will ask. Use the actual order amounts when the requests arrive.

Suppose you also plan $180 of additional support staffing. Under the 18-ticket scenario, the identified cash requirement is $1,116 before any other costs. That doesn't tell you the event's final profit impact. Some payment charges may remain payable, other costs may change, and fees can involve another party. Finance needs the actual settlement arrangements.

Don't quietly deduct an unexpected processing cost from a refund you've promised in full. Establish who funds each component before announcing the arrangement. If your message says the ticket and mandatory fee are covered, the amount customers receive needs to match that promise and their applicable entitlement.

Be careful about assuming the released tickets will all sell again. The change itself may make the event less suitable for some buyers, and there may be little time left to sell. Count replacement revenue when a new paid sale is confirmed, while maintaining enough cash to complete the approved refunds without relying on those sales.

Use reminders to resolve a decision, rather than repeat the apology

A reminder should help somebody do something useful. Perhaps an affected purchaser hasn't replied about selected tickets, or the event is approaching and attendees need the current entry rule before travelling. Match the message to that need instead of sending the entire announcement repeatedly.

In the fictional example, a short arrival reminder can say that Harbour Sessions still starts as planned and public re-entry is unavailable. It can link to the dated policy update and give the event-day support route. Don't send cancellation prompts to people whose tickets have already been cancelled and refunded.

If you asked for replies by a planning date, check what that date means before describing it in the reminder. An internal deadline for processing requests before doors should not turn into a statement that customers lose rights afterwards. Make the distinction clear wherever the request appears, including support templates.

Monitor failed deliveries and use another appropriate contact route when the change is significant and you can lawfully do so. An email delivery report tells you about the message's journey, not whether the recipient read and understood every condition. Keep help available at the event for people you didn't reach.

Where somebody has already travelled, address the immediate practical problem before discussing the history of the notice. Confirm a safe place to get assistance with the responsible venue team. Don't tell people to leave bags unattended, gather outside a closed entrance or follow an improvised route while support investigates.

Record unresolved cases for the next shift. A customer who was told "we'll check and reply" should not have to restart when another staff member takes over. Give the next person the relevant facts, the agreed next action and who is responsible, with private information limited to what that work requires.

Check the announcement against the actual operation

Before sending, ask a colleague who didn't write the message to explain what they would do as the purchaser. Give them the original ticket description as well as the new notice. Can they identify the change, the event date, the effect on attendance and the route for help without you adding an explanation?

Then test the awkward cases. One customer bought before the change, another bought through an outdated seller page, and a group wants to cancel only one ticket. Someone has an access arrangement, someone contacts you after the requested planning date, and someone arrives without having read the email. The responsible team should be able to describe a usable response to each.

Read the test email on a phone, including with images hidden. Follow the public update link and check the reply address. Inspect any form customers must complete, including the error message and what happens after submission. A correct paragraph still fails if its contact route leads to an unattended inbox.

Verify the financial promise with the person who will carry it out. Confirm funding, order checks, cancellation of admission rights and payment-status messages. If another seller handles some bookings, obtain its confirmed process instead of implying your own team can perform actions outside its control.

Finally, ask the entrance and exit leads to read the same notice and explain their instructions. Resolve any disagreement before opening. If customers are being offered help that staff cannot provide, the policy response needs another decision, not another round of polishing the email.

Close each affected booking, then fix the source of the change

After the announcement, keep track of what remains unresolved. Separate questions waiting for an answer, cancellations awaiting confirmation and payments still being checked. Use the records your ticketing and payment tools already provide, with a short case note for work they don't capture.

Close a case when the agreed action has been verified and the customer has received an accurate explanation. A refund request being accepted, a refund being submitted and money appearing for the purchaser are different stages. Tell people what you can verify at each stage rather than treating a support reply as proof that the payment process is finished.

After the event, review why the earlier promise and delivered rule differed. Did the venue approve a policy too late? Did a copied page carry a rule from another edition? Did a partner keep publishing an obsolete description? Find the specific cause so the next event doesn't start with the same disagreement.

If the original arrangement couldn't be maintained, record which replacement or remedy the team approved and whether it worked in practice. Include the entrance questions and support workload, not just the number of cancelled tickets. Buyers who kept their tickets may still have had difficulty using the event.

Before the next on-sale, confirm the rule with the people responsible for delivering it and read the complete purchase information again. Your next buyer should be able to plan from what you're selling today. For the customers already affected, finish the outstanding action you promised and tell them when it has actually happened.