Loopyah Icon

· 27 min read

How to move ticket holders between performances after a cast change

Featured image for How to move ticket holders between performances after a cast change article

You've sold Friday's performance around a particular actor. Then the cast changes, Saturday's show still has the advertised performer, and buyers start asking to move. You want to help them without promising the same seats twice or charging somebody more to receive the experience they thought they'd already bought.

The first thing you want to do is establish what the change means for the buyer's rights. Then offer exchanges only into performances and seats you can actually provide, with the price treatment explained before anybody agrees. A completed exchange needs a confirmed new booking, a clear answer about the old ticket, and a payment record that matches both.

That sounds straightforward until one buyer wants to move two of four tickets, another needs a wheelchair position beside a companion, and the most popular alternative has six places left. A blanket "contact the box office" email leaves your staff making policy while customers wait. Give them the decisions and the stock controls first.

This guide walks through a performance ticket exchange policy for a cast change, including who gets an offer, how to handle different prices, what to send buyers, and what the door team needs. The worked theatre examples are fictional and use USD throughout. They illustrate the decisions, rather than report a customer's results or set a legal refund formula.

First establish what changed in the sale

A cast change can describe very different situations. An understudy performs a role in a production advertised around the show itself. A named guest misses an appearance sold specifically around that guest. Or a producer moves an advertised lead to different dates after selling tickets. Your team should understand the actual promise before replying with the same answer to everyone.

Keep the event page, relevant adverts, purchase confirmation and terms that applied when the tickets were sold. Record which performances changed and what is now confirmed. If the casting information was different at purchase, that matters. A buyer who booked after a clear announcement may have bought a different offer from somebody who booked before it.

For Australia, the ACCC's guidance for businesses selling event tickets says an organiser's cancellation or major change can give consumers a refund entitlement. It gives a changed festival headline act as an example. It also distinguishes changes caused only by others, where contractual and other legal rights can apply. That is Australian guidance, not a worldwide rule declaring every cast substitution refundable.

Have the responsible person assess the facts against your market's law and the original offer. Tell support which cases qualify for a refund, which have a voluntary exchange option, and which need individual review. "Cast subject to change" in the terms is something to assess with that advice. It should not become an automatic reply that ignores what you advertised.

The commercial decision comes after that assessment. You might offer an exchange more generously than you must because you can accommodate the buyer and want them to enjoy the show. Fine. Record that as the offer you're choosing to make. Don't describe an exchange as the only route when somebody has a right to their money back.

Our wider event refund policy guide covers the distinction between changes made by the organiser and ordinary attendee requests. Here, the specific job is moving an admission between performances without losing the buyer's choice or creating conflicting bookings.

Agree on the public facts before opening exchanges

Ask production to confirm the affected performance, the replacement arrangement and the information you're allowed to publish. Somebody must own each later casting update. If Saturday's appearance is still uncertain, say that. Moving a buyer on the strength of an unconfirmed promise can create another round of the same problem.

Protect the performer's privacy. Buyers need to know who will appear and what their choices are. They usually don't need personal medical details or an internal explanation of employment arrangements. Your announcement should be candid about the performance without turning private information into a reason buyers must accept the change.

Keep new sales consistent too. Correct the event page and scheduled promotions, including partner listings you control. An accurate exchange email won't help if a new buyer purchases from an advert that still promises the old cast. Record when the public information changed so staff can understand later questions about what somebody saw.

If casting changes again after an exchange

An exchanged booking needs a fresh assessment if its advertised performer later withdraws too. Keep the original reason for the move and the new confirmation available. The buyer may have accepted Saturday specifically because you confirmed that performer. Don't apply an ordinary change-of-mind rule without considering the promise made during the exchange.

Stop using the affected alternative in new offers while production confirms the facts. Find the buyers already moved there and contact them with the revised choices. Keep any original top-up or partial refund linked to the case so finance can calculate the correct next adjustment. Starting a new unconnected case makes it much easier to overlook money already paid or returned.

Write the offer before sending the announcement

Decide exactly what you're inviting buyers to do. An offer might let eligible Friday holders move into selected Saturday or Sunday performances, subject to suitable seats, with no exchange administration charge. It should also explain the refund route where applicable and what happens if the buyer prefers to keep Friday.

