How to manage admission when one ticket covers several people

Someone buys a ticket for six people. Three arrive together, two come straight from work, and the last person messages to say they're running late. Your first door worker scans the booking and sees a successful check-in. Twenty minutes later, another worker scans the same code and sees "already used."

Both groups have paid to attend. Your entrance process has turned a perfectly ordinary arrival into a dispute.

If you allow people on a group ticket to check in separately, you need a reliable record of each person's admission, or a shared booking balance that reduces by the number actually entering. A yes-or-no check-in for the whole booking cannot tell you how many paid places remain. Decide which arrangement your ticketing setup supports before selling the group offer, then test it with people arriving at different entrances.

The simplest option for independent arrivals is usually a separate admission ticket for each person, all linked to the same purchase. Where you genuinely need one group credential, partial admission must work across every place checking it. This guide explains both arrangements, the instructions buyers need, and how your team should handle the awkward cases without handing out extra entry rights.

Decide what the group ticket actually represents

Start with the offer you sold. "Group ticket" might mean six individual admissions bought at a discount, one table reservation that includes six people, or an admission for a party required to arrive together. Those offers may cost the same and need very different entrance procedures.

For six independent adult admissions, each person can normally use their own ticket under your published terms. The buyer settles the purchase, but doesn't need to accompany everyone. If names matter, your registration process assigns the places to attendees. If names don't matter, each distinct ticket still needs a clear way to be distributed and used once.

A table booking adds another record. The group owns the agreed places at a particular table, but admitting three people doesn't create a second table for the other three. Your check-in record and seating record need to describe the same purchase. Keep table identifiers visible where staff direct arrivals, without making a table number sufficient proof of admission.

An arrive-together offer is different again. It may be reasonable for a supervised activity or a package whose delivery depends on the group entering at once. Tell buyers before purchase. You shouldn't discover at the entrance that your software only supports full-booking admission and turn that limitation into a new condition of sale.

For family combinations, settle eligibility and supervision separately. Our guide to defining family tickets covers who is included and which ages qualify. Allowing separate arrival doesn't remove an accompanying-adult requirement. A place remaining in the booking isn't permission for a child to enter alone.

Write a private description your whole team can repeat. For the worked example in this guide, one purchase includes six adult admissions to one evening event. Separate arrivals are permitted. Each person may enter once, with any subsequent return handled under a separate re-entry policy. The buyer's presence isn't required, and substitutions follow the event's published terms.

That description establishes what you owe the group. It doesn't establish that a particular scanner can deliver it. The next decision is how to represent those six admissions in the tools your entrance team will actually use.

Choose individual tickets or a tested partial-admission balance

Separate tickets are usually easier when people travel independently. The buyer receives or distributes six distinct admission tickets. Each arrival presents the ticket assigned to them, and the door checks that specific admission. The parent purchase remains useful for customer service and accounting without becoming the only entry credential.

The distribution needs care. Telling a buyer to forward the entire confirmation can give every friend every ticket. Two people may then open the first code in the message and accidentally present the same admission. Explain how to identify and share each distinct ticket through the supported delivery method. Test the actual email and mobile view rather than assuming six tickets are obvious because six were purchased.

If the platform supports attendee assignment or ticket transfer, use its supported process where appropriate. Confirm what happens to an old ticket when you replace it. A renamed guest list and an unchanged valid code can describe different people. Our ticket-management guide explains the wider relationship between orders, tickets, transfers and admission records.

A shared credential can work when the system genuinely records partial use. The worker finds the six-person booking, chooses how many people are entering now, commits that admission and sees the updated remainder. The next worker must see the same current balance. A local note on one phone doesn't give another entrance that information.

Ask to see the result of each operation. "Supports group tickets" may describe checkout pricing, ticket bundles or seating, without answering partial admission. You need to know whether a scan admits everybody, opens a quantity choice, or simply retrieves the order. Check whether the worker can undo a mistake without restoring admissions already used by other people.

Loopyah's online ticketing solution describes QR tickets delivered through the confirmation, phone scanning and check-in access for door staff. Those capabilities help staff admit ticket holders without sharing the organizer's full account. They don't, by themselves, establish partial use of a single group code. Test the exact configuration you intend to sell and ask for confirmation of any behaviour the public documentation doesn't describe.

