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.
- Conference Management
- Features
- Admissions
Admissions
Reserve event capacity and retain the record of actual admission.
OverviewAdmission lines×
Conference Management · Admissions
New
Admission lines
Admissions
| Id | Parent | Line number | Attendee reference | Quantity | Reserved at | |
|---|---|---|---|---|---|---|
| IDD-949 | EVN-87532 | 820 | AR-229 | 180 | 05 Oct | |
| IDD-351 | EVN-11343 | 130 | AR-367 | 910 | 12 Oct | |
| IDD-701 | EVN-57392 | 450 | AR-782 | 700 | 04 Oct | |
| IDD-809 | EVN-79583 | 170 | AR-251 | 170 | 04 Oct | |
| IDD-961 | EVN-76103 | 100 | AR-646 | 220 | 07 Oct |
6 of 6 records
IDD-949Admissions · ADM-74305
ParentEVN-87532
Line number820
Attendee referenceAR-229
Quantity180
Reserved at05 Oct
What you can do
Separate reservation from arrival
An admission line belongs to one event. It carries a line number, revision, attendee reference, quantity, price, reservation time, admission time and provider receipt. Admissions Lead uses it to distinguish capacity held for a registration from people who actually arrived. The line’s parent must be the selected event, because two conferences may run near each other and use the same venue.
A reservation is a capacity effect. An admission is an observed entry. Admissions Lead records the admission time exactly once when a scan occurs. That protects the historical arrival record when staff retry a request or reconcile an interrupted operation. The operation receipt records the action, expected event revision and result; a stable operation key helps prevent repeated execution from making a duplicate admission.
How the work is organized
- Reserved scope. Admissions Lead checks the event and available capacity before adding an admission line.
- Actual entry. The admission time records the attendee’s arrival without changing the earlier reservation time.
- Provider effect. Verified capture evidence supports a completed reservation, separate from the capacity check.
What to agree during setup
Agree how the attendee reference is supplied, what quantity represents and who may record entry. Decide how a provider receipt relates to the payment evidence record. Choose the source of authoritative capture events before the first live registration. An internal note about payment should not replace the provider’s confirmed event.
Rehearse a retry from the admissions desk. If the first action appears to time out, staff should inspect the operation receipt and admission line before repeating it. If the expected event revision has changed, the request needs review against the current event. Reconciliation should identify a missing or inconsistent effect; it should not cause a second external execution.
Check the handoff on an actual case
Use an event with limited capacity and an approved registration. Admissions Lead creates the reservation under that event, recording the line number, quantity and reservation time. Finance Reviewer checks the related provider capture and its verified state. At the door, admissions records the actual admission time once. The team can now compare reserved quantity, admitted quantity and event capacity without treating the booking time as the entry time.
For an interrupted scan, inspect the operation receipt. If an admission time is already recorded, preserve it. If the receipt is pending and the linked effect is absent, Finance Reviewer checks the local records and any external reference before marking the result. The difference between missing evidence and a failed action must stay visible.
What your team sees
- Admission lines — See reserved and admitted quantities with their separate timestamps.
- Active registrations — Check which registration records have reached approval or completion.
- Receipts needing review — Investigate operations whose expected effect has not been verified.
Follow the work through
See admission for capacity and entry checks and event close for reconciliation at the end of the event.
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.
- Registrations
- Participant registration records submitted for review and completion.
- 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- Admissions Lead
- , Registration Coordinator, Finance Reviewer, Event Owner.
- Admissions Lead
- Records the entry; Finance Reviewer resolves evidence discrepancies; the owner retains overall event accountability.
Set up Conference Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.