# Empty State Copy Sheet

Explain why a product area has no content, whether anything is wrong, what the user can do next, and which prerequisites or alternatives apply.

## Usage note

Identify why the state is empty before writing. First use, cleared filters, missing permission, delayed processing, offline data, and system failure require different messages and actions.

## How to use this template

1. Inventory every first-use, no-result, filtered, permission, delayed, offline, and failure cause.
2. Record the system truth, likely user concern, available action, and information boundary.
3. Draft a concise heading, explanation, specific action, and alternative for each distinct cause.
4. Test transitions, errors, accessibility, localization, and the destination of every action.
5. Instrument state causes and maintain copy with product and permission changes.

## Blank template

### Empty-state diagnosis

- **Surface and state ID:** [Enter]
- **Trigger or cause:** [Enter]
- **State type:** [First use / No result / Filtered / Denied / Delayed / Offline / Error]
- **What the system knows:** [Enter]
- **What remains unknown:** [Enter]
- **Likely user concern:** [Describe]
- **Data or privacy boundary:** [Describe]
- **Owner:** [Product/content]

### Copy card

- **Heading:** [State or outcome]
- **Explanation:** [Why empty and whether anything is wrong]
- **Primary action:** [Exact label and destination]
- **Expected result:** [What happens next]
- **Secondary or alternative action:** [Enter]
- **Help or support path:** [Enter]
- **Illustration purpose:** [Informative / Decorative / None]
- **Variable and fallback:** [Enter]

### Cause-specific checks

- [ ] First-use copy explains value without requiring unrelated setup.
- [ ] No-result states preserve input and offer clear adjustment.
- [ ] Filtered states show that content may exist outside current filters.
- [ ] Permission states avoid revealing hidden item details.
- [ ] Delayed and offline states distinguish waiting from data loss.
- [ ] Failure states offer tested retry, recovery, or support.
- **Irreversible action nearby:** [Describe or None]
- **Recovery verified:** [Name/version/date]

### QA and measurement

- **Transition tested:** [Populated to empty / Empty to populated]
- **Device and assistive technology:** [Enter]
- **Long translation result:** [Enter]
- **Action destination result:** [Enter]
- **Analytics state identifier:** [Enter]
- **Observed confusion:** [Enter or None]
- **Approved version:** [Enter]
- **Update trigger:** [Permission/filter/storage/import/change]