# Ticket check-in window: boundary test card

Use an authorized sample ticket, never an attendee's live credential. Record the configured rule and the scanner's real response before briefing the entrance team.

**Event / occurrence:** ____________________  **Ticket type:** ____________________

**Configured check-in mode:** ____________________

**Intended first check-in:** ____________________  **Intended last check-in:** ____________________

**Displayed time zone:** ____________________  **Test owner:** ____________________

| Controlled test | Intended decision | Actual scanner result | Pass / follow-up |
| --- | --- | --- | --- |
| Before the first allowed time | ____________________ | ____________________ | ____________________ |
| Within the allowed interval | ____________________ | ____________________ | ____________________ |
| After the last allowed time | ____________________ | ____________________ | ____________________ |
| Wrong event or ticket type | ____________________ | ____________________ | ____________________ |

**Separate purchase-window check:** ____________________

**Unexpected result and approved correction:** ______________________________________

**Exception owner at the gate:** ____________________  **Retest completed by / at:** ____________________

Do not treat a sale date, event date or successful purchase as proof that the credential is valid for a particular scan time. Platform modes and boundary behavior differ. Use the provider's actual control and record the observed result; follow the approved admission decision if a live scan is refused.

Provider reference: [Tickera check-in date and time availability](https://tickera.com/tickera-documentation/faq/set-available-date-time-ticket-check/) · [Tickera ticket-type settings](https://tickera.com/tickera-documentation/ticket-types/)