Operations

Onsite registration kiosks: getting check-in right

Kiosk count, layout, staffing, and queue-management tactics that move attendees through registration in under 3 minutes at peak.

7 min read · Published March 23, 2026

The queue for check-in at a 1,500-person enterprise conference snaked past the coffee bar, around a sponsor booth, and out into the hotel corridor. Average wait time: 42 minutes. The opening keynote started with a half-empty ballroom. By the time attendees found their seats, the CEO was four minutes into the opening story and visibly annoyed at the empty rows. Nothing about this scenario was unavoidable. The organizer had planned for six kiosks. A peak-load analysis would have recommended twelve. That single decision, made three months out, cost the event more in attendee frustration than any other single choice on-site.

Check-in is where the event begins. It is also the single highest-leverage operational choice for first impressions. This guide covers how to size kiosk capacity, lay out the check-in flow, staff the space, and handle the specific edge cases that clog queues at peak.

1. How many kiosks you actually need

The working rule: roughly 1 kiosk per 75 expected day-one peak attendees, plus 2 dedicated walk-up kiosks. For a 1,000-attendee event expecting 70% arrival in a 90-minute peak window, that is 10-12 kiosks.

Two adjustments:

  • If check-in is staffed (not self-serve): you can reduce to 1 per 100. Staffed is slower per attendee but better at resolving edge cases.
  • If your audience skews senior or international: add 20%. Older audiences take longer at self-serve kiosks; international attendees have more name-spelling edge cases.

The common mistake is planning for average arrival, not peak. Most attendees arrive in a 60-90 minute window before the opening keynote, not spread across the 4-hour check-in period on the agenda. Size for peak or plan for a queue.

2. Layout — two lanes, not one

A single queue with eight kiosks at the end feels orderly but produces bottlenecks. The pattern that flows better:

  • Two separate lanes: pre-registered and walk-up. Pre-registered attendees should move in under 60 seconds. Walk-ups take 5-7 minutes. Mixing them destroys the pre-registered queue.
  • Visible signage at eye level. "Pre-registered — use the QR code on your confirmation email" on one side, "New registrations and questions" on the other. Typography should be readable from 30 feet.
  • A floater zone. Space for a staff member to pull edge cases out of the queue and handle them away from kiosks.
  • Overflow space. If the queue grows, where does it go? Plan for 3-4× the nominal queue length.
  • Badge pickup as a separate step. If you print badges on demand, separate the check-in step from the badge pickup. Splits the bottleneck.

Top hotel and convention-center venues usually have ample space for this layout. The risk is at constrained venues — smaller hotels, converted industrial spaces — where queue overflow can block corridors, fire exits, or other event operations.

3. Self-serve vs staffed

Self-serve kiosks scale fast per attendee but break for walk-ups and edge cases. Staffed check-in handles edge cases well but is slower per attendee. The best answer for most events is a hybrid:

  • Self-serve for pre-registered attendees with a QR code. Attendee scans QR, kiosk prints badge, done.
  • Staffed kiosks for walk-ups, substitutions, and problems. One staff member per 2-3 kiosks, plus a dedicated "complex problems" desk.
  • Mobile staff floating the queue. They spot likely edge cases (attendee who cannot find email confirmation, attendee with a group registration issue) and pull them out before they reach a kiosk.

Self-serve kiosk UX is worth testing. Run a rehearsal with 10 people who do not work at your event and watch where they get stuck. The stumbles will surprise you.

4. The specific edge cases that slow everything down

