---
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


---

# Add a task to the crisis event

# Add a task to the crisis event {#ariaid-title1}

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

Add a task to the crisis event in BCM UIB Workspace. You can then monitor and complete the required actions to respond to the crisis event.

## Before you begin

Role required: sn_bcm.planner, sn_bcm.program_manager

## About this task

Users with an edit access to the event record can edit the fields in the recovery tasks list simultaneously:

* State
* Assigned to
* Actual start
* Actual end
* Assigned group

{#add-event-task-to-crisis-event__ul_qnf_2mf_3bc} For more information, see [Structured workflows for Crisis events](https://servicenow-prod.fluidtopics.net/qVDuVO8cStA86qBBiGQkpQ "Manage crisis events using structured workflows in the Business Continuity Workspace (also known as BCM Configurable Workspace).").

## Procedure

1. Navigate to WorkspacesBusiness Continuity Workspace.
2. In the List view, navigate to Crisis eventsPending and select the crisis event in the list.
3. Select the Event tasks tab.  
   Note:  
   For the crisis events, the event type is Actual.  
   When you add or update the plan to the crisis event, the related plans, assets, and event tasks that are associated with the plan also get pulled into the event.
4. To add event tasks in bulk from a task template group, on the Event tasks tab select More ActionsAdd groups.  
   The Select task template groups dialog opens as a two-step wizard. In step 1, select one or more groups. In step 2, select the activated plan that the new event tasks should be associated with. Step 2 is skipped when you invoke Add groups from the Event tasks tab of an activated plan, because the activated plan is already known.

   The dialog filters groups by Active = true. Filters that are currently applied to the Event tasks list --- for example, Phase = Recovery validation --- are applied as default values on the created tasks. Phase values that are already set on a task template take precedence over the list filter.

5. To add individual task templates without a group, on the Event tasks tab select More ActionsAdd tasks.  
   The Select task templates dialog uses the same two-step wizard and the same filter rules as Add groups.

6. After the bulk add completes, wait for the auto-refresh banner to dismiss, or select Refresh to refresh the Event tasks list manually.  
   The Event tasks list does not auto-refresh row by row. Instead, the banner The event tasks are updated. Select Refresh to see updated data. List will auto-refresh once all tasks are created. is displayed while the system creates the tasks. About ten seconds after the last task is created, the list refreshes once. This avoids repeated refreshes on event tasks lists that contain a large number of rows. For more information, see [Event task creation progress in exercise and crisis events](https://servicenow-prod.fluidtopics.net/TK0Tpuu0HRAcib9C4EF~oQ "When event tasks are created in bulk from task template groups or task templates, the Event tasks list defers refresh to avoid impacting large events. This topic explains the banner and auto-refresh behavior.").

7. To save a set of crisis event tasks as a reusable task template group, select the tasks in the Event tasks list and then select Save as groupSave tasks.  
   To append them to an existing group, you can select Save as groupAdd to group. Event tasks are saved as task templates that can be applied to crisis events, exercise events, activated plans, plans, loss scenarios, or recovery strategies. The element definition associated with
   each event task is preserved on the resulting templates so element-definition filtering still applies when the group is reused.

8. To add an ad-hoc task to the event, select New ad-hoc task.  
   Note:  
   An ad-hoc task is added to the crisis event so that you can take corrective actions for the crisis event. When you add an ad-hoc task to the crisis event that is in the Work in progress state and if the activated plan is in the Work in progress state, the tasks will be in the Open state. If the activated plan is in the Pending state, the task will be in the Pending state.
   For more information on the fields in the New Event Task form, see [Create Event Task form](https://servicenow-prod.fluidtopics.net/XsoPklYFWaexu~WymhuYMA "Use the Create New Event Task form in BCM UIB Workspace to add details about an event task.").  
   Note:  
   You cannot create an ad-hoc task for the activated plans that are in Closed Complete or Closed Incomplete state.
9. To start the crisis event, select Start Event.  
   After you start the event, the event state is updated to Work in Progress.  
   Note:  
   If the event task has a circular dependency, you have to trigger the tasks manually for this event.
10. Select the first task and select Trigger.
11. Complete all the activated plans of the event tasks for the crisis event and select Submit for Approval.
12. To generate a PDF, select Generate PDF.  
    If you have edit access to the crisis event, you can save a copy of the event in PDF format to your local hard drive.  
    Note:  
    By default, the PDF is generated and attached after the event is closed.
13. Navigate to the Results section on the Details tab and update the Actual start and Actual end dates for the event task.
14. Update the assignment fields, if necessary.
15. Enter any event task-related information in the Work notes field of the Activity section.
16. Select Save.
17. Select the refresh icon (![Refresh icon.]()) to display the updated state of the asset or plan, and the actual time taken to recover the asset.
{#add-event-task-to-crisis-event__steps_bb1_l2p_xxb}

*[\>]: and then