Choose the arrangement you can explain and demonstrate. If separate arrival matters to your audience and one shared code can't preserve the remaining places reliably, configure distinct admissions using a supported method before sales open. If you have already sold the offer, arrange a verified replacement or controlled entrance process that preserves what buyers purchased.

Count people against capacity, even before they arrive

Six admissions reserve six places in the relevant event allocation. They don't reserve one place because the sales screen shows one package. Nor do the unused places become available for walk-up sales when only half the group has arrived.

For an illustrative evening event, suppose your approved attendee allocation is 240 people, with staff and other occupants accounted for separately in the venue plan. You sell 20 six-person bookings and 100 individual admissions. That commits 120 group places plus 100 individual places, leaving 20 unallocated attendee places. It doesn't leave 120 spaces because only 120 products appeared in a report.

Now suppose 60 group attendees and 80 individual attendees have entered. Your arrival record shows 140 unique attendees admitted. Another 80 paid attendees still have unused admission rights. The original 20 unallocated places remain the only unsold allocation in this example, subject to any holds or other commitments. Those 80 expected people haven't forfeited admission because they're outside.

Great Britain's Health and Safety Executive recommends monitoring both overall numbers and how people are distributed within the venue in its crowd-monitoring guidance. A ticket count is one input. It doesn't replace the event's arrangements for assessing occupancy, queues and local crowding.

Keep the units clear in staff reports. "Twenty group bookings sold" is a commercial measure. "One hundred and twenty group admissions committed" describes the people entitled to attend. "Sixty group attendees admitted" describes arrival progress. All can be correct at the same moment.

The same distinction matters for inclusions. Six dinner places may be committed even if only three guests have entered. If your caterer has prepared six meals, the late arrivals haven't reduced that cost. Agree any service deadline and its consequences before purchase; don't let an admission timestamp silently cancel a benefit.

For reserved seating, retain the six allocated seats while recording who has arrived. Reassigning an empty seat because one group member is late can create a second dispute even when the entrance balance is correct. If your event has a lawful, clearly stated late-seating rule, staff need that rule and its approved application.

Tell buyers how their friends get in

An arrangement is only useful if the buyer can pass it on. Explain whether each person needs a distinct ticket, whether the group shares a booking credential, and what a late arrival should do. Put that explanation beside the group offer, then repeat the relevant instruction in the confirmation and pre-event reminder.

Loopyah's Worth It Event Index asked 500 US consumers how clear they usually felt about the experience before buying an event ticket. In the survey fielded on 11 February 2026, 31% answered "a moderate amount," 5.8% "a little" and 0.4% "none at all." These are general expectations, not findings about group tickets or proof that particular arrival wording increases sales. The full Worth It Event Index gives the context.

For distinct tickets, a useful instruction would be: "Your booking includes six separate admission tickets. Send each guest their own ticket using the ticket-sharing method in your confirmation. Guests may arrive separately. Please check that everyone has a different ticket before travelling. If you can't distribute them, contact our team through the support details below."

For a tested shared-balance arrangement, the instruction changes: "Your booking covers six adult admissions. You may arrive separately. Present the booking credential at the group-admission desk and tell the worker how many people are entering with you. Staff will check the booking and record only those arrivals. Later guests should use the same desk and follow the booking instructions."

Adapt the proof and delivery method to your actual setup. Don't tell people that a surname, order number or screenshot is enough unless you have deliberately approved it as part of the process. Publicly guessing a buyer's name shouldn't be an easy route to using their remaining places.

The buyer may be staying home. Make sure the instructions don't require them to answer a call at the entrance unless that requirement was part of the offer. A company coordinator or birthday organizer can buy admission for others without becoming an unpaid remote check-in worker all evening.

Use your confirmation email to answer the immediate next question: what should the buyer do now? If ticket delivery is still pending, state when and how it happens. Don't send "you're all ready" while every guest still needs an action nobody has explained.

Keep instructions accessible as text. A picture showing which QR code to tap can help, but it shouldn't be the only explanation. W3C's guidance on user notifications recommends clear feedback and instructions for resolving errors. Apply that thinking to delivery and assignment too: tell people what succeeded, what remains incomplete and where to get help.

