Event Entry Management: Calculate and Cut Queues (2026)

Event entry management means working out in advance how many guests per minute your entrances can process, then setting up lanes, staff and communication so that the arrival peak never exceeds that rate. The core formula is simple: lanes needed = peak arrivals per minute ÷ guests per lane per minute, rounded up. Combine it with a realistic arrival curve and you know before doors open whether your queue will last 5 minutes or 45. Below we calculate it for 300, 1,000 and 3,000 guests and show which levers actually shorten queues, as of November 2026.

Key takeaways

• Entry time in minutes = guests ÷ (lanes × scans per lane per minute). For the peak: lanes = peak arrivals per minute ÷ scans per lane per minute.
• Guests don't arrive evenly. Plan for the busiest 15 to 45 minutes, not the average across the whole doors window.
• The slowest step sets the pace: bag searches, ID checks and wristbands need their own capacity, calculated separately.
• Separate lanes for guest list, box office and accessible entry keep the main ticket lanes fast.
• Telling guests "open your ticket before you queue" is the cheapest speed-up you'll ever buy.

What is event entry management?

Event entry management is the planning and control of everything between a guest arriving at your site and stepping into the event area: approach routes, queues, ticket validation, bag and age checks, special cases and communication. Its goal is safe, fast and fair access.

Ticket scanning is only one part of it. How the scan itself works, which hardware to use and how to brief helpers is covered in QR code ticket check-in without an app. This guide answers the question before that: how many lanes do you need, and when will it get tight?

Long queues are more than an annoyance. A queue that spills onto a pavement or road becomes a safety issue, and venue licences and national assembly rules often set conditions for escape routes and stewarding. In Germany, for example, the model venue regulation applies to rooms for more than 200 visitors and requires a safety concept for venues with more than 5,000 places. Rules differ by country and region, so check your licence conditions.

How do you calculate entry throughput?

Three formulas cover almost every planning question:

Always round lanes up.

When the peak exceeds your capacity, the queue grows by the difference every minute:

• Backlog after the peak = (arrivals per min − capacity per min) × peak minutes
• Extra wait for the last person ≈ backlog ÷ capacity per min

Which scan rate should you assume?

The scan rate is the most important and least certain number. Published figures vary: one vendor puts a smartphone at about 400 scans per hour and a laser scanner at about 800 (Snapticket); the UK guide site tickts.co.uk states roughly 300 to 400 per hour for a QR scanning point, dropping to about 200 per lane with bag searches. Real doors are slower than demos because guests hunt for emails, phones are dim and someone always has a question.

For the examples below we use three assumptions, not measurements:

Measure your own: count successful scans at one lane for five minutes at your next event. That number beats any table.

Worked examples: 300, 1,000 and 3,000 guests

Step 1: the even-arrival view

These figures assume guests arrive evenly, which they don't, but it's the baseline. Minutes are rounded up.

300 guests (club night, school prom, community concert)

1,000 guests (concert hall, gala, carnival session)

3,000 guests (festival day, arena show)

Step 2: plan for the peak

Now add an arrival-peak assumption for each size and calculate lanes from the peak rate.

Worked through for 1,000 guests at assumption B: 20 ÷ 6 = 3.3, so 4 lanes. With only 2 lanes (12 per minute), the queue grows by 8 guests every minute. After the 30-minute peak, 8 × 30 = 240 people are still waiting, and the last of them waits about 240 ÷ 12 = 20 extra minutes. Your show starts late.

For 3,000 guests, don't calculate one big number. Split the calculation per entrance, because guests rarely spread evenly across gates. If 60 % use the gate nearest the station, that gate needs 60 % of the lanes.

Step 3: add the roles around the lanes

This is an example staffing plan, not a standard, and it excludes security staff. Bag checks come on top.

Why does the arrival curve matter more than the average?

Guests come in waves: a calm start after doors, a steep peak shortly before the main act, then a tail. If more guests arrive per minute in that peak than your lanes can handle, the queue grows even though the average looked fine. Weezevent's access-control guidance makes the same point: a headline act creates a peak half an hour to an hour before it starts.

Typical arrival patterns

These patterns are experience, not statistics. If your ticketing system stores check-in times, read your real curve from the last event.

How do you flatten the peak?

• A reason to come early: welcome drink until 19:30, support act, DJ set, photo booth.
• Time slots per ticket type: "Standing from 18:30, seated from 19:15" for big shows.
• Clear entrance allocation: by ticket type or block, printed on the ticket and in the info email.
• Doors and start time stated separately: "Doors 19:00, show 20:00" beats "20:00".

Which separate lanes do you need?

Every exception at the main lane costs time for everyone behind it. Separate by effort:

