A form should collect the data the team needs for its next action. Every field should be justified by one question: what will change in the first reply thanks to this information?
Separate what is needed from what can be clarified later
Start with contact details, topic and a description of the task. Company, budget and other details may each need a separate decision depending on your model. Do not ask for sensitive documents if they are not needed to understand the request initially.
Explain what happens after submission
The hint should help people describe their task, not advertise the company. Check the error message and the confirmation of receipt. Only state a response time that the team is genuinely ready to keep.
How to justify each required field
For each field, write down the decision the team makes based on the answer. Contact details let you continue the conversation, the topic routes the enquiry and the description helps you understand the task. If an answer is only needed when preparing a contract, it can be dealt with at that stage. Do not collect sensitive materials just because the form allows attachments. The hint should explain how much detail is useful. An overly broad request such as “tell us everything” shifts the job of defining the task onto the person and can lead to excessive sharing of personal data.
Which submission scenarios to test
Using agreed test data, check a normal enquiry, a missing required value and a temporary delivery failure. Make sure the success message corresponds to actual receipt and that an error explains the available action without losing the text already written. Check double-clicking and selecting a service from different pages. The test does not end in the interface: the designated recipient must see the correct topic and materials. If the customer receives a confirmation, check its language, content and that it does not needlessly reveal the full enquiry.
What to check
- Appoint an owner for incoming enquiries.
- Check that the selected service is preserved.
- Test both an error and successful delivery.
- Explain the next steps in plain language.
Checking whether form fields are needed
Before adding a field, explain how the team will use the answer. If the information does not affect the first action, consider asking for it later.
| Field | Purpose | Check question |
|---|---|---|
| Contact | Get in touch about the request | Does the reply channel provided actually work? |
| Service | Pass the request to the right person | Is the choice from the previous page kept? |
| Description | Understand the task | Does the hint help people write a meaningful message? |
| Timeframe | Clarify expectations | Does the form avoid promising availability? |
| Attachments | Get material that is actually needed | Are they really needed in the first enquiry? |
| Confirmation | Explain the next step | Does the text match actual delivery? |
Example situation
The “message” field becomes more useful with a hint about the task, city and timeframe than with the generic text “tell us about yourself”.
Next step
A good form makes it easier to start a conversation and does not create extra questions instead of an answer.
Official information on this topic
Checklists and examples are organisational recommendations. Requirements depend on the procedure, the city and your situation; check them with the relevant office before you act. Please discuss legal and tax questions with an authorised professional.
This article was prepared with the help of AI. The example illustrates the approach and does not describe a client case.