How to move attendees to another event time slot

Define exactly what is moving

Download the source-and-destination verification card (Markdown, English)

Identify the event, original slot, requested slot and number of entitlements affected. Is the request for one attendee, a booking group or everyone in the source slot? Determine the scope before using a transfer control. Name the role that approves the move and the role that verifies its outcome.

Record the current ticket state

Open the authoritative order or attendee record. Note ticket type, current slot, active or void status, and prior check-in. Eventbrite's organizer change route excludes checked-in orders and has other eligibility conditions. Tito's option-change route applies to a ticket booked into an option. Record your system's state; a new slot on the public page does not prove this ticket can move.[1][3]

Check destination capacity

Compare the destination's approved limit with issued places, active holds and the proposed move count. Capture the source count too. Interfaces may permit over-limit moves: Tito warns an organizer but allows one; Quicket says its bulk transfer proceeds regardless of destination ticket capacity. Neither behavior approves more capacity. Resolve a shortfall with the capacity owner first.[2][3]

Choose the provider-supported route

Use the platform's supported path. Eventbrite documents an organizer route to change ticket type, event or seat, subject to payment, availability and order conditions. Quicket moves everyone in a source slot, not one selected attendee. Tito moves one person to another option within the same session. Confirm scope and prerequisites before changing a live record.[1][2][3]

Stop on unresolved conditions

Pause if the destination is full, the ticket checked in or voided, the order ineligible, or the platform cannot express the move. Tito's organizer control can enter a full or clashing option; Eventbrite restricts sold-out and checked-in cases. A permissive control does not override the event plan. Give unresolved cases an owner instead of improvising another ticket.[1][3]

Make the change and retain evidence

Perform the approved operation once and retain its order, batch or audit reference. Check any attendee-facing explanation against the real change. Quicket includes its transfer reason in a confirmation email. Tito offers an email choice and records the move in the order and both options. Inspect the provider's confirmation before repeating a delayed step.[2][3]

Reconcile both slot counts

Refresh both slot reports. Record the number moved, source places released or retained, destination places used, holds and discrepancies. Tito releases the previous option's place after an individual move. Quicket says its bulk transfer does not automatically resolve capacity differences. Use your platform's definitions; neither synchronized balances nor extra capacity can be assumed.[2][3]

Verify the ticket and admission record

Inspect the current entitlement and admission view for the new slot. Verify ticket reference or replacement, prior check-in and accepted door credential. Tito keeps the ticket reference and check-ins on an option move; Eventbrite makes its changed ticket accessible in the attendee's account. Neither sets a universal QR-code rule. Escalate mismatches before approving entry.[1][3]

Confirm communication and handoff

Confirm what the attendee and any booker were told, including the new slot and arrival details. Quicket emails its entered reason; Tito has provider-specific resend and calendar behavior. A saved transfer does not prove delivery. Give admission staff the verified change and open exceptions, then close the card with report time, owner and next action.[2][3]