Build a quote-request form that asks for the right details

Map the first response before choosing fields

Write the decisions your team makes when an enquiry arrives: whether the work is within scope, whether its location or delivery mode is supported, who should respond and what missing information prevents an estimate. For each decision, name the smallest answer that enables it.

A fictional garden-design studio might need the service type, approximate project location, a brief description and a reply address. A precise plant list is not necessary to decide whether a consultation is appropriate. Conversely, location can be essential when the studio only visits a defined area.

The GOV.UK question-page pattern emphasizes understanding why every question is needed. Apply that discipline without automatically splitting a small commercial form into many screens. The best grouping depends on the actual task.

Ask about the job in the customer’s language

A person may know that their garden floods but not whether they need drainage design or landscape architecture. Offer understandable service choices with a Something else or Not sure route when your team can handle it. Avoid forcing prospects to solve your internal routing problem before they can contact you.

Use a short prompt for the description: what are you trying to change, and what is not working now? A helpful example explains the level of detail. It should not encourage customers to disclose access codes, medical information or unrelated personal history.

WAI’s forms tutorial supports purposeful, understandable forms with labels, instructions and grouping. Our form accessibility guide covers implementation checks so this qualification exercise does not become an excuse to rely on disappearing placeholders.

Handle budget and timing honestly

If there is a real minimum project size, explain what it covers before asking whether the prospect’s budget fits. A hidden minimum followed by a compulsory exact amount wastes effort on both sides. Do not publish a false starting price just to make the form look approachable.

When a range is useful, use ranges that map to decisions your business actually makes and include an unsure option. Do not interpret that selection as permission to charge the top of the range. The later quote should describe scope, assumptions and the actual price.

Distinguish a preferred completion date from a fixed external deadline. For the fictional studio, an upcoming event may matter more than a vague As soon as possible response. Explain that entering a date requests consideration; it does not reserve capacity or create a delivery commitment.

Make files optional unless they are necessary

A photograph can clarify a garden enquiry, but requiring an upload may block someone who is on a different device or has not prepared images. Provide an alternative short description and state any genuine file-size and format limits before the person starts uploading.

File handling also creates storage, access and deletion responsibilities. Use the contact-form upload workflow to plan those independently. Do not ask people to upload sensitive documents just because the form builder supports attachments.

For the studio, an optional overview photograph may support routing. A complete property plan might be requested after a suitable staff member explains why it is needed and which secure route to use. That staged process can be more useful than collecting every possible document in advance.

Explain what happens after sending

Describe who reviews the enquiry, the supported next step and any genuine response expectation. If the business cannot consistently promise a response within a stated period, do not manufacture one. Explain whether the first reply arranges a call, asks for details or provides an initial estimate.

Keep the action label aligned with the commitment. Request a quote does not mean Buy now, book a confirmed appointment or receive an instant fixed price. If the page offers an immediate calculation, explain its assumptions and how it differs from an accepted proposal.

WAI’s notification guidance supports understandable feedback after the action. Show a confirmation only for the outcome actually established by the form system. If the accepted enquiry exists but the notification fails, the customer should not be told to start again without checking the first request.

Review a realistic enquiry from beginning to end

In an authorized test environment, submit a synthetic request for a small garden redesign with an unknown budget and no file. Check that staff can decide whether it fits and produce the promised next response. Repeat for a location outside the service area, an urgent deadline and an enquiry that needs clarification.

Test the actual mobile keyboard, conditional fields, required-field errors and success state. Keep the form readable without horizontal scrolling. Do not grade only how attractive the empty form looks; long answers, validation messages and file names change its geometry.

If the enquiry never reaches the working process, follow our contact-form delivery diagnosis. A lower field count cannot repair a missing accepted record or broken notification route.

Improve qualification without chasing fewer fields at any cost

Review useful enquiries, not just raw submission counts. If a removed question creates repeated unnecessary follow-up, refine its wording or restore a justified version. If an answer is collected but nobody uses it, remove it from the first step.

Keep a short field inventory with its decision, required status, owner and later-stage alternative. That record makes future additions reviewable. A good quote form is compact because each question earns its place, while the customer understands both what to send and what the business can honestly do next.