> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/cyber-best-practices/manage-a-cyberattack/bcp-drp.md).

# BCP/DRP

The **Business Continuity & Disaster Recovery Plan** is a template you fill in to prepare your company for a major IT outage or cyberattack, so you can keep operating and recover quickly.

The document has two parts:

* **Part 1, the framework:** written by Stoïk and the same for every insured company. It explains how to analyze your risks, organize crisis governance, operate in degraded mode, communicate, and maintain the plan. It is not meant to be edited.
* **Part 2, your plan:** the tables and forms you complete with your own specifics (contacts, priority risks, critical activities, recovery objectives, IT recovery procedures). This is the part you activate during a crisis.

{% hint style="info" %}
**Download the document:** the BCP/DRP template is available in Word (`.docx`), in English, French, German, Dutch and Spanish, on our drive: [BCP/DRP template on Google Drive](https://drive.google.com/drive/folders/1XsDBoDOeXViLE4t6Y7iMPDLt7y3LgU4t?usp=drive_link)
{% endhint %}

## Why download it

* A plan that exists and gets used beats a perfect plan forgotten in a drawer.
* It makes you decide in advance, and calmly, what matters most and who does what, instead of improvising mid-crisis.
* It has to stay available even when all your IT systems are down, which is only possible if you have prepared and printed it beforehand.

## What to do with it

1. Download the template.
2. Fill in each `[bracketed field]` with your company's specifics.
3. Print it and store an offline copy in a location accessible even when your systems are down.
4. Review it at least once a year, and after any significant IT change.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stoik.io/cyber-best-practices/manage-a-cyberattack/bcp-drp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.