An Airtable event check-in exception queue gives front-desk staff a place to send cases that ordinary registration lookup cannot resolve. Use miniExtensions to capture the exception and let a designated event lead review it in Airtable. Keep the normal arrival line moving without treating every unmatched name or repeated scan as an admission decision.

At fictional Westbridge Design Day, an attendee uses a different surname from the registration, another ticket appears checked in already, and a third person cannot find a confirmation. These are different problems. A shared queue preserves the context of each case while the event lead decides what should happen next.

Keep exceptions separate from registrations

Retain the existing Registrations table as the source for booking and attendance information. Add an Exceptions table with Exception reference as autonumber, Created time, Event as link, Desk or entrance as single select, Observed name as text, Supplied booking reference as text, Exception type as single select and Desk note as long text.

Add Assigned reviewer, Review state, Confirmed registration as a staff-managed link, Decision, Decision reason, Decided at and Resolution completed at. Suggested types are Not found, Already checked in, Name correction and Other. Suggested states are Waiting, In review, More information needed and Resolved. The distinction between a decision and its execution matters when a volunteer must still escort someone or correct a record.

Do not let a desk submission rewrite the original registration name, reset attendance or create an additional ticket automatically. A proposed correction belongs in the exception until the reviewer has resolved the identity and booking question under the event’s policy. These are workflow fields you configure, not a built-in ticketing adjudication service.

Make the desk intake short and staff-only

Set up a miniExtensions Portal for the people staffing the desk, with a Staff users table and a direct linked user field on Exceptions. The Users Table documentation explains the required link between a portal’s data table and its users. Plan those links before configuring the portal.

Populate Staff users only with approved desk workers, using one valid staff email address per record. In Users & Login, open that email login field and enable Two-Factor Authentication (Email verification), as described in the verification setup. Do not treat knowing a colleague’s email as authentication. Use individual accounts and check sign-out behavior on shared devices because a browser may remember its login.

For each desk worker’s exception view, choose Personal records only under the view’s Filter and Sort settings. The per-user record guidance describes this option. The event lead can manage the complete queue in Airtable through their existing staff access rather than exposing all attendees to every desk account.

Configure the exception creation form with only the intake fields a desk worker needs. Leave reviewer decisions, confirmed-registration links and resolution timestamps out of the editable intake. Verify that new exceptions receive the intended staff-user link before use. A person’s typed name in a text field is not a substitute for the linked access relationship.

Use different review paths for different problems

For Not found, the reviewer checks the correct event, plausible alternate spelling and supplied booking reference in the authoritative registration system. A match may exist under the booking contact rather than the person attending. If no booking can be established, the event’s walk-in or refusal policy determines the outcome. The queue does not create eligibility.

For Already checked in, preserve the existing attendance record while investigating. A previous scan could be a legitimate arrival, a staff mistake or another situation requiring review. Do not label the person fraudulent based on this state alone, and do not clear the original timestamp simply to make a second scan succeed.

For Name correction, store the proposed spelling separately from the confirmed registration. The event lead verifies that the requested change concerns the same attendee before updating the authoritative record. A correction is not permission to transfer a ticket. Record the factual reason for any authorized change without collecting unnecessary identity-document images.

Own the decision and the handoff

Use an Airtable review view grouped or filtered by Review state, with Assigned reviewer visible. The lead takes responsibility for a case before resolving it and checks whether another desk has already raised the same issue. Similar names are not enough to merge cases. Compare event, booking reference and context first.

For the attendee using a different surname, the lead might establish the existing booking, link the confirmed registration and record “Return to reception for check-in.” A desk worker then performs the event’s ordinary check-in action and records that the resolution was completed. Approval in Exceptions should not be mistaken for an attendance update in Registrations.

Communication remains explicit and manual in this baseline. The lead tells the desk worker what to do using the event’s agreed channel, and the worker checks the latest decision before acting. Adding a status value does not send a notification. If several staff work simultaneously, agree who owns the final action; this design does not provide a transactional lock or prevent every duplicate action.

Preserve a useful record without overcollecting

Write operational notes such as “booking found under organizer contact” instead of speculative judgments about the attendee. Keep sensitive explanations out of a general desk queue. Restrict access to registration details to people whose event role requires them, and apply the organization’s retention policy after the event.

This exception queue complements a registration or scanning workflow. It is not an offline check-in system, a ticket-payment service, a capacity reservation mechanism or proof of identity. If connectivity fails, follow the event’s approved fallback procedure and reconcile any authorized offline records afterward rather than pretending the portal has recorded an action.

Rehearse the awkward cases

Before opening the doors, use fictional registrations for a misspelled name, a repeated arrival, a wrong-event reference and two desks reporting the same case. Check a second staff account to verify visibility. Confirm that desk workers cannot change decisions or attendance through another view, expanded record or profile route.

Also rehearse an approved decision that has not yet been carried out. The event lead should be able to find it without assuming the attendee is inside. These are recommended checks, not reported test results. A useful exception queue ends with a clear decision and a completed handoff, while keeping the authority to admit someone with the event team.