Record the people entering now, then confirm the remainder

Let's follow the six-person booking. We'll call it booking G104. The label and numbers are fictional and describe a procedure, not a screen in any named platform. Initially, six admissions are valid and none has been used.

At 18:10, three guests arrive together. The worker validates their right to use G104, establishes that three people are physically entering, records three first admissions and checks that the saved remainder is three. They then direct those guests onward. If entry requires a separate search or eligibility check, complete the relevant checks before treating the people as admitted.

At 18:35, two more arrive. The next worker retrieves the current record, sees three admissions remaining, validates the request and records two. The booking now shows five unique people admitted and one valid place remaining. A later presentation of the code doesn't change those facts until another admission is actually authorized and recorded.

At 19:05, the sixth attendee arrives and uses the final place. The balance reaches zero. Any further presentation needs investigation rather than another group admission. The code may still identify the purchase, but identifying a paid purchase doesn't create an unused admission within it.

For each partial admission, the useful record is straightforward: booking reference, number admitted in that action, time, entrance, staff identifier, successful save and remaining balance. If the system identifies each individual ticket, preserve those ticket identifiers instead of inventing a second manual count. Use the platform's existing history where it supplies the information.

Confirm the saved result before letting a second action depend on it. A worker may tap a button and lose connection before seeing whether it succeeded. Repeating the action blindly can record the same people twice. The right response is to retrieve the current record or escalate through the agreed process, then establish whether the first action completed.

Don't ask staff to keep the balance in their heads. A queue interruption, shift change or noisy radio call can turn "three came through earlier" into a guess. Record the event while it happens, and make the current balance readable to the next person who needs it.

Stop two entrances using the same remaining place

The difficult case is often simultaneous arrival. G104 has one place left. Someone presents the booking at the main entrance while another person presents it at a side entrance. Both workers initially see one available place. If each can independently approve it, two people can enter against the final admission.

Your provider should be able to explain what prevents that result. Ask the question in operational language: "If both workers try to use the last group place at the same time, which admission succeeds, and what does the other worker see?" A demonstration with two devices is more useful than a promise that the numbers sync eventually.

The underlying software needs a way to treat checking availability and committing admission as one protected operation. PostgreSQL's documentation on transaction isolation explains why concurrent changes can produce inconsistent results without appropriate controls. Your door team doesn't need to choose database settings. Your supplier needs to demonstrate the correct outcome in the check-in product you're buying.

Test the failure message as well as the successful scan. The second worker needs to see that no place was consumed by their attempt and that the attendee needs help. A vague warning that leaves staff uncertain encourages repeated taps or discretionary admission.

If your available setup can't safely share the balance across entrances, restrict shared-code processing to one controlled admission point. Other workers direct the group there without consuming or promising a place. This is a fallback that needs queue planning and clear signs, not a reason to wave people between entrances until someone says yes.

Great Britain's HSE discusses entrances, queuing systems and keeping emergency routes clear in its crowd-control guidance. Position your resolution point where people can wait safely. Don't create a group-ticket desk that obstructs the accessible entrance or forces a queue into an exit route.

For individual tickets, the analogous test is two people presenting the same distinct ticket. Whatever ticket arrangement you choose, duplicate use needs a reliable response. Replacing one shared credential with six separate ones improves distribution, but each credential still needs protection against being used twice.

Resolve an already-used message without accusing the guest

"Already used" describes a system state. It doesn't establish that the person in front of you is trying to cheat. A friend may have shown the wrong ticket, a worker may have admitted the whole group accidentally, or the current guest may genuinely be returning after entering earlier.

Move the question to the person authorized to resolve it. The scanning worker can say: "This booking shows earlier admission. We'll check which places were used and whether yours is still available." That explains the issue without announcing a fraud accusation to everyone in the queue.

Look at the admission history and the booking's actual entitlement. For G104, three admitted plus three remaining is consistent with three later guests. Six marked admitted after only three physically entered suggests a recording problem, but you still need evidence before restoring places. Check the worker's action, entrance record and any individual ticket history available.

