When should you use a ticket ballot instead of a sales queue?

You've announced a small show, demand looks strong, and everyone wants to know when tickets go on sale. A queue seems obvious. Open checkout at a fixed time and let people buy. But if you already expect far more buyers than places, you have another decision to make. Should getting a ticket depend on being available at that exact moment?

A ticket ballot lets people apply during a window, then uses a draw to decide who receives tickets or an opportunity to buy them. Use one when you have credible excess demand and want eligible applicants to have a chance without racing through checkout. A sales queue suits an event where immediate purchase, customer choice and a straightforward route to payment matter more than separating applications from allocation.

The extra work comes after the draw. Successful applicants can ignore an offer, fail to pay or discover the tickets don't suit their group. Meanwhile, your event still needs the revenue. Let's work through when a ballot is worth that work, how to define a fair process and how to turn allocations into completed purchases without promising more than you can deliver.

Start by checking whether the tickets are actually scarce

The first thing you want to do is separate excitement from purchase intent. A crowded announcement post tells you people noticed the event. It doesn't tell you how many will pay the advertised price on the available date. A free registration form can exaggerate demand further because entering costs almost nothing.

Look for evidence from comparable paid sales. How many tickets sold at the previous edition's full price? How quickly did the final release go? Did your waitlist convert when tickets became available? If the new event costs more, changes venue or offers a different programme, explain why you expect the earlier behaviour to carry over.

You don't need perfect certainty to choose a ballot. You do need a reasonable case that more eligible people want the available tickets than you can accommodate. Otherwise you ask buyers to fill in a form, wait for an email and return to pay for something they could have bought immediately. Every extra stage needs a reason.

Imagine a hypothetical performance with 400 sellable seats after production holds and other commitments. Your previous comparable show sold 400 at the same price, and you have a substantial group of disappointed buyers asking for the next date. A ballot might solve a real allocation problem. If the previous show sold 180 seats over several weeks, start by investigating demand rather than planning a draw.

Capacity also needs a clean definition. A venue's maximum occupancy isn't necessarily the number you can offer in the ballot. Deduct production holds, artist allocations, sponsor commitments and any separately reserved places first. Keep accessible seating and companion arrangements explicit. Don't run a draw against tickets that another team member has already promised elsewhere.

Understand what the queue and the ballot each decide

A sales queue controls when someone reaches checkout. Its allocation rule depends on the system. Some queues follow arrival order; others randomise a waiting room before admitting buyers. Ask how yours works before describing it as first come, first served. A queue position also doesn't necessarily guarantee that a particular price band will remain available.

A ballot usually closes applications before selecting recipients. People can apply throughout the window without improving their odds by submitting earlier, provided that's the rule you've chosen. This can help buyers who work shifts, live in different time zones or can't spend a launch morning watching a screen.

The LTA's Wimbledon ballot explanation offers a useful real example. It says eligible entries have an equal random chance, with no advantage for opting in earlier. Successful applicants then receive an opportunity to purchase within a set window, subject to availability. That's an opportunity to buy, which is a different promise from receiving a reserved pair of seats.

Be equally precise about your event. You might allocate an exact ticket quantity to each selected application, or give selected people access to a later sale. In the second model, there can still be competition at checkout. Calling both models a ballot without explaining the difference leaves buyers guessing about what success means.

Neither method removes scarcity. A queue can leave someone disappointed after waiting; a ballot can disappoint them after applying. Your job is to choose the process whose rules make sense for your audience and whose outcome you can explain honestly. Avoid promising that everybody will consider it fair simply because a computer makes the selection.

Choose a ballot when time at launch shouldn't decide access

A ballot makes sense when you want a defined group to have an opportunity over a reasonable application period. A limited anniversary show, a small capacity headline performance or an especially popular workshop can fit. People may need to check travel, agree plans with a friend or confirm they qualify before entering.

It can also make sense when you want to verify eligibility before offering tickets. You might reserve a draw for current members or previous purchasers. The application window gives your team time to check those rules before allocating scarce places. That only helps if you have reliable records and a process for correcting mistakes.

The commercial argument is stronger when the event is likely to sell regardless of whether you collect payment instantly. You can afford an application period and later purchase window because access, rather than awareness, is the main problem. Confirm that timing against supplier deposits and your cash forecast. An event can be popular and still run short of cash before ticket money arrives.

A ballot is less convincing when you need spontaneous purchases. A buyer choosing between several weekend events may prefer a confirmed plan today. If your show still needs active promotion to fill, delaying that commitment can send them elsewhere. You can't solve weak demand by presenting ordinary availability as a scarce opportunity.

Start with the smallest allocation that meets the purpose. You could ballot one genuinely scarce performance while selling other dates normally. You could also reserve a defined member allocation and sell the public allocation separately. Our guide to presales for different audience groups explains how to keep separate audience promises within the same total inventory.

