# Event-ticket reminder: schedule and recipient preflight (English)

Use this with controlled test records. Keep names, email addresses and ticket codes in the sending system, not this sheet.

- **Event / occurrence:** ____________________
- **Local start / time zone:** ____________________
- **Provider and reminder mode:** automatic reminder / scheduled broadcast / other: __________
- **Message owner / exception owner:** ____________________

| Check | Expected state | Observed state / next action |
| --- | --- | --- |
| Site-wide switch, if this provider has one | | |
| Event-level switch, if this provider has one | | |
| Relative trigger or fixed send time and time zone | | |
| Shared versus event-specific template | | |
| Correct subject, event facts, ticket or join route, support link | | |
| Buyer with one ticket | | |
| Buyer with several tickets; separate holder email if stored | | |
| Another date or occurrence excluded where needed | | |
| Cancelled or otherwise ineligible record handled as provider specifies | | |
| Test email renders on phone; actual recipient preview/count checked separately | | |
| Saved schedule and later send status recorded | | |

If the event time, venue or audience changes, reopen the saved reminder. Check whether the provider recalculates pending messages; do not assume a test email proves who will receive the live message.

- **Schedule checked by / date:** ____________________
- **Unresolved mismatch / owner:** ____________________