Use cases for business continuity planning

  • Release version: Xanadu
  • Updated July 31, 2025
  • 4 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 Use Cases for Business Continuity Planning

    The Business Continuity Management application facilitates various use cases to help organizations develop effective business continuity plans. These use cases can be implemented individually or combined to align with specific requirements, ensuring preparedness for events like ransomware attacks that disrupt critical services.

    Show full answer Show less

    Key Features

    • Create a standardized recovery plan: Helps mitigate risks during an event by outlining action items such as assets, activities, and recovery teams. Plans progress through states from Draft to Archived.
    • Update dependencies in the plan: Enables users to configure affected assets, monitor Recovery Time Objective (RTO), Recovery Point Objective (RPO), and identify gaps when assets are down.
    • Configure the dependencies for the plan: Allows custom configurations for asset dependencies, including sources from the CMDB and notification settings for users and groups.
    • Create documentation: Provides templates for documenting goals and objectives necessary for the plan.
    • Create recovery teams: Identifies teams responsible for executing recovery plans during crises.
    • Monitor loss scenarios: Facilitates the creation of crisis scenarios to include in the plan, helping to prepare for specific risks.
    • Submit for Approval: Standardizes the approval process by configuring groups, users, or rules for plan approval.
    • Generate PDF: Summarizes plan details in a PDF format, allowing for customization through templates and scripts.
    • Copy Plan: Enables users to duplicate existing plans and their details.
    • Add related plan: Facilitates the inclusion of related plans to enhance plan comprehensiveness while avoiding cyclic task issues.
    • Task execution order: Supports both parallel and sequential task management based on dependencies within a plan.

    Key Outcomes

    Implementing these use cases allows ServiceNow customers to efficiently prepare for and respond to disruptions. With a structured approach to business continuity planning, customers can enhance their resilience, minimize downtime, and ensure critical services remain operational during emergencies.

    This section describes the common use cases that are used for business continuity planning in the Business Continuity Management application. You can deploy these use cases individually or you can combine them to meet your specific needs.

    You can build your business continuity plan based on your recovery strategy, partners, teams, tools, and processes that are needed to implement the plan.

    Consider the example of a ransomware attack on a financial corporation. The attack may disrupt critical services such as utilities, transportation, payments, and so on. If a business continuity plan is in place, the emergency IT consultants and professionals can take the following preventive actions:
    • Shut down the IT services.
    • Restore the services from the disaster data recovery component in the plan.
    • Control the damage by moving the essential data servers to an off-site location.

    Typical use cases for Business Continuity Planning

    Table 1. Typical BCP use cases
    Use case name description Roles Actions for the use case
    Create a standardized recovery plan

    BCP helps you enact and mitigate risk at the time of an event by addressing action items such as plan assets, activities, recovery teams, documentation, policies, and procedures.

    The plan record will go through a cycle of states before:

    • Draft -> In review -> Pending approval -> Approved -> Archived
    • In the Pending approval state, plan can be rejected back to Returned state.
    		 BCM Planner, BCM Manager, BCM Admin User creates a plan
    Update dependencies in the plan Update dependencies in the plan:

    1. Allows users to view and configure the assets that are affected within the plan

    2. Monitor the RTO, RPO, and Recovery Tier of each asset and identify any gaps/risks when the asset is down

    3. View the relationship of the primary assets and related assets

    		 BCM Planner, BCM Manager, BCM Admin

    User selects Update dependencies button.

    2. Scheduled job Update BCP dependencies snapshot is executed.
    Configure the dependencies for plan

    Provide configurations for users to configure what dependencies they want for plans including:

    1. Configure the sources that they want to pull in from their dependencies including CMDB, BIA downstream, BIA upstream
    2. Choose whether they want to pull the last updated record or all records from the source
    3. Configure the users, and groups that they want to notify via emails
    4. Configure what plan's fields will be updated every time they update the dependencies
    5. Configure what type of plans the configurations should be applied to
    		 BCM Admin

    User creates or updates records by navigating to

    All -> Planning dependency update configuration
    Create documentations Provides a section and templates for the user to document the goals, objectives, and scopes that are required within the context of the plan. BCM Planner, BCM Manager, BCM Admin

    User creates a plan using a plan template with document sections defined.

    2. User selects Create new section in the Documentation tab.
    Create recovery teams Defines the teams responsible for executing the plans during the recovery process. It is currently used in recovery tasks BCM Planner, BCM Manager, BCM Admin User selects New button in the Recovery teams related list.
    Monitor the loss scenarios of the plan Create crisis scenarios that can be included in your plan (for example, Loss of Datacenters or Vendor disruption) and add assets dependencies or recovery strategies to the loss scenarios. BCM Planner, BCM Manager, BCM Admin

    User creates a plan using a plan template with Loss scenarios defined.

    2. User selects Add in the Loss scenarios tab.
    Submit for Approval Create approval configurations including groups, users, or rules to standardize the approval process BCM Planner, BCM Manager, BCM Admin User selects Submit for approval.
    Generate PDF

    Summarize the details of the plan (scopes, asset dependencies, related plans, recovery teams, recovery tasks) in a PDF format.

    2. Allows users to write scripts and format the PDF through document templates, and document scripts.

    		 BCM Planner, BCM Manager, BCM Admin User selects the Generate PDF button.
    Copy Plan Copy existing plans including their details and related lists BCM Planner, BCM Manager, BCM Admin User selects the Copy button.
    Add related plan Add related plan relationship to plan's related list. BCM Planner, BCM Manager, BCM Admin User adds a related plan.
    Avoid creating cyclic tasks for the same plan while adding plan dependencies. Stop processing same plan if its already part of the hierarchy. Avoid creation such plan dependencies during planning phase. Verify that plan dependency in recovery task doesn’t create a cycle. BCM Planner, BCM Manager, BCM Admin User adds an activated plan to the plan recovery task.
    Task execution order Tasks under a plan can be parallel and sequential based on the task dependencies. Therefore, the tasks in a plan should be ordered. BCM Planner, BCM Manager, BCM Admin User adds recovery tasks