# Event ticket fraud: control and handoff worksheet

Copy this worksheet into your private event operations space. Enter references to authorized systems, not card numbers, full ticket codes, passwords, identity documents or attendee details. The rows below are prompts, not automatic fraud findings.

**Event:** [name]  
**Approved public event page:** [URL]  
**Approved ticket seller and help path:** [URL / contact]  
**Version / owner / review date:** [date, time zone, person]

| Stage | Risk or signal to review | Authoritative record | Owner who can decide | Safe immediate action | Buyer / staff message owner | How to verify closure |
| --- | --- | --- | --- | --- | --- | --- |
| Public link | Copycat listing or changed destination | Approved link register and event page | [name / role] | Preserve URL; check with seller; correct approved channels | [role] | Confirm each published link and affected buyer contact |
| Purchase | Unusual payment or order pattern | Payment and ticket order records | [name / role] | Review through provider's approved process; avoid assumptions | [role] | Record reviewed order state and buyer outcome |
| Offers | Code used outside intended audience | Offer rule and redemption record | [name / role] | Review scope; pause or change only with authority | [role] | Confirm new rule across all channels and orders affected |
| Change / transfer | Old and new entitlement conflict | Ticket status and transfer history | [name / role] | Hold uncertain entitlement for review | [role] | Confirm exactly one current admission right |
| Entrance | Unknown or repeated code | Current ticket and check-in history | [name / role] | Pause second entry; refer to staffed help point | [role] | Record gate decision and current ticket state |
| Dispute | Payment dispute or buyer complaint | Provider case, order and communications | [name / role] | Preserve relevant records in authorized system | [role] | Close provider case and customer follow-up |

## Handoff rehearsal

1. A buyer reports a ticket offer on an unfamiliar site. Who checks the URL and purchase route?
2. An order reference appears in a complaint, but the gate sees a repeated code. Who reviews payment, ticket status and the previous scan separately?
3. What can the gate do while that review is pending, and where does the guest wait?
4. Who sends the factual buyer message, and who checks that public links are corrected?
5. Which record proves each decision was closed? Record the owner and next review date.

Keep detailed cases in access-controlled systems. Review this worksheet before on-sale, before doors and after a material incident.