Manage group-ticket entitlements, entrance checks and attendance reporting around the rules of your venue.
Define the admissions included in each bundle.
Show used and remaining entitlements separately.
Keep the session, entrance and time connected.
Distinguish ticket bundles, entitlements and admissions.
Connected teams
Track bundles and admissions separately.
One guest on a two-person ticket arrives early; the other arrives later. Staff need to see how many admissions remain. Marking the whole ticket as used creates a dispute at the second arrival. Leaving it unused obscures the admission already recorded.
Separate the ticket bundle from its admission entitlements. Staff act on a defined number of admissions, while managers distinguish bundles sold, people entitled to enter and admissions checked in.
This approach is relevant to recurring shows with group tickets or several entrances. Where an existing platform already supports the required rules, assess that capability before commissioning additional software.
From request to action
Staff select a session and entrance, enter a sample ticket reference and confirm. The result identifies the session, ticket type, used and remaining entitlements, time and entrance.
After one admission is used on a two-person ticket, the result shows one used and one remaining. The organizer workspace keeps the corresponding entry, helping staff check the next arrival and trace earlier admissions.
Available admission
Available admission
Check in a guest to see how bundles and admissions differ.
The operating model
| Situation | Rule to settle | Record required |
|---|---|---|
| A group arrives separately | Whether partial admission is allowed and how many entries to use | Used and remaining entitlements |
| A ticket is presented again | Whether admissions remain or the attempt is a duplicate | Previous results and times |
| A ticket is refunded or for another show | Whether to refuse entry and who handles escalation | Reason and responsible operator |
| A staff member makes a mistake | Who may reverse the action | Original entry, reversal and reason |
Define these decisions before implementation, then test them with the equipment and entrances used on site. The demo shows ticket-reference entry and feedback. Concurrent devices, cameras, scanners and recovery after a network outage require separate validation.
Rules that travel with the work
| Measure | Business question | Definition to agree |
|---|---|---|
| Ticket bundles sold | How many sales units were issued? | Treatment of refunds, complimentary tickets and cancellations |
| Admission entitlements sold | How many people may enter? | Admissions included in each ticket type |
| Admissions checked in | How many entitlements were used? | Reversals and repeated presentations |
| Check-in rate | What proportion of entitlements has been used? | Included sessions and reporting cutoff |
The demo presents these units separately and displays its check-in-rate formula. The operational benefit is a shared definition of sales and attendance. Refund, channel and settlement reporting also requires agreed source data.
Used entitlements ÷ Sold entitlements
Sales and attendance answer different questions.
Ready for the next handoff
The organizer workspace lists shows with ticket types, sales and remaining quantities, plus search, filtering and sorting. The audience view displays categories, times, locations and starting prices.
For recurring events, define which information can be reused and which must be confirmed for each show: entrances, admission times, complimentary allocations and refund policies. If several sales channels are involved, establish how each supplies order and check-in data before designing a consolidated view.
A wider perspective
PianoFight
Workflow illustration based on the published case.
Eventbrite’s historical PianoFight case connects mobile ticket buying, entrance check-in and API-based internal reporting. For a venue with a regular program, the buying decision extends from selling tickets to running the door and using the data afterwards. The vendor-published case concerns 2015–2016; it does not establish current operating scale or a return for this solution. PianoFight case study
Charging models affect the decision too. Ticket Tailor offers pay-as-you-go ticket fees and prepaid credits, with payment processing charged separately through connected payment services. Compare the software and collection costs together, and check how refunds and existing payment accounts will work. Ticket Tailor pricing
These products provide references for the same operating tasks. Availability, payment options and channel suitability depend on your market. Retain channels that contribute useful sales; scope additional software around gaps in your admission rules, reporting and staff authorization.
Choose the right approach
Select an approach to focus your evaluation01 — 03
Check that the platform’s rules, channels and data terms fit your operation.
01Confirm who owns orders and refunds, who maintains entitlement status, which records feed finance and who handles entrance exceptions. Assess investment against actual ticket volume, channel contribution and the long-term support plan.
A practical first release
Bring a representative ticket-type table, group-ticket rules, refund policy, entrance and device list, and the channels you want to retain. Use them to define the first release, design the workflow, develop integrations and rehearse on site before launch.
Acceptance should cover valid tickets, remaining entitlements, repeated presentations, refunds, the wrong session and operator mistakes. Multiple entrances require simultaneous tests on the actual devices and network.
The demo uses local data and simulated payments. Live ticket sales require connected order, payment, refund and admission services, with an agreed operating and support arrangement.
Assess its configuration and interfaces first. Keep suitable channels and scope only the operational or entrance connections that are needed.
Define the policy before designing the entitlement and refund relationship. Include examples of partially used tickets and transfer requirements in acceptance.
Each entrance needs a shared entitlement state and clear duplicate feedback. Rehearse simultaneous use of the same ticket across the actual devices before launch.
Record the work involved in exceptions, reporting and channel reconciliation. Compare available platform capabilities with development and ongoing maintenance. Validate the scope before committing to a larger rollout.
Related solutions
AI, capital-markets docs, OCR, vision, IoT and membership operations — composable for your industry.
Connect exhibition listings, personal visit plans and editorial updates so audiences can plan a visit with the right information.
Help shoppers move from a room brief and budget to comparable furniture options, a 3D preview and a store appointment.
Give families a structured introduction to your programmes through grade-based activities, clearly explained results and course enquiries.