# Attendee self-check-in kiosk — preflight and exception worksheet

Use one copy per station. Record station references and test outcomes only. Keep live ticket codes, attendee names, contact details, passwords and kiosk links in the approved system, not on this sheet. A check-in mark, printed badge and admission decision may be different states.

## 1. Define the station

| Event/date and station reference | Eligible ticket types | Check-in mode and lookup options | Printer/badge needed? | Admission decision owner | Exception owner |
| --- | --- | --- | --- | --- | --- |
| __________ | __________ | __________ | __________ | __________ | __________ |

- [ ] Confirm which action records arrival and where its authoritative status appears.
- [ ] Confirm whether the kiosk checks admission eligibility or only records a check-in; name the separate decision point if needed.
- [ ] Confirm what attendees can see or change on the screen, including lookup and badge reprint options.

## 2. Prepare the physical station

| Device and scanner method | Power/network check | Printer/media proof | Assisted-help location | Station start owner | Closure owner |
| --- | --- | --- | --- | --- | --- |
| __________ | __________ | __________ | __________ | __________ | __________ |

- [ ] Open the intended provider mode for the exact event on the actual device.
- [ ] Test a readable ticket scan or the documented alternate input method.
- [ ] Proof a badge on the actual printer if badge output is part of this station.
- [ ] Confirm that an attendee who needs help has a visible route to a staffed desk.

## 3. Rehearse with authorized sample records

Write what the attendee screen showed, what the source record became, and whether a badge was printed. Run samples only where they cannot create unintended live admissions or charges.

| Scenario | Expected decision | Screen observed | Check-in record observed | Badge observed | Pass / hold / owner |
| --- | --- | --- | --- | --- | --- |
| Valid ticket for this event and date | __________ | __________ | __________ | __________ | __________ |
| Invalid or wrong-event ticket | __________ | __________ | __________ | __________ | __________ |
| Already-used ticket | __________ | __________ | __________ | __________ | __________ |
| Attendee without ticket at hand | __________ | __________ | __________ | __________ | __________ |
| Printer fails after a valid attempt | __________ | __________ | __________ | __________ | __________ |
| Retry or badge reprint request | __________ | __________ | __________ | __________ | __________ |
| Assisted desk takes over | __________ | __________ | __________ | __________ | __________ |

If the status and badge disagree, do not infer the ticket outcome from the paper output. Send the reference to the exception owner and resolve it in the authoritative system before resuming that case.

## 4. Open and close

- [ ] Station owner confirms the event, mode, printer and help route before opening.
- [ ] First live results match the rehearsed valid and exception paths.
- [ ] Unexpected acceptance, duplicate count or unclear print result pauses the station; arrivals use the staffed route.
- [ ] At close, the closure owner uses the provider's shutdown control and verifies that the station no longer accepts arrivals.
- [ ] Reconcile check-in records, badge output and unresolved desk cases; hand over each open reference and owner.

Provider differences to verify: [Ticket Fairy](https://www.ticketfairy.com/guides/set-up-a-self-service-check-in-kiosk-for-your-event) describes ticket scan/code entry, optional email-code lookup, one badge per ticket at the kiosk, staff-managed reprints and a stoppable kiosk link. [Eventleaf](https://www.eventleaf.com/event-management-platform/self-check-in-kiosk) says its kiosk can allow attendee badge reprints and detail corrections. These are examples, not a shared feature contract.