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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Update the planning dependencies

# Update the planning dependencies {#ariaid-title1}

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

Update the plan dependencies manually from the snapshot if the scheduled job is not activated in the Planning dependency update configuration module. You can update the dependencies in an active plan.

## Before you begin

Role required: sn_bcm.program_manager, sn_bcm.planner, sn_bcm.admin

## Procedure

1. Navigate to WorkspacesBusiness Continuity Workspace.
2. Open a BCP in the Draft state and navigate to the Scope tab.  
   If the dependencies have been updated in the sources, the scheduled job fetches the dependencies. You can select the snapshot record to view the updates.
3. To view the snapshot record, select the Pending updates module in the Planning list view and select a snapshot record.  
   The Plan dependency delta snapshot is displayed.

   The BCM application stores one active snapshot for the BCP at a time. The snapshots that are in the Completed state and that have not been updated in
   the past six months are removed from the application automatically.
4. To update the dependencies manually, navigate to the plan and select Update dependencies.  
   A UI message is displayed on the screen: Dependencies are being updated.
5. To save the changes to the plan, select Save.  
   The plan owners and BCM lead can update the planning dependencies by saving the changes to the plan.
{#import-cmdb-updates-in-bcp__steps_ybr_nxy_mzb}

*[\>]: and then


