01 / FIELD NOTE
Decide what your team needs to respond
Before adding fields, identify the information that helps someone give a useful first reply. A project-based business may need a brief description of the work and a preferred contact method. A local service may need a postcode to confirm coverage. A support team may need an order reference.
Separate essential details from information that can wait until a conversation. Asking for a full budget, a long project specification, and multiple contact details can make a first enquiry feel like an application. Keep the initial request focused on what genuinely affects the response.
02 / FIELD NOTE
Use clear labels and helpful examples
Every field should say what it is for. Labels such as “Your message” are understandable, but a short prompt can make the answer more useful: “What would you like help with?” If a format matters, provide an example and make the expected format clear.
Do not rely on placeholder text as the only label; it disappears when people start typing and may be difficult to read. Mark required fields visibly, identify optional fields, and explain why sensitive information is needed before requesting it.
03 / FIELD NOTE
Make the form work for different people
A form should be usable with a keyboard, screen reader, touch screen, and browser zoom. Associate each label with its input, provide clear focus indicators, and connect validation messages to the relevant field. Do not communicate errors through colour alone.
Use appropriate input types for email addresses, phone numbers, and dates so mobile devices can offer useful keyboards. Preserve entered information when validation fails, and place an error summary or concise message where it can be found. Test the complete journey with keyboard navigation rather than checking only how the form looks.
04 / FIELD NOTE
Set expectations around privacy and response
Tell people how their information will be used and link to a relevant privacy notice. Collect only the personal data needed for the stated purpose, and avoid adding marketing consent by default. If separate permission is appropriate, present it as a distinct, optional choice.
After submission, confirm that the form was received and explain what happens next. Give a realistic response window only if your team can maintain it. A clear confirmation prevents duplicate submissions and helps people understand whether they should expect an email, a phone call, or another step.
05 / FIELD NOTE
Measure whether the journey is actually useful
Track successful submissions and, where appropriate, the points where people leave the form. Use privacy-conscious analytics and make sure measurement respects your consent and data policies. A high submission count alone does not show whether the form is bringing in suitable enquiries.
Review the quality of incoming requests with the people who respond to them. If important details are consistently missing, add one well-explained question. If visitors abandon the form, check the effort required, the mobile experience, loading performance, and whether the page explains what happens after submission.