Structured workflows for BCPs

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Structured workflows for BCPs

    This content outlines the structured workflows for creating and managing Business Continuity Plans (BCPs) within the Business Continuity Workspace (BCM Configurable Workspace) in ServiceNow. It guides BCP owners through the process of using templates, adding assets, defining loss scenarios, recovery strategies, and generating documentation and reports. The workflows ensure a comprehensive, organized approach to business continuity planning and recovery execution.

    Show full answer Show less

    Key Features

    • Hierarchical Plan Structure: Introduced in BCM 9.x.x, this feature enforces a logical parent-child relationship between plans, enabling controlled and sequential execution of recovery tasks. It avoids circular dependencies, supports parallel task execution within plans, and ensures only relevant child plans execute during an event.
    • Nested Related Plans: Starting with the Xanadu release, improved management detects cyclic dependencies and refines recovery timelines, allowing precise tracking of planned versus actual recovery times across assets and tasks.
    • Reusable Templates: Recovery strategy and task templates enable planners to reuse common recovery structures, reducing repetitive work and improving consistency across plans.
    • Asset and Scope Management: Assets and their scope can be added to plans, ensuring accurate recovery focus and scope definition.
    • Task Management and Automation: Recovery tasks can be added, ordered, and visualized via Gantt charts for timeline clarity. Tasks can be automated by attaching automated flows, accelerating recovery efforts.
    • Phase Mapping: BCM administrators can define active phases and map recovery tasks to these phases to enforce logical sequencing of recovery activities.
    • Synchronization: Assets can be synchronized between plans, loss scenarios, and recovery strategies to maintain consistency and accurate recovery timelines.
    • Plan Approval and Reporting: BCPs can be submitted for approval and exported as PDF or Microsoft Word documents for record-keeping and stakeholder communication.
    • 360° Relationship Visualization: Users can access a comprehensive view of a BCP and its related entities at any time, facilitating better understanding and management of plan dependencies.
    • Auto-Update of Related Assets: Plans can be scheduled for automatic updates based on CMDB data and dependencies, with notifications sent to keep planners informed.

    Practical Application for ServiceNow Customers

    ServiceNow customers can leverage these structured workflows to streamline the creation and management of robust business continuity plans. The hierarchical plan structure and automated dependency checks reduce errors and improve recovery execution. Reusable templates and task automation save time and increase consistency across multiple plans. Visualization and reporting features support clear communication and oversight, while automated updates ensure plans remain current with underlying asset data. Overall, these capabilities enable efficient, controlled, and effective continuity planning and response within the ServiceNow BCM environment.

    Perform the structured workflows that are outlined in this section to create a business continuity plan in Business Continuity Workspace (also known as BCM Configurable Workspace).

    The business continuity plan owner creates plans using templates, adds assets and scope, creates documentation sections, adds recovery teams, defines loss scenarios with recovery strategies, and generates PDFs.

    Hierarchical plan structure enhancement

    Starting with BCM, version 9.x.x, the hierarchical structure of parent-child plans verifies logical organization and execution of recovery tasks. When an event is triggered, only relevant child plans are included, allowing plan execution and dependencies to cascade downward in a controlled manner.

    Parent plans are excluded to prevent the inclusion of unrelated scenarios that may require subsequent cancellation. This approach confirms that only relevant plans are considered, maintaining a focused and efficient recovery process.

    The system also performs cyclic dependency checks automatically, ensuring that the hierarchy flows uni directionally—from parent plans to child plans.

    Implementing the hierarchical plan structure offers these key benefits:
    • Logical task execution: Only after the necessary tasks in the parent plans have been completed, tasks in the child plans are executed, ensuring a controlled and sequential recovery process.
    • Avoidance of circular dependencies: The system is designed to prevent circular dependencies, maintaining a unidirectional flow from parent to child plans and avoiding potential conflicts.
    • Parallel execution: Tasks within the same plan can be executed in parallel when possible, optimizing recovery time and efficiency.

    By introducing this hierarchical structure, the system provides an organized and manageable approach to plan management, enhancing efficiency and effectiveness in disaster recovery planning and execution.

    Nested related plans

    Beginning with the Xanadu release, the handling of nested related plans has improved. This enhancement helps in managing potential cyclic dependencies by detecting and highlighting any problems that could cause cyclic dependencies during the execution of tasks.

    Additionally, the refined recovery timelines enable you to monitor the planned and actual timeframes. A task can be applied to all assets within a plan or to none, facilitating accurate aggregation of recovery timeframes across assets, tasks, and plans.

    Additional information on Business Continuity Planning