Avoid "free exchange" unless you can explain every possible extra payment. A waived handling charge doesn't tell somebody whether a more expensive performance costs extra, whether a cheaper seat produces a refund, or whether the new ticket keeps their original discount. Put those answers in the offer your staff will use.

Set an operational request deadline that gives the team time to finish changes before entry. Show the date, time and time zone, and offer help for a request already received but not yet processed. Have the deadline checked against applicable rights. Your support cutoff cannot simply erase a remedy that the buyer remains entitled to claim.

Say what happens when somebody does nothing. If the changed performance is going ahead and their original booking remains usable, tell them that after confirming their rights and options. Don't silently move an entire audience to another evening. People booked around childcare, work, transport and companions, and your alternative date may be impossible for them.

Give staff enough authority to answer consistently

Choose one owner for the exchange operation. That person approves the dates, price rules and exceptional decisions. Box-office staff need enough authority to complete ordinary cases without asking the owner every time, alongside a clear point at which to stop and escalate.

An agent might be allowed to move an eligible ticket into a confirmed, equivalent seat on the approved dates. They might need approval to waive an optional upgrade charge, move outside those dates, or resolve a disputed original promise. Define those boundaries in useful language, then make sure system permissions fit the tasks.

Give the team a small set of worked answers. Include a two-ticket booking, a discounted purchase, a partial group move, an access requirement and a refund request. These cases expose gaps faster than another paragraph of policy. If two trained agents reach different outcomes on the same example, settle the rule before the announcement goes out.

Count usable alternatives before offering them

Your alternative performance needs its own current stock check. Start with its agreed seating plan, existing valid bookings, production holds, guest allocations and any seats that are unavailable for this particular show. An apparently empty place on a general venue diagram is not necessarily a seat you can offer.

Then look at the shape of the remaining stock. Six individual seats scattered across the room won't accommodate three couples who each want to sit together. A pair in a restricted-view section isn't equivalent to an unobstructed pair just because the ticket price happens to match. Decide what counts as suitable before an agent promises an exchange.

Consider a fictional Saturday performance with 120 authorised audience places. There are 96 valid admissions already booked, eight places under genuine production holds, and four guest allocations. That leaves 12 unallocated places. The calculation is 120 minus 96 minus eight minus four. It says nothing about whether those 12 form usable pairs or meet a particular access need.

For this example, the producer sets aside eight of those 12 places for the exchange offer and leaves four on public sale. If two exchange pairs are confirmed, four of the eight reserved places remain. A request for six more tickets cannot be approved just because the public website also appears to show four available. Somebody must authorise a stock change after checking current bookings.

This is an inventory exercise, not a safe-capacity calculation. Your venue and competent event team establish the actual permitted layout and audience limits. A box-office spreadsheet cannot approve adding chairs, changing accessible positions or selling a production hold before the responsible person releases it.

Keep online sales and box-office offers connected

Use the ticket provider's supported reservation and exchange controls wherever available. Ask how an agent can offer a seat without another buyer purchasing it during the conversation. If offers expire, staff and buyers need the same expiry time. A note in an inbox does not reserve stock on a public sales page.

If your system cannot protect a proposed seat while a buyer decides, narrow the process. You could handle requests during staffed sessions, stop selling the specific allocation through another route where supported, or explain that an unreserved suggestion remains subject to availability. Choose a process the provider and venue can support, rather than keeping a second unofficial seat plan.

Decide how you'll handle requests when suitable stock runs out. A waiting list records interest, while a confirmed exchange commits actual places. Keep those states separate in the message and the order record. Ask whether the buyer is willing to consider another date or seat category, and make clear which original booking remains valid while they wait.

Use an agreed allocation method for ordinary requests, with the relevant access requirements handled properly. Record when a request arrived and when an offer was made. If you give somebody a temporary reservation, explain when it expires and how to accept it. Don't let unanswered informal promises keep usable seats unavailable indefinitely, but check before releasing a place somebody has already accepted.

Loopyah's seat charts let organisers draw a venue layout, price its sections and let buyers choose seats. Those capabilities help describe the available offer. Before promising a cast-change exchange, verify separately how your actual setup handles reservations, cross-performance changes and the original ticket. A seat map alone doesn't establish those controls.

