Practical guide

Handle an already-checked-in result without guessing who is at fault

Last materially reviewed 2026-09-28

Quick answerInvestigate the recorded action and the event’s re-entry policy before changing a ticket’s status.
What to know

Treat the result as a record

An already-checked-in message reports a prior status; it does not by itself explain the person’s intent. The cause could involve re-entry, an operator mistake, group handling or a genuine duplicate attempt. Keep the interaction calm and move the uncertain case to the responsible person. The volunteer should not accuse someone or erase the earlier action merely to make the warning disappear.

What to know

Inspect the available history

Ticket Tailor’s guide describes seeing the earlier time and scanner information. Use only the access granted to the role and compare that record with the organizer’s current policy. A history entry can narrow the investigation without answering every question. If devices were disconnected, note that limitation. Do not equate a single screen with a complete account of what happened across all entrances.

What to know

Separate correction from re-entry

Correcting an accidental record and admitting someone who legitimately left are different decisions. Name who may make either change and how the reason is recorded. Avoid a blanket instruction to check every warning out and back in. That would remove useful context and could misstate attendance. The process should preserve the original uncertainty until an authorized person resolves it. Keep the displayed device and time with the private investigation, rather than concluding that a repeated status proves the same person entered twice.

What to know

A fictional return visit

A guest leaves briefly and returns to a different entrance. The device reports the earlier admission. If the event permits re-entry, the lead follows that defined route; if not, the volunteer does not invent an exception. The report after the event should still distinguish unique attendance from repeated entrance interactions. A policy decision, a software action and a reporting interpretation are three separate responsibilities.

Continue when useful

Next: Re-entry rules

Software can record changes of status; the organizer decides whether and how re-entry is permitted.

Open Re-entry rules →

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: attendee check-in — Merchant documentation · help.tickettailor.com · Merchant-controlled · checked 2026-09-28
  2. Ticket Tailor: check-in reporting and its limitations — Merchant documentation · help.tickettailor.com · Merchant-controlled · checked 2026-09-28