Skip to content
19 10240119 Tools

Copyable template

Microcopy Review Template

Copy a microcopy review template with screen context, line checks, rewrite variants, accessibility notes, and boundary reminders.

Updated 2026-06-09

Use this microcopy review template when buttons, errors, empty states, helper text, or confirmation messages need a quick screen-level tone check. It is not a full accessibility, legal, brand, localization, or usability review.

Copyable Template

# Microcopy Review Template

Product area: [Screen, flow, or feature]
Audience: [Who sees this copy]
Target tone: [plain / calm / friendly / direct]
Reviewer: [Name]
Review date: [Date]

Screen context:
- What is the user trying to do? [Goal]
- What happened immediately before this copy appears? [State]
- What should the user do next? [Action]
- What risk exists if the copy is misunderstood? [Low / medium / high]

| Surface | Current copy | User state | Tone issue | Rewrite option | Final decision |
| --- | --- | --- | --- | --- | --- |
| Button | [Current label] | [Ready to act] | [Too vague / fine] | [Clear action label] | [Use / revise] |
| Error | [Current error] | [Task blocked] | [Blame / pressure / jargon] | [Calm next action] | [Use / revise] |
| Empty state | [Current text] | [No data yet] | [No next step] | [Explain first step] | [Use / revise] |
| Helper text | [Current helper] | [Needs guidance] | [Too long / unclear] | [Short instruction] | [Use / revise] |

Tone checks:
- [ ] The line names the next action or state.
- [ ] The line avoids blame, shame, or dramatic urgency.
- [ ] The line avoids private details in visible UI text.
- [ ] The line works beside the real button, field, or screen.
- [ ] The line is short enough for the component without hiding meaning.
- [ ] The final copy has an owner for product, brand, accessibility, or legal review when needed.

Rewrite notes:
- Short version: [Option]
- Calmer version: [Option]
- More direct version: [Option]
- Final version: [Chosen copy]

Boundary reminders:
- Do not use this template as legal, accessibility, compliance, medical, financial, or safety approval.
- For high-stakes account, billing, privacy, or regulated screens, route the copy through the proper review process.
- Check localization and truncation separately when the product supports multiple languages.

Useful variants

  • Payment error review with a calm next action
  • Empty state review for a new dashboard
  • Button label review before a design handoff
  • Support notification review where privacy details must stay out of visible copy
  • Mobile form helper text review where space is tight

How to adapt it

Replace bracketed text with your details, remove sections you do not need, and keep the final version short enough for the reader to act on.

FAQ

Can this work for product teams?

Yes. It is useful for designers, product managers, engineers, marketers, and support teams reviewing small UI text changes.

What should the reviewer add?

Add the screen context, exact line, user state, risk, rewrite options, and final owner.