Try the example, then check the result.
Download the fictional material and follow the steps below. The video uses English illustrative diagrams; it does not present a live app recording. Product controls may vary by version.
Check the answer before applying the method to your own data. How we review guides ↗
Watch the complete lesson.
The video uses English illustrative diagrams; it does not present a live app recording. English captions. Product menus may differ in your account.
Add Google Forms response validation to fictional contact and quantity questions, then test invalid and valid answers. Download the fictional practice and answer check.
Before starting: Response validation checks email format and a numeric range. It does not prove that a mailbox exists, and Number > Between 1 and 5 does not by itself enforce whole-number seats. The preview test is local to the form editor; no external invitations or production data are needed. No live account workflow has yet been reproduced for this package.
1. Set up the fictional form
Create a form called Workshop Registration Practice. Add a Short answer question for Contact email and another Short answer question for Seats requested. Mark both required. Keep the form private while testing; use example.com addresses only. These Short answer fields demonstrate email-format and numeric-range rules. If a real form must accept only whole seats, use a 1–5 Multiple choice question for that field instead.
Checkpoint: Two Short answer questions; Both required; Use example.com.
2. Validate email format
On the Contact email question, open More > Response validation. Select Text > Email address and add a helpful error message such as Enter an address like name@example.com. This checks the shape of the answer. It does not verify that the mailbox exists or belongs to the person who entered it.
Checkpoint: More > Response validation; Text > Email address; Explain the format.
3. Limit the seat count
On Seats requested, add another Response validation rule: Number > Between 1 and 5. Enter a message that tells a respondent the permitted range. Keep the question required. This checks the bounds, but does not establish that the answer is an integer. A decimal such as 2.5 lies within the range. For a real count of whole seats, use Multiple choice with the five allowed values and test the form again.
Checkpoint: Number between 1 and 5; Custom error message; Whole seats require fixed choices.
4. Try two deliberate failures
Open Preview. First enter alex.example.com with 2 seats. The email should fail because it has no @. Next enter alex@example.com with 8 seats. The second answer should fail because 8 is outside the 1–5 range. These two failures prove that each question's rule is attached to the correct field.
Checkpoint: Bad email rejected; 8 seats rejected; Rules on correct fields.
5. Try the passing answer
In Preview, enter alex@example.com and three seats. Both answers meet the stated rules. You can stop before recording a response if you want only a UI check; if you submit a fictional response, label it as practice in your notes. Do not promise that validation prevents a correctly shaped but nonexistent mailbox or a fractional seat answer inside the numeric range.
Checkpoint: Valid email format; 3 is in range; No real respondent needed.
Verify the result
Read the question labels, validation settings, and error messages together. A form that says five seats maximum but validates up to ten misleads people. The answer check lists the two failing tests and the passing pair. It also notes that this Number rule is a range check. For a real seat-count question, change it to Multiple choice with 1, 2, 3, 4, and 5, and confirm a fractional answer such as 2.5 is not available before sharing.
Expected result: The practice form has two required Short answer fields. alex.example.com fails email-format validation; 8 fails the 1–5 numeric range; alex@example.com plus 3 passes. The Number rule does not enforce whole seats. For a real 1–5 seat count, replace that field with a required Multiple choice question offering exactly those five values. Validation does not prove the email address exists.
Official instructions: Google Forms help, checked 15 October 2026. Screens in the companion video are illustrative diagrams, not captured app footage.
Practice downloads.
The exercise files contain invented information. Save a local copy before editing.