A fictional example
This illustration uses made-up totals for Example Venue on October 3, 2026. It is not a customer case study or a report issued by Check ID. The tables illustrate selected summary fields; your exported report may include other sections and use a different layout.
| Summary field | Count |
|---|---|
| Received scan records | 240 |
| Staff decision: accepted | 228 |
| Staff decision: rejected | 12 |
| Repeat-entry alerts | 8 |
Accepted and rejected describe the staff decision, not proof of document authenticity. Repeat-entry alerts can occur on either result, so the eight alerts are already part of the 240 scan records, not eight additional visitors.
| Hour beginning | Received scan records |
|---|---|
| 6 PM | 24 |
| 7 PM | 48 |
| 8 PM | 72 |
| 9 PM | 60 |
| 10 PM | 24 |
| 11 PM | 12 |
The busiest recorded hour here is 8 PM. Scan volume can inform shift planning, but it is not a count of unique guests, occupancy or total attendance. Repeat scans and checks made outside the app affect that comparison.
Ungated aggregate example. No customer data, employee names, report-verification link or valid signatures.
Summary report or per-scan log?
The PDF summary groups received scan activity, including totals, staff decisions, recorded rejection reasons, scan methods and hourly activity. A per-scan CSV log lets you review individual records. Exported logs use internal operator references rather than employee names; owners and managers can match those references inside Check ID.
Scan records omit the scanned person’s name, birth date, address, document number and ID image. Records can still contain facts derived from a scan and operational metadata. Guest-list names your team adds are separate data. See what Check ID keeps.
How should you review a real report?
- Choose the venue and date range. Check the report’s time-zone and business-day labels before comparing shifts.
- Reconnect scanning devices and review pending uploads. Reports only include records the service received and still retains.
- Keep the app’s check outcome separate from the staff decision. A repeat-entry prompt or REAL ID marking does not prove forgery or authenticity.
- Compare exceptions with your procedures. A report or record-integrity check does not certify legal compliance or prove that every customer was checked.
Use the staff handoff and reconnect drill and review what each check means.