# How to Check In 1,000 Event Attendees Without Long Queues

> Work out how many check-in lanes and staff 1,000 attendees need, with worked arithmetic, a stopwatch rehearsal, and a plan for the moment the line builds.

Source: https://laces.run/blog/how-to-check-in-1000-event-attendees (HTML version of this page)

Checking in 1,000 people without long queues comes down to one sum: how many people arrive in your busiest half hour, divided by how many one lane can clear. Most queues are decided before the doors open, by too few lanes or one slow step at the front of each. This guide shows the sum, then how to test your numbers with a stopwatch.

[Create your event](https://laces.run/app): Create your event and every registration comes with a QR ticket. Your gate team only needs the app.

## Do the sum before you hire anyone

Your total ticket count isn't the number that matters. A thousand people spread over three hours is a calm gate. A thousand people who all want to be in their seats for the first song is not.

You need three numbers: how many will turn up, how many of them arrive in the busiest 30 minutes, and how long each person takes at the front of a lane.

**This example is an illustration. Every input is made up, so replace them with your own.**

| Step | Sum | Result |
| --- | --- | --- |
| Tickets sold | | 1,000 |
| Expect 90% to turn up | 1,000 × 0.9 | 900 people |
| Say 60% arrive in the busiest 30 minutes | 900 × 0.6 | 540 people |
| Arrivals per minute at the peak | 540 ÷ 30 | 18 a minute |
| Say 20 seconds per person | 60 ÷ 20 | 3 a minute, per lane |
| Lanes needed | 18 ÷ 3 | 6 lanes |

Add a spare and you have 7. A spare is not waste. It covers a phone that dies and a scanner who needs a break.

Now see what moves the answer:

- **Slower lanes.** At 30 seconds a person, one lane clears 2 a minute, and you need 9 lanes.
- **A flatter peak.** If only 40% arrive in the busiest half hour, that's 360 people, or 12 a minute. At 20 seconds each, 4 lanes will do.

That second line is the cheap one. Moving arrivals costs less than adding staff. A real reason to come early does more than any reminder: doors well ahead of the main item, a warm-up speaker, food stalls that are open, or kit you can only collect before a set time.

## Find your real seconds per person

Don't use our 20. We have no figure to give you for how fast a lane runs, because it depends on your crowd, your light and your signal. Time your own.

Run a rehearsal with real tickets, on the phones you will really use, at the real gate if you can. Use a stopwatch from the moment one person reaches the front to the moment the next one does. Time at least 20 people, and include someone who has to hunt through their email.

Then look at what eats the time. On most gates it isn't the scan:

- **Finding the ticket.** This is usually the biggest loss. Put a marshal on the queue saying "ticket open, brightness up" before people reach the front.
- **Bag checks.** If security searches bags, that is a queue of its own. Do the sum for it separately, and put it before or after scanning, never in the same spot.
- **Handing things over.** Wristbands, lanyards and programmes all add seconds. Hand them out a few steps past the scanner, so the lane keeps moving.
- **Glare.** Sun on a participant's screen makes scans fail. Put the scanners in shade.
- **Groups.** See below.

## Group orders take longer than you think

On Laces, the QR code on a ticket leads to the whole order. When one person bought five tickets, scanning any of the five shows a list of the five names under "Who is this?", and the scanner taps the right one. That tap records the arrival. For the next person in the group, they tap **Scan next** and scan again.

So a family of five is five scans and five taps. Tell your scanners to expect this, or they will think something is broken. If you sell many group tickets, such as a corporate conference, keep one lane just for groups, so it doesn't slow the others.

## Who stands where

Here is a staffing plan for the 7 lanes in our illustration. It's a starting point, not a standard.

| Job | People | What they do |
| --- | --- | --- |
| Scanners | 7 | One per lane, one phone each |
| Queue marshals | 2 | Get tickets open, split groups, point to the short lane |
| Help desk | 2 | Take every hard case away from the lanes |
| Relief | 2 | Cover breaks and dead batteries |
| Gate lead | 1 | Watches the lines, opens and closes lanes, makes the network call |

That is 14 people, plus security, which is its own job. The two that people skip are the help desk and the gate lead, and they are what keep one confused guest from stopping a lane.

Each scanner signs in on their own phone with their own team account. Give them the Volunteer role, tied to this event. They can scan and search by name or phone, and they see no revenue. Our guide to [managing event volunteers and staff](https://laces.run/blog/how-to-manage-event-volunteers-and-staff) covers the roles and how to invite people.

## Lay the lanes out so people choose well

- **Make each start obvious.** One lane per scanner, with a visible start. People won't join a lane they can't see the end of.
- **Leave room to queue.** Walk it. Work out where 100 people will stand, and make sure they aren't on a road or blocking an exit.
- **Separate lanes by ticket only if you want to.** A scan works in any lane, and the screen shows the ticket name.
- **Keep the help desk out of the flow.** Off to one side, with a sign.

## Tell scanners what each screen means

A green screen shows the person's name and ticket. If the same ticket was already scanned, it also shows a label like "Checked in 10:42", which is the time of the first arrival. It doesn't turn red. Your scanner has to notice that label and send the person to the help desk.

A scan also doesn't check the date on a day ticket. If you sell Saturday and Sunday passes, a Saturday pass still reads as valid on Sunday. So scanners have to read the ticket name.

We cover every screen in the [QR ticket guide](https://laces.run/blog/qr-code-tickets-event-check-in), and copied tickets in the guide to [preventing duplicate or fake tickets](https://laces.run/blog/how-to-prevent-duplicate-or-fake-event-tickets).

[Talk to the team](https://laces.run/contact): Send us your venue, crowd size and door times, and we can talk through your check-in plan.

## Plan for the network, because 1,000 phones share it

Every scan looks the ticket up online. No data at that moment means "Could not check that ticket", and a retry. That message says nothing about the ticket, so staff must never turn someone away because of it.

A crowd can make a good signal bad. Test at the gate at the same time of day as your event, then again when the venue is filling if you can. Carry SIM cards from more than one network and keep a charged hotspot phone close.

Decide in advance who calls the switch to a paper list, and what triggers it. For example: "If two lanes fail for two minutes, the gate lead moves to paper." Our comparison of [QR check-in and paper lists](https://laces.run/blog/qr-code-check-in-vs-paper-attendance-lists) explains how to set that backup up. Bring power banks too, because scanning with a camera all day uses a lot of battery.

## When the line builds anyway

Decide this ladder now, so nobody invents it in a panic:

1. **Open the spare lane.** Do this early, before the line looks bad.
2. **Move marshals up the queue** to get tickets open sooner.
3. **Pull every problem case** to the help desk at once.
4. **Pause bag checks or handouts** if the line is reaching somewhere unsafe, if your security lead agrees.
5. **Tell the queue what is happening.** People wait better when someone is talking to them.

Crowd safety beats a clean scan count. If the queue is becoming dangerous, your security lead decides how to clear it, and you sort out the records afterwards.

Afterwards, write down your real figures while you remember them: when the peak came, how long it lasted, and how many lanes you ran. That turns next year's sum from a guess into a measurement.

## Frequently asked questions

### How many scanners do I need for 1,000 people?

It depends on your peak and your speed. Divide the people arriving in your busiest half hour by 30 to get arrivals per minute, then divide by what one lane clears in a minute. In our made-up example, that was 6 lanes plus a spare.

### Can a phone be my scanner?

Yes. On Laces, your team scans with the app on an ordinary phone, using its camera. Each scanner needs a data connection.

### Can I check people in without internet?

Not by scanning. The lookup happens online, so plan a paper list as your backup.

### Does Laces tell me how many people have checked in so far?

No. The app shows an arrival time when you scan or search for one person, but it doesn't give a running count or an attendance list. If you need a live count, use a clicker at the gate.
