# Which survey platforms let you set up branching logic so questions actually change based on how people answered earlier ones?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">For a piece I'm putting together on<a class="a a--md" elv="true" href="https://www.g2.com/categories/survey"> </a><a class="a a--md" elv="true" href="https://www.g2.com/categories/survey">survey software</a>, I'd like to understand which platforms let you set up branching logic so questions actually change based on how people answered earlier ones. On paper, most tools mention conditional logic. In practice, the quality varies a lot, some make it genuinely easy to build branching paths without a developer, others require you to map logic manually in a way that breaks the moment someone answers unexpectedly.</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">From G2 reviews where branching logic comes up specifically:</p><ul>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/surveymonkey/reviews"><strong>SurveyMonkey</strong></a><strong>:</strong> Reviewers describe routing respondents to different questions based on answers, which keeps surveys shorter and more relevant. Some specifically called out skip logic as the thing that stopped everyone answering everything. Advanced skip logic does sit behind higher-tier plans though.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/typeform/reviews"><strong>Typeform</strong></a><strong>:</strong> Conditional logic that adapts the form based on a user's answers is consistently described as the standout feature. Reviewers specifically call out more personalized form flows and better response quality as the result. </li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/jotform/reviews"><strong>Jotform</strong></a><strong>:</strong> Comes up for teams needing conditional logic across different question types including custom fields. Drag-and-drop interface makes it accessible without technical setup.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/questionpro/reviews"><strong>QuestionPro</strong></a><strong>:</strong> Well regarded for complex survey logic including branching, piping, and display conditions. Tends to come up more in research contexts where the logic tree needs to be deep. Does the branching builder stay manageable when you have 20+ branches?</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/alchemer-survey/reviews"><strong>Alchemer Survey</strong></a><strong>:</strong> Surfaces for teams needing advanced branching logic with custom scripting. More powerful than most, but reviewers note the learning curve is steeper.</li>
</ul><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Which of these has held up for a genuinely complex branching setup? Would love to know where the logic editor broke down for anyone.</p>

##### Post Metadata
- Posted at: 3 months ago
- Author title: Marketing Executive
- Net upvotes: 1


## Comments
### Comment 1

&lt;p&gt;Ask the platform team what happens when respondents do things you didn&#39;t anticipate. The quality of a branching tool isn&#39;t really measured by how good your planned paths are, it&#39;s how well it handles the paths you didn&#39;t plan.&lt;/p&gt;

##### Comment Metadata
- Posted at: 12 days ago
- Author title: Marketing Executive



### Comment 2

&lt;p&gt;A separate thing branching does, which catches people on the analysis side: every question ends up with its own denominator. If only the 40 percent who said yes to Q3 ever saw Q4, then Q4&#39;s percentages are of that subset, not of respondents. That&#39;s fine as long as the export distinguishes not-shown from shown-and-skipped from answered-blank, and not every export does. When those three collapse into one empty cell, you can&#39;t tell whether a low response rate means people avoided a question or never saw it, and those mean opposite things. So alongside the logic map, I&#39;d ask to see a raw export from a branched survey before buying, since that&#39;s the artifact you&#39;ll actually live in. QuestionPro coming up for deep logic trees makes this more relevant rather than less, because the deeper the tree, the more denominators you&#39;re carrying.&lt;/p&gt;

##### Comment Metadata
- Posted at: 13 days ago
- Author title: Tech Consultant



### Comment 3

The build is rarely where branching fails. Maintenance is. Insert one question into a live survey and every branch pointing &quot;after Q7&quot; can silently re-target, and a broken branch doesn&#39;t throw an error; respondents just flow to the wrong place and you discover it in the data weeks later. Which makes the feature worth asking about here not the logic builder, but whether the platform gives you a full visual map of every path so you can audit the tree after each edit.

##### Comment Metadata
- Posted at: 3 months ago
- Author title: Tech Consultant





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4