Keep a queue when buyers need to choose and commit immediately

A queue can be a better fit when people need to compare dates, seat locations and prices before deciding. They can inspect actual availability and pay for a known choice. A ballot that assigns an unsuitable date or expensive section creates avoidable declines, especially when people are coordinating a group.

That's also why a large programme shouldn't automatically use one event wide draw. Someone interested in a particular speaker may have no interest in the remaining sessions. If applications cover several options, decide whether people rank preferences, accept any listed option or enter separate draws. More choice makes the allocation rules harder to explain and test.

Queues also simplify the relationship between an order and revenue. A completed paid order gives you a purchase to reconcile. A successful application gives you an offer to manage until the buyer commits. There can still be payment failures and abandoned baskets in a queue, but you aren't deliberately adding a separate application and notification stage.

If the main concern is a sudden burst of traffic, talk to your provider about launch capacity and admission controls. That is a different problem from deciding which people should receive tickets. You may need a robust checkout without needing a ballot. Equally, a ballot registration form still needs to handle traffic near its deadline.

For an ordinary release, Loopyah's ticketing tools support ticket types, releases and buyer ticket limits. Those help define what is on sale and how much one buyer can purchase. They don't establish a random allocation process. If a ballot is essential, confirm the separate application, draw and winner access arrangements before announcing one.

Decide whether you are drawing people, applications or groups

Here's where the promise of equal chances gets complicated. If one person submits one application and another submits five under different addresses, equal treatment of applications doesn't produce equal treatment of people. Start by defining who may enter and how often, then decide what evidence you can reasonably check.

For many independent events, one application per eligible person is easier to explain than one per household. Household rules can exclude unrelated adults sharing an address or make it awkward for people without a stable address. If you use one, state exactly what it means and provide a way to challenge a mistaken exclusion.

Group applications need a separate decision. Suppose an application can request either one ticket or two. Are you selecting applications and honouring their requested quantities, or drawing individual seats? Can you offer fewer tickets than requested? A couple who planned to attend together may decline a single ticket, so ask whether partial offers are acceptable in advance.

Keep the arithmetic consistent. If your hypothetical event has 400 tickets and every selected application receives two, you can make 200 initial offers. That doesn't mean 200 paid orders exist. If applicants can request different quantities, the number of successful applications depends on those requests and your published allocation method. Don't announce a fixed success rate before knowing the valid pool.

The same care applies to reserved groups. Members and general applicants may have different pools, quantities or eligibility rules. An equal chance within each pool isn't an equal chance across everybody who applies. You can defend a deliberate member benefit, but describe it as that. Don't advertise a universal equal chance while quietly weighting one group more heavily.

Check entries without collecting a dossier on every buyer

A basic application needs enough information to contact the applicant, establish the relevant eligibility and understand the tickets they would accept. Anything else should have a clear purpose. Asking for an address, birth date and identity document because another event does so isn't a sufficient explanation.

The UK's Information Commissioner's Office describes data minimisation as collecting information that is adequate, relevant and limited to what's necessary for the purpose. Apply that principle to the actual entry rule. A previous purchaser check may need an account or order reference, while a local resident allocation raises a different verification question.

Keep suspicious entries separate from confirmed duplicates. Several applications from the same network might come from a workplace or shared connection. Similar names can belong to different people. Use proportionate checks and a documented review process rather than deleting every match automatically. Record why an entry was excluded so support can explain a decision consistently.

Publish a correction route before applications close. People mistype email addresses, change names and misunderstand forms. Decide which details they can amend, whether an amendment replaces the original entry and when the record becomes final. Without that rule, a helpful support reply can accidentally create a second entry or change the pool after the draw.

Explain the privacy position at the point of entry. Tell applicants who runs the process, what information is needed, which providers handle it and how long you expect to retain it. Our event privacy notice guide helps you organise those explanations. Keep access to applicant records limited to the people doing the relevant work.

Treat marketing permission as a separate choice

An application gives you a reason to communicate about that application. It doesn't automatically mean the person wants promotions for every future show. You should be able to send a result and explain a payment deadline without converting the form into compulsory newsletter signup.

For UK marketing, the ICO's direct marketing planning guidance explains the need to choose an appropriate lawful basis and consider electronic marketing rules. Where you rely on consent, it should be a genuine, specific choice. Work through the rules applying to your organisation and recipients rather than assuming every territory treats email the same way.

Keep optional promotion wording separate from the ballot terms. Tell people whether the choice affects their chance, and make sure it doesn't if you've promised equal treatment. A checkbox saying that someone has read a privacy notice isn't the same as a clear request for marketing permission.

