> For the complete documentation index, see [llms.txt](https://docs.catchify.sa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catchify.sa/portal-guide/pentest-management/pentest-statuses.md).
# Pentest Statuses
This is your guide to understand your pentest status.
You can track every pentest in Catchify using status labels. Each status reflects the current stage of the engagement and who is responsible for the next action.
* **Requested** – You’ve submitted a request and are discussing the scope, timeline, and budget
* **Quoted** – Catchify has reviewed your request and shared a proposal including cost, testing duration, and start availability
> You can approve the quote, suggest changes, or hold off until you're ready
* **Scheduled** – The pentest has been approved and is locked in to begin on a specific date
* **Onboarding** – Project kickoff begins. Asset access, permissions, and environment handoff take place
* **In Progress** – The pentest is underway. You’ll receive updates as findings are discovered
* **Remediation** – Findings are delivered. Your team can begin remediation and request retesting
* **Offboarding** – Final review, report handoff, and scheduling for future tests
* **Done** – The pentest is complete and closed
* **Canceled** – The request or project was canceled before or during execution
***
Status
---
# 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.catchify.sa/portal-guide/pentest-management/pentest-statuses.md?ask=&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.
