Rating Scales in Google Forms on iPhone (2026 Guide)
Pick the Right Scale Question
| Rating (stars) | Linear scale | Multiple choice grid | |
|---|---|---|---|
| Reads as | ”Rate us” — instant | ”How much do you agree" | "Rate each of these” |
| Levels | 3–10, icon-based | Configurable, end labels | One scale × many rows |
| Best for | Satisfaction taps, polls | Agreement, likelihood, NPS-style | Comparing items |
| Mobile feel | Excellent — one tap | Good | Long — use sparingly |
All three live in the question-type picker in mobile Safari; the Rating type additionally lets you choose the icon (star, heart, thumb) and level count.
The Rules That Keep Scale Data Usable
- Five points, usually. Ten-point precision is imaginary (answers cluster at 7–8); three points blunt everything. 1–5 keeps averages meaningful.
- Label both ends, always. An unlabeled “1 to 5” means different things to different people; 1 = Very dissatisfied / 5 = Very satisfied means one thing.
- One direction per form. If 5 is good anywhere, 5 is good everywhere — mixed-direction scales are how feedback data turns to noise.
- Odd for a neutral option, even to force a lean. Convention says odd; comparability says pick one and stop.
- Never reword a live scale. The question text is the spreadsheet column and the trend line; edits fork your history. Add a new question instead.
Reading the Numbers
Scale answers land as plain numbers — one column each — so the analysis toolkit is immediate: AVERAGE by month off the Timestamp column, a pivot table by segment, an Excel export for whoever asks. Star-rating and linear-scale data are interchangeable in the sheet; choose the question type for the respondent, not the analyst.
Building multi-scale forms is also where mobile Safari’s cramped question cards grind most — five settings taps per question adds up. Our Forms for Google Drive iOS app edits the same questions in a native interface, and its AI drafting will happily produce a properly labeled five-point block from a one-line description.
Frequently Asked Questions
What is the difference between the Rating and Linear scale question types?
Rating shows tappable icons — stars, hearts, or thumbs — over 3 to 10 levels; it reads instantly ('rate us') and suits satisfaction moments. Linear scale shows numbered buttons with your own labels at both ends; it suits agreement and likelihood questions where the endpoints need defining. Same data shape underneath — a single number per response — different reading experience.
How many points should my scale have?
Five for most jobs: respondents use the whole range, and month-over-month averages stay interpretable. Ten-point scales add precision people don't actually express and cluster at 7–8; three-point scales blunt the signal. The strongest rule is consistency — pick one width for a metric and never change it, or your trend line breaks.
Odd or even number of points — should I include a middle?
Odd scales offer a genuine neutral, which is honest but attracts fence-sitting; even scales force a lean, which sharpens signal but frustrates truly neutral respondents. For satisfaction tracking, odd (1–5) is the convention and comparability usually beats cleverness. Go even only when a forced choice is the point.
How do I label a linear scale properly?
Label both ends explicitly — '1 = Very dissatisfied, 5 = Very satisfied' — in the built-in end labels, and keep the direction consistent across every scale in the form. Mixed directions (5-is-best on one question, 1-is-best on the next) are the single most common cause of garbage scale data.
Can rating questions be required, validated, or auto-graded?
Required, yes — both types take the standard toggle. Validation is neither available nor needed: the scale itself constrains input. In quizzes, neither Rating nor Linear scale takes an answer key; they collect opinion, not correctness, and simply sit ungraded alongside scored questions.
How do rating answers look in the response sheet?
As plain numbers, one column per question — which is the quiet superpower: averages, monthly trend lines, and pivot tables work immediately. Multi-row grids expand to one column per row. Keep question titles short, since they become the column headers you will read in Sheets forever.