If the first worker accidentally consumed all six, a supervisor should use the supported correction process to reverse only the mistaken part. Preserve the three genuine admissions. Record the reason and the person authorizing the correction. Don't reset the entire booking to unused and let the first three tickets become valid for new first entry.

Where the software only supports undoing the entire booking, pause and establish a controlled method with the authorized lead. You may need to reconstruct the current valid admissions using supported records before scanning resumes. Don't improvise a sequence that briefly exposes all six places to use at other entrances.

For distinct tickets, ask which ticket the earlier guest presented. If two friends shared the same first ticket, one of the other legitimate tickets may remain unused. Help the buyer distribute the correct credential through the supported method. The answer isn't to issue a seventh ticket simply because two people have the same screenshot.

Sometimes the evidence is inconclusive. Your supervisor then needs the event's approved exception policy and current capacity position. An extra admission, if genuinely authorized and safe, must be recorded as an extra admission with its reason. It shouldn't be hidden as a correction to make the original purchase appear to cover more people.

Keep re-entry, replacements and refunds separate

A guest who used an admission and stepped outside is different from a guest arriving for the first time. If the returning guest consumes the final unused group place, the sixth attendee may be refused later. Your re-entry procedure needs to recognize the earlier attendee without reducing the group's remaining first admissions.

Don't let a generic "undo check-in" instruction become the standard way to let someone return. Depending on the system, it can restore a first-entry right and remove evidence of attendance. Agree what staff should do for returns and how that affects occupancy monitoring. Neither a valid re-entry credential nor an unused ticket establishes that an area currently has room to admit someone safely.

A replacement guest raises another question. If the original person hasn't entered, your transfer policy may permit someone else to use the place. If the original person has already attended, swapping the name doesn't automatically create another admission. Apply the offer's actual terms, and keep the record of what happened.

For a table of six, someone leaving early doesn't normally release their seat and admission for a seventh guest under an ordinary six-person offer. If your event deliberately sells shared use at different times, define that product and its operating conditions explicitly. Don't let it emerge from an informal conversation at the door.

A refund for a cancelled place changes both the money and the valid admissions. Suppose you approve cancellation of one unused place in G104 before entry. Record that the booking now carries five valid admissions, subject to the agreed terms and applicable rights. Processing money back without updating admission can leave all six places usable.

The reverse matters too. Cancelling an admission doesn't prove the refund reached the buyer. Follow the supported payment process and retain its result. Our event refund policy guide explains how to distinguish voluntary changes from situations where the event hasn't delivered the promised service.

If you cancel the sixth unused place after three have entered, the valid total becomes five, admitted remains three and unused becomes two. There is no reason to alter the three people already recorded. This arithmetic is simple enough to include in staff rehearsal and important enough to verify after the correction saves.

Collect enough information without exposing the group

A shared booking process can become intrusive when staff compensate for weak credentials by asking everyone personal questions. Decide how you will establish a person's right to an unused admission before event day. Use the minimum information that genuinely helps with that task.

A surname on its own may be easy to guess. A booking reference shared in a group chat may identify an order without proving that the person has permission to use it. Distinct tickets distributed through the supported process, approved attendee assignment, or an agreed authorization route can make the decision more reliable. Choose a proportionate method for the event rather than assembling ad hoc questions at the entrance.

Don't ask later guests to recite the purchaser's address or payment details. It puts the group in an uncomfortable position and can encourage the buyer to share information that their friends don't need. A payment-card image should never become an improvised event credential.

The UK's Information Commissioner's Office describes keeping personal data adequate, relevant and limited to the purpose in its data-minimisation guidance. The guidance is under review following changes to UK law. Apply the requirements that govern your event and ask which information staff actually need to resolve admission.

Keep sensitive access arrangements out of a general group list. A worker may need to know that a guest should use an agreed entrance, while having no need to see the medical explanation behind the arrangement. Share the practical instruction with the people delivering it and protect the underlying conversation.

For assigned-seat events covered by the US rules, the Department of Justice's ticket-sales guidance includes accessible seating, companion seating and group sales. Check those requirements when planning how a group is seated and admitted. A shared booking rule shouldn't create a new barrier for someone using accessible seating.

