---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Define the scope and dependencies

# Define the scope and dependencies {#ariaid-title1}

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

Define the scope of the Scenario analysis by selecting the service to analyze and adding the dependencies that support it during a disruption.

## Before you begin

Role required: sn_oper_res.admin, sn_oper_res.manager

## About this task

The Scope step consists of two sub-steps: adding a service and adding dependencies. Both sub-steps must be completed before advancing to the next playbook step. Once the Dependencies sub-step is marked
complete, the selected dependencies cannot be changed.

## Procedure

1. Navigate to AllOperational ResilienceScenario Analysis and open the scenario analysis record form.
2. In the Playbook stage panel, select Scope, then select Services.
3. To open the Select Services dialog, select Add.  
   An information banner is displayed in the Select Services dialog.  
   Note:  
   Only one service can be added as shown in the example; to change it later you must create another scenario analysis record.
4. Browse or search by Name, Owner, Business Criticality, Operational Status, or Class.  
5. Select the service, then select Add.  
   The service appears in the Services table with its Impact Tolerance columns populated. Because you can add only one service, the Remove button for the service becomes inactive after the service
   is added.
6. Select Continue to advance to Dependencies.
7. In the Playbook stage panel, select Dependencies under Scope.
8. Choose the source of dependencies from the picker, then select dependencies, and select Add.
   1. Use Selected dependencies to scope the analysis to the existing dependency map.  
      This is the default option. It lists only the dependencies already related to the service that is in the scope.
   2. Use All dependencies option when you need to bring in a dependency that is not yet related to the service.  
      It lists every dependency available in the instance, regardless of whether it is related to the selected service.

   The selection pop-up is paginated and shows the columns Name, Owner, Class, Appetite status, and Pillar. Filter
   and sort controls are available. Selections made across multiple pages are retained when you select Add.
9. Review the list to confirm that all critical dependencies are included.  
   Each row shows the Dependency name and its Pillar, for example Processes (Account Opening Workflow, Account Closure Handling, Closure Request Handler) or Application Services
   (Core Banking Portal). A warning banner is displayed on the Dependencies step: Once you complete this step, the selected dependencies cannot be changed.
10. Select Mark as complete.  
    Note:  
    Once you mark this step as complete, the selected dependencies cannot be changed.  
    The Scope step shows a completed status in the stage panel.

## Result

The Scope step is complete. The selected service and its dependencies are locked and are used for scenario testing.

## What to do next

To add scenarios and review reference data such as incidents, see [Add scenarios and review reference data](https://servicenow-prod.fluidtopics.net/LDFYOCAqxOAjOX9JkpvTAA "Select the adverse-event scenarios to test against the scoped service, then review the historical reference data that the system will use to auto-populate simulation inputs.").

*[\>]: and then