Event Check-In: Move the Line, Then Use the Data
Event check-in confirms a registered person at the door and hands over a badge. It has two jobs: keep the line moving at the arrival peak, and leave one clean record per person of who came and when. Size the stations to the busiest 15 minutes, not the day total, and keep check-in separate from registration.
The sections below cover the check-in methods and what each costs at the door, a hypothetical station calculation, the exceptions that break most check-in data (walk-ins, substitutions, name changes, reprints), and what the record is for after the event. How each collection method is counted is in event attendance tracking, and the division itself is in event attendance rate.
Which event check-in methods are there?
Five methods cover most in-person events. They differ in how long one person takes at the station, how many staff a station needs, and what record the method leaves.
| Method | How it works | Where it slows down | Record it leaves |
|---|---|---|---|
| Pre-printed badges | Badges printed before the event, laid out by surname, handed over at a desk | Finding the badge; late registrations and name changes need a reprint desk | A pickup mark, often typed in by staff, sometimes only at the end of the day |
| Print on demand | Staff look up or scan the registration and print the badge on the spot | Printer jams and slow lookups by name | A check-in with the time the badge printed |
| QR scan | The attendee shows a code from the confirmation email; staff scan it | People searching their inbox at the front of the line | A check-in tied to the registration ID, with capture time |
| Self-service kiosk | The attendee scans or types their name at a screen and the badge prints | First-time users and anyone whose lookup fails | A check-in with capture time and the kiosk that took it |
| Mobile check-in | Staff with phones or tablets scan codes along the line, away from the desks | Badge printing still happens somewhere; connectivity at the venue | A check-in from the device, sometimes uploaded later if the device was offline |
Most events mix methods: QR scan at the main desks, a reprint and exceptions desk to one side, mobile staff working the line when it backs up. Mixing works if every check-in record says which method and which station produced it.
How many check-in stations do you need?
Enough to clear the busiest 15 minutes, usually the window before the opening session. Spreading the day total evenly across the morning hides that peak, which is when the line forms.
Throughput per station per 15 minutes = 900 seconds ÷ Seconds per check-in
Stations needed = Peak arrivals per 15 minutes ÷ Throughput per station per 15 minutes, rounded up
Both inputs can come from your own records. The peak share comes from last year's check-in timestamps, grouped into 15-minute windows. Seconds per check-in come from the same file (check-ins per station in the peak window) or from timing a rehearsal with real staff and the real printers.
Take a hypothetical conference that expects 1,000 arrivals on the first morning. Last year's timestamps put 22% of the morning's arrivals in the 15 minutes before the opening keynote, so the peak is 1,000 × 0.22 = 220 people.
| Method | Seconds per check-in | Check-ins per station per 15 minutes | Stations needed |
|---|---|---|---|
| QR scan with print on demand | 30 | 900 ÷ 30 = 30 | 220 ÷ 30 = 7.3, so 8 |
| Pre-printed badge pickup by surname | 45 | 900 ÷ 45 = 20 | 220 ÷ 20 = 11 |
| Self-service kiosk | 60 | 900 ÷ 60 = 15 | 220 ÷ 15 = 14.7, so 15 |
With 8 QR stations the peak capacity is 8 × 30 = 240, a margin of 20 people. With 6 stations the capacity is 6 × 30 = 180, and 220 − 180 = 40 people are still in line when the keynote starts, joined by whoever arrives next. Kiosks need more units but fewer staff per unit, so compare staff hours as well as station counts, and keep at least one staffed desk beside the kiosks for failed lookups.
Plan a separate desk for exceptions so they never stop a main station. If a walk-in registration takes 3 minutes, one desk handles 60 ÷ 3 = 20 an hour. Thirty walk-ins expected across the peak hour need 30 ÷ 20 = 1.5, so 2 desks.
How do you handle walk-ins, substitutions, and name changes?
Each exception has one rule: create or correct the registration first, then check the person in against it. The check-in should never be the only record that someone was there.
Walk-ins. Register them at the exceptions desk, with a ticket type and an onsite flag, and then check them in. Do not hand over a blank badge and plan to fix the list later. Walk-ins can be a real share of the room. The Maritz Registration Insights Report analysed 360,000 registrations across 30 trade shows and found that in 2023, 9% of registrants registered on site (PCMA Convene). Those are trade show registration records, not a survey and not association conferences, so plan from your own walk-in count where you have one.
Substitutions. When a colleague comes in place of the registrant, record it as a transfer on the original registration: who registered, who attended, and when it changed. Overwriting the name loses the person who bought the ticket, and skipping the record sends the follow-up to someone who was not in the room.
Name changes. A misspelt name or a married name is a correction to the same registration, under the same registration ID. Reprint the badge; do not create a new registrant.
Duplicate badges. A lost badge gets a reprint flagged as a reprint, not a second check-in. Where badges grant access to paid sessions or receptions, mark the old badge void.
Do VIP, speaker, and sponsor lanes need their own process?
Yes. These groups arrive at different times from the general audience, and they often belong on a different line of the report.
Give speakers and VIP guests a short lane with pre-printed badges and a named greeter, so the person giving the keynote is not standing behind 200 attendees. Check sponsor and exhibitor staff in under their own ticket types, often during build or before doors open. With the ticket type kept on every check-in, a report can show paid attendees, comped guests, speakers, and exhibitor staff as separate counts, which matters when the paid audience is the number sponsors bought. Comped registrations covers why free badges belong in their own line.
How is session check-in different from event check-in?
Event check-in records once that a person entered the venue. Session check-in records that they entered a particular room, so the two answer different questions and belong in different fields. What people do once they are inside is the subject of attendee engagement.
Do not treat the first session scan of the day as venue entry unless you decided that before the event and wrote it down. A person can collect a badge and skip every breakout. Another can miss the main desk because a side door was open. Keep both records with their labels; the attendance tracking guide linked above covers how each is counted.
What is the check-in record for after the event?
It does four jobs, and each needs a clean record.
- The attendance rate divides checked-in people by valid registrations, run separately by ticket type. One check-in per person is what makes the numerator a count of people.
- Registrations without a check-in are the no-show list. No-shows need a different message from attendees, sent within days: the recording or slides, and a date for the next event.
- Sponsor reports use checked-in attendees as the denominator for reach, because people who stayed home could not visit a booth. Sponsorship effectiveness uses it that way.
- CRM matching uses the email on the registration as the key that links an attendee to a CRM contact. A substitution with a new email needs that email recorded, or the match goes to the wrong person. Event identity matching covers the rules.
A smaller fifth job is next year's staffing: this year's station timestamps give next year's calculation its peak share and seconds per check-in.
Which data rules keep check-in records usable?
Agree these before badges are ordered, because none of them can be applied later to records that were never kept. The event registration form field guide covers the identity and ticket fields the check-in record will need to reference.
| Rule | Why | How |
|---|---|---|
| One check-in per person per event | The attended count should count people, not scans | Keep re-entries as entries; mark the first qualifying check-in |
| Keep the timestamp | Peak analysis, late arrivals, next year's staffing | Store the capture time; if a device uploads later, store the upload time separately |
| Do not overwrite the registration | Registered and attended are two counts | Keep the check-in as its own record, linked by registration ID |
| Label the method and station | Comparisons across years depend on it | Record desk, kiosk, or device on each check-in |
| Register walk-ins first | An attendee with no registration breaks the rate | Create the registration with an onsite flag, then check in |
| Link substitutions to the original | Follow-up and CRM matching should reach the person who came | Keep the original registrant and the attendee on one record |
| Reprints are not check-ins | Duplicates inflate attendance | Flag reprints; void the old badge where it grants access |
| Corrections have an owner and a reason | Someone will ask why a number changed | Log who changed the record, when, and on what evidence |
Where EventIQ fits
EventIQ replaces nothing. It connects on top of 15+ platforms, among them Cvent, Zoom, and Swapcard for events and Salesforce, HubSpot, and GoHighLevel for CRM. Platforms with an API outside that list are connected on request.
For check-in, Cvent and Eventbrite supply registrations with their date, ticket type, and price where the platform provides them, and the check-in mark. Registration and check-in stay separate records, so registered and attended are two counts, and the attendance rate is a division you run on them. Records sync on a schedule: Cvent every 30 minutes by default, configurable per source. Contacts are matched to CRM by exact email, and each record keeps the result: matched, unmatched, or no email.
EventIQ does not run the door. Scanning, badge printing, and walk-in registration happen in your check-in workflow, and the rules on this page are applied there. It does not merge one person across sources either, so someone registered in two systems appears once in each.
Book a demo to see registrations and check-ins as two separate counts on a sample event, in a 30-minute demo.