For children, keep the approved supervision requirements visible to the responsible worker without publishing unnecessary details to every device. If your process involves school or youth groups, use the event's safeguarding arrangements rather than treating a remaining numeric balance as sufficient authority for entry.

Prepare a fallback before devices stop talking

A shared balance becomes much harder when entrance devices lose connection. Two downloaded copies of the same booking can each show the same unused places. Recording admissions locally and hoping the copies reconcile later cannot prevent both entrances consuming those places now.

Ask your supplier exactly what works without a connection in the chosen configuration. Test a device that disconnects before a scan and another that loses service after the worker submits it. The second case matters because the admission may already have saved elsewhere. A missing success message doesn't prove that nothing happened.

For a modest event, a controlled fallback may route shared bookings to one staffed point with one current record. Establish when that point takes control, how the other entrances stop processing the affected bookings, and how already admitted people are accounted for. A supervisor owns the switch. Individual workers shouldn't decide independently to start their own paper list.

If you use paper, protect it and keep it current. Record each admission and correction against the booking, assign one writer, and prevent other devices continuing to consume the same balance. An old printed list needs reconciliation with admissions already saved before it becomes usable. Otherwise the fallback starts by forgetting people who entered earlier.

When service returns, reconcile the controlled record with the platform before reopening group processing elsewhere. Someone needs to check which actions already reached the system and which still need recording. Entering every paper line again can double-count admissions that succeeded before the connection failed.

For larger or more complicated events, specify the resilience you need during procurement and work with your provider and event operations lead. One desk may be inadequate for your expected arrival demand. The right solution has to maintain admission control and manage the physical queue under the conditions your venue can support.

Tell staff what to say while the fallback is activated. "We're checking your booking at the group desk" is useful when that desk exists and knows what to do. "Try the other entrance" only transfers the confusion unless the other entrance has accepted responsibility.

Tell the next shift what the booking currently allows

A late arrival may meet a worker who wasn't there for the original group. Make the handover describe the saved position and any unresolved question. "There was some trouble with this group earlier" doesn't tell the next shift whether they can admit someone, and it encourages the guest to explain the whole evening again.

For G104 after the first five people have entered, a useful handover says that five first admissions are recorded, one valid first admission remains, and no correction is pending. Include where to find the record and who resolves a dispute. If the final guest has already contacted support, add the practical instruction that staff need, without copying a private conversation into a general briefing.

When a correction is still under investigation, identify the worker responsible and what action is paused. Perhaps G104 must be processed by the supervisor until an earlier mistaken scan is resolved. Other entrances need to know that restriction. They shouldn't see an unexplained balance and attempt another repair while the supervisor is working on the first one.

Make sure permission changes follow the handover. Someone finishing their shift shouldn't leave their signed-in phone with a replacement who then records admissions under the wrong identity. Use your supported staff-access arrangement so the history identifies who actually made the decision. The point is to make later questions answerable, not to blame workers for every guest problem.

There is also a handover to the people delivering the event. If three guests from a six-person table have arrived, the host may need to know which table to direct them to and that three places remain expected. They don't need a separate authority to admit three more people outside the check-in process. Keep arrival confirmation and table service coordinated without creating two competing entrance records.

Close unused places deliberately after admission ends

Decide what "unused" means in your final records. For the normal six-person example, five unique arrivals and one unused valid place means one person didn't attend. It doesn't mean five purchases, a cancelled ticket or an automatic refund. Those are different facts with different consequences.

Where the offer includes a published last-entry time, make the cutoff clear before purchase and use the event's approved exception process. An attendee delayed by transport may contact you before that time. Record the decision you actually make and pass it to the entrance lead. Don't leave a support promise in an inbox while the door applies a different answer.

Don't release late places for new sales simply because arrival has slowed. Before a genuinely cancelled place becomes available again, verify that the original right has ended through the supported process, that selling it complies with your terms and applicable obligations, and that the event can still deliver the replacement admission safely. A no-show forecast isn't a cancellation record.

After doors close, preserve the distinction between what was sold and what was used. If the six-person purchase remained valid and only five attended, keep the paid quantity and the attendance quantity separately. That makes your next forecast more useful. It also prevents a later customer-service worker from reading a no-show as evidence that the buyer was promised money back.

