Practical guide

Give the door team responsibilities, not a shared owner password

Last materially reviewed 2026-09-28

Quick answerAssign scanning, exception handling and administration separately, then verify each person can do their actual job.
What to know

Start with the decisions

List what each position may decide: ordinary admission, a disputed ticket, a changed booking or an on-site sale. These are not necessarily the same role. An operator who can scan valid tickets may not need access to all customer information or account settings. Avoid using the owner’s login as a universal shortcut. It makes accountability and later removal harder, even when the team is small and people trust one another.

What to know

Connect the role to an event

Ticket Tailor documents event access for check-in users. For your own process, record which event and date each person needs, who grants that access and when it should end. A volunteer returning from a previous event may still need a new assignment. Check the actual screen available to that person rather than assuming their name in a team list proves readiness. Keep credentials out of briefing sheets and shared chat messages.

What to know

Give exceptions a destination

Name one reachable person or desk for cases the scanner operator should not decide. Explain how to pass the minimum necessary information without announcing private attendee details to a queue. The handoff should say what has been checked and what remains uncertain. A broad instruction to “ask someone” leaves the volunteer to improvise. The organizer remains responsible for the event’s admission rules and the authority delegated to each role.

What to know

A fictional role rehearsal

A volunteer can see Saturday’s event but not Sunday’s. That may be correct, not an error. Ask them to locate the intended event, find a fictional ticket and identify the exception route. Separately, have the supervisor verify the administrative tasks they own. Save a role-by-task result, not a list of passwords. Before the next event, review changed people and dates instead of copying the prior briefing unchanged.

Continue when useful

Next: Volunteer briefing

Put the event scope, ordinary action and exception route before background information.

Open Volunteer briefing →

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: printing a doorlist — Merchant documentation · help.tickettailor.com · Merchant-controlled · checked 2026-09-28