This event SOP template uses three roster codes and one recorded check-in to demonstrate a desk review. A code checker distinguishes E01 with no supplied receipt, E02 with prior C02, and unknown E99. It returns the next record question without adding an attendee or making an entry decision.
Keep roster membership separate from arrival
The fictional paper-workshop roster contains E01, E02, and E03. Only E02 has a supplied receipt, C02. The initial unique recorded check-in count is therefore one, not three. E01 and E03 have no supplied check-in evidence in this snapshot; that absence does not establish what happened outside it.
Put the actual session and roster revision beside the records. A receipt from another session cannot answer the prior-record question here. Before use, the coordinator supplies authorized staff roles, the code and identity-check method, record permissions, reentry policy, and the exception route. An exact roster match alone supplies none of those decisions.
Give the desk a usable sequence
Start by confirming the maintained session roster and the staff route. Match the presented code exactly, inspect existing receipts for the same session/code, and follow the authorized process for either a single record or a hold. Preserve duplicate and unknown-code exceptions, then reconcile unique recorded codes for the handoff.
Eventbrite's event checklist includes check-in-flow planning and team communication. Use those planning ideas to make the desk procedure explicit. This original paper example does not adopt a ticketing app, scanning feature, registration system, or email workflow. Keep the complete controlled SOP and actual receipt records in the event's native format.
Try the three code cases
Enter E01 and choose Inspect code. The code matches the roster, but no prior receipt is supplied. The result asks for the authorized recording process; it creates no receipt. Enter E02: C02 is retained, the repeated presentation is identified, and the unique count stays one. A duplicate record question does not determine whether the person may reenter.
Enter E99 to see the unknown-code route. It calls for coordinator review without creating another roster member or an entry outcome. Blank input asks for a code; a differently cased code does not silently become an exact match. Editing the input clears the previous result so an old E02 message cannot appear to describe E99.
Keep the hypothetical count labeled
If a later authorized E01 receipt were supplied, the unique count would be two: E01 and E02. That conditional comparison helps check the counting rule, but it is not evidence that E01 arrived. The example creates no new receipt or coordinator decision; those belong in the maintained event records.
An exception record should retain session/revision, presented code, match result, prior receipt, reason for review, coordinator route, and actual decision/reference/date. Repeated presentations belong outside the unique arrival count. Leave unknown owners and contact routes unresolved until the coordinator supplies them. The final handoff should identify both the counted IDs and the open decisions, so the next desk worker can inspect the same record basis.
Copy this prompt to adapt the example
Design an event check-in review sheet with the ordered procedure beside the sample roster and a separate exception-record outline. Return one self-contained HTML file with embedded styling and working interactions. Use readable type, strong contrast, clearly labeled keyboard controls, and a layout that flows on a narrow phone. Identify the supplied data as a fictional example.
Create a fictional paper-workshop check-in SOP review. Roster codes E01, E02, E03; only E02 has sample receipt C02. Display roster count 3 and unique recorded check-ins 1, with counted ID E02. Show the ordered procedure: confirm session roster/staff route, exact code match, same-session prior receipt check, authorized single-record-or-hold process, exception/decision, unique-ID handoff. Actual authority, roster revision, identity method, reentry policy, and coordinator route are unconfirmed.
Provide a labeled blank code input and Inspect code button. Exact E01/E03 matches show no supplied receipt and ask for the authorized recording process, without creating a record. E02 retains C02, flags repeat, and leaves count 1; do not infer denial or reentry. E99 and other unmatched strings route to coordinator review without adding attendees. Empty input asks for a code. Do not silently normalize case into an exact match. Input edits clear stale output. Add the clearly hypothetical note that a later authorized E01 receipt would make 2 unique IDs. List the information required for an actual exception record as prose; do not present it as a completed receipt or decision. No real registration, scan, payment, sending, saved state, or staff authorization.
Put E02 and E99 on the coordinator's review agenda: one needs a same-session duplicate decision, the other has no roster match. An HTML view in NOS keeps those two paths beside the proposed desk procedure during the discussion. Use the coordinator's answers to finish the reentry rule and exception route before handing the procedure to the check-in team.