How to choose ticket types for a multi-day event

For a multi-day event, start with a full-event pass and day tickets only where each day gives buyers a worthwhile experience. Set quantities against each included day's safe capacity, price the pass against the money each attendance adds after costs, and add premium options only when you can explain and deliver the difference.

The mistake is building your ticket menu before deciding what people are buying. A weekend pass sounds simple. But does it include Friday evening? Can someone hand it to a friend on Sunday? Does Saturday admission include the workshop with fewer seats than the main hall? Those answers change your prices, your available places and what your team has to check at the entrance.

This guide walks you through the ticket choices, a worked price and capacity example, upgrades and optional extras, and the admission rules to settle before sales open. We're talking about one event spanning several days. Selling two separate events together is a different offer with its own reporting and cancellation decisions.

Start with the days people actually want

The first thing you want to do is read your programme as a buyer. Forget your ticket categories for a moment. What would make someone give you their whole weekend? What would make another person come for Saturday and leave happy?

A conference with a connected teaching programme may need a full-event pass as its main offer. If Sunday's exercises assume people completed Saturday's training, a Sunday ticket can create a disappointing experience. You can still admit suitable attendees separately, but explain the prerequisite and decide how you'll check it.

A music festival with a different lineup each day often has a clearer reason for day tickets. Some buyers want one headliner. Others want the complete weekend. Give both groups a useful choice rather than trying to force every interested person into the most expensive ticket.

Now consider your travel audience. Someone booking accommodation may prefer a confirmed pass before committing to the trip. A local buyer may only have one free afternoon. You don't need a category for every life circumstance, but you do need to know whether a shorter attendance is a real purchase your programme supports.

Look at your own previous sales and attendance by day where you have them. Ask returning buyers which days they considered and why. Treat answers as evidence about your audience, not a forecast that guarantees they'll buy. When you have no history, use a small initial allocation and review actual purchases before releasing more.

Write a plain description for each possible admission. "Saturday ticket includes the Saturday programme, from doors opening until the final session ends." If that sentence needs several exceptions, resolve the programme or simplify the offer. Clear ticket choices start with an event people can understand.

Keep admission choices separate from price releases

A ticket type describes the access someone gets. A release describes the price or quantity offered at a particular sales stage. Keeping those separate stops your menu growing into a list of almost identical choices.

Your standard weekend pass might have an early release and a later release. Both admit the same person to the same days and areas. You don't need buyers comparing "early weekend", "regular weekend" and "last weekend" as though they were different experiences. Show the currently available price and explain what it includes.

Day tickets deserve separate names because their admission differs. "Saturday admission" tells people more than "general entry B". If the programme runs into the following morning, include the actual hours. The calendar date printed on a ticket should not make a late performance look excluded.

A sensible starting menu for a two-day event is one full-event pass, Saturday admission and Sunday admission. Remove either day ticket if that day cannot stand alone. Then consider whether one premium experience earns a place beside standard admission. Start with fewer decisions and add a choice when demand or the programme gives you a reason.

Our ticket pricing guide covers the broader pricing choices. Here, the immediate job is to keep the access promise clear while prices change. A cheaper release should not quietly become a shorter visit or lose a benefit buyers reasonably expected.

Loopyah's ticket selling tools let you give a ticket type several releases, each with its own price and quantity. When a release sells out, the next opens at its price. That helps you run a planned price progression without switching releases yourself. It doesn't establish that different day tickets and passes automatically share your daily capacity limits.

Build your capacity record for every day

A full-event pass reserves admission on every included day. You cannot count it only once when deciding how many Saturday places remain. One paying person may create several promised daily admissions, and each day must have room for them.

Before setting quantities, agree the usable audience capacity for each date with the venue and the people responsible for your safety plan. Account for the actual layout, entry and exit routes, staff and other people present. The number in an old venue brochure isn't a substitute for that assessment.

The UK's Health and Safety Executive's crowd risk assessment guidance asks organisers to determine safe capacity and consider which event days will be especially busy. Use that approach to challenge a weekend total that hides a crowded Saturday. Your applicable local requirements and competent safety advice still determine the limits for your event.

