# Feature Page Content Brief

Explain a feature's user job, workflow, availability, evidence, limits, prerequisites, privacy implications, alternatives, and appropriate next step.

## Usage note

Complete this brief with current product, support, billing, privacy, security, and accessibility information. Demonstrate only behavior available in the named plan, version, region, and interface. A feature page should help a suitable person understand and evaluate a workflow; it must not imply a result the feature cannot guarantee or conceal significant prerequisites and limits.

## How to use this template

1. Define the user, job, starting state, desired output, and responsibility retained by the user.
2. Confirm product behavior, plan, version, region, prerequisites, formats, limits, and data handling.
3. Map a realistic workflow with examples, errors, recovery, accessibility, and alternatives.
4. Attach appropriate evidence to every benefit or performance claim.
5. Approve an accurate next action and assign updates for product or policy changes.

## Blank template

### User and feature

- **Feature name:** [Approved product term]
- **Plain-language description:** [What it does]
- **Primary user:** [Role and context]
- **User job:** [Progress or task]
- **Starting state:** [Required input or setup]
- **Output:** [What the feature produces]
- **User responsibility:** [Review, decision, configuration, or other]
- **Non-fit case:** [When not to use it]

### Workflow and evidence

- **Step 1:** [Action and expected state]
- **Step 2:** [Action and expected state]
- **Step 3:** [Action and expected state]
- **Plans/regions/versions:** [Availability]
- **Prerequisites and permissions:** [Requirements]
- **Formats and limits:** [File, quota, size, or duration]
- **Data handling source:** [Authoritative policy or documentation]
- **Failure and recovery:** [Likely symptom and next step]
- **Benefit claim and evidence:** [Claim; source]
- **Material limitation:** [What it cannot do]

### Publication checks

- [ ] Plain description is understandable without the feature name.
- [ ] Workflow matches the live approved product.
- [ ] Availability and limits are dated and explicit.
- [ ] Screenshots and examples contain no sensitive data.
- [ ] Data and privacy statements link to authoritative details.
- [ ] Claims match evidence and avoid guarantees.
- [ ] Non-fit users have an appropriate alternative.
- [ ] Call to action states the real commitment.