Preview shows you one path at a time. Your respondents will find all of them. Learn how to test survey logic without spending hours manually clicking through preview mode.
Quick quiz: How many routes does your survey really have?
Think of the last survey you launched with branching in it. How many different routes could a respondent take from the first question to the last?
If you said “a handful” or “I’d have to check,” you’re in good company. Almost nobody knows the real number. A survey with nine branch points can produce dozens of routes. Preview, the one tool most survey software gives you, shows one route at a time.
So you do the sensible thing. You test the main path, the obvious screen-out, maybe one strange combination. Then you trust the rest and publish.
That trust is where it goes wrong. A condition that can never be true doesn’t throw an error. A question hidden by one rule and never shown by another doesn’t send an alert. The survey just runs, and you find out when a question has zero answers and fieldwork is halfway done.
A survey path simulator closes that gap. It reads your logic, lists every route, and flags the questions nobody can reach. You check the whole survey, not just the parts you remembered to click.
Learn More: See how the survey path simulator works in QuestionPro
Why survey logic breaks without telling you
New to this? Skip logic sends respondents to different questions based on their answers. Show/hide rules decide what appears. Compound logic combines several conditions into one rule. Block flow moves whole sections around. Our guide to skip logic in surveys covers the basics, and the survey logic page lists the full toolkit.
Each rule is simple on its own. The trouble is how they stack. A screener quietly removes the group you meant to keep. A block waits behind two conditions that can’t both be true. Someone rewords an answer option in question four, and a section three pages later is cut off from everyone.
None of this is a software error. The logic does exactly what you told it to. It just isn’t what you meant, and nothing says so until the data comes back thin. By then, the fix means re-fielding, or explaining the gap to a client.
What a survey path simulator does, in plain terms
Think of it as a map of your survey. It’s drawn from the rules you set, not from responses. In QuestionPro, you open the survey path simulator from the survey editor toolbar and pick a starting question. Your survey then appears as a flow diagram with every decision point marked.
From there, three things matter.
- Every route, listed.
Turn on Compare All Paths, and you see each complete route from your starting question, labeled completed or terminated. Click one, and it lights up on the map. Filter to terminated, and every screen-out sits in one list you can check against the project brief.
- Unreachable questions, with reasons.
One tab lists the questions and blocks no respondent can ever see, along with why. Maybe a block sits inside a logic container whose criteria can never be met. They’re outlined in red on the map. A question is flagged only when you can prove it’s unreachable, so a flag is worth acting on.
- The reason behind each turn.
Click a branch marker and the branching reason shows the skip, compound, or show/hide rule behind it. Or step through one respondent’s journey, choice by choice, until the path ends.
It’s read-only, so exploring is safe. To change a rule, go back to the survey, edit it, and reopen the survey path simulator.
Where a survey path simulator earns its keep
A screener on a paid sample.
Picture a market research agency fielding a screener-heavy study on a panel sample. The project lead filters to terminated routes and reads each screen-out against the client brief. One route removes a group the brief says to keep. It gets fixed before any sample is spent.
A tracker between waves.
An FMCG brand in the US runs the same tracker every quarter, edited by several people. After a change to an early answer option, the research manager reruns the survey path simulator. Any block cut off from the main flow shows up as unreachable before the wave closes.
A CX follow-up.
A telecom CX team asks promoters and detractors different follow-up questions. The program manager isn’t a survey programmer, and doesn’t need to be. They step through a detractor’s path and see the exact questions that person would get, no rule syntax required.
A survey you inherited.
A client sends over a questionnaire, or a colleague leaves behind a tracker, and nobody can fully explain the logic. Open the map, click the branch markers, read the branching reasons. That beats auditing rules one question at a time.
When you can skip the survey path simulator
Not every survey needs a map. If yours is linear, with no branching, preview is all you need. The survey path simulator also shows what is possible, not what happened, so use your reports to see how many respondents took each route. For logic that depends on open text, date, rank-order or card-sort answers, a clean result is a strong check, not a guarantee. Those conditions count as possibly true.
How to run the survey path simulator in QuestionPro
- Open your survey in the editor and click the survey path simulator button in the toolbar, next to preview. Unsaved edits are saved first.
- Choose a starting question from the dropdown.
- Turn on compare all paths to see every route, then filter with the tabs: all, completed, terminated or unreachable question.
- Click any branch marker to read its rule, or switch compare all paths off to step through one respondent’s path.
- Fix what you find in the editor, then reopen the survey path simulator to confirm.
Make it a habit: run it before every publish and after every logic change. Rename key routes, like the screen-outs, so reviewers can find them fast. The help file on the survey path simulator walks through each screen.
Get started
Testing survey logic doesn’t have to mean another afternoon of clicking. Try the survey path simulator on your next branching survey or create a free account and start your trial. Open the map before your respondents do.
Frequently asked questions
A survey path simulator reads your survey’s branching rules and maps every route a respondent could take, including how each route ends. It also flags questions that no respondent can reach. Because it works from your logic rather than live responses, you can use it before fieldwork starts.
Preview shows the single path your answers create, so you only test the routes you think to try. A survey path simulator shows all routes at once, with outcomes and reasons, and highlights questions that never appear. Preview still helps you judge wording and feel. Use preview for the experience, the survey path simulator for the structure.
List every screen-out and branch in your project brief. Check each one against the full set of routes, not just the ones you click through, and confirm every question can be reached. In QuestionPro, the survey path simulator does this checking for you. Rerun it after every logic change, since small edits can disconnect later sections.
No. The flow diagram is visual, and clicking any branch marker shows the rule behind it. A CX program manager, an analyst or a client reviewer can follow a respondent’s path without reading rule syntax. You still decide what the logic should do. The survey path simulator shows you what it currently does.
Run the survey path simulator before you publish for the first time, and again after any change to skip logic, show/hide rules, or block flow. It also pays off when you inherit a survey, receive a client questionnaire, or update a tracker between waves.
Yes. Filter the routes to terminated, and you get every screen-out in one list, which you can read against your screener criteria and project brief. If a route removes people the brief says to keep, you see it before any sample is spent.
