Event Check-In Glossary and FAQ Hub
Plain-language definitions for the terms organizers, venue staff, and software vendors use when talking about attendee check-in, badges, and scanning, followed by answers to the questions we hear most often.
- Access control
- The rules and mechanisms that decide which attendees may enter which spaces. At events this usually means checking a badge or ticket type at a room or area entrance, either visually or with a scanner, and turning away anyone who is not eligible.
- Attendee record
- The single entry in the check-in system that represents one person: name, email, ticket type, registration date, badge fields, and check-in status. Every scan, print, and session entry should reference this record rather than a copy of it.
- Badge stock
- The blank badge material loaded into an on-site printer, typically card stock or synthetic sheets cut to a standard size. Running out of badge stock is one of the most common and most avoidable causes of a stalled check-in line.
- Badge template
- The layout applied to every printed badge: which fields appear (name, company, ticket type, QR code), their sizes, and any color coding. A template is set up before the event so on-site printing needs no design decisions at the door.
- Barcode
- A one-dimensional code of vertical lines that encodes a short identifier. Older check-in systems and some ticketing platforms still use barcodes on printed tickets, though QR codes have largely replaced them because they hold more data and scan from a phone screen more reliably.
- Capacity cap
- The maximum number of people allowed in a room or session, set by fire code, seating, or the organizer's own limit. Session scanning tools compare live entry counts against the cap to signal when a room is full.
- Check-in rate
- The number of attendees processed per station per unit of time, usually per minute or per hour. Measuring the real rate during the first fifteen minutes tells you whether the current number of stations can absorb the peak.
- Check-in station
- One staffed or self-service position where attendees are checked in. A station typically consists of a device running the check-in software, a scanner (often the device camera), optionally a badge printer, and one or more staff members.
- Duplicate check-in
- The same attendee recorded as checked in more than once, usually because two stations processed them during a sync gap or because a name search matched the wrong record. Good systems flag duplicates for review rather than silently counting both.
- Express lane
- A dedicated line for attendees who can be processed quickly, typically those with a QR code ready and no changes needed. Separating them from walk-ups and exceptions keeps the main flow moving during the peak.
- Kiosk
- A self-service check-in station where the attendee scans their own code or types their name, and a badge prints without staff involvement. Kiosks add parallel capacity but need floaters nearby for people who get stuck.
- Lanyard
- The cord worn around the neck that holds a badge. It sounds trivial, but lanyards are a real logistics item: they need to be sourced, are sometimes sponsor-branded, and must be handed out at check-in without slowing the line.
- Lead retrieval
- The process by which exhibitors and sponsors scan attendee badges at their booth to capture contact details. It relies on the same badge codes as check-in and is typically governed by the attendee's consent settings and the event's privacy policy.
- No-show rate
- The share of registered attendees who never checked in. It varies widely with ticket price, event type, and reminder cadence, and it is only knowable if check-in is recorded for everyone rather than estimated from a headcount.
- Offline mode
- The ability of a check-in app to keep working without a network connection by holding a local copy of the attendee list and queuing check-ins to sync later. It is the single most important resilience feature for event-day software.
- On-demand badge printing
- Printing each badge at the moment of check-in rather than in advance. It eliminates badge waste from no-shows and ensures the badge reflects current data, at the cost of needing printers and stock at the venue.
- Pre-printed badges
- Badges produced before the event from a registration export, usually sorted alphabetically for pickup. They avoid on-site printing but lock the data at the export date and require a separate process for corrections and late registrations.
- QR code
- A two-dimensional square code that encodes an identifier, sent to attendees in their confirmation email and scanned at check-in. QR codes scan quickly from phone screens and printouts and are the standard for modern check-in.
- Registration export
- A file, typically in CSV or spreadsheet format, containing the attendee list pulled from the registration or ticketing platform. It is the usual way to load attendees into a check-in tool when the two systems are not directly integrated.
- RFID badge
- A badge containing a small radio chip that can be read by a nearby reader without a line of sight. RFID and the related NFC technology allow tap-based or even walk-through check-in and are common for reusable credentials at recurring events.
- Scan-in and scan-out
- Recording both when an attendee enters a session and when they leave, giving a live count of people currently in the room. Scan-out is rarely enforced at conferences, so most events rely on scan-in counts with a manual reset between sessions.
- Session scanning
- Scanning badges at the entrance to individual sessions, workshops, or areas, rather than only at the main door. It supports capacity control, access enforcement, and detailed attendance reporting per session.
- Sync conflict
- A situation where two devices made conflicting changes to the same attendee record while disconnected, such as both checking the same person in. How a tool resolves these conflicts (earliest timestamp, latest write, or flag for review) determines whether the final data can be trusted.
- Thermal printer
- A printer that produces images by heating special paper or using a heat-transfer ribbon, common for on-site badge printing because it is fast, quiet, and needs no ink cartridges. Direct thermal output can fade over time, so it suits single-day badges best.
- Throughput
- The overall number of attendees an entire check-in operation can process in a given period, combining the rate of every station. Throughput is what determines whether the line during the peak window stays short.
- Waitlist
- A list of people who wanted a spot in a sold-out event or session and are admitted in order if capacity opens. Session scanning with a capacity cap makes it possible to release waitlist spots based on real attendance rather than registrations.
- Walk-up registration
- Registering and checking in an attendee who arrives without having registered in advance. It typically happens at a dedicated desk that can take payment, create the record, and print a badge, and it should feed the same attendance data as everyone else.
Questions people ask
How early should check-in open before an event starts?
Open at least an hour before the first session for a single-day event, and earlier if you expect a large crowd or a compressed arrival window. Multi-day conferences often open check-in the evening before so returning attendees can pick up badges without a morning line. The goal is to spread arrivals across a wider window rather than compress them into the last twenty minutes.
What is a realistic no-show rate to plan for?
There is no universal number. Free events typically see a much larger gap between registrations and arrivals than paid events, and the gap tends to grow with each additional day of a multi-day program. Use your own history from previous events if you have it, and if you do not, plan catering and seating with a margin rather than assuming every registrant will appear.
Do I need a badge printer at every check-in station?
Not necessarily. Some setups put a printer at every station so each transaction is self-contained, while others share one or two printers among a cluster of stations and have a runner hand badges over. The shared model costs less but adds a handoff step and a queue at the printer. For high-volume peaks, a printer per station keeps throughput predictable.
What should be printed on an event badge?
At minimum, the attendee's name in large type readable from a conversational distance, and a scannable code for session scanning and lead retrieval. Company or affiliation, ticket type, and a color band for access tiers are common additions. Avoid printing personal contact details on the badge itself; keep those behind the code and the attendee's consent settings.
How do you check in attendees who did not bring their QR code?
Name search is the standard fallback: the staff member types part of the name or email, confirms the match, and checks the person in. Because this is slower and more error-prone, route these attendees to a separate lane when the main line is busy. A reminder email the evening before with the code attached reduces how often this happens.
Is it better to check in by name or by scanning a code?
Scanning is faster and removes spelling and typing errors, so it should be the primary method at any event with a meaningful line. Name search should always exist as a backup for people who forgot the code or registered under an unexpected email, but a station that relies on name search as its main path will process people noticeably more slowly.
How do you stop someone from sharing a QR code or badge with a friend?
The check-in system should mark a code as used the first time it is scanned and alert staff if it appears again, which catches shared codes at the door. Photo verification or ID checks are used at high-security or high-value events but slow the line considerably. For most conferences, the used-code alert plus attentive staff is enough.
What hardware do you need for on-site badge printing?
A badge printer compatible with your badge stock, the stock itself with spares, a device running the check-in software at each station or cluster, and a stable connection between the device and the printer, whether cabled, wireless, or through a print server. Add a backup printer and a backup device for every few stations, because hardware fails most often exactly when the line is longest.
How do you handle a name change or typo at check-in?
The staff member should be able to edit the attendee record on the spot and reprint the badge, which is one of the strongest arguments for on-demand printing over pre-printed boxes. Edits should sync to every station so the correction is visible everywhere. For pre-printed events, a reprint desk with a printer and edit access is the workaround.
Should speakers, sponsors, and staff be checked in too?
Yes. Waving familiar faces through feels friendly but leaves gaps in the attendance data and means those people have no scannable badge for sessions or lead retrieval. Give them a dedicated lane or an early pickup window so they are not competing with general attendees, but record their check-in like everyone else.
What data privacy issues come with badge scanning?
Every scan creates a record tied to a person, so attendees should know at registration what will be collected, who can see it, and how long it is kept. Lead retrieval in particular should be opt-in or clearly disclosed, because it shares contact details with third parties. Limit what is printed on the badge, restrict who can export data, and delete or anonymize records when they are no longer needed.
How do you check in attendees for a multi-day event?
Most multi-day events check attendees in fully on their first day and issue a badge that is valid for the whole program, then use lighter daily scans at the door or at sessions to measure attendance on later days. Keep the same attendee record across all days so reports show who came when, and expect later days to have lower turnout than the first.
What should you test the day before an event?
Test the full path on the real devices at the real station locations: scan a real code, confirm the record, print a badge, and verify the check-in appears on a second device. Then test the failure paths: turn off wifi and check in someone, run the printer out of stock, and search for a name that is not on the list. If any of those surprises you the day before, it would have hurt far more on the morning of the event.