Practical guide

Hand over an admission shift without losing unresolved cases

Last materially reviewed 2026-09-28

Quick answerTransfer the current scope, device state and outstanding decisions—not merely the scanner.
What to know

Name what is changing

A shift handover can change the person, device or responsibility. Say which of those is happening. The incoming volunteer should know the event occurrence, accepted ticket types and exception lead before taking over. Do not assume an outgoing operator’s familiarity transfers with the phone. Keep personal account access separate from the physical device, following the organization’s approved sign-in and sign-out process.

What to know

Review current conditions

Mention meaningful changes since the original briefing: lost connectivity, a device restriction, a revised entrance instruction or a late-sale procedure. Distinguish a confirmed change from a rumor. The incoming person should know which current instruction applies and where its source is recorded. A long history of every minor interaction is less useful than a short statement of the present state and the next unresolved decision.

What to know

Transfer exceptions privately

Pass only the information needed by the authorized recipient. Do not leave attendee identifiers on an unattended desk or in a public handover photo. Record the owner of each unresolved case so that it is not assumed to be someone else’s responsibility. An issue can remain pending across a shift; the important thing is that its status and owner remain clear. The incoming operator should identify the selected event and active ticket filter before taking over the device.

What to know

A fictional mid-event change

The main entrance is connected, while a spare device has not yet downloaded the current occurrence. The outgoing lead labels the spare as unprepared and hands over that fact explicitly. The incoming team does not mistake its full battery for readiness. One unresolved ticket question goes to the named supervisor rather than being lost in casual conversation. The handover ends when the new operator can explain the current task and escalation route.

Continue when useful

Next: Device readiness

Check the real device, event and operator together; installing an app alone is not readiness.

Open Device readiness →

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: assigning the team to an event — Merchant documentation · help.tickettailor.com · Merchant-controlled · checked 2026-09-28
  2. Ticket Tailor: when check-in data synchronizes — Merchant documentation · help.tickettailor.com · Merchant-controlled · checked 2026-09-28