Map the journey
List entry, required fields, help, attachments, consent, submission, error, success and follow-up message.
GUIDE / PROTOCOL
Audit a form from start to finish
A form works when a person understands the request, can correct errors and knows what was submitted.
Direct answer
What should be checked beyond the submit button?
Walk through every form state with keyboard and mobile. Check the need for each field, clear labels, errors, server-side validation, data retention and the confirmation actually received.
01 / Review method
Review method
Test input
Try valid, empty, long, international and invalid values; review labels, examples, tab order and preservation of entered data.
Check server response
Inspect server-side validation, targeted errors, duplicates, network failures, repeated submissions and timeouts.
Check what follows
Verify acknowledgement, functional recipient, stated timeline, stored data and the ability to resume without needless re-entry.
02 / Evidence to keep
Evidence to keep
Case matrix
Inputs, expected state, displayed message and observed outcome for each case.
Journey capture
Labels, help, focus, errors, summary and confirmation on mobile and keyboard.
Redacted technical log
Response status, timestamp and test identifier without real personal information.
Decision
Barrier, task impact, fix, owner and retest.
AFTER THE REVIEW
Decide from the evidence
An error clears previously entered fields
Treat data loss as a journey failure. Preserve non-sensitive values, focus the error summary and retest correction.
Success appears without verifiable receipt
Do not mark the journey complete. Check the server response and actual processing with fictitious data, then fix the message.
03 / FAQ
Frequently asked questions
Is JavaScript validation enough?
No. It helps immediate feedback, but validation is also required on the server.
Should required fields be identified?
Yes, clearly before input and in error messages.
What after an error?
Explain the fix, connect the message to its field and retain other values where possible.
How to test without sensitive data?
Use fictitious cases and check minimized logs.
04 / Official references