> For the complete documentation index, see [llms.txt](https://help.cabi.org/pest-risk-analysis-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cabi.org/pest-risk-analysis-help/getting-started/pra-stages.md).

# PRA stages

The tool is structured around the three stages of Pest Risk Analysis:

#### [Stage 1: Initiation](/pest-risk-analysis-help/pathway-initiated-pra/introduction.md)

Identifying the reason for the PRA and the pest(s) of concern to the PRA area

#### Stage 2: Risk assessment

Determining the likelihood of entry, establishment, spread and potential consequences of an individual pest in order to determine whether it meets the criteria of a regulated pest

#### Stage 3: Risk management

Selecting the appropriate management options to reduce the risks identified in Stage 2.


---

# 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://help.cabi.org/pest-risk-analysis-help/getting-started/pra-stages.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.