# Event reminder automation QA matrix (English)

Copy this sheet for one event edition and one flow version. Use case references; keep email addresses and other personal data in the authorized sending system. Example rows describe test states, not real attendees or an instruction to send live email.

Event / edition: ____   Flow version or ID: ____   Provider: ____
Approved event date, time zone and source: ____   Sending owner: ____
Test environment or narrowly scoped live segment approved by: ____

## Path inventory

| Message ID and purpose | Entry trigger or campaign | Eligible recipient state | Exclusion / stop rule | Re-entry rule confirmed in provider? | Owner |
|---|---|---|---|---|---|
| ARRIVAL-1 / practical arrival reminder | Registration state becomes confirmed | Valid registrant for this edition | Cancelled or no longer eligible | Unknown until checked | ____ |
| ARRIVAL-1 / same purpose | Date-based automation | Valid registrant for this edition | Already sent ARRIVAL-1 | Unknown until checked | ____ |
| ____ | ____ | ____ | ____ | ____ | ____ |

If two rows can reach one contact with the same message, identify which route owns the send before release.

## Controlled case matrix

| Case reference | Starting state and test action | Expected message ID(s) | Expected count and suppression | Actual flow path / send evidence | Result PASS / FAIL / UNVERIFIED | Exception and owner |
|---|---|---|---|---|---|---|
| T1 | New eligible registration | ____ | ____ | ____ | ____ | ____ |
| T2 | Already registered before flow activation | ____ | ____ | ____ | ____ | ____ |
| T3 | Cancelled before reminder | ____ | ____ | ____ | ____ | ____ |
| T4 | Previously completed flow; attempted re-entry | ____ | ____ | ____ | ____ | ____ |
| T5 | Event date changed before reminder | ____ | ____ | ____ | ____ | ____ |
| T6 | Eligible for both automated flow and separate campaign | ____ | ____ | ____ | ____ | ____ |

Record the provider's message or campaign identifier, not just the subject line. Mark unavailable history as UNVERIFIED. Do not use real attendees solely to probe a flow.

## Exception, retest and release

Flow or audience change made: ____   Owner: ____   Time and zone: ____
Affected cases reset to a clean controlled state: ____   Retest evidence: ____
Copy / links reviewed separately for the final version: ____
Decision: GO / HOLD   Decision owner: ____   Decision time and zone: ____
Observation window and responsible person after activation: ____
If a trigger, exclusion, audience or event date changes, identify which cases must be repeated: ____