HigherStack Validation & required fields
How required answers and format checks keep submissions clean — on both the client and the server.
Validation makes sure you collect usable answers. It runs as people fill the form and again on our servers when they submit, so the rules can’t be bypassed.
Built-in checks
| Field | Checked for |
|---|---|
| A valid email address format | |
| Phone | A valid phone number |
| Number | A real number |
| Any required field | A non-empty answer |
When validation runs
- Per page — required and format checks run when someone clicks Next on a multi-page form.
- On submit — everything is re-checked before the response is accepted.
- Conversational mode — each question is checked as the respondent advances.
Only relevant fields are required
A field that’s hidden by logic or on a page the respondent never reaches won’t be required. The server uses the same logic and routing as the form, so it only enforces the questions that were actually shown.
Tip
Error messages are shown in the respondent’s language automatically. Write clear labels — the messages read like “{label} is required”.
Still need help?
A dedicated support form is coming soon. In the meantime, jump back into the product or reach the team from the contact page.