Conference check-in: QR scanning, staffing and lanes

What does good conference check-in look like?

Check-in concentrates a large share of attendees into a short window. In an illustrative 400-person scenario, two stations working at 45 seconds per attendee provide capacity for only 160 check-ins an hour. Compare that capacity with your expected peak arrivals before deciding whether two stations are enough.

The math is simple and unforgiving. Divide the number of people arriving in your busiest hour by the number of scanning stations, then multiply by your seconds per attendee. If that number exceeds 60 minutes of station time per hour, you have a queue that grows all morning.

Cut avoidable steps before adding staff. Pre-print and sort badges, move payments to a separate line and collect required data before event day. Measure the complete interaction in rehearsal rather than assuming the QR scan is the only constraint.

How many check-in scanners and staff do you need?

Estimate arrivals from past check-in logs, transport schedules and the agenda. If you have no history, model several cases—for example half, two thirds and three quarters of attendees in the hour before the keynote—and staff for the case whose wait you are unwilling to exceed. Opening registration earlier may spread arrivals, but measure whether it does for your audience.

The table applies the starting assumption above. Treat it as a rehearsal plan, not a staffing benchmark.

Desk staff outnumber scanners because someone hands out badges, someone directs the queue, and someone handles problems. A scanner operator who stops to solve one problem stops the whole lane.

Which check-in lanes should you set up?

• Pre-registered scan. Attendees with a QR code on their phone or printed. Use your paid-order and ticket-delivery data to estimate how much of the arrival volume belongs here.
• Name lookup. For attendees who cannot find the email. One or two stations, clearly signposted, staffed by someone comfortable searching and spelling names back.
• Walk-up sales. People who did not buy in advance, plus anyone whose payment failed. Keep payment away from the main scan lane because it adds steps and variable handling time.
• VIP, speaker and staff. Speakers arriving late for a 09:00 slot cannot queue. Sponsors carrying booth equipment cannot queue. Give them their own table, ideally with the speaker and sponsor comp tickets already issued as their own ticket types so the scan tells staff which lanyard to hand over.

For walk-ups, put a poster with a QR code linking to your ticket page next to the desk. The buyer completes the purchase on their own phone, receives the QR ticket by email, and rejoins the scan lane. That converts your slowest interaction into a self-service one.

What happens when you scan a ticket QR code?

Every ticket carries a unique code, which is what makes the third point possible. If the same code is copied or forwarded, the scanner should make the later attempt visible to staff.

Canceled and refunded tickets are the other case. If you refund an attendee two days before the event, that QR code has to stop working, otherwise your gate is decorative.

How do you check in an attendee who cannot find their ticket?

The causes are mundane: the confirmation went to a work address they cannot reach on their phone, a colleague bought the ticket for them, or it is in spam.

Group bookings need particular attention because the buyer may use one email address for several attendees. Rehearse how staff will search by the attendee or buyer details the scanner actually supports, and tell group buyers how to distribute individual tickets before the event.

Checkout Page's scanner searches by name, email, ticket code or order ID. Attendees can also pull the ticket up themselves in the customer portal while they queue, which is worth a sign at the front of the line.

What is the fallback if the venue network fails?

Three things to arrange in advance:

If the network drops, switch the whole desk to paper at once. Mixed modes are how people get checked in twice and how you lose the count.

How do badges fit into check-in?

Your export should carry exactly the fields on the badge: badge name, organization, job title, pronouns if you collect them, and ticket type so the lanyard color matches the access level. That is the argument for collecting those fields properly on the registration form.

Set a badge print cutoff about a week out and say so. Anyone registering after it gets a blank badge written by hand at the desk, which is fine as long as staff know the rule.

Consider separating the badge handler from the scanner operator so one scans while the other retrieves the badge. Rehearse that arrangement against a single-person station and use the faster layout at your entrance.

How does re-entry work on day two of a multi-day conference?

If you do not need a second-day attendance record, a wristband or visible badge check may avoid repeating the full scan process. If you do need that record, model the second-day arrival window and staff it explicitly.

Scan again on day two when the days are sold separately, when a sponsor or grant requires per-day attendance figures, or when day two is in a different venue with its own capacity limit.

If you sell single-day tickets alongside a full pass, make them separate ticket types anyway. That gives you a per-day capacity, a per-day scan, and the badge color logic falls out of it for free. Multi-day pass structures are covered in the ticket tiers guide.

What do you do with check-in data after the event?

No-show rates vary by event, price and audience, so use your own numbers rather than an assumed universal rate. Track attendance by ticket type over two or three editions before using it to plan catering or room capacity.

What to do with the export:

• Send sponsors the attendance figures they were promised, and nothing more than the attendees consented to share.
• Segment the post-event email. People who attended get the recordings and next year's early bird. People who paid and did not show get a different, kinder message.
• Compare the arrival curve to the desk plan, and write down the scanner count you actually needed.

The arrival data also feeds next year's ticket sales timeline: the attendance rate tells you how many seats to sell against a fixed room capacity.

Day-of check-in checklist

The night before

• Export and print the attendee list, sorted by surname, with ticket type and badge name.
• Charge every scanning device and pack chargers plus a power strip.
• Sort printed badges into labeled trays by surname range.
• Confirm staff accounts work by having each person log in once from their own device.
• Brief the team on the planned lanes and on who handles problems, then run at least one normal scan and one exception together.

Sixty minutes before doors

• Test one real scan end to end, with a real ticket, from the actual desk position.
• Test the backup hotspot by putting one device on it.
• Put up lane signage and the walk-up purchase QR poster.
• Set out markers, blank badges, lanyards and a problems table away from the queue.

During

• Watch the queue, not the screen. If it passes 10 minutes, open the VIP table as an overflow scan lane.
• Send problems sideways to the floating staff member immediately, never up the lane.

After doors close

• Enter any paper check-ins into the system.
• Export the check-in data and note the attendance rate per ticket type.