Click Scan log from a site's detail page to see every badge scan at that site's gate, newest first: timestamp, worker, result, and — for a blocked scan — exactly which credential types were missing.

Result types

  • Cleared — the worker held every required credential type at scan time.
  • Blocked — at least one required type was missing, expired, or untagged.
  • No requirements — the site had no required types set, so the scan trivially passed.
  • Unrecognized badge — the QR/slug scanned didn't match any worker.
  • Unrecognized gate — the device's configured site wasn't recognized (inactive or mistyped).
This can't be spoofed from the device that's scanning. Clearance for the log is recomputed on the server at the moment of the scan, from the worker's actual record — never trusted from whatever the scanning device displayed. A gate tablet showing a stale or tampered "cleared" screen still logs the true result.

Reviewing the log requires an admin login. The gate scan flow itself (badge scanning) never requires signing in by design — so the log records which device/worker was scanned, not which staff member ran the scanner. If you need to know who personally checked someone in, that's a bigger identity change beyond what FieldCred tracks today.