> 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/starting-a-pest-risk-analysis.md).

# Starting a pest risk analysis

The tool has two workflows for PRA. The one you choose depends on the reason for conducting the analysis.

### By Pathway

For example: a request to import onions from South Africa to Zambia.

1. Identify the pests that are associated with the pathway
2. Conduct a risk assessment for all the major pests that may be introduced to the risk area via this pathway

{% content-ref url="/pages/NweJ5u9ryubEeyPipq93" %}
[Pathway-initiated PRA](/pest-risk-analysis-help/pathway-initiated-pra/introduction.md)
{% endcontent-ref %}

### By Pest

For example: risk of red palm weevil (*Rhynchophorus ferrugineus*) for Ghana

1. Identify the potential pathways for pest entry to the risk area
2. Assess the likelihood of introduction of the pest via each pathway. Then continue the single pest risk assessment

{% content-ref url="/pages/EEwql7A1xwLFO1m4Qw0R" %}
[Pest-initiated PRA](/pest-risk-analysis-help/pest-initiated-pra/introduction.md)
{% endcontent-ref %}


---

# 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/starting-a-pest-risk-analysis.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.