Forms · Glossary
Primacy and recency effects in survey answers
Primacy is the tendency to choose options presented early in a list; recency is the tendency to choose the ones presented last. Which appears depends on how the question is delivered. Options read on a screen favour the top of the list, while options read aloud on the phone favour the ones heard most recently.
Order effects are one of the few survey biases with a clean, replicated explanation, and one of the least often controlled for. The order you happened to type the options in is quietly part of your results.
Indunil Asanka · Co-founder
6 min read · Published
| Mode | Dominant effect | Why |
|---|---|---|
| Online form, options visible | Primacy | Reading stops at the first acceptable option |
| Paper questionnaire | Primacy | Same reading behaviour, with more of the list visible |
| Telephone interview | Recency | Only the last few options are still in working memory |
| Face to face with a show card | Primacy | The card makes it a visual task again |
| Long list on a small screen | Primacy, more strongly | Later options require scrolling to reach |
| Scale with labelled ends only | Weak order effects, stronger anchoring | The ends dominate rather than the sequence |
Why the direction flips
The explanation survey methodologists give is about processing rather than preference. When somebody reads a list, they evaluate each option in turn and often stop at the first one that is good enough, so early options get more consideration and more selections. When somebody hears a list, the early options have decayed from working memory by the time the reading finishes, so the last one or two are the ones available to choose. The pattern has been replicated across decades of research, and it is stronger when the respondent is tired, when the list is long, and when the options are similar enough that no single one obviously wins. That last condition describes most survey option lists.
How much it matters
Enough to change a conclusion when two options are close. If an option gains a few points simply by being first, then a result showing option A narrowly ahead of option B tells you nothing you can rely on unless the order was controlled. It matters less when one option is far ahead, and it matters most in exactly the situations people care about: ranking priorities, choosing between similar features, picking a preferred time. The effect is also asymmetric across waves. If the option list is reordered between rounds because somebody added an item at the top, the change in results will be attributed to a real shift rather than to the edit.
What to do about it
Randomising the order of options across respondents is the standard control, and it spreads the bias evenly rather than concentrating it on one option. Option randomisation is not a feature of this product, so the practical alternatives are to fix a defensible neutral order and to keep lists short. Alphabetical order is neutral in the sense that nobody chose it to favour anything, though it does favour whichever option happens to start with an early letter, which is why it works better for long lists of names than for a handful of concepts. Chronological or numeric order is genuinely neutral where it applies, such as time slots or price bands.
Reducing exposure rather than controlling it
Since the effect grows with list length, the most reliable defence available is a shorter list. Six options rather than twelve halves the number of positions that can carry a bias, and it also improves the quality of every answer. Splitting a long list into a category question and a follow up does the same thing, at the cost of a routing rule. Where the comparison between two specific options is the point of the question, ask about them directly rather than burying them in a list of ten. And when you report results from a list that was not randomised, say so, because a reader who knows the order can judge how much weight to put on a narrow gap.
Building order aware questions in a form
Radio, dropdown and checkbox fields can be laid out in one, two or three columns. Column layout changes what counts as first: in a three column grid the reading order is not a simple top to bottom sequence, so a long list in columns spreads attention differently from the same list stacked. Keep scales in a single row or column so their order is unambiguous. Where you split a long list across two questions, conditional logic is jump rules only, so the second question is reached by routing rather than by revealing a field in place.
Keeping the order stable across waves
Order effects become an invisible trap in any recurring survey, because option lists get edited between rounds. Somebody adds a new product at the top of the list, and next quarter that product appears to be gaining share when what changed was its position. The defence is bookkeeping rather than method. Record the exact option list and its order alongside the data for every wave, and treat any change to the list as a break in the series that has to be noted in the report. Where a new option genuinely has to be added, put it at the end rather than in a logical position, and say in the commentary that its first wave is not comparable with anything. Reordering an existing list to look tidier is the change most likely to be made without thinking and most likely to mislead.
Questions people ask
Does randomising options solve it completely?
It spreads the bias rather than removing it, which is usually what you want, since no single option is systematically favoured. It does add noise to individual estimates and it makes the data slightly harder to reason about. Where randomisation is not available, a short list and a neutral fixed order get most of the benefit.
Should scale points be randomised?
No. A scale is ordered by definition, and shuffling the points would make it unreadable. Scales are subject to anchoring effects at the ends rather than to list order effects, which is a different problem addressed by labelling every point and keeping the direction consistent through the form.
Does it affect open questions?
Not in the same way, since there is no list. Something similar appears in what people recall: the most recent experience dominates an open answer about a period. Naming the period in the question, such as the last month, helps anchor the memory rather than letting the latest event stand for all of it.
Is the effect stronger on mobile?
Generally yes for long lists, because options below the fold require scrolling and some respondents choose before they reach them. Keeping lists short enough to fit one screen removes most of that. It is another reason to prefer a small set of radio options over a long list that has to be scrolled or opened.
What about the order of questions rather than options?
Question order has its own effects, usually through priming rather than memory. Asking detailed questions about problems before a general rating lowers the rating. Put general questions before specific ones when you want an unprimed view, and keep the order stable across waves so any change in results is not caused by the survey itself.
How do I report results from a non randomised list?
State the order used and note that options were presented in a fixed order. Then avoid drawing conclusions from small gaps between adjacent options. If the difference between the top two matters to a decision, run a follow up question that compares them directly rather than relying on the list.
Make one with forms
The button opens the generator with this use case already described. Change the wording to match your own.
Create a form with OneCraftRelated questions
- What is survey fatigue?Survey fatigue is the drop in response quality and completion as a survey gets longer or arrives too often. How length affects drop off and what to cut.
- Dropdown against radio buttonsShow fewer than six options as radio buttons and use a dropdown beyond that. How option count, mobile and default values decide between dropdown and radio.
- Single select against multi select questionsSingle select takes one answer, multi select takes several. When to use radio against checkbox, how results are counted, and the select all undercount.
Step by step in the builder: Every form field and when to use it, then View, export and manage your responses.
Written and checked by the OneCraft team. Last checked .