> 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/managing-business-impact-analyses-apps/creating-and-managing-bias.md).
# Creating & Managing BIAs
Perform tasks assigned to your role to advance requests through the BIA Management workflow.
## Workflow Overview
The **BIA Management** workflow governs the creation, completion, and review of Business Impact Analyses (BIAs).
{% hint style="danger" %}
Following approval, BIAs are evaluated against the [configured eligibility criteria](/interfacing-help-files/administration-and-configuration/configuring-application-settings/business-continuity-application-settings/criteria-for-sending-to-bcp.md) for inclusion in operational plans. Eligible BIAs become available when creating Business Continuity Plans (BCPs), Disaster Recovery Plans (DRPs), and Crisis Management Plans (CMPs).
{% endhint %}
***
## Interactive Tour
Explore the **BIA Management** workflow and learn how each stage works, with key guidance and best practices along the way.
{% @howdygo/embed url="" %}
***
## Workflow Stages
The workflow is organized into **four key stages**, each with specific roles and responsibilities.
{% hint style="success" %}
For detailed instructions on any stage, click the corresponding button.
{% endhint %}
{% stepper %}
{% step %}
### Request BIA
> **Performed By:** Requestor (e.g., Department Manager, Project Manager, Business Unit Director)
**Responsibilities**:
* Identify the business process that requires a BIA.
* Assign the BIA to the appropriate analyst.
* Verify the process information and request details.
* Submit the request to initiate the workflow.
***
{% endstep %}
{% step %}
### Complete BIA
> **Performed By:** Assigned Analyst (e.g., Process Owner, Subject Matter Expert, Business Continuity Coordinator)
**Responsibilities**:
* Review the business process and its supporting information.
* Assess alternative workarounds, recovery requirements, and recovery objectives (RTO/RPO).
* Evaluate the financial, non-financial, and disaster impacts of a disruption.
* Submit the completed BIA for review.
***
{% endstep %}
{% step %}
### Review BIA
> **Performed By:** Requestor (e.g., Department Manager, Project Manager, Business Unit Director)
**Responsibilities**:
* Review the completed BIA for accuracy, completeness, and alignment with business requirements.
* Evaluate the assessment, recovery objectives, and impact analyses.
* Provide feedback if revisions are required.
* Approve the BIA or return it to the analyst for modification.
***
{% endstep %}
{% step %}
### Modify BIA
> **Performed By:** Assigned Analyst (e.g., Process Owner, Subject Matter Expert, Business Continuity Coordinator)
**Responsibilities**:
* Review the feedback provided by the reviewer.
* Update the BIA to address requested revisions or additional information.
* Resubmit the BIA for review.
{% hint style="warning" %}
This stage is triggered only if the reviewer returns the BIA for modification.
{% endhint %}
***
{% endstep %}
{% endstepper %}
***
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://interfacing.gitbook.io/interfacing-help-files/business-continuity/managing-business-impact-analyses-apps/creating-and-managing-bias.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