Here's a fictional two-day event, with all prices in US dollars. These are planning examples, not industry benchmarks or a claim about an actual venue. Assume the approved audience limits are 600 on Saturday and 500 on Sunday, after the safety team has accounted for the other people and operating conditions.

You allocate 300 standard weekend passes, 180 Saturday tickets and 120 Sunday tickets. You also reserve 40 audience admissions each day for invitations and other confirmed allocations. The initial promises total 520 for Saturday and 460 for Sunday. That leaves 80 Saturday places and 40 Sunday places unallocated.

Selling another weekend pass uses a place on both days. With that starting allocation, you can add no more than 40 weekend passes unless you reduce another allocation or release a confirmed hold. Saturday's extra space doesn't fix Sunday's smaller allowance. The tightest included day sets the available pass quantity.

Keep invitations visible even when they produce no ticket income. Include young attendees and anyone else your safety plan counts in the audience limit. Don't treat a child ticket as half a person because it costs half the adult price. Your safety assessment determines how everyone counts.

Reserve quantities before chasing sales

Allocations are commercial decisions inside the safe limit. They let you decide how much room to protect for weekend buyers, day buyers and legitimate holds. They are not extra capacity, and they must all fit together.

In our example, the Saturday and Sunday ticket allocations are already promises you could sell. Don't release 80 extra Saturday tickets and 40 extra weekend passes simultaneously. The passes also use 40 Saturday places, which would take Saturday beyond its limit if every allocation sold.

Instead, decide which offer receives the remaining places. You might release 40 additional weekend passes and then 40 Saturday tickets. Saturday reaches 600 promised audience admissions and Sunday reaches 500. You could choose another mix, but write it into the daily record before changing the sales quantities.

This is where people confuse a forecast with a promise. You may expect some pass holders to skip Sunday. Their entitlement still exists. Unless your event has a specifically approved operating arrangement that supports a different approach, protect every promised admission. Don't create saleable places from a guess about no-shows.

Review holds with the people who own them. A sponsor may have ten passes reserved but confirm only six before an agreed deadline. Release the unused four only after that confirmation. An unclaimed hold still occupies capacity while someone has the right to use it.

The daily audience limit also doesn't guarantee space in every room. A workshop holding 60 people needs its own booking or entry arrangement even when the main event can accommodate 500. State whether the pass includes a reserved workshop seat or simply lets the attendee join subject to availability. Those are different promises.

Price the pass using what it leaves after costs

A full-event pass can encourage a longer visit, but every extra day has a cost. Compare the money it leaves after those additional costs with what buyers would otherwise purchase. A bigger order value doesn't automatically make the offer better for your business.

For the fictional event, assume Saturday admission costs $80, Sunday costs $60 and a weekend pass costs $125. Two individual tickets total $140, so the pass saves $15. These are total buyer prices for this simplified example, with no additional buyer fees or taxes. Your actual price display and tax treatment need their own checks.

Assume serving an attendee costs $18 on Saturday and $12 on Sunday. Also assume a hypothetical ticketing and payment cost of $5 per day ticket and $8 per weekend pass. These costs are invented for the calculation. They are not Loopyah's fees or a claim about any provider's charging model.

A Saturday ticket leaves $57 after its $18 attendance cost and $5 transaction cost. A Sunday ticket leaves $43 after $12 and $5. Someone buying both separately leaves $100. A $125 pass leaves $87 after $30 in attendance costs and $8 in transaction costs.

That $87 contributes towards the bills you pay regardless of attendance, such as the booked venue and agreed production costs. It isn't profit for the whole event. The US Small Business Administration's break-even guidance separates selling price, variable costs and fixed costs. Carry those distinctions into your event budget.

If someone would have bought both days anyway, the pass reduces this contribution by $13. If a Saturday-only buyer chooses the pass, it increases the contribution by $30 compared with their $57 Saturday purchase. The offer depends on which behaviour it changes, not simply how many passes you sell.

