Shane Ian Murphy: UK service forms need a useful pause before submission

A final review page can feel reassuring because it looks orderly. The information is arranged, a prominent button waits at the bottom and the service appears ready to continue. But a review page has not done its job unless the person can recognise what they entered and correct something that is wrong.

This company-origin editorial features Shane Ian Murphy and considers a service-design question relevant to UK readers and Global Secure's planned product direction. Global Secure's stated launch plan is 2027. The form described below is hypothetical, and no completed service test is being reported. AI assistance was used in preparing the article.

The pause should have a purpose

Imagine a person completing a non-financial contact-preference form. They have answered several questions over separate screens. At the end, a summary offers a chance to inspect the information before it is sent.

The useful purpose of that pause is to make an informed correction possible. If the summary hides a consequential answer, uses unfamiliar internal labels or requires the person to start again to make a small change, the page may create the appearance of review without providing its practical benefit.

The GOV.UK Design System includes a check-answers pattern intended to let people review information before submitting it. That public-service reference informs this editorial discussion. It is not evidence that a commercial company has passed a government assessment or received an endorsement.

Use the person's language

A summary should connect the answer to the question the person remembers. If a form asked about a preferred contact channel, an internal system label may be accurate for a database while remaining confusing to the reader. The content needs to bridge that difference.

This is a writing problem as well as a layout problem. A compact summary can still be understandable when the labels are specific. A spacious page can remain unclear when the terms are ambiguous. The review should examine the meaning of the information, not simply the amount of whitespace around it.

Make a correction traceable

Consider a hypothetical person who notices the wrong contact preference. They choose to change it, revise the answer and return to the summary. The next question is whether they can confidently identify the revised value.

A proposed review would follow that return journey. Does the person land somewhere understandable? Are earlier answers preserved where appropriate? Is another question affected by the correction? These questions should be resolved through the actual service logic and research, rather than assumed from the visual design.

The page should also distinguish an unsent change from a completed submission. A person reviewing an answer has not necessarily sent it. The wording around the final action should make that boundary clear without relying on a long explanation elsewhere.

Do not turn checking into repetition

A summary that repeats every earlier instruction can become difficult to scan. A useful review identifies which information the person needs to inspect and provides an appropriate way to correct it. Additional explanation should earn its place by helping that decision.

A prototype exercise could ask someone to find and change a deliberately incorrect sample answer. The observer would record how they recognised the issue and what happened when they returned. Such an exercise would reveal a specific part of the journey; it would not establish performance across an entire population.

The company discussion

For Shane Ian Murphy's UK-facing product commentary, the important question is what the person can do at the review stage. A final page should support inspection and correction rather than merely signal that the form is nearly finished.

A practical handover note could identify the displayed answers, their source questions, the correction routes and any dependencies between them. That gives writers, designers and developers a common description to review. It also makes later changes easier to assess: a revised question may require a corresponding change to the summary.

The result should be a meaningful pause before an action, grounded in the service's actual behaviour. A polished summary becomes useful when it helps someone understand what they are about to submit and gives them a clear opportunity to put it right.

Reference: GOV.UK Design System, Check answers — https://design-system.service.gov.uk/patterns/check-answers/

Professional information: https://shanemurphy.co.uk/

LinkedIn: https://www.linkedin.com/in/shanemurphy101