Match the experience, including access and group needs

Start the conversation with what the buyer needs to keep. That includes the number moving, whether they need to remain together, their seat category, the view and any access arrangements. Offer an actual performance time and actual seats. "We'll put you somewhere similar" is too vague for an agreement that changes their evening.

Check the new performance as a whole. A captioned show on Friday and an uncaptioned show on Saturday are different offers for somebody who needs captions, even if the seat location matches. The same goes for step-free routes, companion arrangements or a relaxed performance. Ask what the buyer requires to attend, without making them disclose an unnecessary personal history.

The US Department of Justice's ADA ticket-sales guidance explains requirements for accessible seating information, companion seats and sales practices for covered venues. For a US operation, check those requirements as well as your exchange procedure. Don't invent an accessibility surcharge or release protected accessible stock simply because other customers are asking for it.

If the buyer's needs can't be met on the alternative date, explain that honestly and return to the other applicable choices. An unsuitable seat is not a resolution because your team found a way to issue a ticket. Record which requirement couldn't be met so the next agent doesn't repeat the same offer.

A partial group move needs ticket-level instructions

Imagine order H204 contains four Friday admissions, A1 through A4, originally bought together. Two people want Saturday and two want to stay on Friday. Confirm which actual tickets are moving, whether the booking conditions allow the split, and whether any linked benefits or group discount need attention under the reviewed terms.

The intended result is precise. Friday tickets A1 and A2 are replaced or invalidated through the supported process. A3 and A4 remain valid for Friday. The two Saturday admissions identify their own seats and date. The buyer should receive a confirmation explaining that split without having to infer it from several separate receipts.

Don't tell the buyer to delete their entire original email if it still contains the two valid Friday tickets. Give instructions that identify the replaced tickets and the retained ones. This matters when one person has forwarded tickets to friends. Ask them to pass on the updated instructions and make ticket retrieval clear for the people actually attending.

Where a school, tour group or sales agent bought the tickets, agree who has authority to request the change. The person who contacts you may hold the admission without controlling the original payment. You need a supported way to verify the request and direct any refund to the proper route. A recognisable surname alone doesn't settle either question.

Explain how much the buyer pays or gets back

Choose a price rule before taking requests. You may offer a protected move into an equivalent category at the original amount paid, a move priced against the alternative performance, or an optional upgrade. The appropriate treatment depends on the buyer's rights, your original terms and the offer you make. Don't turn whichever price the agent sees first into the policy.

Use the actual paid amount. Suppose our fictional buyer paid $80 each for two Friday tickets, so the original ticket amount is $160. If your agreed offer protects an equivalent Saturday pair at no extra cost, they still have $160 applied to two admissions, even if Saturday's public price is now $95 each. The public price is not evidence that you've received another $30.

For a separate optional upgrade scenario, assume the buyer is entitled to a suitable equivalent option and actively chooses premium seats priced at $100 each instead. Applying the original $160 leaves a $40 top-up. Explain the alternative, show the total, and obtain agreement before collecting it. Don't present a necessary remedy as an upgrade merely because equivalent seats are scarce.

For another separate scenario, the buyer accepts suitable seats priced at $70 each under an offer that returns the difference. The new ticket amount is $140 and the refund is $20. Show the refund separately from the updated admission. If the original purchase also included taxes, fees, donations or extras, calculate their treatment explicitly rather than assuming every item follows the seat price.

Discounts need the same care. If the two tickets actually cost $72 each after a discount, the starting ticket amount is $144, not $160. Work from the paid record and the agreed terms. Explain any allocation across a package before requesting consent, particularly if the package includes something that won't be available on the new date.

Fees need an amount and a reason

Decide whether you absorb additional processing costs when you offer an exchange. If the organiser changed the advertised performance, charging the buyer a handling fee to obtain an appropriate remedy deserves especially careful review. A provider charging you does not by itself establish what you're entitled to charge the buyer.

For covered US live-event ticket offers, the FTC's fee-rule guidance explains total-price disclosure and prohibits misleading fee representations, including claims about refundability. It does not prescribe every cast-change remedy. Check the applicable price and consumer rules before putting a fee in your exchange message.

