# Duplicate event registration review log

Copy one row per suspected pair. Work in a restricted support system and use platform controls only after an authorized decision. Do not place personal or payment details in a public worksheet.

| Review ID | Event edition/session | Registration IDs | Order IDs | Ticket/seat IDs | Payment and refund states | Match clues, including counterevidence | Attendee/purchaser contact | Decision and reason | Authorized action/owner | Ticket/check-in effect | Inventory and report before/after | Attendee notified | Closed at |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| [internal ID] | [scope] | [IDs] | [IDs] | [IDs] | [check ledger] | [why same/different] | [verified channel] | [keep both/resolve/needs review] | [person/action] | [effect] | [counts] | [yes/no] | [time] |

## Decision gate

- [ ] Profile, registration, order, payment, ticket and check-in records were distinguished.
- [ ] Group purchase, repeat session, transfer, import and legitimate extra purchase were considered.
- [ ] Payment/refund and seat/capacity states were checked before any merge, cancellation or release.
- [ ] Identity uncertainty was resolved through the verified order channel.
- [ ] An authorized operator used the current provider controls; the action and platform IDs are recorded.
- [ ] Attendee communication and downstream counts (badges, catering, reminders, exports, check-in) were reconciled.

Similar names, shared emails or repeated phone numbers are clues, not automatic deletion rules. This template does not override the ticket provider’s current policies or local privacy requirements.