Provide a review and summary before submission
Aliases: review step · submission summary · check your answers
What it is
Facts collected across steps need to be laid out as a readable summary before they are submitted. Asking the user to synthesise “what I just filled in” inside their head parks the whole flow’s memory load on the last second. Review before submit is a chance to replace recall with recognition: every fact that will go out is on one screen, wrong ones editable, right ones checkable.
It lists collected data, not a restatement of the single action “you are about to pay.” Restating the action answers “what am I pressing”; the summary answers “which facts am I sending.” A decent checkout has both; they are not the same surface.
Why it happens
What people do with a just-walked sequence is reconstruction, not playback. Any interruption, any comparison among options, lets detail be crowded out or rewritten. A summary freezes that interval of input into a list, so checking becomes “is this item this?” rather than “what did I type?”
If the summary cannot be edited, or changing one item restarts the flow, the second half of the reduction fails: people skip the check to avoid redo, or they check and cannot fix. Each “Change” should return to that section without wiping later steps. A screenshot of the form as the summary fails for screen-reader and magnification users; the reduction then only happens for people who can see the picture.
Studying it
For legal, financial, and user-controlled data changes, conformance looks for a review mechanism before submit. More useful observation: how many people jump from the summary to edit, whether other unsubmitted sections survive the edit, how often dwell time on the summary is too short to have read it.
Independent variables: a dedicated review step, per-section edit, text versus image summary. Dependent variables: pre-submit edit rate, abandonment caused by inability to patch locally, errors caught on the summary screen.
Where it stops holding
A one-step form of two or three fields already has the values in view; do not insert an extra summary page. A live preview that already is the full state (a list beside a configurator) can serve, if it covers every fact that will be submitted and can be edited from the preview. A summary that omits hidden fields (a pre-ticked subscription, tax, a delivery window) manufactures false confidence, which is worse than no summary.
Applying it
- Before final submit, give a text summary grouped by section, with a change link back to that step; after the change, return to the summary, not to the start.
- Amounts, dates, and consents must appear in the summary, not only in earlier steps.
- Verify: from the summary screen alone, the user (or someone who did not fill the form) can name every fact that will be submitted and change one of them without restarting the flow. If they cannot name or cannot change, review did not happen. Then hear the whole summary with a screen reader to confirm it is not an image without an alternative.