Designing forms that people actually finish
How to design website forms people complete, with fewer fields, visible labels, helpful error messages and a clear confirmation.
Every field on a form is a small request, and people have a limited supply of patience for requests from a business they haven't dealt with yet. The forms that get finished ask for less, explain themselves clearly and forgive mistakes.
A form is often the last step between a visitor and an enquiry, a booking or a sale. It is a frustrating place to lose someone, and an easy place to make improvements.
Ask for less
The quickest way to get more completed forms is to remove fields. For each one, ask two questions. Do we need this to respond? Could we ask it later, once we are talking?
A worked example
Say you are a builder with a quote request form that asks for: first name, last name, email, phone, street address, suburb, postcode, property type, project type, budget, timeframe, how you heard about us, and a description.
That is thirteen fields before anyone has spoken to you. Here is a leaner version:
- Name
- Phone or email
- Suburb
- What you would like done (a text box)
- Photos or plans (optional upload)
Five fields. You can still quote, because the rest comes out naturally in the first phone call. The longer form produced tidier data. The shorter one produces more enquiries, which is the point.
Some other ways to lighten the load:
- One name field. Splitting first and last names is rarely needed.
- Mark optional fields as optional, or remove them. If it is optional, how much do you need it?
- Break long forms into steps. If you truly need many answers, as with a new patient form, show a few at a time with a progress indicator. Start with the easy questions.
Use labels people can see
Each field needs a short, clear label sitting just above it, visible at all times.
The common mistake is putting the label inside the field as pale placeholder text. It looks tidy, and it causes real problems. The label vanishes the moment someone starts typing, so they can't check what the field was for. The pale text is hard to read. And some people mistake it for an answer that is already filled in.
Other layout habits that help:
- One column. Fields stacked vertically are faster to complete than fields side by side, and they work on a phone without rearranging.
- Field size as a hint. A postcode box should be short. A message box should be tall.
- Helper text where needed. If you need a format or a reason, say so beneath the label. "We'll only call about this enquiry" eases a common worry about handing over a phone number.
Write error messages that help
Mistakes will happen. How the form responds decides whether the person fixes it or gives up.
Good error handling follows a few rules:
- Say what is wrong and how to fix it. "Please enter a full email address, including the @ symbol" is useful. "Invalid entry" is not.
- Put the message beside the field it refers to, and highlight the field. A single red line at the top of a long form sends people hunting.
- Keep what they typed. A form that wipes every field after one error is the surest way to lose an enquiry.
- Wait until they have finished a field before complaining. Flashing "invalid email" while someone is halfway through typing it is just rude.
- Be relaxed about formats. Accept phone numbers with or without spaces. Accept capitals in an email address. The site can tidy these up quietly.
Make it easy on a phone
Most forms are filled in with thumbs, so small technical choices matter a great deal.
- The right keyboard. A phone number field should bring up the number pad. An email field should bring up the keyboard with the @ symbol. This is a simple setting in how the form is built, and it is often missed.
- Autofill. Phones can fill in name, email, phone and address in one tap, but only if the fields are set up correctly. Ask your designer to check that it works.
- Big targets. Fields and buttons tall enough to tap accurately, with space between them.
- Fewer dropdowns. Scrolling a long list on a phone is fiddly. For two to four options, use buttons people can tap directly.
Confirm what happened
When someone presses send, they need to know three things: it worked, what happens next, and when.
A good confirmation says something like: "Thanks, we've received your enquiry. We'll call you within one business day. If it's urgent, ring us on" followed by your number.
Back it up with an automatic email saying the same. It reassures the customer and gives them your details for later.
What to avoid is a form that simply clears itself, or shows a tiny line of green text that is easy to miss. People will wonder whether it sent, and some will submit again or go elsewhere.
A test for your own form
Fill in your form on your phone, as a stranger would, and check:
- Can I finish it in under a minute?
- Is every label visible while I type?
- Did the right keyboard appear for phone and email?
- Did autofill offer to help?
- If I make a deliberate mistake, is the message clear and are my other answers kept?
- Is it obvious that the form was sent, and what happens next?
- Did the enquiry actually arrive?
Then count the fields one more time and remove the one you would miss least.