---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Decision stages

# Decision stages {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Create and define branches with different conditions for different paths between stages.

## Before you begin

Role required: playbook.admin

## About this task

Add a decision node between stages to determine which stage to run next, based on runtime conditions. For example, in a recruitment playbook, you can have multiple stages for each interview round and
one disqualification stage. After each interview stage, you can add a decision to automatically select whether to run the next interview round or proceed to disqualification based on the completed stage.  
Adding decision between stages help you achieve the following benefits:

Simplified authoring
:   Reduces the need to copy run conditions across stages.

Improved transparency
:   Makes branching logic more visible and easier to manage.

Enhanced runtime experience
:   Displays only the relevant stages to the end user, improving performance and clarity.

## Procedure

1. In Diagram view, select the + icon.
2. From the mini-picker, select the diamond icon ![Diamond decision icon in Diagram view mini-picker.]() to add a decision.  
   A decision is added with two branches and the side panel opens for configuration.
3. Under the Details tab, fill in the following fields.  
   {#create-decision-stage__table_jpj_mfx_c1c__entry__2}

   | Field | Description |
   |-|-|
   | Label | Enter a unique name for the decision. |
   | Description | Enter some descriptive details about the decision. |
   | Start Rule | Choose when you want to evaluate the decision. Options include: * When playbook starts: The decision starts running as soon as the playbook starts. * After specific stages: The decision starts running after specified stages have finished running. {#create-decision-stage__ul_cz4_5fv_21c} |
   [Table 1. Decision details]

   {#create-decision-stage__table_jpj_mfx_c1c}
4. **Optional:** Select Show additional options to specify the following optional fields:  
   {#create-decision-stage__table_ajv_h3m_2hc__entry__2}

   | Field | Description |
   |-|-|
   | Display order | When multiple stages run at the same time, define the order in which stages appear during a playbook run. Note: In Workflow Studio, this can also be helpful when viewing parallel stages and activities in Diagram view. |
   | Start with delay | Specify a duration of time to wait before running a stage whose start rule and conditions have been met. For more information, see [Start with delay input properties](https://servicenow-prod.fluidtopics.net/EdInaaLAHZCnrBcJbs96Lw "Specify a duration of time to wait before running an activity or a stage whose start rule and conditions have been met. Give users time to act during automated playbooks. Give users time to wait for a specific date and time to complete actions."). |
   | Restart rules | Choose what this activity does when a playbook is restarted: * Skip on restart: Skip this stage when the run is due to a restart. * Run always: Always run this stage, including first runs. * Skip on first run: Skip this stage during the first run. {#create-decision-stage__ul_z2n_lqs_rzb}For more information, see [Configure restart for Playbooks](https://servicenow-prod.fluidtopics.net/fDTysgsDrbJu17~DEIy2tg "Configure restart so that agents and fulfillers in Playbook Experience can restart a playbook from the beginning, or from a specific stage or activity."). |
   [Table 2. Additional options]

   {#create-decision-stage__table_ajv_h3m_2hc}
5. Under the Branches tab, select your new branch to begin configuring it.
   1. Give your branch a unique label.
   2. Select the Add Condition button.  
      The [condition builder](https://www.servicenow.com/docs/access?context=c_ConditionBuilder&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US) displays.
   3. Select or enter a field, operator, and value.
   {#create-decision-stage__substeps_jr4_x1x_c1c}
6. Add more branches as needed.  
   Branches can only be added via the side panel.
7. If you add two or more branches, select whether to process all branches with conditions that are met, or just to process the first listed branch with conditions met.
8. If you selected to Process only the first one that is true, drag and drop the branch that you want to be evaluated to the top.
9. Select Save and close.
{#create-decision-stage__steps_qtg_kgg_cgc}

## Result

You've added and configured decision branches between stages.

## What to do next

Complete and test the playbook. For more information, see [Test a playbook](https://servicenow-prod.fluidtopics.net/_N5PlzezzLZda1P_VEeEBQ "Verify that your playbook works as expected by running the playbook with test trigger data. Identify and resolve all errors before activating your playbook.").