Design & UX

Form Design That Gets Completed: Fewer Fields, Better Leads

Forms are where interest turns into a lead, and where many visitors give up. Learn how to choose fields, structure layouts, handle errors and follow up so more forms get completed.

Illustration of a short, clean web form with clear labels, a friendly inline error message and a large submit button

Your form is the moment of truth. Everything else on the page, from the headline to the testimonials, has worked to bring the visitor to this point. Then they meet a wall of fields, a CAPTCHA they cannot solve, or an error message that does not explain what went wrong, and they leave. Following form design best practices is one of the quickest, cheapest ways to get more and better leads from the traffic you already have. This article covers which fields to ask for, how to lay them out, how to handle errors, and what should happen after the click.

Why forms fail

Forms are abandoned for predictable reasons:

  • Too much effort: too many fields, or fields that require looking something up
  • Uncertainty: unclear purpose, unclear next step, or worry about what happens to their data
  • Friction: wrong keyboards on mobile, strict formatting rules, tiny tap targets
  • Errors: validation that rejects valid input or explains problems badly
  • Distrust: no visible privacy information, or a form that looks out of place on the page

Each of these is a design problem with a design solution.

Choose fields ruthlessly

Start by listing every field and asking three questions:

  1. Do we need this to respond well? If not, remove it.
  2. Do we need it now? If it can be gathered in the follow-up conversation, move it there.
  3. Can we infer it? Location from postal code, company from email domain, or source from campaign parameters.

Fields that often survive this test on a lead form:

  • Name
  • One contact method (email or phone; let people choose where possible)
  • One qualifying question, such as project type, product interest or timeframe
  • An optional message

Fields that often do not: job title, company size, fax number, full postal address, "How did you hear about us?" when analytics already tracks the source, and separate fields for things that could be one.

Fewer fields usually means more submissions. But quality matters too. A single well-chosen qualifying question can help sales prioritize without discouraging serious buyers.

Form design best practices for layout and labelling

Use a single column

Single-column layouts are easier to scan and complete, especially on mobile. Side-by-side fields work for closely related short inputs, such as city and postal code, but avoid complex grids.

Labels above fields

Place visible labels above inputs. They remain visible while typing, work well on narrow screens and support translation into longer languages. Avoid using placeholder text as the only label; it disappears when typing starts and fails accessibility requirements, as covered in our guide to accessible web design and WCAG.

Mark what is optional

Most fields on a good form should be required, so marking the few optional ones with "(optional)" is usually clearer than scattering asterisks.

Longer forms benefit from logical sections with short headings, such as "Your details", "Your project" and "Timing". Grouping reduces perceived effort.

Make input easy

Small technical details make a big difference, particularly on mobile:

Detail What to do Why it helps
Input types Use email, tel, number, url appropriately Brings up the right keyboard
Autocomplete Set autocomplete attributes for name, email, phone and address Lets browsers fill known details
Formatting Accept spaces, dashes and country codes in phone numbers Users type numbers many ways
Local input Accept local digits and characters in multilingual sites Avoids rejecting valid input
Choices Use radio buttons for a few options, selects or search for many Reduces taps and reading
Tap targets Make inputs, checkboxes and buttons generously sized Prevents mis-taps
Defaults Pre-select sensible defaults where honest Saves effort

On bilingual and right-to-left sites, fields like email and phone often need left-to-right input direction even on an RTL page, and validation must accept Arabic-Indic or Persian digits. Our article on RTL website design covers this in detail.

Validation and error messages

Validation should help, not punish.

  1. Validate inline, after the user leaves a field, not on every keystroke and not only after submission.
  2. Explain the fix: "Enter an email address like name@company.com" is better than "Invalid input".
  3. Place errors next to the field and summarize them at the top of the form when submitting, with links to each problem.
  4. Never clear the form after an error. Losing everything is a common reason people give up.
  5. Be liberal in what you accept: trim spaces, normalize formats on the server, and accept reasonable variations.
  6. Do not rely on colour alone to show an error; use text and an icon.

Client-side validation improves experience, but all input must also be validated and sanitized on the server for security.

Key takeaway: Ask only for what you need now, make each field easy to complete on a phone, and treat errors as moments to help. Most form improvements are small, inexpensive changes with a direct effect on leads.

Single-step or multi-step?

For short contact forms, keep everything on one page. For longer processes, such as detailed quote requests, applications or onboarding, multi-step forms can help:

  • Start with easy, low-commitment questions.
  • Show progress clearly, with the number of steps.
  • Use earlier answers to skip irrelevant questions later.
  • Save progress so people can return, where appropriate.
  • Allow going back without losing data.

Trust and privacy at the point of submission

People hesitate when they are unsure what will happen to their information. Near the submit button:

  • State briefly how you will use the information, and link to your privacy policy.
  • Keep marketing consent separate and unticked by default, in line with anti-spam laws such as Canada's CASL. Get professional advice for your specific obligations.
  • Use a specific button label: "Request my quote" or "Book a call", not "Submit".
  • Tell people what happens next and when.

Measuring form performance

You cannot improve what you do not measure. Beyond counting submissions, track:

  • Form starts versus completions, to see how many people begin but do not finish
  • Field-level drop-off, which shows the exact question where people give up
  • Validation errors by field, which often reveal overly strict rules
  • Completion by device, since mobile problems are common and easy to miss
  • Lead quality, judged by sales, so that shorter forms do not simply produce more unqualified enquiries

Review these after any change to the form, and keep a short log of what you changed and why.

Spam protection that does not hurt real users

Spam is real, but heavy-handed challenges cost legitimate leads. Start with measures users never see: honeypot fields, minimum time-to-submit checks, server-side rate limiting and content filtering. Add a visible challenge only if needed, and choose a low-friction option. Our article on CAPTCHA alternatives covers the options.

After the submit button

The experience after submission affects conversion quality as much as the form itself:

  1. Show a clear on-page confirmation with next steps.
  2. Send a confirmation email summarizing what was submitted.
  3. Route the lead to the right person automatically, and respond quickly.
  4. Track the submission as a conversion, with source information preserved.
  5. Monitor deliverability so form notifications do not land in spam folders.

A form that submits silently, or a lead that waits days for a reply, wastes all the effort upstream.

Next steps

If your forms get plenty of views but too few submissions, a focused review usually finds quick wins. DigiVort's UI/UX design team designs and builds forms that are accessible, mobile-friendly and connected properly to your CRM and analytics. Tell us what you are working on through the project wizard.

Frequently asked questions

How many fields should a contact form have?

There is no universal number, but every field should justify itself. Many lead forms work well with a name, one contact method and a short message or qualifying question. If sales genuinely needs more detail to respond, ask for it, but consider collecting it later in the conversation.

Are multi-step forms better than single-page forms?

Multi-step forms can work well for longer processes such as quotes or applications, because each step feels manageable and early answers can tailor later questions. For short forms, splitting into steps just adds clicks. Use steps when the form is genuinely long or branches.

Should we use placeholder text instead of labels?

No. Placeholders disappear when users start typing, which hurts memory and accessibility, and they are often low contrast. Use visible labels above fields and reserve placeholders for short format examples, if at all.

How do we stop spam without hurting real users?

Start with invisible measures such as honeypot fields, time-based checks and server-side rate limiting. Add a challenge only when needed, and prefer low-friction options over puzzles. Always validate and sanitize input on the server regardless of client-side checks.

What should happen after someone submits a form?

Show a clear confirmation on the page, send a confirmation email that summarizes what they submitted, and explain what will happen next and roughly when. Internally, route the submission to the right person quickly and track it as a conversion.