A practical guide

Write a form error message a customer can act on

Use a fictional repair-enquiry example and an error-copy worksheet to write clear messages from confirmed rules, without inventing delivery promises.

“Something went wrong” tells a customer that a task stopped. It does not tell them whether to change an answer, wait, or check whether their request arrived. A useful error message helps someone take the next sensible step without making promises the website cannot support.

This is a writing exercise for a small-business website team. Content Charlie does not provide an enquiry form or a form-building service. Use the page-content brief to record the real rules and evidence before writing messages for your own service.

Find out what actually happened

Ask the person responsible for the form to distinguish three situations:

  • An answer needs correcting. The form knows a required item is missing or an entered value falls outside an accepted rule.
  • The service is unavailable. The customer cannot solve the problem by changing a valid answer.
  • The outcome is uncertain. The browser did not receive a reliable confirmation, but that alone does not prove that the request failed.

These situations need different words. In particular, “Your request was not sent” is unsafe copy when the team cannot determine whether it arrived. The GOV.UK Design System distinguishes validation errors from service problems; its patterns are useful examples, rather than a requirement to copy government branding.

Work through a fictional repair enquiry

Imagine a furniture workshop has a form asking for an email address, an item description and a preferred appointment date. The workshop and form are fictional. Assume its developer has confirmed the rules below; these are not suggested business policies for every repair service.

Confirmed rule or state Weak message More useful draft
Email is required Invalid input Enter an email address so we can reply
The chosen date precedes today Date error Choose today or a future date
The description is required Required field Describe the item and the repair you need
The form service is unavailable Check your answers The enquiry form is unavailable. Try again later

Each replacement names the relevant thing or action. None blames the customer. The service-unavailable draft still needs the actual fallback added if one exists: a verified telephone number, a monitored email address or a service-status page. Do not invent a contact route to make the message feel complete.

The date draft is appropriate only because the fictional workshop permits same-day enquiries. If the real service requires two working days’ notice, that rule needs to be explained before submission and reflected accurately in the error. Copy cannot repair an undefined booking policy.

Write the missing confirmation separately

Now imagine the browser times out after submission. Before writing “Try again”, ask whether repeating the action could create two requests, bookings or payments. A safe next step depends on what the service can actually check.

For a service with a reliable request-status screen, a draft might direct the customer there before repeating the action. For a service without one, the team needs an honest support process. Do not claim the enquiry is saved, promise a reply time or tell someone they have paid unless the underlying system can establish it.

Record this as an unresolved operational question in the brief when necessary. A clearly identified gap is more useful than confident text that hides uncertainty.

Make the correction easy to find

An editor should supply the words for both the field-level message and any summary at the top of the form. Keep their meaning consistent. A summary such as “Check the date” should take the reader to the date answer, rather than leave them to search the page.

The GOV.UK pattern uses linked summaries and messages beside affected answers. W3C’s explanation of WCAG 2.2 requires automatically detected input errors to identify the item and describe the problem in text; colour alone is not enough. Implementing focus, field associations and assistive-technology behaviour requires development and testing as well as copy. Clear wording by itself is not a claim of full accessibility compliance.

Add an error-copy sheet to the brief

For each message, record:

  1. The field or service state that triggers it.
  2. The rule, its owner and where it was confirmed.
  3. What the customer can do next.
  4. What entered information is retained, if anything.
  5. The exact message and summary wording.
  6. A safe test case and the person responsible for checking it.

Use fictional entries in a development environment. Ask someone unfamiliar with the form to explain the next action in their own words, then check the implemented keyboard and screen-reader experience appropriately. Do not claim that this article has tested your service.

The finished handover should let a writer, developer and service owner agree on the same outcome. When the form cannot offer a clear next step, resolve the workflow before polishing the sentence.

Sources

  1. GOV.UK Design System: error message
  2. GOV.UK Design System: error summary
  3. W3C WAI: understanding error identification