At small events one person can cover several roles, but keep the box office physically apart from scanning. How to set it up is explained in box office and door sales, and the name-list side in guest list management.

How do you plan accessible entry?

• A step-free, signposted route from car park or stop to the entrance.
• A dedicated lane or priority without guests having to justify themselves.
• A clear rule for companion tickets, if you offer them.
• A scanner within reach from a seated position, or a helper who brings the device.
• Information in advance: where the accessible entrance is, whether there's a quiet area, whom to ask.

How do bag checks and ID checks change the numbers?

The slowest station sets the pace. If a bag search happens at the scan point, your rate drops from assumption B to A or below.

The ticketing provider Simpleticket publishes planning values for security checks: about 10 seconds per visitor for light checks, 20 for normal and 30 for strict ones. Treat these as planning assumptions and convert them into a per-checker rate:

For the 1,000-guest example with a peak of 20 per minute, a normal bag check needs 7 checkers in front of 4 scan lanes. Plan fewer and the bag check becomes your queue.

Practical rules:

1. Order the stations: bag check, then scan, then wristband, each at its own position.
2. Calculate every station: the formula applies to each step. The step with the lowest total capacity is your bottleneck.
3. Prepare guests: "small bags only, A4 maximum" in the info email; cloakroom after entry, not before.
4. ID in hand: for age-restricted events, ask guests to have ID ready in the queue.
5. Space behind the door: if the bar or cloakroom sits right behind the entrance, the queue backs up inside.

Weezevent recommends Z-shaped barriers for long queues and placing the search area before ticket control, with mixed-gender search teams. Your security provider and licence conditions decide the details.

How do you communicate with guests before and at entry?

Most seconds at the door are lost because guests aren't ready.

Info email or post 1 to 3 days before

• Doors time and start time, stated separately
• Which entrance for whom: tickets, guest list, box office, accessible
• "Open your ticket before you queue, brightness up, PDF or printout"
• Bag policy, prohibited items, ID for age limits
• Travel, parking and the expected peak ("it gets busy from 19:30")

On site

• Signs readable from the back of the queue: "Tickets", "Guest list", "Box office"
• A queue walker asking "ticket ready?"
• Honest updates during delays: estimated wait and reason
• Social media or the event page for last-minute changes

What if the queue keeps growing?

Set escalation steps in advance so your door manager doesn't improvise:

Triggers are examples. Align them with your venue and safety plan.

How to do this with Eventoren

With Eventoren you open extra scan lanes without installing anything. You create scanner links, for instance one per device and entrance, and send them to helpers, who open them in their smartphone browser and scan with the camera. If the camera can't read a code, they type it in. A reserve lane is therefore just one more link sent to one more helper. The scanner needs internet for every scan; there is no offline mode, so plan a backup network route.

During entry, check-in statistics per entrance and ticket type show how many guests are in and which entrance is falling behind. Rejected scans show the reason, so helpers send exceptions straight to the help desk.

For the separate lanes: the guest list supports quotas and 0 to 5 plus-ones per entry with check-in on the list. Walk-up guests buy cashless via the box-office QR poster on their own phone at your box-office prices, then join the main lane with a ticket. There is no cash till or card terminal. Questions go to the contact page; the German version of this guide is Einlassmanagement (in German).

Frequently asked questions

How many ticket scanners do I need for 500 guests?

It depends on the peak and your scan rate. If half of them arrive in the last 30 minutes, that's about 8.3 per minute; at 6 scans per lane per minute you need 2 lanes, at 4 you need 3. Add one reserve lane and a separate help desk.

How long does a ticket scan take?

The read itself takes a moment. What counts is the total time per guest, including finding the ticket, adjusting brightness and any questions. That's why this guide plans with assumptions of 4 to 10 guests per lane per minute and recommends measuring your own rate.

When should doors open?

For events with a fixed start, 45 to 60 minutes before is a common starting point, and Weezevent suggests half an hour to an hour. Check with the formula whether your lanes can handle the peak in that window, and give guests a reason to arrive early.

Does a small event need entry planning at all?

Yes, on a smaller scale. With 150 guests, one lane and 4 guests per minute, entry takes about 38 minutes if everyone came evenly, longer at the peak. A second lane and a separate guest list roughly halve that.

What is the biggest mistake at event entry?

Doing everything at one spot: scanning, selling, guest list, bag search and ID. Then the slowest case sets the pace for everyone. Separate the steps physically and give each its own capacity.

Sources

• Weezevent: how to improve check-in and access control
• Tickts: how to manage event queues and entry flow
• Simpleticket: entrance management for events and festivals
• Snapticket: entry calculator with scanner benchmarks
• Bauministerkonferenz: German model venue regulation (MVStättV)