> 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/complete-bia/bia-scoring-framework.md).

# BIA Scoring Framework

Scoring criteria for BIA.

Each tab in the [**Complete BIA**](/interfacing-help-files/business-continuity/managing-business-impact-analyses-apps/creating-and-managing-bias/complete-bia.md) form is scored using the criteria described below.

#### Alternative Workarounds Tab

This tab contains several questions, but only the following four contribute to the overall score:

* **Does this process have a manual workaround?**
  * No = 5 points
* **Can this process be performed remotely?**
  * No = 5 points
* **Which locations are impacted by this process?**
  * One or More Locations = 5 points
* **If this process fails, can the customer access an alternate process?**
  * No = 5 points

***

#### RTO & RPO Tab

The selected **RTO** is scored as follows:

| RTO                   | Score      |
| --------------------- | ---------- |
| 0 Minutes             | 20 points  |
| 24 Hours              | 15 points  |
| 48 Hours              | 10 points  |
| 72 Hours              | 7.5 points |
| Greater Than 72 Hours | 5 points   |

The selected **RPO** is scored as follows:

| RPO                    | Score      |
| ---------------------- | ---------- |
| High Availability (HA) | 20 points  |
| Less than an Hour      | 15 points  |
| 1- 7 Hours             | 10 points  |
| 8 – 23 Hours           | 7.5 points |
| Over 24 Hours          | 5 points   |

***

#### Financial Impact Tab

Each financial impact level is assigned the following score:

| Impact Level | Score      |
| ------------ | ---------- |
| Very High    | 4 points   |
| High         | 3 points   |
| Medium       | 2 points   |
| Low          | 1 point    |
| Very Low     | 0.5 points |

The total **Financial Impact** score is the sum of the scores for all selected time intervals (e.g., 2 hours, 4 hours, 24 hours, 48 hours, and 72 hours).

***

#### Non-Financial Impact Tab

Each non-financial impact level is assigned the following score:

| Impact Level | Score      |
| ------------ | ---------- |
| Very High    | 0.8 points |
| High         | 0.6 points |
| Medium       | 0.4 points |
| Low          | 0.2 points |
| Very Low     | 0.1 points |

The total **Non-Financial Impact** score is the sum of the scores across all effect categories.

***

#### Disaster Impact Tab

Each disaster impact level is assigned the following score:

| Impact Level | Score    |
| ------------ | -------- |
| Very High    | 5 points |
| High         | 4 points |
| Medium       | 3 points |
| Low          | 2 points |
| Very Low     | 1 point  |

***


---

# 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/complete-bia/bia-scoring-framework.md?ask=<question>&goal=<endgoal>
```

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