QR code check-in for events

Give each ticket its own code, keep the guest list as a CSV file, and scan at the door with a phone that flags duplicates and codes that aren't on the list.

QR check-in works by giving each ticket a unique code, keeping the guest list as a spreadsheet, and scanning each code at the door against that list. The scanner tells staff whether the ticket is valid, already used, or not on the list.

Give each ticket its own code

The code on a ticket should be an ID, not the guest’s details:

  • Unique. One code per ticket (or per guest), so a second scan of the same code can be caught.
  • Hard to guess. A long random string such as T-7Q4M-X92K-PL3R is better than 0001, 0002, which anyone can guess and print.
  • Short enough to scan easily. A short ID makes a less dense code that reads well from a phone screen or a crumpled printout.

Names, emails and seat numbers belong in your list, not in the code. That keeps personal details off printed tickets and lets you correct a name without reissuing the ticket.

Send codes by email as images, print them on tickets or badges, or print them on label sheets (see print QR code labels).

Keep the guest list as a CSV file

Most ticketing tools and spreadsheets export CSV (comma-separated values). A useful guest list has one row per ticket and columns such as:

ticket_id name party_size type
T-7Q4M-X92K-PL3R Sam Rivera 2 Guest
T-B81Z-44RD-QW0N Ana Costa 1 Speaker

The ticket ID column must match exactly what’s inside each QR code. Watch for spreadsheets that turn long numbers into scientific notation or drop leading zeros: save the code column as text.

At the door

A door scanner has to answer one question fast: let this person in or not. Plan for these cases:

  • Found. The code is on the list and not used yet. Check it in and show the name so staff can greet the guest.
  • Already checked in. A second scan of the same code. Show when it was first checked in, so staff can tell a re-scan from a shared screenshot.
  • Not on the list. A code from another event, a typo, or a fake. Keep a record of these to sort out later.
  • No code. A guest with a dead phone. Staff should be able to search the list by name and check the guest in by hand.

Re-entry and party size

  • Re-entry. If guests can leave and come back, each scan should count as an entry with its time, instead of being refused as a duplicate.
  • Party size. For a ticket that admits a group, each scan counts one more arrival until the whole party is in.

Offline and more than one door

Event venues can have weak mobile signal. If the list is stored on the scanning phone, check-in doesn’t depend on a connection. With two or more doors, each phone has its own copy of the list, so you need a way to combine their results afterward without double-counting a guest who was scanned at both.

Checking in with QR App

QR App for Android has Lists (Tools → Lists), which do this on the phone, with no internet connection. What it does:

  • Import a CSV or TSV file (comma, semicolon or tab separated). You choose the code column, a title column shown large when a code is found (such as the name), and a few more columns to show with each code.
  • Matching options: ignore spaces around codes, ignore upper and lower case, and ignore leading zeros for codes made of digits only.
  • List types: Check-in (each row checks in once, and a second scan says it’s already checked in), Re-entry (each scan is an entry with its time), Party size (each row admits a party, from a column or a default size) and Inventory (for counting stock).
  • Scanning in Look up or Check in mode, with Undo last scan, typing a code, and finding a row by code or name.
  • Codes not on the list are listed separately, with how many times and when each was scanned.
  • Merge from another phone: import the other phone’s export of the same list. The earliest check-in is kept for rows checked in on both; for party sizes and counts, you choose whether to add the two phones’ counts (different doors) or keep the higher one.
  • Export as a CSV or Excel file: your original columns, then the check-in time and status of each row, plus the codes that weren’t on the list.

Scans against a list don’t go to the app’s scan history.

After the event

Export the final list and keep it with your event records: check-in times show when people arrived, and the codes that weren’t on the list show where tickets were mistyped or copied. When you no longer need the guest list on the door phones, delete it there.

Tips for a smooth door

  • Test the whole flow a day before with a few real tickets, printed and on screen.
  • Turn screen brightness up on phones showing tickets; screen glare and low brightness slow scans.
  • Give each door phone a charger or power bank.
  • Agree in advance what staff do with already checked in and not on the list, so they don’t have to decide in front of a queue.

Questions and answers

What should the QR code on a ticket contain?

A ticket ID that's unique to that ticket and hard to guess, such as a long random string. Names and email addresses don't need to be in the code; they stay in your guest list.

Can I check guests in without an internet connection?

Yes, if the list is stored on the scanning phone. Doors in basements, tents and fields can have weak signal, so an offline list keeps the line moving.

What happens if someone shows a screenshot of another guest's ticket?

The first scan checks the ticket in and a second scan of the same code shows that it's already checked in. Staff can then ask for the guest's name or ID.

How do I handle guests who bring a plus-one?

Put the party size in a column of the guest list. Each scan of the ticket counts one more arrival until the whole party is in.

Sources