The cost of every extra required field

Somebody in a meeting says it would be useful to know company size. Nobody objects, because it would be useful. A dropdown appears on the form, marked required, and the meeting moves on.

The cost of that decision is never measured, because the people it affects leave without saying anything. The benefit is never measured either, because nobody checks whether the column is used.

Six months later the form has eleven fields, four of which nobody has ever filtered on, and the enquiry rate is lower than it was without anyone knowing why.

This is not an argument for collecting nothing. It is an argument for making the trade explicitly, once per field, instead of never.

The intuitive model is that each field costs a few seconds. The real cost is larger and less linear, because a form is evaluated before it is filled.

A visitor scans the form and decides whether the exchange is worth it. That judgement happens in about a second and is based on apparent length more than actual effort. A form that looks long is declined before a single character is typed.

Required fields carry extra weight in that judgement because they remove the option of skipping. A long form of optional fields reads as a conversation; the same form with everything marked required reads as an interrogation.

And the fields near the end are the expensive ones, since a person who abandons at field nine has already invested effort you have now wasted for both of you.

Abandonment is not random. It is weighted towards specific groups, and they are usually the ones you would least like to lose.

Mobile users abandon more, because typing is harder. People in a hurry abandon more, and urgency often correlates with intent to buy. People uncomfortable sharing details abandon more, which includes anyone at a company with a policy about it.

Meanwhile the segment that patiently completes every field includes a healthy proportion of people who are researching rather than buying, and everyone submitting automated junk, who never abandons anything.

So a long form does not simply reduce volume. It selects, and not in your favour.

Before any field is marked required, three questions are worth answering honestly.

Can you do your job without it? If a colleague could answer this enquiry without knowing the value, it is not required, whatever anyone says. Will the answer be true? A field people do not want to answer generates fabricated values, which is worse than a blank. And is now the right time to ask, or could it wait until you are in conversation?

A surprising number of fields fail all three. Budget on a first enquiry is the classic: people guess, the guess is wrong, and you would have asked anyway on the call.

A field that fails any one of the three should be optional or removed.

Some of what you would ask for is already arriving without a question.

The page they submitted from tells you what they were reading. The campaign parameters tell you which source and campaign brought them. The referrer tells you where they came from, and the timing tells you how long they spent.

Between them, those cover a good portion of what a qualification field would tell you, without adding a single input. A person submitting from your enterprise pricing page after arriving from a comparison article is qualified by context.

Every field you can replace with something captured automatically is a pure win: better data, because it is observed rather than self-reported, and no cost at the point of conversion.

The choice is not between asking now and never knowing. Most information can be collected after the first contact, and it is usually more accurate then.

A reply that says happy to help, roughly what size is the project, gets an honest answer from someone already in conversation. The same question on a cold form gets a guess or an abandonment.

This also reframes what the form is for. It is not a data collection exercise, it is the beginning of a conversation, and it needs only enough to start one and be able to respond.

For most businesses that is a contact method and a sentence about what they want.

Where a field is genuinely needed but only sometimes, ask conditionally rather than universally.

A form that reveals two extra fields only when someone selects a particular enquiry type keeps the default short while collecting what is needed for the case that requires it.

The trap is doing this badly. Fields that appear and disappear as the visitor changes their mind, or a form that grows visibly as they complete it, produce a worse experience than simply asking. Reveal once, keep it stable, and never make the form appear to lengthen as a reward for progress.

Used carefully, it is the best of both, and it is available in essentially every form builder.

A common defence of long forms is that they deter automated junk. It is half true and mostly beside the point.

Length does reduce some low-effort automated submission, but the modern varieties handle multi-field forms without difficulty, and the ones that cannot are trivially caught by a honeypot and a timing check that no human ever notices.

Using form length as spam defence charges every genuine visitor for a problem that has purpose-built solutions costing nothing.

If spam is the concern, address it directly. The tools are better and the price is not paid by your customers.

The audit is a spreadsheet exercise and takes twenty minutes.

Export or open your submissions and, for each column, calculate the proportion that is blank, the proportion that looks fabricated, and the number of times anyone has filtered or sorted on it. That last one is usually a memory exercise, and the honest answer for several columns will be never.

Any column that is heavily blank, obviously fabricated, or never used has failed. Remove it or make it optional.

Then watch the submission rate for a month. The change is often large enough to see without any statistical sophistication.

For most service businesses the honest minimum is a name, a way to reply, and a message. Everything else is optional or automatic.

That form converts well, produces data you can actually use, and starts a conversation in which the rest of your questions get better answers than any form would have collected.

The remaining context arrives on its own, attached to the row, in the sheet where the enquiry lands.

Every required field should be earning its place, and the test is whether you could do your job without it. Most cannot pass that test, and the ones that cannot are charging your best prospects for information you were going to obtain anyway.

Ask for what you need to reply. Observe what you can. Ask the rest in the conversation you just started.

The version of this that persuades people internally is not the argument, it is the audit. Open the sheet, count the blanks in each column, and ask when anyone last filtered on it. A field nobody has used in a year is very hard to defend once somebody has looked.

How many fields is too many?

Does making a field optional actually help?

What about qualification for sales?

Do longer forms reduce spam?

Is a phone number worth requiring?

How do I know which fields to cut?

Should I A/B test form length?

What if a colleague insists on a field?