Resources

Survey glossary

This glossary defines 18 terms used in survey design, survey logic, measurement and data protection, in plain British English. Each entry gives a tight definition first, then when to use the thing, the mistakes people usually make with it, and, in most entries, a worked example. Where a term maps onto something in NumoForms, the entry says exactly how — and where it does not, it says that too.

Written for people who have to run a survey next week, not for people studying survey methodology.

All terms

Question types

The shapes a question can take, and what each one does to your data.

Logic & flow

How a survey decides what to show, and in what order.

Measurement

The numbers people quote about surveys, and what they actually mean.

Methodology

Survey design and sampling ideas that decide whether the results are worth anything.

Privacy & compliance

The obligations that come with collecting answers from people.

How to use this glossary

Most survey vocabulary is borrowed from social research and then bent by whichever tool a team happened to use first. The result is that two people can say "branching" and mean genuinely different mechanisms, or say "response rate" and be quoting numbers with different denominators. Each entry here therefore starts with a definition tight enough to disagree with, and then says where the term is used loosely.

Three conventions run through the set. Where a term has a strict technical meaning and a looser everyday one — Likert scale is the clearest case — both are given, and the difference is explained rather than ignored. Where a definition depends on how a particular tool implements it, the entry says which tool it is describing. And where NumoForms does not do something, the entry says so plainly instead of leaving the impression that it does: see the note on jump targets in branching, or on disqualify actions in screener questions.

Nothing here is a substitute for legal advice. The DPIA, data residency and WCAG entries summarise obligations accurately as far as they go, but the obligation sits with whoever is running the survey, and the details of your case matter.

Definitions become decisions in the builder.

Every term defined here describes something you can put in a survey: a logic rule, a matrix grid, a screener, a hidden field. Building one is the quickest way to find out which of them you actually need.

  • All sixteen question types, matrix and ranking included
  • Conditional logic written per question, not as a routing map
  • Responses stored in London and exported as CSV
Start building