What it is
A focused review of interface and content text against clarity, accuracy, voice-and-tone, and terminology standards, catching problems a visual review misses.
When to use it
During Prototype and Implement, before release and whenever copy changes.
Why (value)
Words carry much of the experience; a copy review catches confusing, off-brand, or inaccurate text that undermines otherwise good design.
How to run it
- Gather the copy in context, not as a spreadsheet alone.
- Review against voice, clarity, and terminology standards.
- Check accuracy, error messages, and edge cases.
- Mark edits with rationale.
- Reconcile with design and legal as needed.
Inputs and outputs
- Inputs: The copy in context and the content standards.
- Outputs: Edited copy and a list of content issues.
Time and effort
Low. Scales with the amount of text.
Evidence and limitations
Produces expert-review judgment about quality and conformance, not direct-user evidence of comprehension; confirm critical wording with readers. See Evidence and limitations.
Tips and pitfalls
- Review copy in its real UI context.
- Do not forget microcopy and error states.
- Keep a terminology source of truth.
Variations
Editorial review, voice-and-tone review, and legal or compliance review.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Plain-language editing — Rewrite content so people can read, understand, and act on it the first time.
- Voice and tone guidelines — Define how the product sounds so content stays consistent and on-brand across contexts.
- Readability analysis — Measure how hard your text is to read and whether it suits your audience's reading level.
