Halloween Party Check-In: QR Tickets, Guest Lists, and Door Planning

Choose a single source of truth for confirmed guests. Distinguish a confirmed booking from an invitation or an unanswered RSVP. Decide how staff will handle complimentary guests, plus-ones, and walk-ins, and assign someone who can resolve changes on the night.

Give each admitted person an individual pass where possible. For plus-ones, confirm how their details and pass will be delivered, especially if they arrive separately. Avoid sending a single QR code to a whole group and expecting each scan to identify a different guest.

Decide the walk-in process before doors open, including who checks remaining availability and confirms any payment. Entry scan totals are not a reliable live occupancy count because they do not establish departures. Keep your venue’s occupancy procedure separate.

For a paid party, keep ticket purchase and admission validation connected but distinct. Confirm the purchase in your payment or booking system, then issue the guest’s PassEngine pass. For a free party, use your confirmed RSVP as the issuance trigger.

If you automate issuance through the API or Zapier, test a completed booking from start to finish. Check the guest details, pass category, delivery message, and handling of repeated triggers. Decide how cancellations and refunds lead to revoking the corresponding pass.

Describe any VIP or complimentary category clearly. Printed pass fields help staff understand the booking, but they do not automatically enforce separate rooms, queues, or benefits. Document any checks your door team must make.

Send guests their pass link before the event and repeat it in your arrival reminder. A supported pass can be saved to Apple Wallet or Google Wallet, and the original link also opens in a browser. Ask guests to find their pass before joining the scanning queue.

Include the entrance address, arrival window, re-entry rules, and help contact. If your venue has an identity-check or costume policy, communicate the venue’s actual requirements in advance. A digital admission pass does not prove the holder’s identity or age.

For a party that continues after midnight, set the validity window through the intended closing time on the following date. Check the venue timezone and test a pass against that window before distributing it.

Place the scanning point where staff can safely see both guests and their devices. Keep it away from flashing decorations and the darkest part of the entrance. Test with the actual lighting, rather than assuming a successful daytime scan will work after dark.

Check camera permissions, internet connectivity, battery capacity, and charger access on every scanning device. Rehearse with guests holding passes in their browsers and wallet apps. Ask them to increase screen brightness if the camera struggles to read a code.

Create a separate space for missing passes, booking changes, and disputed results. That gives the scanning team a simple job while an authorized host handles exceptions. Brief each shift on who can make an admission decision.

Use a single-use pass if one successful redemption completes admission. Once used, that pass will not support ordinary re-entry. If guests may leave and return, choose multi-use settings and a validity window that match your policy.

A copied QR code is still the same credential. A single-use allowance limits successful redemptions, but it does not tell staff whether the first person presenting it is the intended guest. Apply your published holder-verification procedure when needed.

For multi-use passes, explain how staff confirm returning guests. Do not use a small total allowance as an accidental re-entry policy: every successful redemption consumes one use. Rehearse both a legitimate return and a repeated presentation that staff should investigate.

When someone cannot find their pass or has a dead phone, send them to the help desk. Confirm the booking using your agreed procedure before resending a pass or authorizing manual admission. Record exceptions so the next volunteer does not have to guess what happened.

Test the scanner’s accepted and rejected outcomes before the party. Door staff should recognize expired, revoked, not-yet-valid, and exhausted passes and know when to ask the host for help. A convincing-looking ticket is not a substitute for a successful validation result.

Have backup connectivity and a documented manual admission procedure. Saving a QR pass to a wallet does not make server-side validation work offline. Reconcile manual entries after service returns, and review unique admitted passes separately from repeat scans after the event.