Check the whole ticket mix before approving it

Now apply those assumptions to the initial paid allocations. If all 300 passes, 180 Saturday tickets and 120 Sunday tickets sell, ticket revenue totals $66,900. That's $37,500 from passes, $14,400 from Saturday tickets and $7,200 from Sunday tickets.

Paid attendance costs total $13,680. The passes account for $9,000, Saturday tickets for $3,240 and Sunday tickets for $1,440. The assumed ticketing and payment costs total $3,900. Subtract both from revenue and you have $49,320 available before fixed bills and the costs of complimentary attendance.

Our example's 40 complimentary attendees on each day add another $1,200 in attendance costs at the same assumed daily rates. After that, $48,120 remains. If fixed event bills are $45,000, this sold-out initial allocation leaves $3,120 before any omitted costs. If you forgot insurance, marketing or a supplier minimum, the result changes.

That calculation is deliberately modest. It shows why "we sold most of our tickets" isn't enough information. Every discounted pass, unused allocation and late supplier charge can matter when the budget has little room. Put your actual commitments into the model before celebrating the revenue total.

Try a lower-sales scenario as well. Reduce each ticket category using a plausible assumption for your audience, keep genuinely fixed bills unchanged, and recalculate attendance costs. A venue bill won't fall just because Sunday tickets underperform. Check whether catering or staffing really changes before cutting those lines.

Then test a stronger pass preference. Some buyers may move from two day tickets to the pass. Others may add Sunday to a planned Saturday visit. Don't label every pass purchase an additional sale. Identify the assumptions your plan needs and compare them with what you learn after launch.

Let buyers upgrade without duplicating admission

A day-to-pass upgrade can be useful when someone likes the programme but won't commit to the whole weekend immediately. Offer it only if the added day has capacity and your ticketing process can change the access correctly.

Using our fictional prices, upgrading a Saturday ticket to the $125 pass could cost $45. The buyer's total payment becomes $125. Moving a Sunday ticket to the same pass could cost $65. These amounts assume you credit the full original day price and charge no additional upgrade fee.

Set the credit rule before selling. If someone paid a cheaper early-release price, will you credit what they actually paid or the current advertised day price? Crediting the actual payment is easier to explain financially, but whichever rule you choose must appear in your terms and match the checkout process.

Also decide which pass price applies. You might use the available pass release when the upgrade happens. Don't promise every day-ticket buyer an earlier pass price indefinitely unless you've budgeted for that. Explain the rule with a real example that uses your actual release prices.

The upgrade must replace or amend the original admission. Selling a separate pass while leaving the day ticket active can create two usable credentials, inaccurate capacity and confusion over refunds. The buyer should receive a clear record of the added access and know which ticket to show.

In the daily record, a Saturday-to-weekend upgrade consumes one additional Sunday place. It doesn't add another Saturday attendee. Confirm the system makes that distinction, including when staff process an upgrade during the event. If it can't, use a supported replacement process or keep the offer simpler.

Don't assume the upgrade brings $45 of extra contribution. Sunday attendance and any additional transaction costs still come out of it. Check whether the change triggers new catering, staffing or administrative costs. The extra payment helps only after you've accounted for delivering what it buys.

Make VIP access specific and optional

VIP earns a ticket type when it gives buyers a defined experience they can value. A different colour on a pass isn't enough. Decide what someone receives, which days they receive it and how many people you can serve before choosing the price.

A weekend VIP pass might include a reserved viewing area on both days and a named reception on Saturday. List those benefits directly. If Sunday has no premium area, don't let "weekend VIP" imply that it does. Either create a consistent offer or explain the daily difference beside the ticket choice.

Capacity follows the smallest included benefit as well as the main event. If the reception holds 50 guests, you cannot sell 80 VIP passes that all include it. Separate any optional bookings or change the package before selling. A vague "subject to availability" should not undo a benefit used to justify the premium price.

