Printed lists are easy to start and hard to coordinate: helpers work from different copies, names are slow to find, and the final count requires manual reconciliation. ArriveList keeps the same narrow name-list workflow in a browser. The organizer pastes the expected display names, saves a private manager link, and shares a separate staff link with trusted helpers.
Prepare only the names needed at the door
Use one display name per line and review the parsed count before creating the event. Blank lines are removed, but duplicate names stay as separate rows because ArriveList does not infer whether two identical names belong to one person. Do not add email addresses, phone numbers, ticket details, notes, or other contact data.
Keep management separate from door check-in
Save the manager link before leaving the recovery screen. It can edit names, rotate staff access, close, reopen, and delete the event. Give helpers only the independently rotatable staff link. Anyone holding that link can see the list and change arrival state while the event is open, so share it only with the intended team.
Search first and mark one row at a time
At the door, keep the Not arrived filter selected and search by the display name the guest gives. Mark the matching row once and let the shared count update. If duplicate names exist, use the organizer's event context rather than asking ArriveList to identify the person; the service does not verify identity or admission rights.
Close and delete the list when the job is done
Close the event when no more door changes should be accepted. Closing blocks staff mutations but keeps the manager's option to reopen. Delete the event when the team no longer needs the names; closed events are scheduled for deletion after 30 days and every event no later than 90 days after creation.