Landing pages
How many fields a form should ask
Each field has to earn its place by changing what your team does with the submission.
The right number of fields is the number your follow-up process uses, and no more. That answer annoys people who want a universal count, such as three fields or seven. There is no universal count. A crew that schedules in-home measurements cannot work from a first name alone. A newsletter that sends a monthly checklist should not ask for a street address and a date of birth. The form is a brief for the next human or the next system. If a blank box does not change that brief, it is weight.
Short forms became a slogan because many forms were padded with curiosity. Marketing teams asked for household details, product preferences, and “how did you hear about us” on the same screen as a phone number, then never opened the extra columns. Visitors felt the padding, even when they could not name it. The repair is not to strip every form to an email address. The repair is to interrogate each field against the operation that happens on the other side.
Start from the conversation, not from the template
Write down the first three questions a competent person would ask on the callback. Those questions are your candidate fields, but only if the visitor can answer them accurately without a conversation. A ZIP code is a good field because people know it and your team can use it to refuse out-of-area work before dialing. “Describe your project” is a good field when the answers really do change who calls back. “Best time to call” is a good field when someone sorts the list by that answer. If nobody sorts, the field is a decoration that also creates a promise you may break.
Prefer fields a person can answer without guessing. “Approximate age of the equipment” with broad ranges is answerable. “Exact model number” on a phone in a parking lot is not, and the garbage you collect will be typed into your records as if it were true. Bad data is more expensive than a missing column. It sends the wrong person, with the wrong expectation, to the wrong address.
Required means you will reject the submission without it
Mark a field required only when you will actually refuse to proceed if it is empty. A required phone number makes sense when the offer is a phone call. A required comment box often does not, because people type “n/a” and you have trained them to treat the form as an obstacle. Optional fields still need a reason to exist. Optional is not a junk drawer. If you would not mention the missing answer during follow-up, delete the field and shorten the privacy description at the same time.
Labels should say what you will do with the answer when that use is not obvious. “Mobile number we will call” is clearer than “Phone.” “ZIP code to confirm we work in your area” is clearer than “ZIP.” The extra words reduce wrong numbers and reduce the feeling that the form is nosy. They also keep the form and the consent language in the same vocabulary. A label that says email, next to consent language that talks only about telephone calls, is a small contradiction. Small contradictions accumulate into a page nobody quite trusts.
The cost of asking
Every field costs completion. It also costs storage, access control, and an explanation in your privacy notice. A phone number is sensitive in a way a favorite color is not, because of what can be done with it. Do not collect a phone number “just in case” on a page whose real next step is email. If you later decide to call, you will be calling people who were not asked about calls. The form you publish is the scope you have to live with. Expanding the scope later is a new ask, not a quiet change in a spreadsheet.
Grouping helps when the form is legitimately long. Put identity fields together, then the fields about the job, then consent. A reader can see the shape: who I am, what I need, what I agree to. A single vertical pile of fourteen identically styled boxes feels like an interrogation even when each box is justified. Order is part of honesty. Ask the easy, obvious items before the item that requires a decision about contact.
Validation should help, not scold
Check the shape of a phone number or an email if you can do it gently, and explain the check in the same screen. “Enter a 10-digit US number” is a useful constraint when that is the only kind of number your team dials. An error that says only “invalid” is a dead end. Do not silently rewrite what the person typed in a way that changes the meaning, such as dropping an extension they included on purpose. And do not block the form because of a trailing space. The visitor’s job is to give you a usable brief, not to satisfy a fussy expression in your code.
Test the form with bad intentions as well as good ones. Submit it empty. Submit it with a one-digit ZIP. Submit it twice. Confirm that a double submission does not create a mess your team will call twice, or that if it does, the team knows how to recognize the duplicate. The thank-you state should repeat the offer and the window. “Thanks! We will be in touch” throws away the specificity you wrote into the headline. Restate the window. Restate the channel. If something went wrong, say how to reach a person without asking the visitor to fill the same form again blindly.
A field audit you can finish in one sitting
- List every field and the person who reads it.
- Delete any field with no reader.
- For each remaining field, write the action it changes.
- Un-require any field you would accept blank.
- Rewrite labels so the channel and the purpose are visible.
- Confirm the privacy notice names the same categories of information.
- Submit a real test and read it the way the follow-up team will.
When the audit is done, the form may be four fields or it may be nine. The count is not the achievement. The achievement is that you can point at each box and say what happens because of it. That is the form you can put under a clear offer, on a phone screen, without feeling that you have to apologize for the length.