> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/business-continuity/developing-business-management-plans-apps/creating-and-managing-plans/create-new-plan.md).
# Create New Plan
Create and submit a new operational plan to initiate the Plan Creation & Approval workflow.
## Workflow Overview
:location-dot: **Current Task:** Create New Plan
:user: **Performed By:** Plan Owner (e.g., Department Manager, Process Owner, Business Continuity Coordinator)
IMAGE
***
## Completing the Form
Use one of the following forms to create a new operational plan, depending on the type of plan required:
* **New Business Continuity Plan**
* **New Crisis Management Plan**
* **New Disaster Recovery Plan**
IMAGE
{% hint style="danger" %}
#### Plan Type Determines Available Tabs
The tabs displayed in the **New Plan** form vary depending on the type of operational plan being created.
* Business Continuity Plan (if the **New Business Continuity Plan** module is selected)
* Crisis Management Plan (if the **New Crisis Management Plan** module is selected)
* Disaster Recovery Plan (if the **New Disaster Recovery Plan** module is selected)
{% endhint %}
{% hint style="success" %}
For guidance on common form features and functions, see [**Working with Forms**](/interfacing-help-files/end-users/exploring-apps/working-with-forms.md).
{% endhint %}
***
{% stepper %}
{% step %}
### Define General Information
Establish the plan’s framework by defining its key details, ensuring proper tracking and management.
#### 1.1 Basic Information
Provide the information needed to identify and manage the plan throughout its lifecycle.
* **Plan Name:** Enter a descriptive name that clearly identifies the operational plan.
* **Effective Date:** Select the date when the plan becomes active or applicable.
* **Plan Reviewer:** Select the user, role, or group responsible for reviewing the plan.
━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Read-Only Fields** (🔒)
* **Creation Date:** The date the plane was created.
#### 1.2 Targeted Scope & Coverage
Define the organizational scope of the plan.
* [**Site:**](#user-content-fn-1)[^1] Select the site or location that the plan will cover.
{% hint style="warning" %}
Once a site is selected, the grid in the [**Asset Priority**](#id-1.4-asset-priority) accordion will automatically populate with all assets assigned to that site.
* Assets are linked to sites in the [**Asset Management**](/interfacing-help-files/administration-and-configuration/configuring-application-settings/business-continuity-application-settings/asset-management.md) module.
{% endhint %}
* [**Business Division:**](#user-content-fn-2)[^2] Select the primary functional unit (department) associated with the plan.
* Selecting a division filters the options shown in the **Business Line** field.
* [**Business Line:**](#user-content-fn-3)[^3] Select the specialized unit within the selected division
{% hint style="danger" %}
#### Plan Versioning & Duplicate Plans
Each plan must have a unique combination of **site**, **business division**, and **business line**.
* If a new plan with the same attributes as an existing plan is submitted, the user is notified and given two options:
* **Cancel the new plan**
* **Create a new version of the existing plan**
When a new version is created, the original plan’s details are copied over, allowing users to update the information before submitting it for approval.
* The original plan remains active until the new version is approved and its effective date is reached.
* If the new version is not approved by the effective date, the original plan stays active, and the reviewer is notified via email.
{% endhint %}
#### 1.3 Relevant Documents
Assign supporting documents to the plan, providing essential context and reference materials.
IMAGE
To assign documents, follow these steps:
* **Select Folder**
* In the **Select a Document Folder** field, click the :angle-down: icon to open a form displaying a tree structure of document folders.
* Double-click the desired folder to select it.
* **Select Documents**
* Once a folder is chosen, its child items populate the grid below.
* Check the **Selected** box for each item you want to assign.
Tip: Use Select All to select all items in the grid, or Deselect All to clear all selections.
Confirm deletion by clicking Save Changes or clicking outside the grid. To cancel, click Discard Changes or Undelete ( :xmark: ).
IMAGE
To review an asset’s details, click the **View** (  ) icon.
#### 1.5 Related Plans
Link related plans that support or interact with the current plan, ensuring alignment across different contingency strategies.
{% hint style="danger" %}
#### Related Plan Linking Rules
The available linking options depend on the type of plan being created:
* **BCP:** Can be linked to related **DRPs** or **CMPs**.
* **DRP:** Can be linked to related **BCPs** or **CMPs**.
* **CMP:** Can be linked to related **BCPs** or **DRPs**.
Each type of related plan is managed in a separate grid within the application. While these grids function independently, they share similar features, which are described collectively below to avoid redundancy.
{% endhint %}
IMAGE
Click **Add** to add a related plan.
Select Plan(s)
The **Select Plan(s)** form allows users to select and link related plans to the current plan.
IMAGE
1. **Access Plans**
* In the **Select Plan(s)** field, use one of the following methods:
* Enter the name of an approved and active plan and select it from the dropdown.\
→ If used, proceed to Step 4.
* Click the :angle-down: icon to open the **Active Plan(s)** form and view all approved and active plans.
2. **Locate Plan**
* Locate the relevant plan in the list.
3. **Select Plan**
* Double-click the plan to select it.
4. **Assign Plan**
* After selecting an plan, choose:
* **Save and New:** Click to assign the selected plan and open a new form to add another.
* **Save and Close:** Click to assign the selected plan and close the form.
Added entries appear in the grid, where they can be removed by clicking **Delete** ( :trash-can: ).
{% hint style="info" %}
Confirm deletion by clicking **Save Changes** or clicking outside the grid. To cancel, click **Discard Changes** or **Undelete** ( :xmark: ).
{% endhint %}
***
{% endstep %}
{% step %}
### Review Business Impact Analyses
Review all active and approved Business Impact Analyses (BIAs) for critical business processes. Use these analyses to identify recovery priorities, operational dependencies, and the potential impact of business disruptions.
IMAGE
{% hint style="danger" %}
For a BIA to appear in this tab, it must meet the criteria outlined in the [**Criteria for Sending to BCP**](/interfacing-help-files/administration-and-configuration/configuring-application-settings/business-continuity-application-settings/criteria-for-sending-to-bcp.md) module, specifically achieving a total score and financial impact that meet or exceed the defined thresholds.
{% endhint %}
***
{% endstep %}
{% step %}
### Develop Operation Plan
Develop the operational plan by completing the information required for the selected plan type.
#### :business-time: Business Continuity Plan
Develop a comprehensive and actionable Business Continuity Plan (BCP) to ensure the continued operation of critical business functions during and after a disruption.
IMAGE
* **Plan Components:** Use the available fields to define and document key elements of the plan.
* **Summary:** Provide an overview of the plan, including its purpose and key considerations.
* **Terms and Definitions:** Define key terminology used throughout the plan to ensure clarity.
* **Purpose and Goal / Objective:** State the plan’s primary objectives and intended outcomes.
* **Scope:** Specify the coverage of the plan, including affected departments, locations, processes, and dependencies.
* **Roles and Responsibilities:** Identify key personnel responsible for executing the plan and outline their specific duties.
* **Policy:** Establish guidelines and principles governing the implementation and maintenance of the plan.
* **Alert Plan for Regular Business Hours:** Outline notification and escalation procedures for disruptions occurring during standard working hours.
* **Alert Plan for After Hours:** Outline procedures for disruptions occurring outside standard working hours.
* **Response Strategy:** Define the approach for mitigating the impact of the disruption, ensuring continuity of critical operations.
A response strategy focuses on stabilizing the situation and maintaining essential business functions during a disruption, distinct from a recovery strategy, which addresses full restoration after the disruption is under control.
IMAGE
* **Plan Components:** Use the available fields to define and document key elements of the plan.
* **Crisis Recovery Plan:** Document the approach for restoring operations after the crisis.
* **Information Services Backup Procedures:** Specify backup and recovery procedures for critical systems.
* **Crisis Recovery Procedures:** Outline the steps to be followed during crisis recovery.
* **Prevention Strategies:** Define measures to reduce risks and prevent the crisis from occurring again.
* **Response Strategies:** Describe actions to be taken in response to the crisis.
* **Summary:** Provide an overview of the plan, including its purpose and key considerations.
* **Actions Overview:** Review the approved actions for the CMP.
{% hint style="danger" %}
Only actions classified under the **Crisis Management** (**CM**) type appear in this grid.
* Actions are defined and managed in the [**New Action Item**](/interfacing-help-files/business-continuity/managing-action-items-apps.md#working-with-action-items) module.
{% endhint %}
{% hint style="info" %}
To view an action’s details, click the **View** (  ) icon.
{% endhint %}
#### :arrows-rotate: Disaster Recovery Plan
Develop a comprehensive and actionable Disaster Recovery Plan (DRP) to ensure the rapid restoration of IT systems, data, and infrastructure after a disaster or significant disruption.
IMAGE
* **Plan Components:** Use the available fields to define and document key elements of the plan.
* **Summary:** Provide an overview of the plan, including its purpose and key considerations.
* **Terms and Definitions:** Define key terminology used throughout the plan to ensure clarity.
* **Purpose and Goal / Objective:** State the plan’s primary objectives and intended outcomes.
* **Scope:** Specify the coverage of the plan, including affected departments, systems, applications, and physical locations.
* **Roles and Responsibilities:** Identify key personnel responsible for executing the plan and outline their specific duties.
* **Policy:** Establish guidelines and principles governing the implementation and maintenance of the plan.
* **Alert Plan:** Outline notification and escalation procedures for disasters occurring during or outside regular business hours.
* **Recovery Strategy:** Define the approach for restoring operations after a disaster, focusing on the recovery of IT infrastructure, data integrity, and system functionality.
A recovery strategy focuses on achieving full operational restoration after a disaster has been contained, distinct from a response strategy, which prioritizes immediate stabilization and continuity during a disruption.
IMAGE
* **Communication Strategy:** Outline the overall communication approach, including communication methods, protocols, and any relevant tools or systems.
#### 4.1 Emergency Contacts
Manage emergency contacts associated with the plan.
* **Assign Responsibility**
* Use the **Emergency Contacts Responsible** dropdown to select the person or role responsible for managing these contacts.
* **Assign Contacts by Disaster Type & Location**
* For each active disaster type and location combination, use the **Emergency Contacts** grid to enter the following details:
* **When to Contact:** Specify the conditions when this contact should be reached (e.g., immediately upon disaster occurrence).
* **Contact:** Select the primary contact.
The following fields populate automatically after selecting and saving a contact:
- Full Name: The full name of the selected contact.
- Phone Number: The contact’s primary phone number.
- Email: The contact’s email address.
- Address: The contact’s physical address.
