Event ticket transfer: an organizer's attendee-change workflow
Handle an event ticket transfer with a ticket-level change log, approval checks and a three-ticket example. Keep one usable admission for each place.

An event ticket transfer needs a recorded decision about who may use one existing admission. Identify the ticket, verify the request, complete the provider's supported change and tell the entrance organizer which record now applies. The number of places stays the same.
For a one-date workshop, studio masterclass or small performance, a request might arrive as “I can't come; can my friend use my place?” Use the decision table and change log below to handle that request before guests reach the door. The workshop ticket checklist covers the original sale and event setup.
Identify the change the buyer wants
A spelling correction, an attendee replacement and a move to another event require different checks. Start by asking which person and which ticket the request concerns. An order containing three tickets needs a ticket-level answer; changing the order's contact name could affect all three guests.
| Request | What to establish | Record to check after the action |
|---|---|---|
| Correct a spelling mistake | The attendee remains the same person | Updated name on the intended ticket |
| Replace one attendee | Another person will use that admission | Approved recipient, current access and original access behavior |
| Recover a missing email | The attendee and admission permission remain unchanged | Delivery to the verified existing contact |
| Move to another date | A different event and its capacity are involved | The provider's separate event-change procedure |
| Request money back | A cancellation or refund decision is needed | Admission status and payment outcome separately |
Tixr's name-change documentation says an attendee-name edit retains the same QR code. A full transfer uses a separate feature. Treat each provider's terminology and access behavior as something to verify.
Decide the rules before the first request
Put the transfer conditions alongside the purchase information. State whether substitutions are allowed, who approves them, the request deadline and the contact route. Give a full date, time and time zone when a cutoff could be misunderstood. Set a deadline you can support with someone available to review requests.
Check any ticket conditions that depend on the participant, such as a stated experience requirement or eligibility for a particular admission. A replacement must still meet the event's published conditions. Confirm access arrangements privately with the incoming participant rather than copying another person's personal notes into their record.
Providers and organizers take different approaches. The Hebrew MyVisito organizer guide describes automatic, approval-required and disabled transfer settings. Crafted Studio's workshop terms require advance approval for a registration transfer. Publish the rules that apply to your event.
An operational instruction might read: “For a participant change, contact [organizer] by [full deadline], quoting [order reference] and identifying the individual ticket. Wait for confirmation before asking the replacement participant to travel.” Fill those fields from the approved event record. Keep any financial or cancellation terms in their existing reviewed policy.
Verify the requester and the individual ticket
Find the original order through your provider's management tools. Use its authenticated request process where available. If a message arrives through another channel, verify the request through the contact already associated with the order or another documented method. A forwarded screenshot alone should not authorize a change of recipient.
Confirm the event date, ticket type, individual ticket identifier and intended replacement. If the buyer says “the second ticket,” match that description to a specific record before proceeding. Collect the new attendee's name and only the contact information needed for the supported delivery process. Keep private ticket links and personal information out of a shared planning sheet.
Check whether the ticket has been used, revoked or involved in an unresolved payment issue. Refer unclear cases to the person responsible for the event. A substitution request does not settle a pending payment. Use the manual-payment workflow for that separate investigation.
Record who is handling the request so two organizers do not make competing changes. If the buyer changes their mind while it is being processed, check the current provider state before reversing anything. A message saying “please cancel my request” may arrive after the recipient has accepted it.
Check what happens to access
Before confirming a replacement, establish what your provider does with the original ticket, the new recipient and any order-wide link. A name edit may leave the credential unchanged. Sending a PDF again may leave every earlier copy usable. Neither action proves that the old holder has lost access.
Tixr's transfer guide says its recipient must accept the invitation to complete the transfer; after acceptance, the sender loses access to those tickets. MyVisito documents a flow in which a completed transfer invalidates the previous barcode. Follow the behavior documented for the service and event you actually use.
Ask these questions before offering transfers:
- Does the action affect one ticket or the entire order?
- Is recipient acceptance required, and how is completion shown?
- What can the original ticket and order links still open afterward?
- Can the incoming attendee retrieve their admission independently?
- What happens if the invitation expires, is declined or goes to the wrong address?
If your service offers only a name edit with the same admission code, explain that limitation to the organizer making the decision. Where a secure replacement is required, use a supported method that controls the old access. If no suitable method exists, ask the provider how to handle the request before promising the change. A spreadsheet entry cannot change what the scanner accepts.
Keep a ticket-level change log
Use the provider's current record as the authority for admission. A small working log can track the request and unfinished checks. Restrict access and record references rather than copying usable codes.
| Field | Example for a fictional request |
|---|---|
| Event and order | Printmaking evening, 18 November 2026; DEMO-428 |
| Individual ticket | T-02 of three admissions |
| Request | Replace Alex with Sam |
| Requester verified | Original buyer contacted through the recorded route |
| Decision and owner | Approved by event organizer, 16 November at 14:10 |
| Provider action | Supported transfer started; acceptance still pending |
| Completion evidence | Fill after checking the provider's completed state |
| Access check | Record the documented old/new access behavior |
| Entrance handover | Updated record checked by the entrance organizer |
“Approved,” “invitation sent” and “completed” may be different stages. Keep the actual provider state beside your task status. If the invitation is still pending, send a pending update rather than a completion message. Check that later processing has finished before closing the row.
Keep purchaser and attendee records separate. A participant replacement does not by itself change who bought the order or the original payment. Tixr's name-change guidance, for example, says its original confirmation and receipt remain unchanged. Handle any requested billing change through the provider's appropriate process.
Work through one change in a three-ticket order
Suppose a fictional workshop has twenty issued admissions and four unsold places, within a participant limit of twenty-four. Order DEMO-428 contains three of those twenty admissions: T-01 for the buyer, T-02 for Alex and T-03 for Jo. Only Alex needs a replacement.
The organizer verifies the buyer, identifies T-02 and approves Sam under the event's stated rules. The supported transfer begins. While recipient acceptance is pending in this example, the organizer leaves the request open and checks which holder the provider currently recognizes. They do not issue Sam an additional complimentary ticket to finish the task faster.
After the provider reports completion, the organizer verifies Sam's access and the old access behavior. T-01 and T-03 remain assigned as before. The workshop still has twenty issued admissions and four unsold places: 20 + 4 = 24. The order still covers three people. A replacement has created no extra place to sell and no extra participant to admit.
If the provider instead requires cancellation and a new issue, confirm its inventory, payment and delivery effects before using that route. Do not assume the released place will stay reserved for the replacement while public sales remain open. Keep the case unresolved until the supported process preserves the intended allocation.
Send the right update and hand over the change
For a pending request, say what remains: “The change for ticket [reference] is approved. [Recipient] still needs to complete [provider step]. We will confirm when the transfer is complete.” Use this only when approval and that pending step are both recorded.
For completion, tell the new attendee where their verified private access was delivered, which event it covers and how to get help. Tell the original requester exactly what the provider confirms about their old access. Avoid saying an old code is invalid unless you have verified that behavior. Use the confirmation email library for the event details that accompany the update.
Before doors open, check completed changes in the admission tool and give unresolved cases to the designated organizer. Retain the earlier decision in the restricted record, without displaying both names as two admissions. The QR check-in checklist covers entrance exceptions after that handover.
For an event you hope to manage with Skedful, contact the team with the date, country and attendee-change requirements. Confirm ticketing availability and the supported handling of that change before advertising transfers to buyers. Rehearse one individual-ticket replacement through the provider's supported test process, including what each participant can open afterward.
About this article
Skedful is the publisher and corrections contact. Our editorial checklist covers product availability, source dates, worked examples and the limits of each claim.
About this articleWorked examples and sample calculations describe hypothetical scenarios. When an article cites research or customer results, follow the source for its context and limits.
Found an error? Send us the article link and the passage that needs a correction.
Report an error to SkedfulReminders come with every Skedful plan, on a schedule you set once. PricingSkedful vs Fresha vs Booksy