A guest forwards a ticket to a friend, but the registration desk still has the original name. The queue is growing and neither person knows whether forwarding the email was enough. This is a process problem worth resolving before event day.
Begin with the actual ticket terms and the capabilities of your booking platform. Some events permit transfers through a defined workflow; others restrict them. Do not promise a name change that the organiser or ticket system cannot honour.
Define the route before requests arrive
If transfers are permitted, tell guests where to request one, what information is necessary, when requests close and how confirmation arrives. Explain what happens to the original ticket or barcode. Use the platform’s supported transfer process rather than improvising a second valid entry.
Keep the request with the booking record and restrict access to people who need it. A public spreadsheet of guest names and email addresses is not a suitable transfer desk.
Rehearse an ordinary exception
Try an invented scenario during the staff briefing: a transfer was approved after yesterday’s printed list, and the new guest arrives with confirmation. Which current record can the desk consult? Who can resolve a mismatch? Where can the guest wait without holding up every arrival?
Give staff a route to a decision rather than telling them to accept every screenshot. Screenshots can be outdated or copied. Verification should follow the organiser’s documented process, with only the personal information genuinely needed.
When the request deadline passes, communicate any remaining assistance route. If changes cannot be made at the door, say so clearly in advance instead of leaving the check-in team to invent a rule.
After the event, review where transfers failed: unclear instructions, delayed confirmations or stale lists. Those observations give the next registration setup a concrete improvement to make, without turning a straightforward guest change into unnecessary paperwork.