# Confirmation Message Checklist

Confirm what happened, what did not happen, what changes next, whether the action can be reversed, what evidence exists, and what the user must do.

## Usage note

Show success only after the system has reached the stated state. Distinguish received, processing, scheduled, sent, paid, approved, and complete; those words are not interchangeable.

## How to use this template

1. Define the exact backend or product event that permits each completion claim.
2. Record the user-facing outcome, object, timing, evidence, next action, and reversal rules.
3. Draft distinct received, processing, partial, complete, and failed communication states.
4. Test accessibility, privacy, duplicate, refresh, delayed, and cross-channel behavior.
5. Verify the released message against system truth and monitor support confusion.

## Blank template

### Outcome truth

- **Action and object:** [Enter]
- **Trigger event:** [Enter]
- **State:** [Received / Processing / Scheduled / Sent / Complete / Partial]
- **What is proven:** [Enter]
- **What is not yet proven:** [Enter]
- **Relevant reference:** [Safe identifier]
- **Timing or next event:** [Enter]
- **Product owner:** [Name/team]

### Message

- **Heading:** [Precise outcome]
- **Supporting detail:** [Object, date, recipient, amount where appropriate]
- **Next action:** [User / Organization / None]
- **Expected timing:** [Range/time zone]
- **Status location:** [Enter]
- **Reversal or change path:** [Enter or unavailable]
- **Support and reference:** [Enter]
- **Privacy-limited display:** [Describe]

### State coverage

- [ ] Received and completed states are not conflated.
- [ ] Partial success identifies completed and failed parts.
- [ ] Delayed processing gives a status and recovery path.
- [ ] Duplicate submission does not create an inaccurate second success.
- [ ] Email or notification failure does not change the underlying outcome.
- [ ] Refresh and return visits show the current state.
- **Irreversible consequence:** [Enter]
- **Expiration or cancellation:** [Enter]

### QA and release

- **Build and test account:** [Enter]
- **Cross-channel comparison:** [Product/email/history]
- **Keyboard and announcement result:** [Enter]
- **Narrow and localized display:** [Enter]
- **Links and account context:** [Enter]
- **Approved wording and version:** [Enter]
- **Support feedback signal:** [Enter]
- **Update trigger:** [Behavior, policy, channel]