Return visitors to review after a targeted correction

What to change

Ask for a targeted editing route that makes the relevant question easy to change and returns to a refreshed review when dependencies allow.

A worked example

Illustrative example

Editing an email address returns to the review with the corrected address visible. Editing location additionally requests a valid service choice for that location.

How to check the result

Accept when changes follow the shortest sensible route and the final review reflects every correction and relevant dependency.

A mistake to avoid

Automatically skipping dependent questions can make editing fast while leaving an internally inconsistent request ready to submit.

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 recordReach the review screen with fictional details and change one simple answer such as a contact number. Count the unnecessary screens required to return.Change an answer that affects later choices, such as location. Ask the supplier to show which dependent questions must be revisited and how this is explained.Check every Change link using a screen reader. Its accessible description should identify the answer being edited, even when several links share visible wording.

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.