# Post-sale seat move — before/after verification card

Use one card for **one ticket in one event performance**. Enter internal references and seat labels only. Keep attendee names, contact details, live ticket codes, payment data and identity evidence in the authorized ticket system.

## 1. Confirm scope and authority

| Event + performance ref | Order ref (short/internal) | Ticket ref (short/internal) | Request authorized by role | Operator | Exception owner |
| --- | --- | --- | --- | --- | --- |
| __________ | __________ | __________ | __________ | __________ | __________ |

- [ ] Same event and performance; a date, ticket-category or holder change uses its separate approved workflow.
- [ ] Check the provider's eligibility for this order and whether the ticket has already been checked in.
- [ ] Check any house hold, companion place or access requirement before selecting a target.

## 2. Capture seat and ticket state **before** changing it

| Record | Original seat: section / row / number | Target seat: section / row / number | Evidence or observed status |
| --- | --- | --- | --- |
| Live seating map | __________ | __________ | Source: __________ / target: __________ |
| Current order/ticket | __________ | __________ | Ticket status: __________ |
| Gate/usher record | __________ | __________ | Last refreshed: __________ |

- [ ] Target appears available for this performance and ticket category in the authoritative map.
- [ ] The ticket and its current seat are unambiguous. If not, stop and assign the exception owner.

## 3. Apply the provider-supported change, then verify **after**

| Check | Expected result for this provider | Actual result / record checked | Pass or hold / owner |
| --- | --- | --- | --- |
| Order / ticket seat | Target seat shown on correct ticket | __________ | __________ |
| Target seat on live map | Provider's expected assigned status | __________ | __________ |
| Original seat on live map | Provider's expected status; do not assume resale | __________ | __________ |
| Current digital/downloaded ticket | Correct event, performance and target seat | __________ | __________ |
| Attendee report or gate/usher view | Same current seat and ticket status | __________ | __________ |
| Old credential behavior | Check if the provider exposes this; do not assume invalidation | __________ | __________ |

- [ ] No second ticket or cancellation was improvised to work around a missing seat-change function.
- [ ] A mismatch between map, ticket and gate view remains open with a named owner.

## 4. Notify and hand off

| Attendee told which seat/current ticket to use? | Notice owner and channel (no address here) | Front-of-house record updated? | Exception contact briefed? | Closed by/date |
| --- | --- | --- | --- | --- |
| __________ | __________ | __________ | __________ | __________ |

Provider examples only: [Eventbrite](https://support.eventbrite.com/hc/en-us/articles/34864724250002-Change-an-attendee-s-ticket-type-event-or-seat) documents a reserved-seat choice in its organizer ticket-change flow, subject to its prerequisites. [Humanitix](https://help.humanitix.com/en/articles/8914357-how-to-move-an-attendee-to-a-different-seat) says its changed seat appears on the digital ticket and attendee report, but it does not notify the attendee. Check the actual behavior in your provider before closing the case.