A quick look at the QR-based check-in and check-out flow used at every myProctor event.
From the moment a proctor walks into the venue to the moment the coordinator sees them as Present.
The proctor reaches the assigned center on event day. No paperwork, no sign-in sheet at the door.
The proctor opens myProctor on their phone and taps Check in. A signed, time-bound QR appears for 60s.
The designated venue iPad — already running myProctor in attendance mode — scans the code. The token is verified server-side.
The coordinator's dashboard updates in real-time. The proctor's status flips to Present; the timestamp is logged.
When the event closes, the proctor checks out the same way — and the audit log seals automatically.
Exam concludes. The proctor heads back to the designated check-in iPad to close out their shift.
The proctor opens myProctor again and taps Check out. A fresh, single-use QR appears.
Same designated iPad. Same scan flow. The system recognizes this as a checkout, not a duplicate check-in.
Total hours computed automatically. The proctor's check-in/out pair is timestamped, signed, and immutable.
Three quiet pieces of plumbing that make the scan trustworthy.
Each QR carries a short-lived token signed with App Attest & HKDF-SHA256. It expires in 60 seconds, can't be replayed, and can't be forged off-device.
The moment the iPad verifies a scan, Firestore propagates the event to every coordinator dashboard in the venue — no refresh, no polling.
Every scan is timestamped server-side. Check-in/checkout pairs roll up into the proctor's shift log automatically — useful for payroll and dispute resolution.