Work backwards from the response

List what a team member needs to send a useful first reply. Usually that includes a reliable contact route, the reason for the enquiry and enough context to route it. Every additional required field should have an operational purpose. Do not collect detailed project information simply because the form builder allows it. Sensitive or confidential material may belong in a later, more suitable exchange.

Use optional questions carefully

An optional field can help a motivated visitor provide detail without blocking someone with an early question. Label required and optional inputs clearly. Explain the kind of answer you need rather than using internal terminology. After publishing, review incomplete or confusing submissions to see whether the question itself is unclear. A form is a conversation design problem as much as a data collection task.

Imagine this

Hypothetical example

A hypothetical events supplier initially asks for a complete budget breakdown before accepting an enquiry. It replaces that requirement with event type, approximate date and contact email. A short optional note lets prepared buyers add detail, while early-stage enquiries still reach the right person.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.