VIP attendees still count in your main daily audience record. If you introduce 30 VIP weekend passes, decide whether they replace 30 standard pass allocations or consume previously unallocated places. Adding a premium label doesn't create a new pool outside the event limit.

Cost the premium separately. Include food, dedicated staff, furniture, cleaning and any minimum supplier charge. Compare the extra price with those extra costs, then check whether enough people want the benefits. Don't turn standard admission into an uncomfortable experience just to make the upgrade sound necessary.

Keep accessibility outside that commercial ladder. The US Department of Justice's accessible ticket sales requirements say accessible seats must be available through the same sales methods and stages, with no higher price than non-accessible seats in the same section. That guidance applies to US ADA-covered situations. Accessibility planning should be part of the admission experience you deliver, not a VIP perk.

Sell extras without rebuilding the ticket menu

An add-on buys something beyond admission. Parking, a specific workshop, merchandise or a meal can fit here when the item is genuinely optional. Keep the basic day or weekend choice clear, then offer the relevant extra.

Give every limited extra its own fulfilment limit. Parking is counted in vehicles, a dinner in diners and a workshop in participants. Those quantities don't necessarily match ticket orders. A buyer purchasing four admissions may need one parking space, while all four people need separate dinner places.

Attach the correct day and time. "Workshop ticket" is weak wording at a weekend event with sessions on both days. Name the session, date and start time. State whether event admission is also required so someone cannot accidentally buy an extra they aren't entitled to use.

Be careful with family packs and group purchases. A pack can simplify payment, but each person still needs the admission that applies to them. Define its adult and child composition, who receives the credentials and whether people can arrive separately. Don't make a group discount depend on your entrance staff doing arithmetic under pressure.

For age-based tickets, state the age boundary and the date on which you measure age. Explain any guardian requirement and whether younger attendees can enter every part of the programme. Check venue and licensing restrictions before offering an all-weekend child admission that excludes the main evening sessions.

Concession tickets need clear eligibility and a respectful verification process. State the accepted evidence and when you check it. Collect only the information you actually need. If concessions get identical admission, don't create a long duplicate menu of every day and release without considering how buyers will choose.

You can omit an extra. If the dinner needs uncertain staffing or the workshop booking process isn't ready, keep it off sale until you can fulfil it. Optional income isn't useful when it creates promises your event team cannot keep.

Review day demand before releasing more passes

Set a review date when you launch, then inspect what each purchase commits you to. If Saturday tickets move faster than passes, look at the programme and the audience before changing prices. People may want the Saturday headliner, have work on Sunday or see too little reason to stay. A pass discount won't fix every one of those problems.

Check the remaining Sunday allowance before promoting passes to Saturday buyers. In our initial allocation, Sunday has only 40 unallocated places. A campaign that successfully upgrades 60 Saturday buyers would need a revised Sunday allocation before those upgrades complete. Reserve the extra admissions through a supported process, rather than letting marketing promise availability the entrance team cannot honour.

Give one person responsibility for approving quantity changes. They should check the daily record, update the sales configuration and confirm that the resulting limits agree. This is oversight of your chosen allocations, not a suggestion to replace working capacity controls with a spreadsheet. Use the controls your setup provides and verify their behaviour.

When sales are weak, diagnose the specific choice. Repeated questions about whether the pass includes Sunday suggest unclear wording. Strong Saturday sales and little Sunday interest suggest a programme or audience problem. Buyers reaching checkout and leaving may have another objection. Change the relevant part and record what happened instead of making every ticket cheaper together.

Put the complete purchase in plain words

The ticket description should make sense without the programme page open beside it. Include the covered dates, daily hours, admission areas and anything important that's excluded. Buyers should not need to infer whether "weekend" starts on Friday or Saturday.

For our two-day example, a useful description would say that the pass includes Saturday and Sunday general admission for one attendee, with the stated opening hours. It would then explain whether the same person must use it throughout and whether leaving and returning is allowed. Replace general language with your actual rules before launch.

