clarify

Help people understand what happened and what to do next.

On this page 3 sections

Use clarify for vague buttons, confusing form instructions, unhelpful errors, or empty states that leave people stuck. Impeccable reads the interaction and rewrites the text around what someone needs to know at that moment.

Try it

/impeccable clarify the profile form, including its validation and save errors.

Include who uses the flow and anything they tend to misunderstand. Existing product context helps Impeccable choose the right terms and level of detail.

How it works

Impeccable reads the whole interaction and rewrites text by its job:

  • Actions and navigation: name what a control does and use consistent terms.
  • Forms: make labels specific and put requirements where people need them.
  • Errors: explain what failed and how to recover, without inventing a cause.
  • Loading, empty, and success states: explain the current state and the next useful step.
  • Help and confirmations: add necessary context, remove repetition, and make consequences clear.
A dead end
Something went wrong.OK
A clear next step
We couldn’t save your changes. Try again.Try again
Illustrated save error, assuming the interface supports retrying. The message names what failed without inventing a cause, and the button says what it does.

Factual meaning and product terms stay intact. Impeccable asks when an important fact is unclear. Shorter copy helps when it keeps the meaning; a deletion warning may need more explanation than a routine success message.

Check the result

Walk through the flow in its success, error, and empty states. Do the labels match what the controls do? Can someone recover from a problem? Check long names, dynamic values, narrow screens, and accessible names too.

Use typeset if clear wording is hard to read, or onboard if the first-use experience needs a broader rethink.