Work out whether the group offer still pays

Reliable admission has a cost, and an awkward group offer can use more staff time than you expected. That doesn't make group sales a bad idea. It means the price and process should account for how you actually deliver the admissions.

Here's an entirely hypothetical USD example, not a benchmark or Loopyah rate. Your event retains $240 from a six-person booking after the payment deductions and taxes included in your forecast. Costs that increase with attendance are $15 per included person, so the six places add $90. The booking contributes $150 toward fixed event costs and profit before any extra support work.

Suppose you plan additional group support of two workers for three hours each, at $25 per hour including the employment overheads used in your budget. That adds $150. Across 20 group bookings, the cost averages $7.50 per booking. Their combined $3,000 contribution before that extra support becomes $2,850 after it, assuming all the other stated costs and sales remain unchanged.

Don't infer that each group needs a particular number of minutes at the entrance from this example. The staffing allocation is an invented budget assumption. Use your own expected arrivals, rehearsals and observed handling times to plan the actual service, then check the queue with your operations team.

Now compare the price with the realistic alternative. If the same six people would each buy a ticket retaining $45, their combined retained revenue would be $270. With the same $90 attendee cost, they contribute $180 before group-specific support. Selling the six-person offer retains $30 less for those attendees. That's a worthwhile choice only when it serves your commercial plan, such as attracting a purchase that wouldn't otherwise happen or filling a quieter session.

Our guide to group ticket discounts develops that pricing decision. A smoother group purchase can be valuable without a discount, and a discount doesn't remove the need for a workable entrance. Keep the promise understandable enough that buyers don't need support simply to distribute the admission they've bought.

Check how no-shows affect the costs before interpreting the result. In the hypothetical six-person booking, if only five attend and the $15 cost genuinely arises only when someone enters, attendee costs fall to $75. The booking then contributes $165 before extra support. But if you committed six meals or materials in advance, the cost may remain $90 and the contribution remains $150. The attendance record alone can't tell you which cost changed.

A voluntary refund needs another calculation. If you return an agreed $40 of retained revenue for one unused place and avoid its $15 delivery cost, the five-person booking retains $200 and costs $75, leaving $125 before support. That is $25 below the original $150 contribution. If the delivery cost can't be avoided, it leaves $110 instead. These are alternative illustrative outcomes, not a refund recommendation or a statement of what your terms permit. Confirm the actual refund amount, fees and supplier commitments before promising money back.

Track actual exceptions after the event. If staff had to resolve the same delivery problem repeatedly, correcting the confirmation may cost less than adding another worker next time. If your chosen ticket structure creates unavoidable manual processing, include that continuing cost when deciding whether to sell it again.

Rehearse the whole booking before opening sales

Create a test booking in the environment your provider supports for testing. Use the actual delivery route, staff permissions and entrance devices. Have someone who didn't configure the offer act as the buyer. Ask them to give five friends their admission instructions without your help.

For G104, admit three people, then two, then one. Check the saved remainder after each action and verify the record on another device. Present the credential again at zero. The worker should be able to explain what happened and where to send a legitimate question without guessing.

Then test the cases that could change the count. Try two devices claiming the last place. Simulate a whole-booking check-in made in error and verify the supported correction. Cancel one unused place, check the remaining valid entitlement and confirm that already admitted people remain recorded. Test a guest returning after entry without consuming a new first admission.

Run the connection-loss scenario, including the moment of switching control and the later reconciliation. Let the staff who will operate the fallback carry it out. A plan that only its author can follow is unfinished.

Write the results into the briefing. Name who approves corrections, who owns the fallback, and which place handles shared-code questions. Include the exact buyer instructions staff will hear repeated back to them. If different people describe the offer differently, settle the difference while you still have time to change the setup or wording.

After the event, compare valid admissions, unique first arrivals, approved corrections and unused places. Investigate unexplained differences before treating the figures as attendance. Separate returns from first arrivals and purchases from people. Use the pattern of exceptions to fix the next group offer, then repeat the same rehearsal on its final configuration before accepting payment.