These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Feature · Admissions
Example screen with sample data
Admissions
Reserve event capacity and retain the admitted outcome.
OverviewReserved admissions×
Event + Ticketing + CRM + Analytics · Admissions
New
Reserved admissions
Admissions
| Parent | Line number | Attendee reference | Quantity | Reserved at | Admitted at | |
|---|---|---|---|---|---|---|
| EVN-14990 | 570 | AR-183 | 810 | 05 Oct | 14 Oct | |
| EVN-25744 | 550 | AR-276 | 670 | 05 Oct | 12 Oct | |
| EVN-84044 | 770 | AR-448 | 220 | 04 Oct | 10 Oct | |
| EVN-73366 | 220 | AR-766 | 180 | 09 Oct | 17 Oct | |
| EVN-22595 | 540 | AR-257 | 80 | 12 Oct | 15 Oct |
6 of 6 records
AR-183Admissions · ADM-84742
ParentEVN-14990
Line number570
Quantity810
Reserved at05 Oct
Admitted at14 Oct
What you can do
Track each admission line
An admission line belongs to an event. It can hold an attendee reference, quantity, price, reserved time, admitted time and provider receipt. Its line number and revision identify the working line. The event is the capacity anchor: a reservation should be evaluated against the same open event that the operator selected, rather than against a similarly named session.
Reservation and admission are different moments. A reserved quantity claims capacity while the team waits for the conditions of completion. The admitted time records that the arrival occurred. The admission operator checks a verified provider capture before completing the reservation and records admission exactly once. These distinctions let the team explain why a place was held without treating every held place as an attendee already admitted.
How the work is organized
- Claim. Use the parent event and line number to identify the reserved quantity.
- Evidence. Compare the provider receipt and verified payment event with the admission claim.
- Outcome. Record admission once and retain the line for closeout reconciliation.
What to agree during setup
Decide how the attendee reference is assigned by the ticket source. Agree the quantity an operator may put on a single line and how price in USD relates to the provider receipt. Confirm which provider event counts as a capture and who checks its verification status. The team should also decide what happens when a reservation expires or an event is cancelled. A cancellation must leave prior admitted history intact.
Choose the person who can correct a line and who must review an executed correction. The event revision and operation key should be checked before a guarded action writes another result. A retry with the same key should return the existing result, not create another capacity claim. Failed or uncertain actions remain available to the reconciliation lead.
Check the handoff on an actual case
At an open conference session, an attendee presents a ticket for two people. The admission operator selects the exact event and records a line with quantity two and the attendee reference. The team checks remaining capacity and the linked provider capture. When both people enter, the operator records the admitted time once. If a network retry repeats the action, the existing receipt explains the outcome. At close, the reconciliation lead compares reserved and admitted quantities with verified capture evidence. A line still reserved but never admitted remains visible for a deliberate closeout decision.
What your team sees
- Reserved admissions — Lines held against event capacity with reserved and admitted times.
- Open events — The events where admission work can proceed.
- Unverified payment evidence — Provider events requiring confirmation before completion.
Follow the work through
See admission and scans for the arrival sequence and event closure for the final comparison.
What it keeps track of
Data model- Admissions
- Reserved and admitted admission lines for an event.
- Events
- Programs, events and sessions with capacity, lifecycle and revision.
- Payment evidence
- Provider payment authorizations, captures, refunds and voids.
- Operation receipts
- Idempotent receipts for guarded operations with expected revision and result state.
Who uses it
Permissions- Admission Operator
- , Event Owner, Reconciliation Lead, Independent Reviewer.
Set up Event + Ticketing + CRM + Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.