> 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/onboarding/claims/action-plan.md).

# Action plan

Follow the action plan of your claim in Stoïk Protect, and tell Stoïk's CERT where you stand on each action without sending an email.

## Open the action plan

1. In Stoïk Protect, go to `Claims` and open the claim.
2. Open the `Action plan` tab.

Until the CERT has shared the plan, the tab shows: "Your action plan will appear here once Stoïk's CERT has shared it."

## Read the plan

Each row is one action, with:

* `Status`: `To do`, `In progress` or `Done`.
* `Priority`: from P1 (most urgent) to P3.
* `Action`: the name of the action.
* `Description`: what to do, with the details written by the CERT.
* `Type`: `Investigation`, `Remediation`, `Legal` or `Communication`.
* `Owner`: who carries out the action.

Actions are listed in the order set by the CERT. You can search, filter by status, priority, owner or type, and sort any column.

## Update the status of an action

1. Click the status badge of the action.
2. Pick `To do`, `In progress` or `Done`.

The new status shows at once and is sent to the CERT, along with who changed it. If the update fails, the previous status comes back and an error message tells you why.

## When the plan changes

The CERT keeps the plan up to date during the incident. Their changes appear the next time you open the tab. The plan stays available after the claim is closed.

{% hint style="info" %}
The action plan cannot be downloaded as a PDF from this tab yet. The CERT still sends it by email.
{% endhint %}

For any question on an action, write to <cert@stoik.io>.


---

# 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/onboarding/claims/action-plan.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.
