How do you prove session attendance for continuing education credits using badge scans at the room door?
Accrediting bodies want evidence that a professional actually sat through a session. Door scans can provide it, but only if you design the process for audits rather than just for counting.

What accrediting bodies typically expect
Continuing education programs for nurses, accountants, engineers, attorneys, and many other licensed professions require the provider to document that each participant attended the session for the claimed duration. The exact rules vary by profession and by state board, but the common thread is that a signature on a sign-in sheet is increasingly seen as weak evidence, and that providers are expected to keep records for several years in case of an audit. Some bodies also want proof of attendance for the whole session, not just arrival.
Badge scanning helps because it produces a timestamped, attributable record with no handwriting to decipher. It does not help if the record is incomplete: a scan at the door proves someone entered at a given moment, and nothing more. To turn scans into defensible attendance evidence, you need an entry scan, an exit scan or an end-of-session confirmation, and a written procedure describing how those scans are collected and reconciled. The procedure matters as much as the data, because auditors read procedures.
Keep reading: How can event organizers speed up the check-in line during the busy first hour of a conference?, What are the benefits of printing event badges on site instead of pre printing them all in advance?, How do organizers track session capacity so a popular conference talk does not become overcrowded?. See how BadgeCheckr helps you event attendee badge check-in and scanning.
Setting up entry and exit scanning that holds up
Station a monitor at each door with a scanning device set to the specific session, not a generic mode. The app should reject a badge that lacks the session entitlement and flag a badge that already scanned in, so the same person cannot be counted twice by walking out and back. Scan at the doorway, not from a seat, so the timestamp reflects when the attendee physically entered. Keep the monitor in place until the session begins plus a short grace period, and record late arrivals separately so the provider can decide whether they still qualify.
For exit, the simplest reliable approach is a scan on the way out at the session end, with monitors at every exit. Where that is impractical, some providers substitute an in-room verification such as a code announced at the end that the attendee enters in the event app, paired with the entry scan. Either way, store both timestamps against the attendee record and compute the attended duration. Decide the minimum qualifying duration in advance and apply it consistently. Related: How can event organizers speed up the check-in line during the busy first hour of a conference?
Reconciling and issuing certificates
After each session, export the scan records and reconcile them against the roster before anyone issues a certificate. Look for attendees with an entry but no exit, which usually means they left early or the exit monitor missed them. Look for exits without entries, which usually means a late arrival who slipped in through an unmonitored door. Resolve each case with a written rule rather than case by case, and keep the resolution notes with the records. Related: How can a large event run multiple check-in stations at once without checking anyone in twice?
Issue certificates only after reconciliation, and generate them from the attendance data rather than from the registration list. A certificate should state the session title, date, duration, and the credit type and hours awarded, along with the provider's approval number where one applies. Many providers now let attendees download certificates from a portal that reads the same data, which reduces the number of emails asking for a reissue and keeps a single source of truth. Related: How should an event handle walk-up attendees who never registered before arriving at the door?
Preparing for an audit before you need one
Keep the raw scan logs, the reconciliation notes, the session agenda with actual start and end times, and the written procedure together in one archive per event. Retain them for at least as long as the strictest applicable board requires, which for some professions runs several years. If the scanning software allows it, export logs in a plain format that will still be readable when the vendor relationship has ended. Related: What are the benefits of printing event badges on site instead of pre printing them all in advance?
Run a mock audit once. Pick a random attendee and try to prove from your archive alone that they attended a specific session for the required duration. If you cannot do it in a few minutes, the process has a gap. Common gaps include monitors who left the door before the session started, devices set to the wrong session, and exit scans that were skipped because the crowd surged out at once. Each one is fixable with staffing or a small process change, but only if you find it before an auditor does.
- A door scan proves entry time only; defensible CE records need an entry scan plus an exit scan or end-of-session confirmation.
- Set scanning devices to the specific session so the app rejects wrong badges and duplicate entries.
- Reconcile scan records against the roster before issuing any certificate, using written rules for edge cases.
- Archive raw logs, reconciliation notes, and your written procedure together, and run a mock audit before the real one.
A check-in line that moves
Event attendee badge check-in and scanning. BadgeCheckr is built to help you put this into practice.
Set up check-inGet the BadgeCheckr playbook
Practical guides on event check-in, straight to your inbox as we publish them. No spam, unsubscribe any time.



