Allow visitors to review without sending accidentally

What to change

Require a clearly identified final action that is distinct from editing, expanding details and navigating away from review.

A worked example

Illustrative example

A visitor opens an address detail panel to check spelling. The request remains unsent until they deliberately activate Send enquiry beneath the completed review.

How to check the result

Accept when review interactions remain reversible and the final sending action is recognisable before activation with mouse, touch and keyboard.

A mistake to avoid

Styling an entire review card as a submit target makes innocent clicks on its content unexpectedly consequential.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordOn the review screen, inspect every interactive area and label. Ask a colleague to point out which single action sends the request before they activate anything.Use keyboard navigation to expand details and follow Change links. Confirm these controls never trigger the final submit action through shared or overlapping targets.Ask the supplier to demonstrate the final action in a test environment. Compare the button's wording, pending state and eventual confirmation with the actual operation.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.