Several entrances or a busy arrival period can make one paper list a bottleneck. ArriveList lets trusted helpers open the same staff view on their phones. They search the same expected-name list, mark arrival, and see the shared count update without participant accounts or an installed application.
Test the staff link on a second device first
From the manager view, use the QR code or its adjacent Copy staff link action to open check-in on another phone. Confirm that the event title, expected count, and guest rows appear. Keep the manager link off staff devices unless a helper truly needs management authority.
Coordinate the team without inventing staff identities
Helpers may divide entrances or parts of the alphabet, but every action still comes through the same bearer capability. ArriveList records that a name was marked through the staff link; it cannot say which person performed the action. Use ordinary team communication when responsibility matters.
Let concurrent taps converge on one arrived state
If two helpers find and mark the same row at nearly the same time, ArriveList uses version checks so the guest remains simply Arrived rather than creating two arrivals. A device that sees a conflict refreshes the current snapshot. Duplicate display-name rows remain independent and must not be merged.
Rotate staff access if the link spreads
The staff link is a key, not an identity. If it reaches someone outside the intended team, rotate it from the manager view; the old staff link stops working immediately while the manager link stays unchanged. Private manager and staff routes are excluded from search indexing and public analytics, but the team must still handle both links carefully.