Name. Email. Phone. Company. Address. Budget. Preferred start date. It is easy to add another field while building a website. Perhaps the information will be useful later. But before the form grows, you need to know what you will actually do with the answer.
Start with the first conversation: what needs to be clear before you can help the customer take the next step?
Give each field a job
Go through the questions and finish this sentence for each one: “We need this answer to …”
“… reply to the customer” is a clear reason to ask for a way to contact them. “… check whether we work in the area” may justify a postcode. “… keep it in our system” says less about why you need it right now.
GOV.UK’s guidance on form questions recommends having a purpose for every question and asking only for information you need. For your business, that may mean moving some questions to a later conversation.
Keep what determines the next step. Reconsider the rest.
A hypothetical example: a painting business
Imagine a painting business receiving enquiries about interior painting. Before suggesting a site visit, it needs to know what the customer wants painted, where the work is, and how to reach them.
A postcode may therefore be useful in the form. Wall colours, company registration details and the full billing address could perhaps wait. If photos help the business understand the work involved, uploading them could be optional, with a brief explanation.
This is a hypothetical example, not a template for every trade. A business providing a specific quote directly from the form will need different information from one arranging a site visit.
Ask for details that affect your response
A short form can also ask too little. If you repeatedly need to send the same follow-up question before assessing an enquiry, that question may deserve a place.
A preferred date may be essential for a photographer. A budget range may be relevant when a project needs to fit a financial limit. Keep these questions when the answers change what you can offer.
But leave room for uncertainty. Someone looking for advice may not have a date or budget yet. “Not decided yet” can be a valid answer. Explain what the information helps you assess.
Make the form understandable
The number of fields is only part of the job. W3C’s accessible forms guidance highlights clear labels, understandable instructions and help with correcting errors.
Write “Phone (optional)” when the number is optional. An error message should explain what to fix. If an email address is missing @, “Enter an email address containing @” is more useful than “Invalid value”. After submission, make it clear that the message has been received.
Explain what happens next, too. If you promise a response within a certain time, your business needs to be able to deliver it.
Try it with a real enquiry
Open the form on your phone and complete it using a typical customer enquiry. Where do you need to look up information? Where is it unclear what to write?
Then ask someone unfamiliar with the business to do the same. Watch where they pause before you explain.
Choose one field to review today. Write down what the answer is used for, who uses it, and when it is needed. That gives you a concrete basis for keeping it, making it optional or asking later.
Sources
- GOV.UK Design System: Question pagesGuidance on the purpose of each question, optional fields and allowing uncertainty as a valid answer. Accessed 8 October 2026.
- W3C Web Accessibility Initiative: Forms TutorialGuidance on accessible labels, instructions, error messages and confirmations. Updated 27 March 2026. Accessed 8 October 2026.
These sources provide guidance on forms and accessibility. They do not establish an ideal field count or predict how many more enquiries a change will generate.