Saving Progress in Long Forms: What Actually Works
Letting people leave a long form or application and return without losing what they entered.
Priya Raghunathan
What is at stake
Long applications are rarely completed in one sitting, and losing entered data is the fastest way to lose an applicant.
The playbook
- Save progress automatically as people type
- Offer a resume link or account save
- Warn before session expiry and allow extension
- Explain what has been saved
- Protect saved personal data appropriately
Where it goes wrong
Avoid:
- Losing data on timeout
- Save buttons users must remember
- Resume links with no expiry
- Storing sensitive data longer than needed
The numbers behind it
| Measure | Figure |
|---|---|
| Session limits | timeouts can destroy unsaved work |
| Resume links | let people return without an account |
| Partial data | saved data may contain personal information |
| WCAG | timing limits must be adjustable |
Getting outside help
When to hand it over: Bring in help when application forms have high abandonment.
Where this comes from
- W3C Web Accessibility Initiative — Understanding SC 2.2.1 Timing Adjustable
- GOV.UK Service Manual — Service design
The figures and practices above come from the sources listed.
Working on something like this?
We take on UI & UX Design work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.