Six edge cases account for most check-in delays:

  • Attendee cannot find the QR code. Solution: staff pulls them out of queue, looks up by email on a tablet. Resolution time: 90 seconds. Avoid: have attendees add the email to a pre-event "cannot find this?" search form.
  • Group registration split across multiple attendees. Solution: one designated group-check-in lane. Avoid: pre-event email to group admins asking who will check in for whom.
  • Name spelling or data issues. Solution: "edit my info" kiosk flow. Avoid: this is unavoidable, but at least make it fixable.
  • Walk-ups who do not know they need to pay. Solution: signage stating walk-up fees, payment at the kiosk. Avoid: announce walk-up pricing in pre-event comms.
  • Badge printer jam. Solution: redundant printers per kiosk, spare ribbons stocked. Avoid: test printers cold-start the morning of, not at 08:00 when doors open.
  • Special guest / VIP identification. Solution: separate VIP check-in lane with staff briefed on the guest list. Avoid: VIPs stuck in the same queue is a reputational hit.

Each edge case case-worked individually is manageable. In combination at peak, they compound into 30-minute wait times.

5. Staffing — more than you think

Budget one volunteer per kiosk, plus one floater per 4 kiosks, plus one on-site lead. For a 10-kiosk setup that is 10 + 3 + 1 = 14 check-in staff at peak. This is twice what most first-time organizers plan.

Brief the staff at 07:00 on day one. Cover:

  • The top 5 attendee questions (where are the bathrooms, where is the opening keynote, when does lunch start, where is the sponsor X booth, wifi password). These are 90% of the questions they will get.
  • The specific check-in flow, including what to do when the kiosk fails.
  • Who to call for escalations.
  • The single most important thing: do not let attendees feel stupid. Every UX issue is the system's fault, not the attendee's.

Brief volunteers individually with printed reference cards. They will forget in the rush. The cards save them.

6. Check-in day-of checklist

  • [ ] All kiosks powered, connected, tested 90 minutes before doors
  • [ ] Backup printers tested and ribbons stocked
  • [ ] Badge paper loaded and spare rolls accessible
  • [ ] Signage in place, readable from 30 feet
  • [ ] Two lanes clearly marked and delimited
  • [ ] Walk-up payment flow tested
  • [ ] Staff briefing completed, reference cards distributed
  • [ ] Venue wifi confirmed stable at expected load
  • [ ] Backup: paper list of registrants printed in case of system outage
  • [ ] VIP lane staffed with briefed greeter
  • [ ] Event app download prompt visible at kiosks
  • [ ] First-session wayfinding signage from check-in to ballroom

Common mistakes

  1. Undersized kiosk count. Planning for average arrival instead of peak produces the 30-minute queue that becomes the event's first impression.
  2. Single-lane layout. Mixing pre-registered and walk-up kills throughput.
  3. Self-serve only. Without staff, 10% of attendees get stuck and back up the whole queue.
  4. Untested printers. A printer failure at 08:30 is the most common cause of check-in delay.
  5. Underbriefed staff. Volunteers who cannot answer "where is the keynote?" create frustration in an already-stressed moment.
  6. No backup for system outage. If the check-in system goes down, can you check people in manually? Have a printed list as fallback.

FAQ

Can I do badge-less check-in? Yes, for some events. If the event app replaces the badge for session access, swag pickup, and networking, skip badges entirely. This works best for smaller, tech-forward audiences. For sponsor-heavy events, sponsors want visible badges for lead scanning.

What about print-at-home badges? They work if attendees actually print them, which 30-50% do not. Plan for the ones who did not. A "print on arrival" lane handles the delta.

How do I prevent queue anxiety? Visible signage of expected wait times (updated by floaters) and a reminder that doors remain open during the keynote. Attendees tolerate a 10-minute wait; they do not tolerate a 10-minute wait when they think they will miss the opening.

Should I use facial recognition check-in? Still feels invasive to many audiences. Legal complexity around biometric data. Unless your event has a specific reason (security-sensitive venues, repeat-customer frictionless flows), stick with QR codes.

How does check-in work for a hybrid event? Virtual check-in is a login flow. On-site check-in follows this guide. Ensure both feed into the same event management software so attendee analytics are unified.

Related guides

Run on-site QR check-in, print-on-demand badges, and walk-up registration from one platform: Create your event on WebMobi →

Related guides

Run your next event on WebMobi

Build the registration page, app, and analytics in under an hour. No credit card required.

Create your event →