Creating action items in crisis events
Summarize
Summary of Creating action items in crisis events
Starting with BCM release 9.0.x, crisis managers can create ad-hoc action items during open crisis events or exercises without needing to map them to event assets or recovery plans. These action items allow real-time task assignments to recovery members or teams and are independent of the event recovery timeline.
Show less
Key Features
- Real-time task assignment: Crisis managers can assign tasks such as injury verification, plan reviews, or situation assessments during a crisis or exercise.
- Action item details: Each task includes fields like actual start/end dates, total time taken, due date, description, type, and assignment details.
- Task states: Action items progress through states—Open, Work in progress (auto-captures start time), Skipped (marked irrelevant, zeroes time), and Closed (auto-captures end time).
- Assignment flexibility: Tasks can be assigned to groups, individual users, or additional assignees.
- Distinct from event tasks: Unlike event tasks, action items have no dependencies or automated workflows, do not roll up time to plans or assets, and are not ordered automatically.
Roles and Permissions
- Plan owners: Can create, read, update, and delete action items if they own the event.
- Program managers: Have full action item management rights across all events.
- Viewers: Can read all action items.
- Recovery event/plan owners: Can read and update action items assigned to them.
Practical Use and Integration
Action items support task and assessment types and can integrate with Smart Assessment for streamlined crisis event management. They empower crisis managers to assign ad-hoc tasks rapidly without impacting the formal recovery timeline, facilitating agile response and assessment during crises.
Starting with BCM release 9.0.x, crisis managers can create action tasks for recovery members or teams anytime during open crisis events or exercises. Crisis managers can create these tasks on the fly without mapping them to event assets or recovery plans. These action tasks are also not included in the event recovery timeline.
Action items in real-time
Action items can be used to assign tasks in real-time. For example, a crisis manager can assign an action item to verify that there are no injuries at a specific office location after an exercise. They can request someone to review the business continuity plan before proceeding to the next steps.
You can also use action items to conduct assessments during a crisis event. For example, in the event of a fire, you can assign an action item to assess the situation, determining the severity, and identify affected employees and buildings. You can perform an assessment and assign an action item.
Fields and states associated with Action items
- Actual start date
- Actual end date
- Total time taken
- Event (Reference)
- Short description
- Description
- Due date
- Task numbers
- Type
- Task
- Assessment
| State | Description |
|---|---|
| Open | First state of the action item. |
| Work in progress | State of the action item when its work begins. When an action item moves to the Work in progress state, the system auto-captures its start time. |
| Skipped | Assigned state of the action item when it is not relevant. When an action item is skipped and considered not relevant, its time fields are removed, resulting in a total time of 0. |
| Closed (complete, incomplete) | Final state of the action item task. When an action item has been completed, the system auto-captures its end time. |
BCM managers or planners can update the action items and can reopen the ad-hoc tasks associated with them.
- Assignment group
- Assigned to
- Additional assignee list
Comparison between event tasks and action items
The action items are distinct from the event tasks in crises and events. The table outlines the differences between event tasks and action items.
| Fields/Criteria | Event task | Action items |
|---|---|---|
| Details |
|
|
| Assignment |
|
|
| Access |
|
|
| Workflow | Pending -> Open -> Work in progress -> Skipped -> Closed (complete, incomplete, failed) | Open -> Work in progress -> Skipped -> Closed (complete, incomplete) |
| Dependencies | Yes | No |
| Automation | Yes | No |
| Orders | Yes, order is auto-calculated based on dependencies. | No, order is not calculated for the action item tasks. |
| Time calculation | Yes, the event tasks time is rolled up to activated plans, and impacted assets. | No, the event tasks time is not rolled up for the action item tasks. |
Roles associated with action items
The roles associated with action items are described in the table.
| Role | Description |
|---|---|
| Plan owner | Can create, read, update, and delete action items when the plan owner is the event owner. |
| Program managers | Can create, read, update, and delete action items for all events. |
| Viewers | Can read all action items. |
| Recovery event/Plan owner | Can read and update all action items that they are assigned to. |