This also matters after an unsuccessful result. An operational message explaining that their application wasn't selected can be necessary to complete the process. Adding an unrelated offer changes what the message is doing. If you want to promote another date, use the audience you are allowed to contact and the appropriate type of message.

Don't count every applicant as a new marketable contact in your campaign forecast. Track applications, eligible applicants, successful offers and marketing permissions separately. You'll learn more about actual ticket demand, and your next launch plan won't depend on sending promotions to people who never agreed to receive them.

Choose how payment commitment will work

There are several ways to connect selection with payment. You can invite selected applicants to pay, ask for advance permission to charge if selected, or collect money before the draw and refund unsuccessful entrants. Each creates a different customer experience and different operational obligations. A form alone doesn't tell you which your provider can support.

For an independent event's first ballot, an invitation to complete a known purchase is usually the simplest approach to explain. State the ticket quantity, total price, payment deadline and what happens if the offer expires. You accept some unclaimed offers in exchange for letting the buyer make a final decision with the details in front of them.

Automatic charging needs much clearer agreement about what people may receive and what they will pay. Check how your provider handles authentication, failed charges, changed cards and cancellation requests. Don't tell applicants that supplying card details guarantees a successful later payment. Their bank can still decline the transaction, and additional action may be required.

A card hold isn't a long term promise of money. Stripe's authorisation documentation explains that holds expire and that uncaptured funds are released when an authorisation expires. The available window depends on the payment method and transaction. Confirm the exact arrangement with your payment provider instead of planning a multiweek application period around an assumed hold.

Collecting money from everyone in advance creates another burden. You need a clear explanation of when money leaves the account, how unsuccessful applicants get it back and what happens if a refund fails or takes time to appear. Before choosing that model, ask whether its commitment benefit justifies the customer confusion and reconciliation work for your particular event.

Publish prices and acceptable choices before entry closes

A ballot entry shouldn't require someone to accept an unknown bill. Publish the ticket price, unavoidable charges and the possible total for the quantity requested. If several price bands are available, let people specify what they would accept and explain how that preference affects allocation.

Keep event details equally clear. People need the performance date, venue, age restrictions and any conditions that materially affect whether they can attend. A draw that assigns a date from a range must say so before entry. Someone who discovers the date only after being selected may have no practical way to use the offer.

Don't quietly expand the applicant's choices to use up awkward inventory. If someone requested the Saturday performance, a Friday ticket is a different offer. You can ask whether they want it, but preserve the meaning of their original application and keep the change separate from the promised selection method.

Accessibility requests deserve a clear route too. Explain how a person requests the relevant seating or assistance, how companion arrangements work and which choices are available. You don't need private health details in a general form when a more limited request will do. Check the venue's actual provision before telling applicants what you can accommodate.

Put the rules where people apply, and retain the version they accepted. A social post is useful for announcing the window; it is a poor place to hide the only explanation of eligibility or payment. If your team changes a material rule, decide how applicants will hear about it and whether they need a chance to amend or withdraw.

Make the draw something your team can explain afterwards

Close entries at the stated time and retain the submitted records. Then create the eligible list according to the published rules. Keep a record of corrections and exclusions rather than editing the original submissions until nobody can reconstruct what happened. The aim is to answer a specific complaint without exposing everybody else's information.

Use a selection method appropriate to the promise. If you've said every eligible entry has an equal random chance, your draw needs to do that. Ask the provider how it generates the selection, records the result and prevents someone from rerunning the draw because the first result was inconvenient.

For a smaller allocation, a supervised process with a second team member checking the eligible count and result may be sufficient operationally. Larger or more sensitive draws deserve stronger independent oversight. Choose the control because of the risk and promise involved, rather than adding a ceremonial witness who can't check anything meaningful.

Decide the reserve procedure before running the main draw. You might produce an ordered reserve list at the same time, or conduct further draws from the remaining eligible pool. Either can work if it matches the published rules. What you shouldn't do is choose replacement buyers informally because they emailed most insistently.

Retain the result securely and limit who can change it. Publish useful aggregate information if you promised to do so, but don't expose names, email addresses or a complete applicant list to demonstrate fairness. An applicant should be able to understand their own outcome without receiving other people's personal data.

Plan the second allocation before you send the first offer

Unused offers are predictable enough to plan for, even when you can't forecast their exact number. Some people will miss the email, change plans or decide the available tickets don't suit them. Treat that as a normal stage of the process. Your event needs a route to sell those seats after the first deadline.

Let's continue the hypothetical 400 ticket event with 200 offers for two tickets each. If 160 applicants complete payment, you've sold 320 tickets and have 80 unclaimed. That is an illustrative calculation, not a conversion benchmark. The remaining 80 can support 40 replacement pair offers once the earlier claims have genuinely expired.

