Practical guide

Make re-entry rules explicit before the first guest leaves

Last materially reviewed 2026-09-28

Quick answerSoftware can record changes of status; the organizer decides whether and how re-entry is permitted.
What to know

State the policy separately

Write the event’s re-entry rule in plain language and identify who can resolve exceptions. A button that changes check-in status is not a policy. The rule may depend on the event’s ticket conditions and venue arrangements, which this publication does not interpret for you. Make sure the same instruction reaches all entrances and the people communicating with attendees.

What to know

Rehearse the intended record

Ticket Tailor documents checking a person out and back in. Determine what your team should record for the actual permitted journey. Do not use repeated changes simply to clear an inconvenient message. The record should remain meaningful for the event’s reporting purpose. Where occupancy or safety counts matter, use the approved venue process rather than treating a software total as a certified safety measure.

What to know

Explain the handoff across entrances

A returning person may approach a different volunteer. That operator should not have to rely on recognizing them. Define the evidence and authorized route the team will use. Keep connectivity limitations visible: a change on one device may not immediately be known to another. A consistent instruction helps, but it does not eliminate the need to verify the relevant system state. Where an exit was not recorded, preserve that missing observation. Do not invent an exit time or silently treat a second scan as a new sale.

What to know

A fictional reporting difference

A guest attends, leaves and later returns under a permitted policy. The event may have several recorded interactions for one person. The final report should not describe those interactions as several unique attendees. Decide which question the report is answering before selecting a count. Preserve the distinction between currently checked in and ever attended, and explain unresolved cases rather than forcing every number to match.

Continue when useful

Next: Already checked in

Investigate the recorded action and the event’s re-entry policy before changing a ticket’s status.

Open Already checked in →

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