Practical framework / 5 MIN READ
Count who arrived without confusing tickets with people
Bridge registration states, check-ins and attendance evidence before reporting event success.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
Registrations, approved places, tickets and check-ins describe different stages of an event. A useful attendance report preserves those distinctions and explains the gaps created by cancellations, group bookings, walk-ins and incomplete check-in processes.
What you will leave with: Create an event attendance bridge with explicit units, reconciliation exceptions and a limited outcome claim.
Use this when
- An event report calls all registrations attendees.
- Door counts and the ticketing platform disagree after a busy arrival period.
This lesson concerns attendance evidence, not event production design or permission to contact registrants.
Define the event unit and outcome
Choose whether the report counts people, tickets, organizations or sessions attended. A group booking can contain several tickets under one buyer, while one person can attend several sessions. Write the unit beside each count and avoid assuming a single registration record equals a single person in the room.
State what attendance means for the decision: checked in at the main entrance, joined an online session, or remained for a defined learning activity. Only use measures the process actually captures. Do not infer participation quality or satisfaction from a registration or entry record.
Map status to evidence
Luma documents registration states such as Going and Waitlist separately from check-in information in its activity timeline. That distinction illustrates why an approved registration is not proof of arrival. Read the actual platform’s status definitions before summarizing.
Record the cutoff used for expected attendance and how cancellations or transfers after that cutoff are handled. Keep the original status history where permitted. A late correction can legitimately change the final report, but should not silently rewrite the count used for staffing or catering decisions made earlier.
Reconcile the arrival process
Compare valid check-ins with the final eligible registration list and separately verified walk-ins. Inspect duplicate scans, group-ticket handling, offline device sync and manual lists. An unmatched record may be a real attendee, a test or a synchronization issue; investigate before deleting or adding it.
Use only necessary personal data and restrict access to the reconciliation team. Do not publish attendee identities in a general campaign report. If entry capture was incomplete, report a supported range or a qualified count with the reason, rather than presenting a guessed exact total as observed attendance.
Report the bridge and the next question
Show registrations, eligible expected attendees, verified check-ins and unresolved differences. Calculate a show-up rate only when numerator and denominator describe the same eligible population. Keep walk-ins separate if they were not in the preregistered denominator.
Then assess the event’s purpose using distinct evidence, such as completed demonstrations, feedback or authorized follow-up outcomes. Attendance is an operational achievement, not automatic proof of learning or future sales. Record the collection improvements needed for the next event without collecting more personal detail than the decision requires.
Make the reasoning concrete.
A hypothetical event has 120 registrations, 20 cancellations before the stated cutoff and 70 verified check-ins among the remaining 100. Ten separately recorded walk-ins also attend. The preregistered show-up rate is 70%, while total verified attendance is 80.
Use all registrations as attendance
Opening: Report 120 attendees and ignore arrival evidence.
Hypothesis: The registration campaign attracted interest.
Risk: Interest is confused with physical presence.
Show the attendance bridge
Opening: Report 100 expected, 70 registered check-ins and ten walk-ins.
Hypothesis: Both the 70% show-up rate and 80-person total are interpretable.
Risk: Any incomplete entry capture still needs disclosure.
Use the reconciled units and cutoff. Keep event attendance separate from claims about participant understanding, satisfaction or commercial conversion.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Unit
Are records people, tickets, buyers or session visits?
Cutoff
Which registration population defines expected attendance?
Evidence
What proves arrival under this event’s process?
Exceptions
How are walk-ins, transfers and duplicate scans handled?
Outcome
What additional evidence addresses the event’s real purpose?
Watch for the wrong conclusion.
- Calling Going or registered status attendance.
- Treating one buyer as one ticket holder.
- Including walk-ins in a preregistered show-up numerator.
- Presenting an incomplete check-in count as a precise census.
Your next action
Build a registration-to-attendance bridge for one event and document every unresolved difference before sharing the result.
Sources & scope
Frameworks, worksheets and hypothetical examples are original editorial synthesis. Linked primary sources support only the stated concepts. Source checking is not an independent audit of effectiveness. No named human author or reviewer is claimed.
- Luma: Updating guest information →Primary technical documentation · Supports: Documents registration states and a separate activity timeline for check-in and ticket changes. Does not make registered or Going status proof of physical attendance.