Structured workflows for Crisis events

  • Release version: Australia
  • Updated March 12, 2026
  • 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 Structured workflows for Crisis events

    This content explains how ServiceNow's Business Continuity Management (BCM) Configurable Workspace helps BCM program managers manage crisis events through structured workflows. Crisis events represent significant disruptions threatening business operations. The workspace enables managers to create and coordinate crisis events by associating impacted assets, business continuity plans, and recovery strategies, then assigning and managing tasks for effective response and recovery.

    Show full answer Show less

    Key Features

    • Create and Manage Crisis Events: Users can start crisis events, classify severity, prioritize, assign teams, and document initial response actions within the BCM Configurable Workspace.
    • Track Impacted Assets and Related Plans: Monitor affected assets and link relevant recovery plans to ensure comprehensive recovery efforts.
    • Add and Bulk Edit Event Tasks: Tasks can be added individually or in bulk via task templates. Starting from BCM version 6.1.x, users with edit access can bulk update fields such as state, assignee, and dates directly from the Event tasks list, streamlining task management.
    • Event Task State Management: The system supports defined state transitions for event tasks (e.g., Pending, Open, Work In Progress, Closed states). Users can open, close, skip, or re-trigger tasks based on permissions and task status, with validations to prevent invalid transitions.
    • Recovery Task Member Interaction: Recovery members, even without access to the full event workspace, can update task statuses via the "My Recovery Tasks" interface, adding activity notes but with limited form field editing once tasks are closed.
    • Automated Task Import and Use: Automated tasks from business continuity plans can be imported and utilized during actual events to improve response efficiency.
    • Action Tasks and Task Grouping: Crisis managers can create unscheduled action tasks for recovery teams during open events, and group similar or duplicate tasks to reduce redundancy and optimize task management.
    • Approval Workflow: The BCM workspace supports requesting and approving crisis events to formalize response actions.
    • Nested Plans and Dependencies: System properties enable automatic creation of nested plans within an event, reducing manual effort and improving performance. Dependencies between plans can be defined within event tasks.

    Practical Benefits for ServiceNow Customers

    • Efficient coordination and tracking of crisis response efforts through structured workflows and centralized management.
    • Improved task management with bulk editing, automated task imports, and clear state transitions that ensure accurate status updates and accountability.
    • Enhanced flexibility by allowing recovery team members to update task progress without full event access, facilitating collaboration across roles.
    • Reduced manual effort and errors by automating plan activation and grouping similar tasks, leading to faster and more organized crisis handling.
    • Formalized approval processes to validate and document crisis event management steps, supporting compliance and auditability.

    Manage crisis events using structured workflows in the Business Continuity Workspace (also known as BCM Configurable Workspace).

    Business Continuity Management (BCM) program managers create crisis events to coordinate response efforts. They associate relevant assets, business continuity plans, and recovery strategies with each event, then assign and submit event tasks to appropriate teams for execution.

    Bulk editing of tasks from the Event tasks related list

    Starting with version 6.1.x of the Business Continuity Management application, users who have editing access to the event record can now perform bulk edits on tasks directly from the Event tasks related list. This feature is beneficial for users who manage multiple event tasks simultaneously.

    In the recovery tasks list, users with the necessary edit permissions can modify these fields simultaneously:
    • State
    • Assigned to
    • Actual start
    • Actual end
    • Assigned group

    Once an event is initiated, these users can also modify the state of an event task either from the list view or the form view. The process for updating the state of an event task from the list view is demonstrated in the example. If a state transition is not allowed, an error message is displayed to indicate that the update is invalid.

    Bulk edits.
    The table details the permitted state transitions for an event task.
    Table 1. Permitted state transitions for an event task
    Transition from state Pending state Open state Work In Progress state Closed Complete state Closed Incomplete state Closed Skipped state Closed Failed state
    Pending No Yes No No No Yes No
    Open No No Yes No No Yes No
    Work In Progress No Yes No Yes Yes Yes Yes
    Closed Complete No Yes No No No No No
    Closed Incomplete No Yes No No No No No
    Closed Skipped No Yes No No No No No
    Closed failed No Yes No No No No No
    Note:
    All changes to state transitions and updates to the start or end dates are listed in the Task activity log.

    Consider these key details about the state transitions of an event task.

    1. The event task can only be opened from the Closed complete state.
    2. Once the event task moves to the Open state, users of the event task can edit it further.
    3. The task can then be moved from the Open state to the Closed Skipped state.
    4. Only users with access to the event can reopen the event task. While recovery task members can change the status of the event task, they cannot reopen it.
    The table summarizes the UI actions available for an event task and their corresponding states:
    Table 2. UI actions and the associated states of the event tasks
    UI action State of the event task Notes
    Trigger Pending This condition is applicable only when an event has been started.
    Skip task Pending, Open, Work in progress -
    Work in progress Open -
    Closed complete Work in progress -
    Closed incomplete Work in progress -
    Closed failed Work in progress -
    Re-trigger as a manual task Closed -
    Re-trigger automation Work in progress, Closed This condition is applicable for an automated task only.

    If a task is mistakenly closed, users of the event task can reopen it to make the required edits, ensuring the recovery process remains accurate and complete.

    Updating the event task as a recovery task member

    Generally, recovery task members update the status of event tasks. Although they do not have access to the event page or workspace, they can navigate to My Recovery Tasks in the instance to access the recovery task. By modifying the UI action, they can change the status of the event task, as demonstrated in the example.

    Update the state of the event task.

    For instance, when members of the recovery task mark the task as Closed complete, all fields on the form become locked. This implies that while members of the recovery task cannot modify the fields, they are still able to add activity notes. Only users who have access to the event task can edit the fields on the form.

    For information on importing the automated task in an event, see Import automated tasks and start an event.

    • For information on reporting a crisis event from the Home page, see Home page view.
    • For information on managing threats, feeds, and alerts in the Crisis map interface, see Crisis map interface.
    • For information on performing administrative tasks in the Crisis map interface, see Setup for Crisis map.