Ticketing

Sold vs Scanned: How to Reconcile Ticket Sales With Gate Entry After an Event

To reconcile ticket sales with gate entry, run a three-way match: valid tickets issued, unique tickets scanned in, and people physically counted through the gates. Each issued ticket must end the night in exactly one state: admitted or not used. Any gap between the three numbers has a cause, and the job is to name it before settlement, sponsor reporting or the safety debrief closes.

Light trails running from a bank of stadium turnstiles up to a single point above empty stands

Part of Post-Event Analytics: Turning One Event's Data Into the Next One's Revenue

Our guide to post-event analytics treats sales-versus-gate as one of five numbers that shape the next on-sale. This article goes one level down: how to build the attendance ledger, how to read each variance, and who signs off the final count.

Why is sold-versus-scanned more than a no-show rate?

Because the gap between tickets sold and people admitted is three things at once: a commercial number, a control number and a safety number. A no-show rate tells marketing how many buyers stayed home. A reconciliation tells finance, operations and the safety officer whether the entry system admitted the right people, once each, and whether the count they report is true.

Each audience needs the number for a different reason:

  • Finance and settlement. Any contract priced on attendance, from hospitality and concessions to sponsor activation, needs a defensible headcount, not a sales figure.
  • Sponsors. A sponsor paying for an audience will eventually ask how many people were actually in the building. A scanned, de-duplicated count answers that.
  • Fraud control. Duplicate attempts, cloned tickets and unticketed entry all leave traces in the gap between the three numbers.
  • Safety. Safe capacity applies to people inside, not tickets sold. The safety team needs a count it can trust while the event is running, not only afterwards.

What goes into the attendance ledger?

The attendance ledger is a single table that accounts for every ticket the system issued and every entry the gates recorded. Build it per event, per session and per zone. If a ticket appears in no row, or in two, the ledger is not finished.

The closing identity is simple: valid tickets at doors should equal unique admissions plus tickets not used. Manual admissions sit outside that identity, which is exactly why they must be logged separately.

What is the three-way match?

The three-way match compares three independent sources: the ticketing system's record of valid tickets, the access-control record of unique scans, and a physical count of people through each entry point. Two sources agreeing proves little. Three agreeing, or disagreeing in an explainable way, proves the count.

The physical count is not optional at many venues. The UK Sports Ground Safety Authority's guidance on ingress says all spectators entering all sections of the ground, including VIPs, should be counted at their point of entry, whatever the means of entry, be it a ticket, an electronic card, a security pass or a badge. The UK Health and Safety Executive's event-safety guidance likewise lists monitoring the overall number of people so safe capacity is not exceeded, using methods from turnstiles and hand counters to chipped tickets and people-counting sensors.

That gives a useful rule. The scan record answers "which tickets came in". The physical count answers "how many bodies came in". Staff passes, accreditation and manual admits explain most of the legitimate difference. Whatever remains is the number to investigate.

How do you read each variance?

Every variance points to a short list of causes, and the pattern usually tells you which one. Read the gaps by gate, by time and by channel before reading the total; a total hides the gate where the problem lives.

More people counted than tickets scanned

The physical count runs ahead of unique scans. Likely causes: staff, crew and accreditation passing through spectator gates without being counted separately; manual admissions; tailgating at turnstiles; or a gate that waved people through during a surge. Check the timing. A gap that opens in the last 20 minutes before doors usually means pressure overrode process.

More scans than valid tickets

Unique admissions exceed the valid tickets at doors. That should be impossible, so it means the ledger is wrong: re-entries counted as admissions, voided tickets still accepted at the gate, or the same ticket admitted on two offline devices before they synced. Each cause is a configuration fix, not a staffing one.

A high not-used rate on one channel

If one channel or tier shows far more unused tickets than the rest, look at who bought them. Our post-event analytics guide notes that complimentary and free tickets no-show at far higher rates than paid ones. A spike in a paid channel is different. It can point to speculative bulk buying that failed to resell, or to a partner block counted as issued but never distributed.

Rejected attempts clustered at one gate

Duplicates spread evenly suggest screenshots shared between friends. Duplicates clustered at one gate, in one window, on one ticket batch suggest a counterfeit source. The section on credentials in our guide to access control modernization explains why static barcodes generate this pattern and dynamic credentials suppress it.

When should reconciliation happen, and who signs it off?

