Two forms collecting identical information can convert very differently depending on layout, labelling, and error handling. A single column, labels that stay visible, and errors that appear beside the field are the changes that matter most, and none of them requires removing a field.

One column, always

The most consistently useful layout rule for forms.

Multiple columns force the eye to move sideways and create ambiguity about the order fields should be completed in. A single column has one path through it, which is faster to complete and considerably better on a phone where a two-column layout either shrinks or wraps unpredictably.

The exceptions are genuinely paired fields such as first and last name, or a postal code beside a city, where the relationship is obvious. Everything else stacks.

Labels above fields, and kept

Two decisions here and both are commonly got wrong.

Position. Labels above the field are read faster than labels beside it, and they work at any screen width without the label being squeezed.

Persistence. Placeholder text inside a field disappears as soon as someone types, which means anyone interrupted mid-form loses the label. It also fails for people using screen readers and it is frequently too low-contrast to read.

Using placeholders instead of labels is a design trend that costs completions. Use both if you like, with the placeholder giving a format example rather than replacing the label.

Say which fields are optional, not which are required

Most forms mark required fields with an asterisk, which means the majority of fields carry a symbol and the marking conveys little.

Marking the optional ones instead is clearer, because there are fewer of them, and it signals that you have kept the required list short. It also invites people to skip rather than to abandon when they reach something they would rather not answer.

Errors, which is where forms lose people

The mobile details that matter

Most enquiry forms are completed on a phone, and a few technical settings change the experience substantially.

Correct input types bring up the right keyboard: a numeric pad for phone numbers, an email keyboard with the at symbol available. A phone field showing a full alphabetic keyboard is a small daily annoyance that costs completions in aggregate.

Autofill support, through standard field naming, lets the browser complete name, email, and phone in one tap. This is one of the largest single improvements available and it is invisible in the design.

Field height and spacing also matter more than on a desktop, since a mistyped entry caused by a cramped tap target is a genuine frustration.

The submit button

Say what happens rather than what the mechanism is.

Send my enquiry, request a quote, or book an inspection all describe an outcome. Submit describes a form action, which is what the visitor least cares about.

The button should also disable itself after being pressed, with visible feedback, since a form with no response to the first press produces duplicate submissions and an anxious visitor.

What happens after

A confirmation that is more than the word thanks.

Say what happens next, when they will hear from you, and give a phone number for anything urgent. That is the moment the visitor is most receptive and most uncertain, and a bare confirmation wastes it.

Sending an automatic acknowledgement by email does the same job, and it also gives the person a record with your contact details in it.

The test worth running

Complete your own form on a phone, on mobile data, as a stranger would, and deliberately make a mistake partway through.

Watch whether the keyboard is right, whether autofill works, whether the error is clear, whether your entries survive, and whether the confirmation says anything useful. Then confirm the message actually arrived, including in the junk folder of the receiving address.

That covers the whole path in about three minutes, and it is the check that catches the silent failures. Which fields to ask for in the first place is a separate question, and the shorter answer is nearly always the better one, as set out in reducing the number of decisions on a page.

Frequently asked questions

Should forms be one column or two?

One, in almost every case. Multiple columns create ambiguity about completion order and behave unpredictably on a phone. Only genuinely paired fields such as first and last name belong side by side.

Where should form labels go?

Above the field, and they should stay visible. Placeholder text inside a field disappears when someone types, which loses the label for anyone interrupted mid-form.

Should I mark required or optional fields?

Mark the optional ones. There are fewer of them, so the marking carries more information, and it signals that the required list has been kept short.

How should form errors be handled?

Beside the field rather than in a summary, specific about what to change, preserving everything already entered, and checked as the person moves between fields rather than only at submission.

What mobile settings matter most?

Correct input types so the right keyboard appears, and standard field naming so autofill can complete name, email, and phone in one tap. Both are invisible in the design.

What should the submit button say?

What happens, such as send my enquiry or book an inspection. Submit describes a form action, which is the part the visitor cares least about.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Form on your site that people start and abandon?

We rebuild the layout, labels, and error handling, then test the whole path on a phone including whether the message actually arrives.

Start a Conversation