> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation/schedule/engagement-status.md).

# Engagement Status

The engagement status reflects the lifecycle stage and comprises six values labeled with color coding throughout the module. 

<div align="left"><figure><img src="https://4252973360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXA6EayCcg12qfDcfXd%2Fuploads%2FjrY0xc83FS239E8bRWDT%2Fimage.png?alt=media&amp;token=f728f5a7-1d47-4cde-81b8-f50c1d948a96" alt=""><figcaption></figcaption></figure></div>

## Status Mappings

Below are the different status states for a report and engagement, the relationship mapping, and any additional notes. Some of the engagement status values are tied to the status of the associated report.

<table><thead><tr><th width="190">Report Status</th><th width="258">Resulting Engagement Status</th><th>Notes</th></tr></thead><tbody><tr><td><em>(not applicable)</em></td><td>Pending</td><td>This status indicates the engagement has been requested but not approved.</td></tr><tr><td>Draft</td><td>Scheduled</td><td>This status indicates that the engagement has been approved and is slated to begin later.</td></tr><tr><td>Draft</td><td>In Progress</td><td>This status reveals that an approved engagement start date has been reached. <br><br>The status will move automatically to <code>In Progress</code> on the start date based on queries that run every hour.</td></tr><tr><td>Ready for Review</td><td>In Review</td><td>This status reveals that the report associated with the engagement is in one of the three view stages.</td></tr><tr><td>In Review</td><td>In Review</td><td>This status reveals that the report associated with the engagement is in one of the three view stages.</td></tr><tr><td>Approved</td><td>In Review</td><td>This status reveals that the report associated with the engagement is in one of the three view stages.</td></tr><tr><td>Published</td><td>Complete</td><td>This status reveals that the report associated with the engagement has been published.</td></tr><tr><td><em>(not applicable)</em></td><td>Canceled</td><td>This status indicates the engagement was terminated.</td></tr></tbody></table>


---

# 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.plextrac.com/plextrac-documentation/product-documentation/schedule/engagement-status.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.