# Escalate door issues

## Public help

Explain when scanner staff should call an organizer or LinkUp support.

## Door procedure

Keep the door process calm. Validate the ticket, compare the event, and escalate uncertain results instead of guessing.

## Implementation note

Scanner behavior must be tested against the Scanner App, scanner API, ticket scan records, and duplicate conflict reports.

## Implementation status

<table id="bkmrk-expected-behaviorsta"><tbody><tr><th>Expected behavior</th><th>Status</th><th>Surface</th><th>Manual check</th></tr><tr><td>Scanner workflow matches app behavior.</td><td>Needs Verification</td><td>Scanner App / API</td><td>Run a scan test with valid, invalid, and duplicate tickets.</td></tr><tr><td>Door staff permissions are limited.</td><td>Needs Verification</td><td>Scanner App / Roles</td><td>Login as scanner and confirm only scanning tools are available.</td></tr></tbody></table>

## Verification checklist

- Test valid ticket scan.
- Test duplicate ticket scan.
- Test no-network behavior if supported.
- Confirm admin scan records.

## Gaps / notes

- Offline-first behavior needs hands-on venue-style testing.
- Exact scanner app labels need screenshots before public use.