# Event registration export-and-handoff brief

Copy a row for every recipient and purpose. Fill this out in an access-controlled location; do not put real attendee data in this blank template.

| Event edition/session | Recipient and role | Decision or task | Row unit (order/ticket/person/check-in) | Included status/filter | Required fields and reason | Excluded sensitive fields | Source and export operator | Snapshot time and zone | Row count/version | Approved delivery route | Print/download/forward scope | Refresh/exception owner | Reconciliation evidence | Return/deletion owner |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| [event] | [team] | [task] | [one unit] | [rules] | [minimum set] | [list] | [system/person] | [time] | [count/version] | [restricted route] | [permissions] | [person] | [source total] | [person/policy] |

## Example view decisions

- Door: enough to admit the correct ticket and refer exceptions; avoid prices and marketing preferences.
- Catering: counts by agreed service choice where possible; share named restrictions only with the staff who need to act.
- Finance: order and payment references for reconciliation, rather than a volunteer guest list.
- Report: totals by relevant status, ticket type and session, without unnecessary personal fields.

## Before release

- [ ] The row unit and event edition are explicit.
- [ ] Pending, refunded, cancelled, complimentary, transferred and checked-in status treatment is documented.
- [ ] Names, accented characters, IDs and dates survive opening in the destination tool.
- [ ] Row count and status totals match the source at the recorded snapshot time.
- [ ] Recipient can access only the approved view and knows when it becomes stale.
- [ ] Refresh, exception handling, print collection and retention owners are assigned.

This operational worksheet does not replace platform instructions or local privacy review.