# QR Code Check-In vs Paper Attendance Lists

> An honest comparison of QR check-in and paper lists: where each one fails, when paper is the better choice, and how to run paper as your backup when data drops.

Source: https://laces.run/blog/qr-code-check-in-vs-paper-attendance-lists (HTML version of this page)

QR check-in beats a paper list when tickets are paid for, the crowd is large, or you need to know who may enter. Paper beats QR when the event is small, the signal is poor, or you need a signed record of who attended. Many events should use both, with paper as the backup. Laces sells QR check-in, so read this knowing that, but paper really is the right answer sometimes.

[Create your event](https://laces.run/app): Each person gets a QR ticket, and you can download your paid list for a paper backup.

## The short comparison

| | QR code check-in | Paper list |
| --- | --- | --- |
| **Needs** | A phone, a charged battery, a data connection | A printed list and a pen |
| **When it breaks** | Data drops, a battery dies, screens glare | Rain, wind, lost pages, bad handwriting |
| **Is the list current?** | Yes, each lookup reads the live record | Only as of when you printed it |
| **Is payment confirmed?** | Yes, the scan reads payment status | Only if the list was right when printed |
| **Who can stand at the gate** | Anyone with a team account | Anyone at all, and that includes people who shouldn't see the list |
| **Personal data at the door** | Staff see the person in front of them | Every name and phone number is on the table |
| **Spotting a repeat** | Shows the first arrival time | Depends on someone finding the earlier tick |
| **Attendance record afterwards** | Per person, not a report (see below) | The sheet itself, with a count you can add up |
| **Cost** | A phone per lane, plus data | Printing |

## Where paper is honestly better

**Small, known groups.** A 30-person workshop, a board retreat or a parents' meeting doesn't need a scan. Someone at the door who knows most of the faces can tick names and greet people at the same time. A scanner can make that moment feel colder for no gain.

**No reliable signal.** Scanning on Laces needs a data connection at the moment of the scan. For a retreat up a mountain or a venue deep underground, plan on paper from the start. A printed list has no dead zones.

**When you need a signature.** A funder asking for proof of attendance, a training course that gives certificates or a school trip register may need a person's own signature. A scan is not a signature.

**When you need an attendance sheet at all.** This is the limit most organizers don't expect. When a Laces ticket is scanned, the arrival is recorded against that person, and the scan screen shows the time when you scan or search for them. A search there records an arrival too, so don't use it to check on someone who hasn't come. But the app doesn't give you an attendance list or a count of who has arrived, and check-ins aren't in the export files. If your report needs "212 of 250 attended", keep a tally or a sheet as well.

## Where QR is honestly better

**Paid tickets.** A paper list only tells you what was true when it was printed. A person who paid 20 minutes ago isn't on it, and someone whose ticket was refunded this morning still is. A scan reads the live record, so it knows about both. An unpaid registration shows "Payment not complete", and a refunded one shows "Entry cancelled".

**Crowds.** Finding one name among hundreds on a page takes time, and it gets slower as the crowd grows. Two people can't easily share one page either. With QR codes, every lane works from the same record, so you can add lanes freely. To size them, see [how to check in 1,000 attendees](https://laces.run/blog/how-to-check-in-1000-event-attendees).

**Several gates.** With paper, a ticked name at Gate A is unknown at Gate B. With scanning, Gate B sees a "Checked in" time from Gate A. Staff still have to act on it, since a repeat scan doesn't turn red. Our guide to [duplicate and fake tickets](https://laces.run/blog/how-to-prevent-duplicate-or-fake-event-tickets) covers that.

**Privacy.** A list on a table is a page of names and phone numbers that anyone in the queue can read or photograph. A scanner's phone shows one person at a time.

## Paper as your backup when data drops

The best setup for most paid events is QR first, paper in the bag. A backup only works if you prepare it before the day, so here is how.

### Print the list close to the doors

From the Laces app, an owner, admin or finance team member can download the participant file as a CSV. It has one row per paid person, including their name, phone, ticket, order code and any answers to your questions.

Download it as late as you reasonably can, because registration may still be open. Registrations after your download won't be on your sheet, and your backup plan should say what happens to them. One option: anyone with a ticket email dated after your print time goes to the help desk.

### Cut the file down

Don't print the whole export. For a gate you need only:

- Name, sorted by surname
- Ticket type
- Order code
- A blank box to tick, and a time if you want one

Leave out phone numbers, question answers and anything medical. A page left on a table should expose as little as possible. Print in large type, on enough pages to split across lanes, such as A to H, I to P, Q to Z. Bring clipboards, and spare pens.

### Agree the switch in advance

Name one person who decides to move to paper, and give them a clear trigger. Lanes then work like this:

1. Ask for the ticket, and read the name and order code on it.
2. Find the name on the sheet.
3. Check the ticket type, and tick and initial the box.
4. If the name isn't there, send them to the help desk. A recent registration might be real.

### Know what paper can't do

Paper can't confirm a late refund or stop a forged ticket with a name someone copied from elsewhere. It also can't see a tick on another page. Accept this for the time you are on paper, and ask staff to check ID if the ticket price makes it worthwhile.

Paper ticks won't appear in Laces afterwards, because there is no way to enter them in the app. If the signal returns while people are still arriving, go back to scanning. Keep the sheets with your event records, then destroy them when you no longer need them. The [Laces Privacy Policy](https://laces.run/legal/privacy) sets out how organizer data duties work.

[Talk to the team](https://laces.run/contact): Tell us your venue, crowd and what records you need afterwards, and we can talk it through.

## Paper also covers cash

Laces doesn't record cash, and it has no desk or walk-in registration. Someone with cash can register on their own phone from your event link. If you take cash yourself, that happens outside Laces, so keep your own signed list and reconcile it after the event. Those people won't have a ticket to scan, so your gate needs to check that list as well.

## Which should you pick?

- **Under about 50 known guests, free entry:** paper is fine. That number is a rule of thumb, not a measurement.
- **Paid tickets of any size:** QR, with a printed backup.
- **Hundreds of people or several gates:** QR, with a printed backup and a named person to call the switch.
- **No signal at the venue:** paper, printed as late as you can before you lose signal.
- **You need signatures or an attendance count:** add a sign-in sheet or a tally, whichever system you use for the door.

If you want to see how scanning fits with registrations and payments, read about [managing registrations, payments and attendance in one place](https://laces.run/blog/manage-event-registration-payments-attendance).

## Frequently asked questions

### Does QR check-in work without internet?

Not on Laces. The scan looks the ticket up online, so the phone needs a data connection. Without one, the app says it could not check the ticket and asks staff to try again.

### Can I print my Laces attendee list?

Yes. Download the participant CSV from the app, open it in a spreadsheet, cut it down to the columns your gate needs, and print that.

### Do paper check-ins sync back to Laces?

No. Laces has no way to enter them. Keep the sheets as your record of those arrivals.

### Can I get an attendance report from QR scans?

Not as a list or a count. Each person's first arrival time shows when you scan or search for them, and check-ins aren't in the exports. If you need a report, keep your own tally at the gate.

### Is a paper list safe to use?

It can be, if you limit it to what the gate needs, keep it out of sight of the queue, and destroy it when you are done. Never share a photo of it in a group chat.