Keep any voluntary upgrade truly optional. Show its complete payable amount before the buyer commits, explain the available equivalent offer, and let them decline. If they select a different performance with a dearer public price, your team must still apply the offer you agreed to make, including any price protection.

Send a notice that lets buyers make a decision

The first announcement should answer the questions somebody can reasonably ask while reading it on their phone. Which performance changed? Who is now scheduled? Can I still attend? What other choices apply? What do I need to do, by when, and who can help if the available dates don't work?

Put that information in the message itself. You can link to fuller terms, but don't make somebody open several pages to discover that the named performer won't appear. A subject line such as "Cast update and ticket options for Friday's performance" is more useful than a vague invitation to read an important announcement.

Here's a fictional notice to adapt after the actual remedy position has been reviewed. "The advertised lead will no longer appear at Friday's 7 pm performance. The production will go ahead with the replacement cast shown on the event page. Your existing tickets remain valid for Friday. Eligible buyers can request an available Saturday exchange, or use the refund route described below. We won't move your booking without your agreement."

Continue with the actual practical details. "To request an exchange, use your order reference and tell us which tickets you want to move. We'll confirm the performance, seats and any agreed price adjustment before completing the change. Please contact the box office by the stated deadline if you need help. A request is not a confirmed new booking."

That is sample wording, not a complete legal notice. Add the real date, time zone, refund eligibility and route, contact details, and what happens to a pending request. If the replacement cast isn't confirmed yet, don't fill the gap with a promise. Tell buyers when you will update them.

If the buyer doesn't reply, keep the result consistent with your reviewed offer. Silence doesn't establish agreement to a different date or an extra charge. You can send a relevant reminder and give a clear help route, but avoid repeated messages that make somebody think their existing admission has disappeared. Separate an unanswered invitation from a change you've actually completed.

For agent bookings, tell the agent what must reach the ticket holder and how completion will be reported back. Ask for confirmation that the notice was passed on where your arrangement supports it. An agency's generic receipt may not contain your latest casting information. Assign follow-up to a named person instead of assuming that the audience has read your public social post.

People care whether the advertised experience is delivered

In Loopyah's Worth It Event Index survey, fielded through Pollfish on February 11, 2026, 500 US consumers answered how confident they usually felt that an experience would match its advertising. The chart shows the full unweighted response distribution for question seven.

Confidence an event will match its advertising (% of 500 US respondents)
Confidence an event will match its advertising (% of 500 US respondents)
LabelRespondents %
Always17.4
Most of the time55
About half the time18.4
Sometimes9.2
Never0

These are general survey responses about event advertising. They don't measure disappointment after a cast change, the proportion who will ask to exchange, or the sales effect of a particular policy. Use your own request numbers to plan the response. The useful question for your announcement is whether it gives buyers accurate information about the experience now available.

Send to the affected booking audience using the appropriate service-message route. Check what your provider can identify, whether it has the current holder's contact details, and how essential updates are handled separately from optional marketing. Don't assume that a marketing segment or a list of email opens proves everyone who needs the notice has received it.

Loopyah's attendee email tools support selecting audiences using purchase information. Verify the exact audience and sending route for your performance update. You remain responsible for the casting facts and offer, and you should check undelivered messages and bookings made through agents rather than treating one send as the end of the communication.

Complete the booking change through a controlled process

An exchange request should have an owner and a visible state. Received means you've heard from the buyer. Offered means you've described an available option. Confirmed means the supported booking change has completed. Payment still pending or ticket delivery failed needs its own follow-up. Avoid a single "done" label that conceals which step actually happened.

Use the provider's supported exchange operation when it can carry out your policy. Have it demonstrated with your actual seat types and a partial order. If the provider instead requires a cancellation and new booking, ask how to protect the alternative stock and handle the money without leaving the buyer with two active admissions or neither booking.

Don't improvise a technical sequence that assumes every system behaves alike. Some tools can carry linked changes together, while others have separate steps and require staff supervision. Agree what happens if any step fails before you process the first customer. Keep the original case open until the final outcome is verified.

At the buyer's confirmation point, repeat the chosen performance, seats, number of tickets moving, money due or returned, and effect on the original admission. W3C's guidance on preventing consequential form errors describes ways to let people check, correct or reverse important submissions. A review step helps buyers catch the wrong date before the change becomes final.

