Begin with the reply you need to give
Decide what information helps the business respond. A simple service enquiry may need a name, contact route and short explanation. A project business may also need a broad location, type of work or preferred timescale.
Distinguish required information from information that can wait. Avoid asking for a full address or attachment merely because another business does. Every field should have a practical role in the next conversation.
Choose fields around the decision
Use a short choice where options are genuinely clear, with room for someone whose need does not fit neatly. Use free text for context, but do not require a long essay before someone can ask an initial question.
If budget or timing affects suitability, explain how the answer helps. Do not imply that a quotation or availability is confirmed by selecting an option. The form collects a request; the business still needs to assess it.
Make instructions and errors usable
Keep visible labels associated with fields rather than relying on placeholder text that disappears. Identify required fields clearly. When something is missing, explain the problem and how to correct it without discarding the person’s other answers.
W3C’s forms guidance covers labels, instructions, validation and feedback. Test with a keyboard and a small screen. Focus, error messages and the success state should make sense without requiring the visitor to infer what happened.
Separate an enquiry from marketing choices
A request for help and a decision to receive future marketing are different actions. Explain each clearly and avoid presenting an optional newsletter choice as a condition for making an enquiry or requesting a resource.
Link the relevant privacy information. Decide who needs access to the message and where it will be stored. Do not put private field values into tracking URLs, analytics labels or a public confirmation page. This is a design checklist, not a replacement for advice about your particular obligations.
Test the complete receiving process
Confirm where submissions are delivered, what the visitor sees and who will respond. Check both missing-information errors and a valid controlled submission. If an attachment is supported, test that path separately.
Keep the test labelled and use an inbox you control. Receiving a confirmation on screen is different from the business receiving the message. Check both, then document what happens if the delivery route fails.
PUT IT INTO PRACTICE
A first-enquiry field worksheet
Use these prompts in your own notes or when discussing the work. This is a reading checklist, with no submission or data collection.
| Information | Possible purpose | First-stage decision |
|---|---|---|
| Name and contact route | Know whom to reply to and how | Usually needed; do not require every contact channel |
| Service or project type | Route the request | Use meaningful choices with room for context |
| Broad location | Check service coverage | Collect only the detail needed at this stage |
| Budget or timescale | Assess practical suitability | Explain why it helps and allow uncertainty |
| Marketing preference | Record a separate optional choice | Keep distinct from the enquiry itself |
Questions, answered
Should I use a single page or a stepped form?
Use the structure that fits the questions. A short enquiry may suit one page; a longer project brief may benefit from clear stages. Test the actual journey.
Is a thank-you message proof of delivery?
No. Verify the receiving inbox or system separately and keep a record of the controlled test.
Where do KAI and EnquiryFit fit?
KAI can support approved questions and agreed handover. EnquiryFit supports a structured project enquiry. Discuss the process you need rather than adding an interaction for its own sake.
Official guidance
For the platform rules and technical detail behind the relevant checks:
YOUR NEXT STEP
Make the next decision with a clearer brief.
Tell KSJ Growth what you offer, what is not working and what you want the website to help you achieve. We can discuss a suitable scope before you commit to further work.
Discuss your business