# International event registration field-purpose audit

Event / edition: __________   Form owner: __________   Review date: __________

First decide whether a mailing address is needed at all. Use fictional records for tests.

| Field / task | Why needed | Whose data | Required? | Label and accepted script | Downstream view | Correction path | Owner |
|---|---|---|---|---|---|---|---|
| Attendee display name for ticket/badge | | | | | | | |
| Name required by a specific verification process | | | | | | | |
| Payer or invoice name | | | | | | | |
| Delivery address for a physical item | | | | | | | |
| Venue address shown to attendees | | Not attendee input | | Official local form | Event page / map | | |

## Acceptance scenarios

| Fictional scenario | Form accepted? | Confirmation correct? | Ticket/badge correct? | Export/shipping correct? | Issue owner and retest |
|---|---|---|---|---|---|
| One-part or long name | | | | | |
| Multiple family names or different order | | | | | |
| Non-Latin name and address | | | | | |
| Address without street number or postal code | | | | | |
| Postal code with letters, spaces or hyphens | | | | | |

Do not place real personal data in a shared test worksheet. Requirements depend on the actual ticketing, shipping and invoicing tasks; this is a design aid, not a universal address schema.