A form is where interest meets effort
A visitor can like your offer and still leave at the form. Typing is work, and every question raises a small doubt: why do they need this, and what will they do with it? Good form design reduces the effort and answers the doubt.
There is no perfect form that suits every business. What follows are widely used principles, and you should check them against your own results rather than treat them as rules.
Ask for less
The most useful question for each field is: what would we lose if we did not ask for this now? If the honest answer is “nothing important”, remove it.
A newsletter signup may need only an email address. An enquiry form may need a name, a way to reply and a message. A request for a quote may reasonably need more, because you cannot price the job without details. The right number of fields depends on the offer and on how much the visitor already trusts you.
Fewer fields tend to feel easier, but that is not automatic. A very short form that attracts unqualified enquiries can create more work than a slightly longer one that asks a useful screening question. If you are unsure, you can compare versions with A/B testing, provided you have enough visitors; otherwise, make one change at a time and watch what happens.
Asking for less is also good practice for privacy. The idea of data minimisation says you should collect only what you need for a stated purpose. Rules about personal data vary by country and change over time, so check what applies to you. This is general information, not legal advice.
Phone numbers are a good example. If you will only ever reply by email, do not demand a number. If you do ask, say why, and mark it optional when it truly is.
Write labels that stay visible
Every field needs a clear label, placed where people can see it while typing. A label that exists only as grey hint text inside the box disappears as soon as someone starts typing, which makes it hard to check or correct an answer. It can also be hard to read for people with low vision or poor contrast.
Keep labels short and plain: “Email address”, not “Please enter your electronic mail address here”. Where a field needs explanation, add a short hint beneath it, such as the format you expect or a reason you ask. The craft of writing this kind of text is covered under microcopy.
Mark optional fields as optional, or mark the required ones. Be consistent, so visitors do not have to guess.
Put the fields in a natural order
Order questions the way a person would expect them. Start with easy, familiar ones, such as name and email, and leave anything sensitive or effortful until later. A single column is generally easier to follow than fields scattered across the page, especially on a phone.
Group related fields, and use headings if the form is long. If the form is genuinely long, splitting it into short steps with a visible indicator of progress can feel less daunting, although it is worth checking that it does not hide problems or make editing harder.
Match the field to the answer
Using the right type of field saves effort:
- Email fields that bring up the right keyboard on a phone.
- Numeric keypads for phone numbers.
- Drop-down menus only when the list is short; a very long list is slow to scroll through.
- Radio buttons or checkboxes when there are a few clear choices.
- A text box big enough for a message, when you actually want a message.
Avoid forcing a particular format, for instance rejecting phone numbers that contain spaces. Accept what people naturally type and tidy it up behind the scenes.
Make errors helpful
Errors are inevitable, and how you handle them decides whether someone gives up. Good error messages:
- Appear next to the field that has a problem, not only at the top of the page.
- Say what went wrong and how to fix it: “Please enter an email address like name@example.com”, not “Invalid input”.
- Do not blame the visitor.
- Keep what the person has already typed, so they do not have to start again.
- Do not rely on colour alone. Add text or an icon so people who cannot distinguish colours still notice the problem. Good colour contrast helps too.
If possible, check simple things such as an obviously mistyped email as the visitor moves through the form, but avoid scolding them before they have finished typing.
Make the button honest
The button should say what happens when it is pressed: “Get the guide”, “Send enquiry” or “Book a call”. A generic “Submit” tells the visitor nothing. This is the same principle as a good call to action in any other setting.
Place a short line near the button about what happens next, for example how soon you will reply, and link to your privacy notice. If you will send marketing messages, ask for permission clearly and separately rather than hiding it. Consent rules for email and SMS differ between countries, so check the requirements that apply to you.
Think about accessibility and mobile use
Many people complete forms on a phone, one-handed. Buttons and fields should be large enough to tap accurately, and the keyboard should not hide the field being typed in. People who use screen readers or keyboards rely on proper labels and a logical tab order. These are covered in more depth by guides on accessible marketing.
Test the form yourself
Fill it in on a phone, then deliberately make mistakes. Check that submissions reach the right inbox, that the confirmation appears, and that a thank you page or message tells the visitor what happens next. A form that fails quietly can lose leads for weeks before anyone notices, which is why form checks belong on any pre-launch list.
Review with real behaviour
If your analytics can show how many people start a form and how many finish, look for the field where people stop. That tells you where to simplify first. Treat any pattern as a clue, not a verdict, and change one thing at a time so you can tell what made the difference.