Form design · Completion & conversion
Form Completion and Conversion
Why people abandon forms, and the specific changes that get them to the submit button.
Every form has a funnel: opened, started, finished. Most teams only ever see the finished count and wonder where everyone went. This section is about the middle of that funnel: the fields that cause drop-off, the reassurance that keeps people going, and the measurable changes (fewer required fields, progress indicators, smart defaults, inline validation) that raise completion rates.
Who this is for
- Anyone whose form matters to revenue or operations
- Teams comparing completion before and after digitizing
- Optimizers who want the highest-leverage fixes first
Key things to know
Every field costs completions
Ask only what you will act on. "Nice to know" fields are paid for in abandoned forms.
Validate inline, not at submit
Errors revealed at the end feel like a punishment. Errors caught at the field feel like help.
Show progress on long forms
People finish what they can see the end of. Steps and progress bars exist for this reason.
Quick answers
What is a good form completion rate?
Context matters, but for an intake or request form reached by motivated users, 70-90% of starters should finish. Below 50% almost always means fixable friction: too many fields, mobile problems, or requests for information people do not have on hand.
What single change most improves completion?
Cutting fields. Halving the number of questions routinely lifts completion more than any visual redesign. Second place: making the form genuinely pleasant on a phone.