---
sourceDocument: Yokohama Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/build-workflows

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Add and configure a stage in a playbook

# Add and configure a stage in a playbook {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Add and configure a stage in your playbook.

## Before you begin

Role required: playbook.admin or pd_author

Review [Stages and activities](https://www.servicenow.com/docs/OWzZoeyDfPk1aB7Mqjn5hw "In Playbooks, an activity represents one step in your overall business process. You can sequence many activities together in the stages of your process.").

## Procedure

1. Add a stage.

   | View | Steps |
   | Diagram | 1. Select the + icon after the trigger to add the first stage in your playbook. 2. In the mini-picker, select the dotted square icon. ![Square dotted stage icon in Diagram view mini-picker.]() {#add-configure-stage__ol_cwq_3rr_d1c} |
   | Board | In Board view, click + Add stage. |
   |-|-|

   {#add-configure-stage__choicetable_z1g_1yz_21c}  
   Your new stage appears, and the Stage properties panel opens.
2. Fill in the following fields.
   1. Provide the basic details of the stage.  

      |-|-|
      | Label | Enter a unique, user-facing name for your stage. This name appears to agents and fulfillers during runtime of your playbook. |
      | Description | Optionally, enter some descriptive details about your stage. |
      | Run condition | After the stage starts, the stage runs only if specific conditions are met. |
      | Start Rule | Choose when you want your stage to start running. Options include: * When process starts: Your stage starts running as soon as the playbook starts. * After specific stages: Your stage starts running after specified stage(s) have finished running. {#add-configure-stage__ul_cz4_5fv_21c} |
      [Table 1. Required inputs]

      {#add-configure-stage__table_zcq_mfv_21c}
   2. **Optional:** Show additional options in the activity for [even more granular control](https://www.servicenow.com/docs/x8Ot8uOvmzstO0cpvmeclA "Display detailed instructions to guide end users through your playbook.").  
      Warning:  
      Changing the advanced property fields of an activity can potentially break your automation. Make sure you understand how the playbook and its activities flow before you make changes.

   {#add-configure-stage__substeps_vmf_ffv_21c}

   | Option | Description |
   | Display order | When there are multiple stages running 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 activities in Diagram view. |
   | Start with delay | Specify a duration of time to wait before running an stage whose start rule and conditions have been met. For more information, see [Start with delay input properties](https://www.servicenow.com/docs/ZO5_TxRewwK7XqnX5otC7A "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."). |
   |-|-|

   {#add-configure-stage__choicetable_ffz_mct_vlb}
3. Click Save and close to finish adding the stage to your playbook.  
   You can continue to add more stages to your playbook and fill in fields as described in the previous steps. In the Board view, use the Stage actions menu ![Stage actions menu]() to add stages between existing stages.  
   Stages are created.

## What to do next

[Add and configure your activities.](https://www.servicenow.com/docs/eH66_4Re8HXK8adZ1kzWiw "Add and configure an activity in your playbook.")
**Related concepts**   

* [Activity definitions](https://www.servicenow.com/docs/r014Lhz_11xoMRZZRHOzcA "Activity definitions describe how the activities in your playbook get the data that they need when your playbook runs.")
* [Automation Assets](https://www.servicenow.com/docs/mU389THCpCX6TcjWJLTNJg "Include all automation assets in the activity picker to add a subflow, flow, or action directly to your playbook without having to create an activity definition.")
* [Optional activities](https://www.servicenow.com/docs/pJEY3EDh5wh5XlpPOIG19Q#optional-activities "Enable your agents and fulfillers to add additional activities as they go through a playbook.")
* [Playbook activity state mapping](https://www.servicenow.com/docs/fmXbaKoPUaBr1Y8dpLJFYA "Use playbook activity state mapping to override the status of a playbook card.")  
**Related tasks**   

* [Add and configure an activity in a playbook](https://www.servicenow.com/docs/eH66_4Re8HXK8adZ1kzWiw "Add and configure an activity in your playbook.")
* [Decision activities](https://www.servicenow.com/docs/4rX5cqI_FXRlYNq~tfDHiQ "Create and define branches with different conditions for different paths that an agent can follow in playbook.")
* [Parallel branches](https://www.servicenow.com/docs/PNev5QskKuGUAmoIHUw0fQ "Add branches for activities and stages that run in parallel to another branch of activities and stages.")
* [Add dynamic inputs to an activity](https://www.servicenow.com/docs/8XnLc2y4MM0hKIntwpZR5A "Configure your activity to show a certain set of fields based on the value of another input, such as a selected catalog item, selected decision table, or even a REST API response.")  
**Related reference**   

* [Start with delay input properties](https://www.servicenow.com/docs/ZO5_TxRewwK7XqnX5otC7A "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.")
* [Questionnaire activity](https://www.servicenow.com/docs/0Zhk1Qtvq62no8BNvPsGbQ "Collects inputs from a user during a playbook run to use later in the playbook.")