Deal with a failure according to what actually completed

Suppose the buyer agreed to the optional $40 upgrade, but payment failed. You have agreement to a proposed change, not proof that the top-up arrived. Follow the agreed reservation and recovery process. Tell the buyer what remains valid and how long any protected offer lasts. Don't send a completed-upgrade confirmation while finance still sees no successful payment.

If payment succeeded but ticket delivery failed, locate the completed booking before trying the payment again. Resending ticket access is a different task from selling another pair. Your staff should be able to see the successful transaction and current ticket record so a delivery problem doesn't become a duplicate charge.

If the original admission was invalidated but the new booking failed, escalate immediately through the provider's recovery procedure. Keep a record of the interruption and give the buyer a clear update. Don't tell them the old ticket will work unless you've verified that it has been restored or you have an authorised entry arrangement.

Our ticket management guide explains the wider relationship between orders, valid admissions and entry records. For this incident, the completion test is narrower. Can staff identify the current performance and seats, the invalid old tickets, any unchanged tickets in the same order, and the linked payment adjustment?

Keep refunds and exchange payments distinguishable

Finance needs the relationship between the original booking and its replacement. Record the original payment reference, the tickets changed, the new booking reference and any adjustment. Moving an $80 admission to a different performance is not automatically another $80 cash sale. A report that counts every replacement as new income will exaggerate what the operation retained.

For the fictional protected pair, the buyer originally paid $160 and pays nothing further. Across the linked records, you've retained $160 before any separately accounted costs or taxes. For the optional upgrade, receipts are $160 plus $40, or $200. For the cheaper-pair scenario with a $20 refund, net receipts are $140. These are alternative cases, not three adjustments to one booking.

Reconcile refunds against the payment provider's actual status. Stripe's refund documentation distinguishes full and partial refunds and explains that funding and payment-method conditions affect processing. A refund request or internal approval is not the same as confirmed returned money. Use the status and expected timing applicable to your actual payment route.

Tell buyers what you've done accurately. "We've submitted a $20 refund to the original payment method" means something different from "The $20 is in your account." If a refund is pending, keep an owner and a next update. If it fails, investigate the supported recovery route before issuing another payment that might duplicate it.

Budget the work as well as the adjustment

Exchanges can retain a sale while adding costs. Build an incident allowance from the requests you actually receive and a planning scenario you label clearly. Include payment costs you absorb, additional support hours and any genuine extra delivery expense. Don't assume the absence of a cash refund makes every exchange costless.

As a fictional staffing calculation, 30 exchanges taking 12 minutes each require six hours. At an assumed staff cost of $30 an hour including employer costs, that's $180. If the operation also incurs $24 in unrecovered payment costs, the combined allowance is $204. These are invented inputs for planning, not an industry service-time benchmark or a provider's quoted fee.

Be careful with the value of a released seat. You may sell a returned Friday seat to somebody happy with the changed cast, but that sale is uncertain until it happens. Likewise, moving a buyer into Saturday could use a seat that otherwise would have sold. Record actual resales and current demand rather than declaring every retained booking a fresh revenue gain.

Use your event cash-flow forecast to check when refunds and additional costs must be funded. A hoped-for later sale doesn't pay a refund due now. If the exchange offer grows beyond the original allowance, the owner needs an updated cash decision before staff make more promises.

Check the effect on each performance as well as the series total. If ten $80 admissions move from Friday to Saturday without a top-up, the series still has the same $800 in ticket receipts from those buyers. The allocation between performances changes. Saturday has ten more valid admissions and Friday has ten fewer, subject to any other bookings. That is a hypothetical movement, not ten new paid customers.

If Friday later sells those ten released places for $70 each, that produces a separate $700 in actual receipts once the purchases complete. Keep that sale separate from the exchange. You still need to account for the costs attached to both performances and any additional payment charges before calling the result profit.

Tell the door team which admissions are valid

The exchange is only useful if it survives arrival. Door staff need the current admission record for the performance they're working, a way to identify an old ticket, and a named person who can resolve an exception. They shouldn't have to reconstruct the buyer's email conversation while the queue grows.

