Help/Building surveys

Choosing the right question type

The type you pick decides how the answer is stored, how it charts on the dashboard, and what you can do with it later. It is worth thirty seconds of thought.

Choice questions

TypePickUse it for
Multiple ChoiceOneMutually exclusive options — one answer is genuinely correct or preferred.
CheckboxesMany“Select all that apply”. Reasons, features used, channels seen.
DropdownOneLong lists where radio buttons would swamp the page — country, department.
Image ChoiceOne or manyConcept, packaging, and creative tests where the image is the question.

Scale questions

TypeUse it for
Rating ScaleQuick satisfaction reads with stars. Familiar and fast on mobile.
Linear ScaleNumbered scales with your own end labels. The general-purpose workhorse.
Net Promoter ScoreThe standard 0–10 recommend question. Charts as Promoters / Passives / Detractors automatically.
Matrix / GridSeveral statements sharing one scale. Compact, and the basis for looped follow-ups.
SliderA continuous value where the exact number matters more than a band.
Constant SumSplitting a fixed total — allocate 100 points across these five things.
MaxDiff (Best/Worst)Forcing real priorities out of a long list. Far better than rating everything 5/5.

Input questions

TypeUse it for
Short TextNames, codes, short factual answers.
Long TextOpen-ended “why” questions. Pair with a loop to keep answers attributable.
Multiple TextboxesSeveral short fields in one question — address lines, three suggestions.
Date / TimeDates, with or without a time component.
RankingPutting a short list in order. Keep it under about seven items.
File UploadReceipts, screenshots, documents from respondents.
Video ResponseRecorded video answers. Research plan.
Tip
Three swaps worth making

Multiple Choice → Checkboxes whenever more than one answer could honestly be true. Forcing one pick throws away most of the signal.

Rating everything → MaxDiff when you have a long list and need to know what actually matters. People rate nearly everything highly; MaxDiff makes them choose.

Several separate scale questions → one Matrix when they share a scale. Shorter to answer and much easier to read on the dashboard.

Writing rows for a Matrix

On an agree/disagree grid, every row should be a first-person statement covering one idea — “I feel supported by my team”, not “Do you feel supported by your team?”. You cannot agree or disagree with a question, so a question-shaped row forces respondents to translate it themselves, and different people translate differently.

It also matters downstream: looped follow-ups pipe the row's own wording into the follow-up question, and a question-shaped row reads badly there.

Related
Did this answer it?

If something here is wrong, out of date, or just does not match what you are seeing, tell us — guides get written and corrected in response to what people actually get stuck on.