Understanding Attendance Verification
When a worker checks in or out at a StandShare event, more than a timestamp gets recorded. StandShare captures verification metadata — a detailed record of how that check-in happened, who initiated it, and what device was used.
This page explains what that metadata is, why it matters, and what coordinators and admins can expect to see.
What Changed from Basic Check-In
Previously, checking in a worker recorded a single fact: this person is present (or absent). That was enough to know who showed up, but it left an important question unanswered — how was that record created?
A record that says "Checked in at 9:02 AM" does not tell you whether a worker scanned their own QR code on the way through the door, or whether a coordinator toggled them in manually from a spreadsheet two hours later. Those two scenarios are very different, and organizations increasingly need to be able to tell them apart.
Attendance verification metadata fills that gap. Every check-in and check-out now carries a full context record alongside the status change.
What Metadata Is Captured
For every check-in or check-out, StandShare records:
| Field | What it captures |
|---|---|
| Who performed it | The coordinator or operator who initiated the scan — or "self" if the worker scanned their own QR code |
| Method used | How the check-in happened: QR scan, manual toggle, bulk check-in, or PWA scanner |
| Timestamp | The exact date and time the check-in or check-out was recorded |
| Device type | Whether the scan came from a mobile phone, tablet, or desktop computer |
Coordinators do not need to do anything differently. Verification metadata is captured automatically in the background on every check-in and check-out flip.
Why It Matters
Compliance
For organizations that participate in grant programs, scholarship reviews, or external audits, attendance records need to be provable — not just present. Verification metadata lets you demonstrate that a check-in happened in real time, using the actual QR code system, rather than being entered after the fact. That distinction matters when records are reviewed by third parties.
Verified Credentials
Attendance verification is the foundation for a future credential system. When families complete event work hours, StandShare will be able to issue verified work-hour credentials — records that carry proof of how the hours were earned. These credentials will be useful for scholarship applications, community service documentation, and program reporting.
Verification metadata is what makes those credentials trustworthy. A credential backed by a QR scan from a specific device at a specific moment is meaningfully stronger than one backed only by a name on a list.
Dispute Resolution
If a question arises about whether a worker attended an event — or when exactly they arrived — the verification metadata provides a clear answer. The audit log shows not just that a check-in occurred, but who performed it and how. This protects workers, coordinators, and organizations alike.
What Admins Can See
Verification metadata appears in the audit log for each event. Admins and coordinators with audit log access can view the full context record for any attendance flip: who initiated it, what method was used, and what device was involved.
To access the audit log for an event, navigate to the event and look for the Audit Log tab in the event detail view.
Workers and families see their attendance status as before — checked in or not checked in — but they do not see the underlying metadata.
Privacy
Verification metadata is not visible to workers or family account holders. They see the same attendance status they have always seen: whether they are checked in or not.
Only admins and coordinators with audit log access can view the detailed metadata. This access is controlled by the same permissions that govern other coordinator-level views in StandShare.
Next Steps
- QR Check-In Dashboard — Monitor check-ins in real time during an event
- Understanding QR Check-In — How the full check-in flow works from worker to dashboard
- Roles and Permissions — Who has access to audit logs and coordinator tools