Event Reception and Check-in: How to Avoid Queues

The event reception shapes an attendee's first on-site experience. Its role, however, goes beyond welcoming guests. It must verify the attendee's identity, record their attendance, issue the correct badge, and direct them onwards—even when they do not have a ticket, their details have changed, or the internet connection fails.

Why do queues form at the entrance?

The common causes are predictable:

• most guests arrive within a short period just before the event begins;
• staff search for names manually on a printout or in a spreadsheet;
• everyone, including people with a problem or a change of details, joins the same queue;
• there are too few stations or they are poorly laid out;
• pre-printed badges are difficult to find quickly;
• staff do not know the procedures and the equipment has not been tested;
• after collecting their materials, attendees block the way for the next person.

The slowdown may be caused by scanning, printing, handing out packages, or resolving payment issues. Measure each stage rather than assuming that the problem affects the entire check-in process.

How to calculate the required reception capacity

Start by forecasting how many people will arrive during the busiest period:

people arriving at peak ÷ arrival window in minutes = required check-ins per minute

If you expect 600 people within 30 minutes, the entire setup must handle an average of 20 check-ins per minute. Next, run a test and measure the actual capacity of one station. Estimate the number of stations by dividing the required rate by the result for a single station, then add a reasonable buffer for uneven arrivals and equipment failures.

Do not base your plan on the average for the whole day. What matters is the busiest 15 or 30 minutes. Estimate the proportion of exceptions separately: walk-in registrations, changes to details, underpayments, guests without a code, and people who need assistance.

If possible, try to reduce the arrival peak itself. You can open the reception earlier and let attendees know that it is worth arriving in advance. For some events, you can also schedule different arrival times for individual groups. The more evenly you spread attendee arrivals over time, the less reception capacity you need at any one moment.

Design several paths instead of one queue

The simplest, clearest division is:

1. QR fast lane for registered attendees with their ticket ready.
2. Self check-in stations—in some systems, attendees can scan their code, confirm their attendance, and collect their badge without assistance. This can increase capacity when there are many straightforward check-ins, but it requires the right infrastructure and should still be complemented by a staffed station.
3. Assisted station for people who need help.
4. Exception desk for changes to details, on-site registrations, payments, and decisions requiring a supervisor's authorisation.

Helping an attendee who needs additional assistance should not slow down entry for everyone else. Before an attendee reaches a station, a queue marshal can check whether they have a QR code and direct them to the appropriate service point.

Continue to monitor the situation while the reception is operating. If a queue starts to form in one lane while other stations are less busy, move staff to where they are needed most whenever possible. The plan prepared before the event should be a starting point, not a rigid allocation of duties that remains unchanged regardless of the actual situation.

Create separate zones for the entrance, waiting area, stations, material collection, and reception exit. The paths of people entering, waiting, and leaving the reception should not cross. Signage must be easy to read from the entrance, and routes must also be accessible to wheelchair users and people who require assistance.

QR codes and digital attendee identification

A unique QR code in a ticket or confirmation message allows the system to find the correct record without staff having to enter a name manually. After scanning, the system can record attendance, check the participation type, and trigger the appropriate print job. A code does not replace a procedure, however: decide what to do if a phone screen is damaged, a ticket has been forwarded to someone else, or the system reports that it has already been used.

Before the event, send a short set of instructions including opening times, an entrance map, and a request to have the code ready. Do not require a printout if the scanner can reliably read a phone screen. An alternative search option should be available, but it does not have to slow down the fast lane.

Print badges on site or before the event?

Printing in advance may be suitable for a small, closed guest list. However, it requires sorting, takes up counter space, and produces badges for people who do not attend. A change of company or name means that a correction is needed.

Pre-printing also means storing a large number of badges containing attendee data at the reception desk and ensuring that unauthorised people cannot access them.

When badges are printed on site, each one is produced only after check-in and uses the attendee's current details. This reduces the need to search through pre-printed badges and makes last-minute changes easier. However, you must allow for printer capacity, printing time, the correct choice of materials, and adequate supplies. Position the printers so that completed badges from different stations do not become mixed up.

Prepare a spare device, cables, rolls, ribbons or toner, and several blank badges that can be completed by hand in an emergency. Test templates with long names, special characters, different categories, and access markings.

Staff roles and rehearsal

Everyone should understand their responsibilities:

• a coordinator makes decisions and monitors the queue;
• a greeter directs attendees to the right path;
• operators handle standard check-ins;
• a technical support person ensures that printers and the network operate correctly and that supplies remain available;
• an experienced team member handles exceptions.

Run a rehearsal using the actual equipment and test records. Practise handling a missing code, a spelling error, a substitute attendee, an additional guest, an unconfirmed payment, a repeated scan, and an internet outage. Staff should know which changes they may approve themselves and which require a coordinator's decision.

Fallback plan

Test network coverage and load in the exact location of the reception. If the solution supports a secure offline mode, agree in advance how synchronisation and conflict resolution will work. Otherwise, prepare a backup connection and a minimal manual procedure.

The emergency list must be protected against unauthorised access and destroyed or stored securely after use. Record support contact details, instructions for restarting a station, and the time threshold for switching to the fallback procedure.

How to measure waiting time and improve the next event

Record the number of arrivals over short intervals, the check-in duration for a sample of attendees, queue length, and the number of exceptions by cause. Distinguish waiting time from the check-in time itself. The first shows how well capacity matches the arrival rate; the second shows how efficiently a station operates.

After the event, compare your forecast with what actually happened. Determine which stage slowed the process down most and make one or more specific changes: adjust peak staffing, signage, pre-event communication, or the station layout.

The CONREGO Check-in module combines code scanning, attendance recording, and badge printing with registration data. Whatever tool you use, the essentials remain the same: calculated capacity, separate exception handling, a trained team, and a rehearsed fallback plan.