Event Check-In: QR Code Scanning and Attendance Tracking
How to use QR codes and the checked_in field on event registrations for day-of attendance tracking and check-in.
Registration tells you who plans to attend. Check-in tells you who actually showed up. The gap between those two numbers is the difference between optimistic planning and ground truth. Falaah bridges that gap with QR code-based check-in tied directly to event registrations.
How Check-In Works
Every event registration in Falaah carries a checked_in field. When an attendee is marked as checked in, this field updates on their EventRegistration record. The data is immediate and permanent — you know exactly who arrived and when.
The check-in flow is straightforward:
- Attendee registers for the event and receives a
confirmation_number - A QR code is generated for the registration (via Falaah’s
QRCodeDisplaycomponent andqr_code_service) - On event day, staff scan the QR code
- The system matches the QR code to the registration and sets
checked_into true - The attendee is confirmed as arrived
QR Code Generation
Falaah’s QR code infrastructure generates codes automatically for event registrations. The qr_code_service creates the QR image, and the QRCodeDisplay component renders it wherever it needs to appear — in confirmation screens, emails, or printable tickets.
The QR code encodes enough information to look up the registration. When scanned, it resolves to the specific EventRegistration record, pulling the attendee’s name, ticket type, and confirmation number for verification.
What Check-In Data Gives You
The checked_in field on each registration creates a clean dataset of actual attendance:
- Headcount accuracy — know exactly how many people are in the room, not how many said they would come
- No-show rates — compare registrations to check-ins to calculate your no-show percentage per event, per ticket type, or over time
- Capacity planning — if your free events consistently show 70% check-in rates, you can safely overbook by 30% on future events
- Compliance and safety — for events with occupancy limits or sign-in requirements, the check-in log is your audit trail
Day-of Operations
On event day, check-in requires nothing more than a device with a camera and access to the Falaah admin. A volunteer with a phone or tablet can scan QR codes as attendees arrive.
For events with multiple entrances, multiple devices can run check-in simultaneously. Since the checked_in field updates on the server, all devices see the same real-time state — an attendee checked in at the front door shows as checked in on the side door device immediately.
The name search fallback handles the attendees who forgot their confirmation email or cannot pull up their QR code. Staff search by name, find the registration, and mark it as checked in manually.
Connecting Registration to Attendance
The real value of check-in data emerges over time. A single event’s check-in numbers are useful. A year of check-in data across dozens of events reveals patterns:
- Which event types have the highest attendance rates
- Whether paid events have better show rates than free events (they almost always do)
- Which ticket types attract committed attendees versus casual registrants
- How far in advance reliable attendees tend to register
This data feeds back into event planning. If your Saturday morning workshops consistently see 85% check-in while weekday evening events hover at 60%, you schedule accordingly.
From the Seed Data
The After-School Tutoring event (April 18, 6 of 10 registered) is a small enough event that a single check-in device at the door handles the flow in minutes. The Neighborhood Clean-up (April 29, 8 of 30 registered) might warrant a sign-in table where a volunteer scans codes as people arrive with their gloves and trash bags.
In both cases, the data tells the same story: who signed up, who showed up, and the gap between the two.