Skip to main content

Add decisions and conditional branches

Create answer choices and activate only the tasks that match the selected outcome.

Use a decision when the next tasks depend on an answer. For example, a startup process might ask whether a permit is required and include permit tasks only on the Yes path.

Before you begin: Use desktop with Editor or Administrator access to build branches. Answer decisions in the actual project or operation when doing the work.

Create the decision

  1. Open the Playbook process and add a row where the question belongs.

  2. Open the row's task-type menu and select Decision.

  3. Name the decision as a clear question.

  4. Choose Add answer and enter the possible outcomes, such as Yes and No.

Add tasks to the branches

  1. Add or move the conditional tasks inside the decision.

  2. Choose the answers that should activate each task.

  3. Review each branch in List or Flow view.

  4. Check for tasks shown as having no answer assignment.

A task can apply to more than one answer. A branch task without any assigned answer does not activate automatically when the decision is answered.

Understand what happens on a project

The Playbook defines the question and branches. When someone chooses an answer on an active project or operation process, the matching tasks become active.

If the answer changes, tasks from the previous branch become inactive and the matching branch becomes active. Previously recorded task data is retained rather than erased by changing the answer.

Keep the structure valid

  • Keep each decision at the main process level. Decisions cannot be nested inside another decision.

  • Place branch tasks under the correct decision.

  • Use answer labels that people can choose consistently.

  • Review branch mappings before removing or renaming answers.

Related article

Did this answer your question?