Google Forms Response Validation on iPhone (2026)
Why Bother With Validation?
Every free-text field is an invitation for creative chaos: ages of “twenty five”, IDs with a missing digit, emails without an @. Validation rejects bad input at submission time — the one moment the respondent is still there to fix it. The alternative is you, later, cleaning the spreadsheet by hand.
Where the rules live: validation applies to short answer, paragraph, and checkbox questions. Multiple choice, dropdown, and scale questions constrain input through their choices. Grids also have separate row and column rules.
Setting a Rule from iPhone
- Open the form at forms.google.com in Safari and tap the question.
- Tap the card’s ⋮ menu → Response validation.
- Choose the rule family and configure it:
| Family | Options | Typical use |
|---|---|---|
| Number | between, not between, greater/less than (or equal), equal, not equal, is number, whole number | Age 5–120, quantity at least 1 |
| Text | contains, doesn’t contain, email address, URL | Email fields, links, must contain “@company.com” |
| Length | maximum / minimum character count | Comments ≤ 500 chars, ID = exact length via regex |
| Regular expression | contains / doesn’t contain / matches / doesn’t match a pattern | Student IDs, phone shapes, postcodes |
- Always fill the custom error text. Google’s default error is vague; “Enter your 6-digit student ID (numbers only)” fixes the answer on the first retry.
Three Regex Recipes Worth Stealing
- Exact 6-digit ID — Matches:
^[0-9]{6}$ - Phone input without separators — Matches:
^[+]?[0-9]{7,15}$(optional leading +, then 7–15 digits; no spaces or separators; this checks format, not whether the number exists) - Reject blank-ish answers — Doesn’t match:
^\s*$(blocks answers made only of spaces)
Keep regex patterns simple and test them in preview with deliberately wrong inputs. Turn on Required separately if an answer must be provided; format validation does not make an optional question required.
What Validation Can’t Do — and What Fills the Gap
Rules see one question at a time. They cannot compare fields (confirm-your-email), verify an address really receives mail, or react to earlier answers — for answer-dependent paths, that is branching logic’s job. And for fields that must arrive in a known format, the cleanest trick is not validating user typing at all but pre-filling the value to reduce typing errors. Pre-filled values remain editable, so keep any validation you still need.
Small honest note on editing comfort: validation setup is fiddly precisely where mobile Safari is weakest — small ⋮ menus and nested panels. It all works, but if you build forms on your phone often, the same rules are a normal native flow in our Forms for Google Drive iOS app, which edits your existing Google Forms with every control visible.
Validate the answer before routing the message
On iPhone and iPad. Forms for Google Drive provides a mobile workspace for editing and reviewing forms. Test both an accepted and rejected example for each validation rule through the actual responder link.
With the Workspace add-on. If an answer supplies a recipient address in Form Notifications by pipiform, use a suitable email question or validation rule and test the mapping. A syntactically valid address can still be misspelled or belong to someone else; validation does not guarantee delivery.
View Form Notifications and its features · Install the add-on · Get Forms for Google Drive on the App Store
The app and Workspace add-ons are separate pipiform products. Forms for Google Drive is US$59.99/year with a 3-day trial; check the App Store offer for your region. Form Notifications’ limited free mode allows 20 emails/day; paid features and recipient options depend on the plan. See current product pricing before subscribing.
Frequently Asked Questions
Which question types support response validation?
The main types are short answer (number, text, length, and regex rules), paragraph (length and regex), and checkboxes (select at least / at most / exactly N options). Multiple choice, dropdown, and scale questions have no validation because their options already constrain the input — the choices themselves are the validation.
How do I make Google Forms validate an email address?
On a short-answer question, open the question's ⋮ menu, tap Response validation, and choose Text → Email address. Forms then rejects anything that is not shaped like an email. It checks the format only — it cannot verify the inbox actually exists, so a typo like [email protected] still passes.
What are practical regex examples for Google Forms?
Three that cover most needs: a 6-digit student ID is Matches with ^[0-9]{6}$; a digits-only phone entry with an optional leading + is ^[+]?[0-9]{7,15}$ (7–15 digits; a format check, not proof of a real number); and blocking empty-ish answers of pure spaces is Doesn't match with ^\s*$. Set Matches or Doesn't match accordingly, and always write a custom error text so respondents know the expected format.
Why doesn't my checkbox 'select exactly 2' rule seem to work?
Checkbox validation only fires on submit, not while ticking — respondents can tick five boxes and only see the error when they try to submit the section. That is normal behavior. Write the requirement into the question text too ('choose exactly 2') so people are not surprised at the end.
Does validation work the same for respondents on phones?
Yes — validation runs in the form itself, so respondents on iPhone, Android, or desktop hit identical rules and see the same error messages. Building the rules from your iPhone is equally equivalent: the validation menu in mobile Safari is the same one desktop shows, just behind the question's ⋮ menu.
Can validation make a field match another field, like confirm-your-email?
No — each rule sees only its own question, so cross-field checks (confirm email, end-date-after-start-date) are impossible in Google Forms. Workarounds: skip confirmation fields entirely (email validation and a pre-filled link can reduce typing errors, but pre-filled answers remain editable), or move genuinely relational logic into how you process responses after export.