Plan and validate form fields
Set field type, required status, order, helper text and mapping for clear input
Every field should make a decision easier or enable a follow-up action. Too many required fields lower completion rate and data quality.
Choosing fields
| Need | Field type |
|---|---|
| Name/email/phone | Text input, email, phone |
| limited choice | Dropdown, radio group, card select |
| several answers | Multi select, checkbox group |
| long description | Text area |
| date or appointment request | Date picker or appointment |
| consent | Checkbox or toggle switch |
| file/photo | File upload |
| device or vehicle | Serial number, vehicle |
| device access | PIN, unlock pattern |
| signature | Signature |
Build the fields
Core fields first
Put name, contact and request at the top. Make a field required only if processing is impossible without the value.
Help and examples
Distinguish label, placeholder and helper text. No real customer data in examples.
Keep option values stable
Name option values clearly and in an evaluable way. Don't rename them after publishing without a migration plan – rather hide an option than delete it.
Check the mapping
In the Maps to section, map the field to a contact, ticket, order or vehicle field (also custom). Mappings shows unmapped and orphaned fields. Open a test submission and check the target value.
A required field without a clear hint looks like a form error. Check the error message and helper text in a mobile test.
Order
Contact → request → details → appointment/upload → consent. Only show conditional fields once a previous answer makes them relevant (Conditional logic section in the field). Split long forms into steps with a page break.
Related topics
How is this guide?