Introduction
Attendance is tracked separately from registration so staff can distinguish between “planned to attend” and “actually arrived.”
That distinction matters in real nonprofit operations.
A registration record tells you who signed up. An attendance record tells you who was physically present or admitted on the day of the event. Those are not always the same people, and treating them as the same can create misleading reporting and weak follow-up.
For example:
- a registrant may cancel late or simply not show up
- a guest may attend even if the primary registrant does not
- a staff team may need attendance totals that differ from registration totals
- post-event follow-up may need to target attendees and no-shows differently
Altrinum separates these concepts intentionally so event teams can understand what actually happened, not just what was expected to happen.
Why attendance is separate from registration
It is tempting to assume that a confirmed registration equals attendance, but that is rarely true in practice.
Nonprofit teams often need to answer questions such as:
- Who actually attended the stewardship dinner?
- Which registrants did not arrive?
- How many guests were checked in?
- Which supporters should receive attendee follow-up rather than no-show follow-up?
- Did the event reach the expected turnout?
Those questions depend on attendance records, not just registration status.
That is why attendance exists as its own operational layer.
Why this matters operationally
Separate attendance tracking is useful across many types of events, including:
- paid events where registration and attendance both matter
- cultivation or stewardship events where presence matters more than signup
- workshops and training sessions where completion or participation may be reviewed later
- member or community gatherings where turnout is part of evaluating success
- events with guests, where the actual attendees may differ from the original registration pattern
In all of these cases, event teams need more than a registrations list. They need a reliable way to record arrival.
How the scanner workflow is designed
The scanner workflow is built for front-desk speed and clarity.
On event day, staff usually need a system that can:
- identify the right attendee quickly
- verify that the QR code belongs to the right event
- prevent duplicate check-in confusion
- work on a phone or tablet
- provide immediate feedback to door staff
That is what the scanner is meant to support.
The system validates the QR token against the selected event and tenant, prevents accidental duplicate entry, and writes a separate attendance trail that staff can later review or export.
What the QR check-in is doing
A successful scan is not just reading a name off a code.
The scanner is checking that:
- an event has been selected first
- the QR token belongs to the selected event
- the token belongs to the correct tenant
- the token is valid for check-in
- the attendee is not being checked in twice by mistake
This helps staff trust the result they see at the door.
It also reduces common event-day problems such as:
- scanning the wrong event’s code
- using a stale or invalid code
- creating duplicate attendance records
- checking in a person under the wrong event context
Duplicate scans are handled intentionally
At busy events, duplicate scans happen all the time.
Someone may:
- step through the line twice
- present the same code again
- be checked by two staff members close together
- ask for reassurance that they were already recorded
Instead of creating duplicate attendance rows, the scanner can return a success-style confirmation that the person is already checked in.
That is important because event-day staff usually need a quick answer, not an error that sounds alarming.
Attendance records support post-event work
Attendance is not only for the front door.
Once the event is over, attendance records can support:
- no-show analysis
- attendee-only follow-up
- attendance exports
- reconciliation between expected turnout and actual turnout
- review of event operations and staffing
- future planning for capacity, reminders, or event timing
This is where separate attendance tracking becomes especially valuable. It gives the team a more honest operational picture than registrations alone.
Why badge generation belongs here too
Badge generation is closely related to check-in and event-day operations.
Badges help with things like:
- name visibility
- smoother front-desk handling
- staff confidence in attendee identity
- large in-person events where quick recognition matters
That is why badge generation often appears in the same operational area as check-in, even though badge layout itself may vary by team process.
Manual and fallback check-in matter
A camera-based scanner is often the fastest option, but events rarely run perfectly.
Teams may also need a fallback when:
- camera permissions are blocked
- a device has trouble focusing
- a code is damaged
- the attendee presents the raw code instead of the QR image
- the front desk is working in less-than-ideal network or device conditions
That is why pasted-code or manual fallback check-in matters operationally. It gives event staff another path to keep the line moving.
A practical way to think about attendance
A healthy event-day attendance workflow usually looks like this:
- select the correct event
- scan QR codes where possible
- use manual fallback when needed
- rely on duplicate-safe feedback at the door
- review the attendance list during and after the event
- export attendance later if needed for follow-up or reporting
This makes check-in more than a momentary scan. It becomes a reliable operational record of who actually arrived.
Tips and notes
Registration tells you who intended to attend. Attendance tells you who actually arrived. Use both, but do not confuse them.
For a busy event, test the scanner and fallback flow before attendees begin arriving.
Note: Duplicate-safe scanner behavior is a feature, not a flaw. It helps staff confirm attendance without creating messy records.
Example: A fundraising breakfast may have 120 confirmed registrations but only 98 attendance records. That difference is often the real basis for no-show analysis and post-event follow-up.