Large events present a different category of problem from private dinners. When five hundred people arrive inside half an hour, the gate is the single point where the whole event can visibly fall apart. Here is how to configure PrivePas so it does not.
Plan for more than one gate
Above three hundred guests, one scanning station is not enough. A scan takes roughly a second, but a person takes longer than that. They have to reach the front, find the code on their phone, hold it up and move on. In practice you should plan around one station per hundred and fifty guests arriving in your busiest window, then add one.
To set this up, go to your Security page and add one staff member per station. Each gets their own scanner link. Send each link to the right person and confirm every one of them works before the day, on the phone that will actually be used.
How the gates stay in sync
While your stations are online, they share one live record. A code scanned at Station A is immediately dead at Station B, with no coordination needed between your staff.
If a station loses network, it keeps scanning against the guest list stored on that device, and syncs everything the moment the connection returns. Worth understanding clearly: while a station is offline it can only see its own scans. If two stations are offline at the same time, a shared code could be accepted at both, and the conflict is flagged when the devices reconnect rather than blocked at the door. At a venue with poor signal, the practical answer is to keep at least one gate on a phone with strong mobile data and route anything unusual there.
Prepare every phone before you travel
Preparing an event downloads the guest list onto the device. It needs a connection to happen, and it needs to happen before you reach the venue. A phone that was never prepared is a phone that cannot scan if the venue signal is weak. Make this part of your checklist the night before, not something you attempt on arrival.
Stagger your arrivals
For events above four hundred guests, consider putting different arrival times on different invitations. Invite one group for five, another for six. You can set this per guest when you generate cards. Every guest who arrives outside your peak window is a guest not standing in your longest queue.
Brief the team properly
With several stations running, your staff cannot see each other and cannot ask each other questions. Brief everyone together before doors open and cover exactly four things. How to read the result on screen. What to do with an invalid scan, which is to step the guest aside and call the coordinator rather than argue in the queue. Who the coordinator is and how to reach them. And that the process is not negotiable regardless of who is asking.
Run an overflow station
Put one person at a secondary point with the guest list open on their dashboard. This station handles dead phones, guests who cannot find their invitation, and anyone whose scan came back invalid. Without a dedicated overflow point, every one of these becomes a blockage at your main gate, and a five hundred guest queue does not recover from a two minute stoppage.
Watch the dashboard during arrivals
Whoever is coordinating should have the dashboard open throughout the arrival window. The number you are watching is the rate, not the total. If check-ins slow sharply while guests are visibly still arriving, something has gone wrong at a station. A phone has died, a staff member has walked off, or a link was opened in the wrong browser.
Events outside your own city
If your event is not in the city where you are based, add a day. Confirm venue signal in advance, prepare every phone before you travel, and carry more power banks than you think you need. The failures that get you at an out of town event are logistical, not technical.
Consider on-site staff
Above five hundred guests, running the gate yourself while also hosting is a lot to hold. PrivePas on-site service deploys trained staff who arrive briefed and equipped. You still own the guest list and still see every check-in on your dashboard. Request it from your dashboard or on WhatsApp, and do it early rather than the week of.