> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/form-designer/questions/question-properties/question-branching.md).
# Question Branching
## ๐ฒWhat is question branching ?
The question branching features let you define [conditions](/form-management/form-designer/condition-rules.md) that will redirect the user to a given question based on his answers. This allows you to change and control the flow of your survey dynamically based on the respondent answers.
{% hint style="warning" %}
Question branching is only available on surveys having the [single question flow ](/form-management/form-designer/form-settings/single-question-flow.md)mode enabled.
{% endhint %}
## โ Adding a question branching
Branching must be added on the [question properties](/form-management/form-designer/questions/question-properties.md) that will trigger the branching or in a more visual way using the [flow logic graphs](/form-management/flow-logic-graph.md).
## ๐ Branching properties
Here we have set the current question to branch to "Q.3" if the condition is met. If the condition is not met ngSurvey will show the next question being after the current question based on their display order in your survey.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ngsurvey.com/form-management/form-designer/questions/question-properties/question-branching.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
