Form design: forms that get filled in, versus forms that get abandoned

Forms get abandoned partway through for a small number of recurring, entirely fixable reasons. Almost none of them are about the business asking for information it genuinely needs. They are about how that request is designed: how many input fields appear at once, whether an unexplained field creates hesitation, and what happens when a user enters something into the form incorrectly.

An enquiry form is arguably the single highest-stakes piece of design on a commercial website. It is the exact point where a visit either becomes a lead or does not. And forms like this are routinely under-designed relative to how much depends on them.

Field count: ask only for what the next step actually needs, one input field at a time

Every additional input field on a form is an additional small cost to the user filling it in. Each field has to earn its place against that cost, and the size of the form itself becomes part of that cost. A first enquiry form needs enough information to start a conversation — name, contact detail, a short description of what’s needed — entered into a small number of fields. It rarely needs the level of detail a business would eventually want for a full quote. That detail can be gathered in the phone call or email that follows, once a visitor has already committed to the conversation.

A form with fifteen fields, several of which duplicate information gatherable later, filters out visitors at the exact moment a business wants the fewest barriers in place. That is precisely backwards from what most businesses actually want their form to do.

Explain unusual or sensitive fields — field size and what a user must enter — or expect hesitation

A field asking for something a visitor doesn’t expect to need — a business registration number on a general enquiry form, a budget range before any conversation has happened — creates a moment of hesitation if it isn’t explained. A short line of text under the field, stating plainly why it’s being asked and what it’s used for, resolves that hesitation in a sentence, rather than losing the visitor to unexplained suspicion.

Errors: identified in the text field itself, not by colour alone or a click away

A form that rejects a submission with a single generic message at the top — “there was an error” — forces a user to hunt back through every field to find what’s wrong. A meaningful share simply give up rather than hunt. Errors should be shown next to the specific field that caused them, in plain text describing what’s needed, not by colour alone. This is also one of the specific checks covered in an accessibility self-assessment. A colour-only error indicator fails for colour-blind visitors and for anyone using a screen reader, in exactly the same way it frustrates everyone else. It’s a usability fault with an accessibility dimension, not an accessibility fault in isolation.

Labels that stay in view, not placeholder text — a form design decision that vanishes too easily

A common pattern puts a field’s label inside the field as placeholder text, sized to look like real content. That disappears the moment someone starts typing. A visitor who gets distracted partway through, or returns to check a field, then sees an unlabelled box with no way to confirm what it was asking for. A persistent, visible label above or beside the field costs nothing, and removes that entire failure mode.

What actually gets abandoned before completion, in order of frequency

Fault	Effect
Too many fields for a first-contact form	Visitors leave before finishing, or never start
Unexplained required fields	Hesitation, sometimes abandonment, at the specific field
Errors shown only at the top of the form	Visitors can’t locate what needs fixing and give up
Placeholder text used instead of a real label	Confusion when a field is revisited partway through
No confirmation the form actually submitted	Visitors resubmit, don’t hear back, or assume it failed silently

Confirmation matters as much as submission

A form that submits successfully but shows no clear confirmation leaves a visitor unsure whether it worked. That uncertainty produces two bad outcomes. A visitor gives up and calls a competitor instead, or a visitor submits a second time, creating duplicate enquiries a business then has to sort through. A simple, clear confirmation message or page, stating what happens next and roughly when to expect a reply, closes the loop the form opened.

Where forms sit relative to buttons and calls to action

A form is, in a sense, an extended version of the same decision covered on buttons and calls to action: a visitor deciding whether to act. Everything that makes a button worth a click — clarity about what happens next, minimal hesitation, no competing choices — applies to a form as well, just spread across more input fields and more steps than a single button click. That is exactly why a form has more places for that clarity to break down, and why the submit button at the end of a form deserves the same attention as any other call-to-action button.

What to test on your own form

Fill in and click submit on your own enquiry form, from a phone, as if you were a stranger who knew nothing about the business. Note every point of hesitation — a field you weren’t sure how to answer or enter text into, an error message that didn’t make sense, uncertainty about whether the click actually sent it. Each one of those moments is a visitor lost, multiplied across everyone who never mentions it, and every one is fixable without asking the business to collect any less of the information it genuinely needs.

Multi-step forms, and when breaking a form up actually helps

For a form that genuinely needs more information than a first-contact enquiry — a detailed quote request, a booking with several options — a multi-step form that breaks the fields into two or three short steps, with a visible progress indicator, can outperform one long single-page form. Each individual step in a multi-step form feels shorter and more achievable than a full page of fields all at once. This only helps if the steps are genuinely short and the progress indicator is honest about how many remain to view. A multi-step form that turns out to have eight steps once someone has already started is a worse experience than one long form stated plainly up front.

What happens after submission matters as much as the form itself

A form’s job doesn’t end at submission. What a business actually does with an enquiry in the following minutes and hours — an automatic acknowledgement email, a fast personal reply, a clear statement of when to expect a response — shapes whether a visitor’s decision to fill in the form was, in hindsight, worth their time. A beautifully designed form that leads to silence for three days undoes most of the goodwill the design itself earned. That is a reminder that form design and response process are genuinely connected, even though one is a design decision and the other is closer to an operational one.

Spam and required-field validation shouldn’t punish real visitors

Anti-spam measures — a honeypot field, a required checkbox, rate limiting on submissions — are a legitimate and necessary part of a working contact form. But they need to be invisible to a genuine visitor, rather than adding friction of their own. A CAPTCHA that’s difficult to read, or a required field validated so strictly that a real, valid entry gets rejected, solves a spam problem by creating a real-visitor problem in its place. It’s worth checking that any anti-spam measure on a form has actually been tested against a real, honest submission, rather than only against the bots it’s meant to stop.