Forms with too many fields cost more than the data is worth

Aug 29
3 min read

Updated: 4 days ago

Introduction

The enquiry form asks for a name, email address, telephone number, company, job title, company size, budget range, project timescale, how they heard about the business, and a message. Each field was added by somebody who genuinely needed that information.

Nobody was asked what each one costs. Every additional field reduces the number of people who finish the form, and the information is worth having only if the enquiry happens at all. Forms grow for a structural reason: the cost is invisible and spread across strangers, while the benefit is visible and belongs to a specific person who asked for the field.

1. Forms with too many fields are a trade, not an improvement

Make the exchange explicit.

Each field buys information and costs completions. Any discussion about adding one should therefore include the question of what proportion of enquiries the business is prepared to lose in exchange for the information.

2. Ask only what you need to reply

The rule that settles most arguments.

A name, a way to contact them, and some idea of what they want. Everything else can be established in the reply, at a point where the person is already engaged and answering costs them almost nothing.

3. Make everything else optional

A compromise that mostly works.

Optional fields are completed by people who feel like it and skipped by people who do not, so you keep some of the data without losing the enquiry. Required fields have no such middle ground: the visitor either supplies the answer or abandons the form entirely.

4. Question every internal request for a field

Where the growth comes from.

Somebody wants source attribution, somebody else wants budget qualification, and each request is reasonable in isolation. Asking who actually reads the field, and what decision they make differently as a result, removes several of them immediately and without argument.

5. Watch the fields that people abandon on

Data settles it.

Form analytics show where people stop typing and leave. The results are frequently surprising, and one particular field is usually responsible for a disproportionate share of the abandonment, which makes the first fix obvious.

6. Split long forms into steps if you truly need the data

The alternative to cutting.

Where the information is genuinely necessary, several short steps complete better than one long page, particularly with visible progress. This applies to applications and bookings rather than enquiry forms.

7. Do not ask for what you already know

An irritation that reads as incompetence.

Returning customers, and anybody arriving from an email you sent, should not be asked for details already on file. Pre-filling what you have shortens the form and demonstrates that records exist.

8. Remember data protection applies

Collecting less is also safer.

Everything gathered must have a lawful basis, be stored appropriately and be kept only as long as it is needed. Fields nobody uses are a liability rather than merely clutter.

9. Test the shortened version properly

Prove it rather than assuming it.

Run the reduced form for a period and compare completions and, more importantly, the quality of the enquiries. Businesses usually find they receive noticeably more enquiries with no fall in usefulness, because the qualifying information arrives in the reply instead.

Count the fields on your own form today. Most businesses that do this discover two or three nobody has looked at in years, and removing those is a change with no cost and an immediate effect.

Conclusion

Treat every field as a trade between information gained and enquiries lost.

Ask only what you need in order to reply, make everything else optional so it costs nothing, challenge each internal request by asking who uses the data, look at form analytics to find the field causing abandonment, split genuinely long forms into steps, pre-fill anything you already know, remember that unnecessary data is a protection liability, and test the shorter version against both completions and enquiry quality.