Separate ordinary re-entry from transferring a ticket. A pass holder leaving for lunch and returning is one person using their admission. A friend arriving with the pass on Sunday is a different person. Choose whether that is permitted, then check the identification, credential and attendance process can enforce the choice.

Show the payable price honestly. In the United States, the FTC's fee rule guidance requires covered live-event offers displaying prices to include known, calculable mandatory charges upfront. Specified charges can be excluded initially, subject to disclosure requirements before payment. Check whether your event falls within the rule and follow other applicable local requirements.

The same clarity applies to optional extras. Explain their price, what the buyer receives and any eligibility condition before they add one. Don't describe a compulsory charge as optional because it appears separately in checkout. Read the completed purchase as a customer and check the total against the advertised offer.

Your confirmation email should repeat the days and access purchased, along with practical arrival information. Someone who buys Saturday admission should not receive a message that appears to promise the entire weekend. When you change a booking, send the confirmed new access and explain which credential remains valid.

Decide what changes mean for pass holders

A multi-day pass needs a cancellation policy that recognises the purchase people made. A buyer missing Sunday by choice is different from you cancelling Sunday's programme. Decide how you'll respond to each situation before payments start.

Don't assume dividing the pass price by the number of days gives the right remedy. Days may have different value, the event may be sold as one connected experience, and applicable consumer rights can affect the answer. Your internal budget allocation helps you explain a decision but cannot override the buyer's rights.

The Australian Competition and Consumer Commission's event ticket guidance explains that cancellation and significant-change refunds depend on the circumstances. Use it for Australian sales, alongside advice on your actual offer. Don't turn one country's guidance into a worldwide refund policy.

Keep enough funds available for the obligations your pass creates across the event. Receiving the whole weekend payment before Saturday doesn't mean you've delivered Sunday. If an included premium reception changes, examine that promise separately rather than treating main-event admission as proof that everything was supplied.

For transfers, distinguish an unused full pass from a partly used one. If you allow a Sunday transfer after Saturday attendance, the recipient must receive only the remaining permitted access. The original holder must not retain a second valid Sunday admission. Test the actual process before promising this flexibility.

Test the pass through every day

Buy each admission through the journey customers will use. Inspect the confirmation and credential, then ask the entrance team to check the exact access. Test Saturday admission on Saturday and on Sunday. The second attempt should follow your refusal process without invalidating a legitimate ticket for its correct day.

For a weekend pass, test arrival on both days and a duplicate attempt on each day. If re-entry is permitted, test leaving and returning as well. The process must distinguish that allowed return from another person trying to reuse the credential. A successful first scan tells you very little about Sunday's behaviour.

Loopyah sends confirmation emails linking to QR tickets and lets you give door staff check-in access. Those are useful parts of delivery and entrance operations. Confirm the specific multi-day redemption, re-entry, upgrade and shared-capacity behaviour required by your setup before relying on it. A general ticketing capability doesn't prove those particular rules are supported.

Try the less comfortable cases too. A buyer loses their phone after Saturday. Another brings the original day ticket after an upgrade. A group arrives separately, and the purchaser isn't there. Your team needs a supported way to find the valid admission and confirm its remaining access without issuing duplicate credentials.

Check a refund before attendance and another after the first day has been used. Confirm which daily places return to sale and which attendance records remain. If a pass is replaced, its old credential must no longer admit another person. Write down the tested result so the support team and the entrance supervisor give the same answer.

Finally, send the exact ticket descriptions to someone who didn't build the menu. Ask them to choose admission for Saturday only, for both days, and for a premium benefit. Listen to their reasoning. If they choose the wrong option, improve the names and descriptions before asking buyers to spend money.

During sales, review remaining places by day alongside revenue. After the event, compare the ticket mix, daily attendance, upgrades, support questions and final costs. Keep the choices that buyers understood and that paid for the access you delivered. Keep the approved descriptions beside your final allocation record. When a colleague proposes another ticket type, ask which buyer needs it and exactly which existing places it will use.

Start the next edition with that evidence, then build a smaller, clearer menu wherever the previous one made people work too hard.