# Event email locale-by-message preview matrix

Copy one row for each language, message and recipient state that your event actually uses. Preview with fictional test data and authorized test addresses only.

| Message and trigger | Recipient state | Locale chosen and source | Approved copy version/reviewer | Event facts source | Subject/preheader | Variables and missing-field behavior | Date/time/zone and currency | CTA/link/attachment language | HTML/plain text/mobile preview | Sender/provider boundary | Rendering and delivery evidence | Decision owner and sign-off |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| [confirmation after registration] | [confirmed] | [locale + where recorded] | [version/person] | [approved record] | [checked] | [test values] | [checked] | [opened] | [checked] | [named] | [reference] | [person/date] |

## State samples to consider

- Confirmed registration or ticket issued
- Payment pending, when your workflow actually has that state
- Waitlisted or application pending, when applicable
- Schedule, venue or access change
- Cancellation or postponement

## Send gate

- [ ] This recipient belongs in the selected message and state.
- [ ] The chosen language has current, approved copy; any fallback is explicit.
- [ ] Dynamic fields, event time and zone, amount and ticket status match the approved source.
- [ ] Subject, preheader, HTML, plain text, alt text and links were previewed.
- [ ] External ticket/checkout pages and attachments were checked or their language limitation is disclosed.
- [ ] Only approved test addresses received the preview; no real attendees were contacted.
- [ ] The sender's rendering and delivery signals are monitored, and the actual send is separately authorized.

This worksheet is a production-review aid, not an instruction to send an email or a guarantee of delivery.