Summary: Ask for the details you need to decide the next step. Make later-stage information optional, explain what happens after submission, and test the complete journey on a phone.
A quote request form for tradies should start a useful conversation, not make a homeowner complete your entire job file before you have spoken. Too little information creates extra calls. Too much can turn a simple enquiry into homework.
The right balance depends on the work. A replacement tap and a full bathroom renovation do not need identical intake questions. Design around the first decision your team must make: can we help, and what should happen next?
Start with the decision, then choose the fields
Write down what happens when an enquiry arrives. If you first check service type and suburb, put those questions near the start. If every quote needs a site visit, do not demand measurements that will be checked during that visit anyway.
For a straightforward residential enquiry, a name, contact method, suburb, service type and short description can be a useful starting point. This is a design suggestion, not a universal minimum. Ask your team which missing detail actually prevents a response.
W3C's form guidance supports clear labels, relevant questions and useful feedback. Those principles are especially helpful when someone is typing with one hand on a small screen.
Use a field-by-field decision table
| Field | Suggested treatment | Why it earns its place |
|---|---|---|
| Name and preferred contact | Required where needed | Allows a useful reply |
| Suburb | Usually required | Checks coverage before arranging travel |
| Service needed | Short list plus Other | Helps route the enquiry |
| Job description | Short free-text box | Captures details a dropdown misses |
| Photographs | Optional initially | Helpful when available, but not a barrier |
| Exact address | Collect when needed | Often unnecessary for the first conversation |
| Detailed dimensions | Service-dependent | Ask only if someone will use them |
Avoid making both phone and email mandatory merely because the software allows it. Decide which channel you actually need, and explain why if both are essential.
Write questions a customer can answer
Replace internal trade terms with customer language. “What needs attention?” may work better than an unexplained technical classification. Give an example without forcing the answer: “For example, a leaking kitchen tap or a hot-water replacement.”
Offer “Not sure” when uncertainty is legitimate. Otherwise people may select the wrong service just to proceed, leaving your team with confidently incorrect information.
For photo uploads, explain what would help and avoid instructions that require unsafe access. A customer should not climb onto a roof or open electrical equipment to finish a marketing form. Let them submit without a photograph.
Make the confirmation useful
A successful submission needs a clear acknowledgement. The following is an illustrative template to adapt to your actual process:
Thanks—your enquiry has been received. Our team will review the job details and contact you during our business hours. This is a quote request, not a confirmed booking.
Add a response timeframe only if your team can support it. Do not say an appointment is booked unless your scheduling process has actually reserved it.
If submission fails, explain what the person can correct. Do not erase every answer because one phone number is incomplete. A visible alternative contact method also gives people a way forward if uploading or validation fails.
Test the job, not just the appearance
Use a real phone and submit a test enquiry with an obvious test name. Check where it lands, who receives an alert and whether the reply reaches the right conversation.
Repeat with an optional photo omitted, an unusual suburb name, a long description and an invalid contact field. Navigate using a keyboard as well. Confirm every field has a persistent label rather than relying entirely on placeholder text.
Then ask someone unfamiliar with the business to complete it. Watch where they hesitate without coaching them. Their uncertainty can expose wording that makes perfect sense to your team but little sense to a customer.
Review the quality of the enquiries
Track completed enquiries and the questions your team still has to ask. Removing fields is useful only if the form still supports the next step. Adding fields is useful only if the answers change a decision.
Try one meaningful change at a time. Keep a record of the date, the change and any shift in incomplete or unsuitable enquiries. Small traffic volumes call for patient observation rather than declaring a winner after two submissions.
For help improving the customer journey on your website, see Tradie Local’s functional websites.
Sources & further reading
Frequently asked questions
How many fields should a tradie quote form have?
Use the fewest fields that support the first useful decision. Service type, location and a way to respond often matter more initially than a complete specification.
Should customers have to upload photos?
Usually keep them optional unless the specific service genuinely requires them. Explain what would help and provide another way to enquire.
Is a quote request the same as a booking?
No. Make that distinction explicit unless the form actually reserves a confirmed appointment in your scheduling system.
Can I use one form for every service?
Yes, if the first-stage questions are shared. Add a small number of conditional questions where different work genuinely requires different information.
How do I know whether the form is working?
Submit real test enquiries and confirm receipt, assignment and reply delivery. Review enquiry quality alongside completion numbers.
