QR Code Event Check-In That Ends in a Spreadsheet
To run QR code check-in that ends in a spreadsheet, import your attendee list into a scanning app, scan each badge at the door, and export the session as CSV afterwards. DataScan verifies every scanned code against the imported guest list on the spot — offline, so bad venue Wi-Fi is irrelevant — and the export opens straight in Excel or Google Sheets with one timestamped row per attendee.
The clipboard line and the SaaS sledgehammer
Event check-in usually fails in one of two directions. The clipboard: a printed list, a highlighter, a queue that grows while a volunteer scans names with a finger — and afterwards, someone retypes the highlights into a spreadsheet. Or the sledgehammer: a full event platform with registration, payments, badge printing, and a per- attendee fee, adopted because the only thing anyone actually needed was a fast door and an attendance file.
If your registrations already live in a spreadsheet — a class roster, a member list, a mail-merge export — the missing piece is small: a scanner that knows the list, says yes or no at the door, and hands the results back as a file. That is a phone-app-size problem.
Attendance scanning to CSV: step by step
- Put a unique QR code on every badge or ticket Any QR generator works — the code only needs to carry a unique ID: a registration number, an email address, a member ID. Mail-merge tools, badge printers, and even spreadsheet formulas that build QR image URLs all do this in bulk. (Paper tickets with barcodes work identically — DataScan reads 13 code types.)
- Import the attendee list into DataScan Export registrations as a CSV — ID, name, ticket type, whatever the door staff should see — and load it into the app's Lookup database. The entire guest list is now on the phone itself, which is why venue connectivity stops mattering.
- Scan badges at the door with Lookup Scan In Lookup Scan mode, each scan instantly shows the matching attendee's fields — the door person sees the name and ticket type and waves the guest through. A code that is not on the list simply finds no match: the universal signal for "this badge needs a human conversation," caught before entry, not discovered in the post-event audit.
- Switch to Continuous Scan when the line surges When 200 people arrive in ten minutes, verification per person is the wrong trade. Continuous Scan captures one timestamped scan per badge as fast as you can aim the camera — with a touch-and-hold pause when the line stalls — and the list-matching happens in the spreadsheet afterwards. Many events run Lookup at the quiet start and Continuous at the peak.
- Export the attendance file Doors closed, export the session as CSV or Excel: one row per scanned badge, each with a timestamp. Email it through your own SMTP server, upload it via SFTP, or share the file to any app. For Google Sheets, import the CSV or use the email-to-Zapier route from the Google Sheets guide.
-
Reconcile attendance against registrations
In the sheet,
=COUNTIF(scans, id)against the registration list marks who showed and who did not. That single column is the no-show list for follow-up, the headcount for the caterer's invoice, and — for training sessions and compliance events — the attendance record with scan-time evidence.
Before doors open: the ten-minute dry run
Do a rehearsal the day before, end to end. Print or display three test badges — one valid, one deliberately not on the list, one duplicate — and run them through the exact flow: the valid badge should show its record, the stranger should come up empty, the duplicate should be blocked. Then export the test session and open it in your sheet, so the first time you see the file format is not at midnight after the event. While you are at it, check the physical realities: glossy badge laminate glares under entrance lighting (tilt, don't fight it), and QR codes on phone screens scan best at full brightness.
Door-tested tips
- Enable duplicate prevention. A re-presented badge is caught at the door instead of surfacing as a mystery in the export.
- One session per door, named accordingly. main-entrance 2026-07-10 and side-door 2026-07-10 merge cleanly in the sheet and tell you which entrance carried the load.
- Brief the door staff on the no-match script. The app's job is to flag; the human's job is the friendly "let me just check you in manually" — decide before doors open where manual additions get written down.
- Timestamps are the bonus data. Arrival-time distribution tells you when to staff the door next time — free insight from data you captured anyway.
Real-world pattern: the event check-in case study runs this exact setup at the door, and the university attendance tracking case study shows the recurring version — the same roster scanned lecture after lecture, exported per session.
When a dedicated check-in platform is the better tool
Honesty about the fit: dedicated check-in tools (OneTap and similar) and full event platforms exist for good reasons — online registration and payment, on-site badge printing, multi-session agendas, kiosk self-check-in, live dashboards across many doors. If you need those, pay for them. The scanning-app approach wins the long tail underneath: rosters that already live in spreadsheets, venues with unreliable Wi-Fi (see the offline scanning guide), recurring classes and member events, and any check-in where the deliverable is an attendance CSV rather than a dashboard. The same Lookup workflow generalizes well beyond events — the database verification guide covers it — and the DataScan overview shows all five modes. The 7-day free trial includes everything, so a dry run with tomorrow's guest list costs nothing.
Frequently Asked Questions
Yes — that is the strongest reason to run check-in this way. The attendee list is imported to the phone beforehand and every scan is stored locally, so verification and capture work with no connectivity at all. Basement venues, tents, and overloaded conference Wi-Fi change nothing. You export the attendance file whenever you next have a connection.
Two layers: DataScan can prevent duplicate scans within a session, so a re-presented badge is caught at the door; and every scan is timestamped, so the export shows exactly when each code was first and subsequently seen. For multi-door events, note that each phone checks its own session — assign doors distinct badge ranges or reconcile the merged files afterwards.
Yes. Export the session as CSV and import it into Google Sheets (File, Import, Append), or email the export to a Zapier-connected address that appends rows automatically. The scan-to-Google-Sheets guide covers both routes in detail.
No — it replaces the door scanning and attendance-report part, not registration. If you need online ticket sales, payment, badge printing, and session-level agendas, a dedicated event platform earns its fees. If registrations already live in a spreadsheet and what you want at the end is also a spreadsheet, a scanning app is the honest-size tool.
