Event Attendance Reconciliation

A sold ticket does not mean someone came, since a guest may enter without scanning, leave and return, bring a child, or attend under a complimentary pass. Different systems count these people differently, so decide in advance whether the reported number means unique people admitted, peak simultaneous occupancy or total entries.

Each serves a different purpose, and the point of reconciliation is to answer a specified question, not to force every source into one figure. Gather ticket and guest lists, scanner logs, manual admission records, staff and exhibitor passes, and any venue count, and deduplicate re-entry scans using an appropriate identifier.

Investigate offline scanners and unrecorded walk-ins, noting that an offline scanner can upload late and create apparent duplicates. Compare device logs, manual entries and badge identifiers before changing the final count, and keep staff and vendors separate from paying attendees unless the reporting purpose includes them.

For safety, the venue's occupancy count may require a live estimate, not a later sales report, and a post-event unique visitor count cannot stand in for that safety control. For catering, the contract may use a guarantee or actual covers, and for sponsors, specify whether the count is verified visitors or total scans.

Never silently use the largest plausible number because it looks better in a recap. Label each report with its definition and time window, and keep an adjustment trail that explains the reason, source and reviewer.

For a multi-day event, decide whether a person attending twice counts once overall or once on each day; both can be useful, but they cannot share the same label. Set a cut-off for a provisional report and a later final report after offline scans settle, and if the final number changes, show the revision rather than quietly replacing a sponsor deck.

An attendance record can contain personal information, so restrict raw identity data, share aggregate counts where sufficient, and retain only what the purpose requires. Do not repurpose check-in data for promotional contact without a separate permission and legal basis.

When a check-in system goes down, staff need a manual fallback with a unique reference and later deduplication, and that process should be tested before doors open. Document the reconciliation differences and owner, because repeated manual admissions may mean access control is too slow, and a large sold-to-attended gap can guide reminders and scheduling.

For owners, a defensible count helps make honest decisions about future capacity and marketing spend while reducing disputes over per-attendee fees. A system that reports accurate totals only when nothing goes wrong is not a reliable counting system.