Someone bought a ticket, then their calendar staged a coup. Now they want their colleague to go instead, and you are the one being asked to sort out the ticket transfer and the name change on the ticket before the doors open. Handled badly, this eats your inbox and hands the door team a guest list that no longer matches reality. Handled well, a transfer event ticket request is a thirty second self-serve job that never touches you at all. This guide covers how to change a name on a ticket cleanly, when to allow it, and how to keep check-in accurate when the names on your list start moving around.
The short version: let attendees transfer their own tickets, reissue a fresh QR code to the new person, void the old one, and set sensible limits. Do that and the headache disappears. Do it with a spreadsheet and a prayer, and you will be manually reissuing tickets at 11pm the night before.
Why ticket transfers and name changes matter more than they sound
A name on a ticket is not decoration. For a lot of events it is the thing that gets someone through the door, onto the delegate list, and into the catering count. When the name is wrong, three things break at once: the check-in scan flags a mismatch, your printed badge says the wrong thing, and your attendance data quietly lies to you. Multiply that by fifty last minute swaps at a conference and your "who actually turned up" report becomes fiction.
People swap tickets for entirely normal reasons. A client sends a deputy. A couple splits up (awkward, but not your problem to referee). A team buys ten seats in March and only decides who is going in September. None of these are edge cases. They are Tuesday. The question is never whether attendees will want to change the name on a ticket, it is whether your platform lets them do it without a support ticket.
If changing a name on a ticket requires an email to you, you have not sold a ticket, you have adopted a pen pal.
The safe way to change a name on a ticket
The gold standard for a ticket transfer is simple: issue a brand new ticket with a new QR code to the recipient, and void the original at the same moment. This matters because it closes the loophole where two people show up holding what looks like the same ticket. If you only edit the name and keep the same barcode, a forwarded screenshot of the old ticket can still scan. A fresh code means the old one is dead the instant the transfer completes.
Most modern platforms now build the whole flow around the attendee, not the organiser. On Eventbrite, for example, an attendee can edit the order to put the ticket under someone else's name and email, and the new person gets prompted to claim it (Eventbrite Help Centre). Universe sends a confirmation email to the recipient, who confirms their own details and claims the ticket (Universe Help Centre). The pattern is the same everywhere good: the buyer starts the transfer, the recipient confirms, and you never lift a finger.
One thing worth flagging to your buyers up front: on several platforms, once a ticket has been transferred the order becomes non-refundable, and the action cannot be undone (Tickera). That is reasonable, but only if you told people before they clicked, not after.
Set the rules before you need them
Self-serve transfers are brilliant right up until someone tries to flip a ticket eight times or swaps the name during the entry queue. A few guardrails keep the freedom from becoming chaos:
A cut-off time. Close transfers 24 to 48 hours before doors so your final guest list, badges and catering numbers actually settle. Live name changes at the scanner are how queues form.
A transfer limit. Two or three transfers per ticket covers every honest use case and shuts down casual resale flipping (Tickera).
A clear policy line. One sentence at checkout: transfers allowed until 48 hours before, new attendee gets a new ticket, transferred orders are non-refundable. Said once, up front, it prevents a hundred "but nobody told me" emails.
Tier awareness. If a ticket includes a workshop, a dinner or a VIP perk, make sure the transfer carries those add-ons with it so the new attendee inherits the whole booking, not just the entry.
Self-serve versus manual: what it actually costs you
The gap between letting attendees handle their own transfers and doing it yourself is not subtle. Here is the same swap, two ways.
| What happens | Manual reissue by organiser | Self-serve transfer |
|---|---|---|
| Who does the work | You, from your inbox | The attendee, from their phone |
| Time per swap | Several minutes each, at your desk | Around 30 seconds, unattended |
| Old QR code | Often still valid (risk of double scan) | Automatically voided |
| Check-in list | Updated only if you remember | Updated instantly and automatically |
| Badge and catering count | Manually corrected, easy to miss | Reflects the real attendee |
| Your evening before the event | Answering swap requests | Yours |
The manual column is not a straw man. It is what happens by default on any tool where name changes route through the organiser. Every one of those swaps is a small tax on your attention, and it always lands in the busiest week.
The dream: your attendee changes the name on their own ticket from their phone while you get on with literally anything else. Credit: Luis Cortes / Unsplash
Keep check-in honest when names move
A transfer is only truly finished when the door knows about it. This is where a lot of setups quietly fall apart: the name changes in one system, but the check-in app is working from a list exported last Tuesday. The new attendee arrives, scans, and gets a red cross for a ticket they legitimately hold.
The fix is not a clever workaround, it is architecture. When registration, ticketing and check-in all read from one live record, a transfer completed at breakfast is already reflected at the door by lunch. The new person's QR works, the old one does not, and the badge prints their name because the badge is drawing from the same source of truth. If you want the mechanics of a scanner that stays in sync with last minute changes, our guide to QR check-in walks through how live syncing keeps the queue moving.
A platform like eventcloud handles transfers this way by design: self-serve name changes, a fresh QR to the recipient, the original retired, and check-in reading the same record throughout, so your attendance figures stay true even after a flurry of swaps. Because the pricing is a flat fee per user rather than a cut of every ticket, reissuing a ticket is not a billing event either, which removes the other quiet reason some platforms make transfers awkward.
When you should just say no
Honesty check: not every event needs a transfer policy at all. A free 30 person community meetup can wave people in and never look at a name. If nobody is checking identity and there is no catering headcount riding on it, building a formal transfer flow is effort you will never get back. Equally, some ticket types genuinely should be locked: heavily discounted comps, press passes tied to a named journalist, or anything where the name is the point. For those, disable transfers on that tier specifically and allow them everywhere else.
For everything in between, which is most paid, seated or badged events, self-serve transfers with a cut-off and a limit are the setting that saves you the most grief. Turn them on before you launch, write the one sentence policy, and let your attendees sort their own lives out.
If you would rather your check-in list correct itself every time a name changes instead of you correcting it by hand, take a look at how eventcloud keeps registration, tickets and the door on one live record.
