Practical guide

Handle a ticket for another date or time slot

Last materially reviewed 2026-09-28

Quick answerA valid purchase for another occurrence does not automatically authorize entry now.
What to know

Confirm the two scopes

Compare the date and time on the ticket with the occurrence selected for the current entrance. Use unambiguous dates in communication, especially where an event repeats or people travel. Avoid relying on a similar event title. The volunteer’s job is to identify the mismatch and follow the agreed route, not to decide spontaneously that all occurrences are interchangeable.

What to know

Use the organizer’s policy

Some events permit flexibility and others do not. The software’s ability to load several occurrences does not establish that policy. Identify who can approve a change and whether it requires an order update or another recorded action. Do not promise a transfer, refund or alternative session before the authorized person has assessed it. This guide is about a clear handoff, not creating customer rights or interpreting ticket contracts.

What to know

Keep the active list understandable

If the team intentionally loads multiple occurrences, brief operators on why and how to interpret them. A broad list may be useful at an exception point but confusing at a single-session entrance. Check that the person can identify the accepted scope without guessing. When the schedule changes, review device selection, printed lists and public directions together; one updated screen does not update every working copy. Record the intended date in the handoff so the lead can distinguish an occurrence mismatch from an absent entitlement.

What to know

A fictional early-arrival case

Someone arrives for a later session and shows a valid code. The ordinary entrance sends them to the named lead. The lead applies the actual event policy and records any authorized change. The scanner operator does not count the person as admitted merely because their purchase is real. At shift handover, the team discusses the pattern in anonymous terms and clarifies the instruction if several people were confused.

Continue when useful

Next: Exception handoff

Give uncertain cases a named owner, a minimum handoff and a clear return instruction.

Open Exception handoff →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Ticket Tailor: selecting occurrences — Merchant documentation · help.tickettailor.com · Merchant-controlled · checked 2026-09-28
  2. Ticket Tailor: attendee check-in — Merchant documentation · help.tickettailor.com · Merchant-controlled · checked 2026-09-28