Run it in three passes: a snapshot when doors close, a full reconciliation once every device has synced and every manual entry has a reason, and a signed count before any settlement, sponsor report or safety debrief uses it. The ticketing lead owns the ledger, the venue operations or safety lead owns the physical count, and finance signs the final figure.

A workable rhythm:

  • Doors close. Freeze a snapshot: unique admissions per gate and zone, physical counts per entry point, rejected attempts and manual admissions so far.
  • Same night or next morning. Confirm every scanning device has synced. Resolve every manual admission against a reason code. Remove re-entries from admissions.
  • Within the settlement window. Close the ledger, explain every variance above your agreed tolerance, and sign. Only then publish attendance to sponsors, partners or the press.

Agree the tolerance before the event, not after the numbers arrive. Base it on your own previous editions per gate type. A tolerance set after the fact is a negotiation, not a control.

What has to be designed in before doors open?

Reconciliation cannot be retrofitted. If the data is not captured at issue and at the gate, no report can rebuild it later. Five design decisions make the difference, and all of them belong in the event setup, not the debrief.

  • One unique ID per ticket, tagged by channel and tier. Every allocation and comp code carries the name of the issuer that requested it.
  • Voids and refunds propagate to the gate in real time. A cancelled ticket must fail at the scanner, online or offline.
  • Re-entry is its own state. A pass-out and return must not count as a second admission.
  • Every manual admission carries a reason code, a staff ID, a gate and a time. No code, no admission.
  • Offline devices have a sync rule. Define how long a device can validate offline, and confirm sync before the snapshot. Our venue entry operations playbook covers connectivity loss as one of the five failure modes of entry.

The live counts that feed this ledger also feed crowd safety during the event. Our crowd management planning framework sets out how zone counts and reconciliation of attendance against sales feed the post-event review.

How webook.com closes the gap between the box office and the gate

The three-way match only works when sales and entry live in one record. On webook.com, the ticket a buyer receives is the credential the gate validates, so issue, void, transfer and entry are events on the same ticket rather than files exported between systems.

On-ground operations cover fast scanning at the gate on standard mobile devices through the webook PRO App, verification of ticket, identity and access rights, zone, gate and tier-based control, and real-time entry counts. The same page states the commitment this article depends on: match attendance to sales, with post-event reconciliation supported. Data analytics and event insights compare sales to gate in real time and after the event, and the Event Reporting App puts those numbers in front of the people who sign them off.

That design is tested at scale. webook.com serves more than 20 million users, processes more than 25 million tickets a year and reaches more than 180 countries. It is trusted by some of the world's biggest events and rights-holders, including Formula 1, MotoGP, FIFA, UFC and Real Madrid.

Make the count you report the count you can prove

If your box office and your gates still keep separate books, the reconciliation will always be an argument. Talk to the webook.com team about running sales, entry and reporting on one record, so the number you publish is the number you can defend.

Frequently asked

How do you reconcile ticket sales with attendance?

Build an attendance ledger that accounts for every valid ticket at doors as either admitted or not used, then match it against unique gate scans and a physical count per entry point. Explain each variance by gate, time and channel, resolve manual admissions and offline scans, and sign the final count before settlement.

What is a normal gap between tickets sold and attendance?

There is no universal figure. The gap depends on ticket type, price, weather, event format and how many comps were issued. Complimentary and free tickets go unused far more often than paid ones. Set your tolerance from your own previous editions, per gate and ticket type, and agree it before the event.

Why would gate scans exceed tickets sold?

Because something in the ledger is wrong, not because extra fans materialized. The usual causes are re-entries counted as new admissions, voided tickets still accepted at the gate, or the same ticket admitted on two offline devices before they synced. Each is a configuration issue to fix before the next event.

Should staff and accreditation passes go through the same count?

They should be counted, but on their own line. Safety guidance in markets such as the UK expects everyone entering to be counted, whatever the means of entry. Keeping staff, crew and media on separate credentials lets you match spectator scans to spectator tickets and still report the true number of people inside.

Who should own the attendance reconciliation?

The ticketing lead owns the ledger, the venue operations or safety lead owns the physical counts, and finance signs the final figure. Settlement, sponsor reports and published attendance should all wait for that signature, so every audience works from the same number.

Related on webook.com

All articles

Get started

Let's build your event's ticketing

Tell us about your event and what you want it to achieve, and we'll put a dedicated team on the setup that fits.

Get started now
Partner with us