What is Branching Logic?
Branching logic (also called skip logic or conditional logic) shows or hides questions based on earlier answers so each participant only sees questions relevant to them. It creates personalised survey paths without needing multiple separate forms.
Branching logic is a setting you add to a questionnaire so later questions appear only when they apply. For example, if someone answers “Yes” to “Do you have children?” the survey can automatically show child-related questions; if they answer “No,” those questions stay hidden and the respondent moves on. Branching can use answers from single-choice, multiple-choice, numeric, date or text questions, and can reveal or skip single questions, whole sections, or end the survey early. It’s sometimes called skip logic, conditional logic or display logic.
Usage example
You create one community feedback form. Question 3 asks “Are you responding as a resident or as a service provider?” If the respondent selects “Resident,” the survey shows questions about satisfaction with local services. If they select “Service provider,” it instead shows questions about delivery challenges. In Hearo the same branching rules apply across every language so you don’t need separate forms for each community.
Practical application
Branching logic matters because it reduces respondent burden, improves data quality and increases completion rates: people don’t waste time answering irrelevant questions. For multilingual surveys it also keeps translations simpler — you maintain one survey and the logic drives which translated text each participant sees. Good branching supports clearer consent flows, tailored outreach, shorter mobile experiences, and more defensible consultations (different communities are asked only the questions that apply to them). Be sure to test each branch in every supported language and keep conditions simple to avoid confusion or hidden required items.
FAQ
Is branching logic the same as skip logic or display logic?
Yes. These terms are often used interchangeably. They all describe rules that show or hide questions based on earlier answers. Some platforms use slightly different names, but the effect is the same: conditional paths through a single survey.
Can branching logic depend on the respondent’s chosen language?
Yes. You can base branches on the language or any other answer the participant provides. In Hearo that means you can both show language-specific instructions and still keep one source survey — the platform handles showing the correct translated text for the branch automatically.
How complex should my branches be — are there downsides to deep nesting?
Keep branches as simple as possible. Deeply nested or highly interdependent conditions increase the risk of logic errors, hidden required questions, and make testing harder. Complex logic can also confuse respondents if they unexpectedly skip sections. If you need many tailored paths, consider splitting the survey into clearly signposted sections or using a short routing section at the start to direct people to the right path.
Will branching logic affect how responses in other languages are shown to me?
No — branching only controls which questions participants see. In Hearo participants can answer in their preferred language and admins will view responses translated back into their chosen review language. You should still test branches in each supported language to ensure translations preserve context that conditions rely on (for example, the exact wording used in a trigger question).