Test the changed tickets using the provider's supported process. Check the new Saturday ticket, the replaced Friday ticket, and an unchanged Friday ticket from the same partial group order. Also test a second presentation of a ticket already used. Those are different states, and staff need to understand the response for each one.

If the system uses offline lists or disconnected scanning, ask how late exchanges reach those devices and whether an old admission could still be accepted. An export created before the change won't update itself. Agree a final update procedure and a controlled exception route before relying on it during a connection problem.

Door staff don't need the reason a performer withdrew or a buyer's private correspondence. Give them the admission facts and the authorised decision route. If a customer presents a screenshot of the original ticket, find the current booking and follow the agreed policy. Don't admit both versions simply because they look plausible.

Make the updated confirmation unambiguous

An exchange completion message should say the new performance's date, local start time, venue and seats. Identify the original admissions it replaces and the ones it leaves alone. State any top-up received or refund submitted separately. Give a usable ticket retrieval route and explain which credential to show on arrival.

For our partial order, the message could say that A1 and A2 have moved to Saturday while A3 and A4 remain booked for Friday. Include the replacement ticket numbers so the people attending can match the confirmation to their tickets. If the buyer has already distributed the tickets, ask them to notify the affected holders and retrieve the updated admissions through the supported route.

Check scheduled reminders after the move. A buyer who receives the correct Saturday ticket and then a Friday "see you tonight" email has a reasonable reason to doubt the change. Verify which messages follow the updated booking and which need intervention. The case isn't finished until its practical instructions agree.

Keep a small record your team can actually use

Record enough information to verify the decision without building a second customer database. The exchange case should link the affected tickets and booking, the selected outcome, the responsible staff member and any unresolved task. Use the ticketing and payment systems for the records they already hold instead of copying everything into a shared sheet.

The UK's ICO guidance on data minimisation explains collecting information that is adequate, relevant and limited to the purpose. That guidance is under review following UK legislation changes. For your exchange operation, choose and document the actual information needed, limit access, and apply the relevant retention requirements in your market.

Usually you need to identify the order, confirm which holder is requesting the change, understand any practical attendance requirement and record the result. You don't need payment-card details sent by email. Nor do you need a diagnosis to understand that somebody requires a step-free route. Ask for the information that lets you provide the appropriate booking.

Keep unresolved tasks visible across shift changes. "Waiting for buyer approval" needs the offered seats and any expiry. "Refund pending" needs the amount and payment reference. "Delivery failed" needs the confirmed new booking and the next contact attempt. Clear states stop a new agent from repeating a charge or approving a seat already promised elsewhere.

Rehearse the difficult cases before the first message

Run a short rehearsal with the people who will answer buyers, manage stock and approve money adjustments. Use supported test orders or a provider demonstration. Don't experiment on a genuine buyer's booking. Ask each person to show the resulting record and explain what the customer would receive.

Start with an equivalent pair moving at no extra cost. Then try the discounted pair, the optional upgrade, the cheaper alternative with a refund, and the four-ticket order where only two move. Include a required access arrangement that isn't available on the proposed date. The correct answer to that last case may be another applicable remedy, rather than a forced exchange.

Test a seat being taken by another sale before agreement. Test a top-up that fails and a completed booking whose delivery fails. Ask what happens when the cast changes again after an exchange. Each case needs a staff owner and an honest customer update, even if the exact recovery requires the provider.

Finish by comparing the original and new admissions, the money, the confirmation and the entry record. If any disagree, fix the process before increasing the volume. A faster reply doesn't help a buyer who arrives at the wrong performance with a ticket nobody recognises.

After the affected performances, close the remaining cases and review the actual work. Count completed exchanges, refunds and unresolved requests separately. Compare the cost of handling them with the allowance you set. Ask which part repeatedly required a second explanation, then improve that part before the next on-sale.

For the next announcement, the immediate decision is whether the offer can be carried out as written. Take one affected booking and follow it through a suitable alternative, the buyer's agreement, the completed change and the door check. Send the offer when the team can show exactly what happens to that booking and its money.

Loopyah Icon

Author: By the Loopyah Content Team

The Loopyah Content Team shares expert insights, practical guides, and industry updates to help event organizers create unforgettable experiences and stay ahead in the event planning world.