# Event email delivery — editable send-and-monitor matrix

Event/date: [ ]  Version: [ ]  Communications owner: [ ]  Mail administrator: [ ]  Ticketing/support fallback: [ ]

| Stream | Purpose and affected audience/source | Sending service and From domain | SPF/DKIM/alignment check owner | Current template and critical link | Marketing/operational classification reviewed by | Test mailbox and result | Provider acceptance/delivery/bounce/complaint observation | Failure owner and fallback |
|---|---|---|---|---|---|---|---|---|
| Registration confirmation | | | | | | | | |
| Venue/program change | | | | | | | | |
| Arrival/access information | | | | | | | | |
| Optional promotion | | | | | | | | |

## Pre-send gates

- [ ] Audience comes from current permitted source; suppression and unsubscribe rules checked.
- [ ] Real From/reply identity and current sender authentication reviewed by mail administrator.
- [ ] Date, timezone, venue, access instructions and links agree with current event page.
- [ ] Representative message sent through the actual stream; mobile and mailbox samples checked.
- [ ] Critical link opens and ticket/registration path works without a private attendee link.
- [ ] Bounce/complaint notification path and review owner active.
- [ ] Essential information also available from a current public page or staffed support route.

## After-send observation

| Time | Stream | Intended recipients | Provider accepted | Reported delivery | Bounce/complaint | Unresolved cases | Action, owner and next review |
|---|---|---|---|---|---|---|---|
| | | | | | | | |

Provider acceptance does not prove inbox placement or reading. Store personal recipient details only in an access-controlled operational system, not this shareable worksheet.
