Choose fields for a Website Form
Match each field to a decision you need to make after the submission, then set labels, requirements, options, and validation clearly.
Follow the steps.
Use your own accurate details and check the result as you go. You can return to the relevant Website editor to make corrections.
Start with the response
Write down what your team needs to know to send a useful first reply. Turn only those facts into fields.
Select the field type
Use text, email, phone, URL, number, long text, select, checkbox, radio, file, date, time, rating, consent, range, hidden, or another supported Form field when it matches the answer.
Write the field details
Give the field a direct label. Add help text, options, placeholder text, accepted file rules, or numeric and date limits only where they prevent a real misunderstanding.
Review required fields
Require an answer when the Form cannot be handled without it. Keep optional context optional, and test the validation message with an incomplete submission.
Illustrative exampleWhat a useful result looks like
- The result
- A short set of questions with required fields and useful guidance.
- What to check
- Remove any question you do not need to respond, and check which fields are required.
Adapt the example to your Website and review the result before moving to the next task.
Use a field type that fits the answer
Short text works for names and concise answers. Long text works for a request description. Select and radio fields help when visitors must choose one known option; checkboxes help with multiple selections or a clear acknowledgement.
- Use email or phone fields for contact details.
- Use date and time fields for preferences, not confirmed availability.
- Use consent fields when the visitor must make an informed acknowledgement.
- Use file fields only when the workflow needs an upload and the accepted format is clear.
Keep advanced fields tied to a real workflow
Hidden values can retain supported source context. Calculations, scores, conditions, and multi-step behavior need a defined purpose and realistic tests before the Form is used publicly.
A larger field palette does not make every Form better. Shorter Forms are easier to complete when each answer has a clear use.
Before you continue
A preferred date, budget, or service choice is information for review. It does not confirm availability, price, or a booking.