Check the order records before reallocating. An email delivery report doesn't establish that someone paid, and an expired link doesn't necessarily establish that a payment failed. Investigate unresolved transactions and release only the tickets you can confirm are available. Otherwise a replacement offer can compete with an earlier customer's completed purchase.

Use the reserve method you announced. Tell replacement applicants how long they have and what they can buy. As the event approaches, you may need shorter windows, but set that expectation early and keep the deadline explicit. Don't promise people days to decide and then quietly withdraw the offer the next morning.

Our guide to managing a sold out event waitlist covers the practical work of contacting the next buyer and confirming inventory. A reserve applicant isn't a paid attendee, so don't include them in attendance or ticket revenue totals. Reconcile the available quantity after every round before opening another.

Write the offer so nobody has to guess what they won

Before sending results, ask someone outside the launch team to read the successful applicant email. They should be able to tell you whether tickets are held for them, what they cost and when the offer ends. If they read "you've been selected" as a confirmed booking when you mean access to another sale, change the wording. The distinction needs to survive a quick read on a phone, not just a careful reading of the terms.

For a reserved pair, the message can say that two tickets for the named performance are available for that applicant to purchase until the stated deadline. Include the total, the official route to pay and the consequence of doing nothing. Explain whether they can buy one instead and whether unused quantity returns to the pool. Keep the instruction close to the payment link so somebody forwarding the message to a friend doesn't remove the essential context.

For access to a later sale, state that availability remains limited and that selection doesn't reserve particular tickets. Include the opening time, the closing time and any buyer limit. People who planned around a guaranteed pair will reasonably be upset if the second stage turns out to be another race. You can avoid much of that frustration by explaining the model on the application form and repeating it in the result. The result email shouldn't be the first place someone discovers this condition.

Unsuccessful applicants need a useful result too. Tell them whether they remain eligible for a reserve round, whether they need to take action and when you expect the process to finish. Don't imply an eventual offer if you have no basis for it. If they can withdraw their application, show them how. A person who has already made other plans helps nobody by remaining in a pool they no longer want to join. You also reduce needless follow up when their turn arrives.

Agree what happens when the notification itself fails. A bounced email isn't proof that someone deliberately ignored an offer, but it also doesn't create unlimited time to claim tickets. Use the published account or status route, the contact details available to you and the remedy you've approved for delivery problems. Keep any exceptional extension recorded against the affected allocation so it cannot be sold again in the meantime. Your support team needs to know whether the deadline still applies before answering the next applicant, and finance needs the same inventory position when reconciling orders after the window closes. Check this handoff in the rehearsal, while you still have time to simplify the instructions and correct confusing messages before real applicants depend on them.

Test the application and purchase journey before announcing it

Walk through the process as an applicant using a phone and an ordinary email account. Can you understand the terms without opening several documents? Does the confirmation explain what happens next? Can you correct a mistake? Then test a successful result and an unsuccessful one, including the support route each person receives.

Test the exception cases as carefully as the happy path. A forwarded winner link, a duplicate entry and a payment attempted just before expiry can expose problems that a straightforward test misses. Confirm whether access is tied to the selected buyer, whether a ticket quantity is reserved and whether an unfinished payment holds inventory.

Accessibility includes timing. The W3C guidance on adjustable time limits explains why some people need longer to complete tasks. It also discusses ticket purchase situations where timing may be essential. Review the actual journey, move avoidable work out of the timed stage and provide a clear way to seek help.

Test reminders without changing the deadline accidentally. A message should repeat the same date, time and named time zone as the offer. Make the result accessible through a trusted account or application status page where possible. Buyers shouldn't have to trust an unexpected payment email with no other way to verify it.

Finally, practise the support handoff. The person answering questions needs the eligibility rule, the result, the deadline and the permitted remedies. Decide who can authorise a correction and how it gets recorded. Make sure the person covering evening support has that information too. If staff improvise exceptions under pressure, the public rules become less meaningful with every reply.

Decide whether the next release still needs a ballot

After the sale, compare the eligible applications with paid purchases and the amount of work required to complete them. Separate initial offer acceptance from later replacement sales. Record how many tickets remained unsold, which offers failed and what people asked support. Those details help explain whether you solved an access problem or added a delay.

Look for avoidable declines. Were the available dates unsuitable? Did the total price surprise people? Were results sent while buyers were unlikely to see them? A low acceptance rate doesn't automatically prove the audience wasn't serious. It can reveal a process that asked people to commit before giving them enough information.

The best reason to repeat a ballot is that eligible demand still exceeds supply and the process offers a better opportunity to the people you want to reach. If that evidence isn't there, make the next release easier to buy. You can retain clear purchase limits and audience rules without asking everyone to enter a draw.