Research & PolicyFree tool
Open-Ended Survey Response Coding Tool
A written codebook for your survey's free-text answers, every response coded and counted on a stated base, and a tally of answers no code fit.
Free to start · Opens in your River workspace, ready to edit and share
How to analyze open-ended survey responses
To analyze open-ended survey responses, you code them: write a codebook that defines each theme, apply it to every answer, and count how often each code appears. A good analysis lets one answer carry several codes and counts the answers no code fit. It says what each percentage is out of and has a second person check a sample.
Write the codebook down before you count anything. A theme you noticed while reading can't be checked. A written rule can: a colleague, a reviewer or next year's team can apply it to the same answers and see whether they get your numbers.
Count what you have before you code
Start with three numbers: the people asked the question, the people who typed anything, and the answers left after you set aside non-answers. Decide what counts as a non-answer first, because it depends on the question.
Pew Research Center's codebook for its 2021 study of what makes life meaningful counted "none" and "nothing" as legitimate answers1. Only a reply that couldn't be read as an answer at all, such as "I don't know", was a non-answer.
The item response rate is the share of people asked who answered, not counting anyone routed past the question. In the US, the Office of Management and Budget's 2006 standards for federal surveys set a benchmark. For any item used in a report, they say to plan a nonresponse bias analysis if the expected item response rate is below 70%2. If yours is lower, compare answerers with non-answerers on the closed questions you have.
That comparison matters because the people who write are not a random slice. In the same Pew study, certain groups, often the more affluent and more educated, were more likely to answer and gave more detail3. Longer answers mention more topics, so those groups can seem likelier to raise rare ones, such as pets. Pew controlled for topics per answer before reporting any group difference.
Draft the codebook on a random sample
Read a random sample of answers, not the first rows in the file (often your earliest respondents), and draft codes from what people actually wrote. Pew's researchers tested their draft on a random sample of 150 responses3, reviewed where coders disagreed and refined it. After three rounds, it was clear enough for other coders to apply consistently.
Give every code four things: a short name, a rule for what belongs, a rule for what doesn't (and where it goes instead), and one real answer as an anchor. If you track a theme from last year, start from last year's codes and note any rule you change.
(2) Family and children
Family, children, kids, being a parent, grandchildren, being a grandparent, my children's future/upbringing, my siblings … relationship difficulties with family/kids
Does NOT include references to "children" if it's absolutely clear that they are not talking about their own (e.g., "I enjoy my job teaching children"). However, if it is ambiguous (e.g., "giving children a better future") then include it. When in doubt, count it.
- What belongs. It lists the everyday words and phrases that count, negative ones included.
- Where it stops. The exclusion is explicit, with the borderline case written out.
- A tie-breaker. "When in doubt, count it" settles every ambiguous answer the same way.
Code every response, then read the leftovers
Code the full set, and let an answer take every code it earns. "Too expensive, and the app keeps logging me out" is both Cost and Reliability. Pew's codebook gave each phrase one category but expected most responses to mention multiple categories1.
Code the topic apart from the tone. Pew told coders to treat "I don't have enough money" the same as "I have enough money", and flagged complaints with a separate code for difficulties or challenges1.
Hold back what fits nothing
Don't force a near miss into the closest code. Set it aside and keep going.
Read the pile on its own
Once everything is coded, read only the leftovers. Themes too rare to show up in your drafting sample can surface here.
Add a code only if it's earned
If several leftovers share one idea, write a new code with its own rules, then recheck the coded answers for it.
Report what remains
Give the final count and its share of codeable answers, and say what they were about.
Don't bury the leftovers in Other
A big "Other" code hides what the leftovers would tell you, including whether your codebook fits the answers at all.
Have a second coder check a sample
Hand a colleague a random sample with your codes hidden, and have them code it from the codebook alone. Communication researchers Matthew Lombard, Jennifer Snyder-Duch and Cheryl Campanella Bracken recommend a reliability sample of at least 50 units or 10% of the full sample4. They add that it rarely needs to be larger than 300.
Measure agreement with a statistic that discounts chance, such as Cohen's kappa, and compute it for each code. Plain percent agreement flatters you: if a code is rare, two coders who never use it agree on almost every answer. The same researchers call .80 or greater acceptable in most situations4, and say .70 may be appropriate in some exploratory studies.
Pew's coders started coding on their own only after scoring at least 0.73 on Krippendorff's alpha, a similar measure. When two coders disagree, rewrite the rule that caused it, not just the answer, and recode.
Report the check with the results
Say how many answers were double-coded, how you picked them, and the score for each code.
Report every count with its base
Every percentage needs a base: the group it's a share of. Open-ended items offer three honest ones, and they can differ by more than 10 points. Name the base in the same sentence as the claim.
One code, three bases
| Base | Who it counts | Share for a code with 412 mentions |
|---|---|---|
| All respondents | Everyone asked the question (2,180) | 18.9% |
| Everyone who answered | Anyone who typed something (1,347) | 30.6% |
| Codeable answers | Answers left after setting aside non-answers (1,229) | 33.5% |
Illustrative numbers. This item's response rate is 61.8% (1,347 of 2,180), below the 70% federal benchmark.
Because one answer can carry several codes, the shares can add up to more than 100%. Say so, and give the average number of codes per answer. Set a minimum base before you look, such as 30 answers, and below it report the count instead of a percentage.
Choose quotes because they plainly fit the code, not because they're vivid, and print each next to its code's count. Pew states that its quotes were purposefully, not randomly, selected to illustrate key points3 and may not represent all responses. Say how you chose yours.
Then carry the counts, bases and quotes into a survey results report that keeps each group's base beside its numbers.
Before you share the results
- The codebook is written down, with include and exclude rules
- Every percentage names its base
- Leftovers are counted and described, not hidden in Other
- A second coder checked a random sample, and the score is reported
- Small groups show counts, not percentages
- Each quote sits next to its code's count
Turn open-ended answers into better questions
Open-ended answers catch what a list of options would miss. After the 2008 US presidential election, Pew asked voters which issue mattered most. When given a list, 58% chose the economy; only 35% named it unprompted5, and 43% of those asked the open version gave an answer the list didn't include.
Pew notes that researchers sometimes pilot open-ended questions to find the most common answers5, then offer them as choices in a closed-ended version. Your biggest codes are candidates for next year's answer options, and the leftovers show what your questions don't yet ask. Draft them in a survey questionnaire design template that ties each question to the analysis it feeds.
For a faster first pass, use the tool at the top of this page. River drafts the codebook on a random sample, codes every answer, counts the leftovers and marks a check sample for a second coder.
How it works
Start by attaching your survey export or pasting the answers, with the question people saw. River first counts who was asked and who answered, then drafts a codebook on a random sample, codes every answer and counts the ones no code fit. You get a sheet with one row per respondent and a document with the codebook, themes, quotes and bases. It never invents a response, a count or a quote.
Add your responses
Attach the export or paste the answers, with the question people saw and any groups to compare.
River codes them
It drafts a codebook on a random sample, codes every answer and holds back the ones nothing fits.
Get your results
A sheet with every coded response, plus a document with the codebook, themes, quotes and their bases.
Check and refine
Give the marked sample to a second coder, then ask River to merge, split or recount codes.
What you get
- A written codebook giving each code a name, what it includes, what it excludes and a real example
- Every response coded in a sheet, one row per respondent, joined to your group columns
- Frequencies for each group, with the base beside every percentage and small groups held back
- A count of the answers no code fit, with a note on what they contained
- Quotes picked because they fit the code, each shown beside that code's count and base
- A random check sample for a second coder, with per-code Cohen's kappa set up to fill in
Common questions
What is the best way to analyze open-ended survey responses?
Code them against a written codebook, then count. Check how many people answered, draft codes on a random sample, apply them to every answer and have a second coder check a sample. The usual mistakes are coding by impression, hiding the leftovers in "Other" and printing percentages without saying what they are out of.
How do I code open-ended responses with River?
Attach your survey export or paste the answers in the box at the top of this page, with the question people saw. River drafts a codebook on a random sample, codes every response and counts what fit nothing. The results open in your free River workspace: a sheet of coded responses and a document you can edit and share.
Will it give me a sentiment score?
No. A score on a two-sentence answer is a guess, and an answer that names a problem doesn't mean the person is unhappy. River codes what people said. If you need tone, ask for it: River codes it as its own dimension, with its own rules and its own count of answers that didn't fit.
What if I only have a few hundred responses?
It still works, with fewer breakdowns. River sets a minimum base, 30 codeable answers unless you choose another, and any group below it gets a count or is left out, never a percentage. A percentage of seven people is noise dressed up as a finding.
Can it compare this year's answers with last year's codes?
Yes. Attach last year's codebook with this year's answers, and River reuses the codes whose rules still hold, flags any it had to change and marks each code comparable or not. That matters because a theme that rose from 10% to 18% means little if its rule got wider in between.
Can I use it for interview transcripts?
It isn't built for them. It expects survey answers, which are short, numerous and meant to be counted. For raw transcripts, the interview synthesis tool finds the themes and counts how many people raised each. If your interviews are already coded, the thematic analysis write-up turns the codes into themes, each with the participants behind it and the extracts that contradict it.
Is the open-ended survey response coding tool free?
Yes, it is free to start. Your codebook and coded responses open in a River workspace, where you can edit them, share them or ask River to change them. Paid plans add more AI use and access to the most advanced models.
Sources
Pew Research Center. “Appendix C: Codebook.” pewresearch.org (opens in a new tab)
Office of Management and Budget. “Standards and Guidelines for Statistical Surveys.” obamawhitehouse.archives.gov (opens in a new tab)
Pew Research Center. “Appendix A: Coding methodology.” pewresearch.org (opens in a new tab)
Matthew Lombard. “Practical Resources for Assessing and Reporting Intercoder Reliability in Content Analysis Research Projects.” matthewlombard.com (opens in a new tab)
Pew Research Center. “Writing Survey Questions.” pewresearch.org (opens in a new tab)
Built by
Chandler Supple
Co-founder & CEO, River
Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.