> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/analytics/buyer-analytics/total-rfqs-by-status-per-buyer.md).

# Total RFQs by Status per Buyer

The Total RFQs by Status per Buyer report summarizes the total number of request for quote events for each buyer. For each buyer's bar, you can view a color-coded display of their number of events in Draft, Opened, Closed, Awarded, Canceled, and Archived status for the filtered time period. Buyers are ordered by their number of request for quote events. To be included, a buyer must have created at least one request for quote event in the dashboard's filtered time period.

[See Event status (Buyers) ](https://docs.fairmarkit.com/glossary/glossary/event-status-buyers.md)for more information on the available statues for request for quote events.

| Data                                          | Description                                                                                                                                                                                                                                                                                        |
| --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p>Total Draft RFQs<br>(yellow)</p>           | <p>Displays the buyer's number of request for quote events in Draft status.</p><p>If you drill into this value, you can review and download a summary of events included. This includes the RFQ ID (with Link), Request ID, Created at Date, Status, Title, Requester Title, and Full Name.</p>    |
| <p>Total Currently Opened RFQs<br>(green)</p> | <p>Displays the buyer's number of request for quote events in Opened status.</p><p>If you drill into this value, you can review and download a summary of events included. This includes the RFQ ID (with Link), Request ID, Created at Date, Status, Title, Requester Title, and Full Name.</p>   |
| <p>Total Currently Closed RFQs<br>(blue)</p>  | <p>Displays the buyer's number of request for quote events in Closed status.</p><p>If you drill into this value, you can review and download a summary of events included. This includes the RFQ ID (with Link), Request ID, Created at Date, Status, Title, Requester Title, and Full Name.</p>   |
| <p>Total Awarded RFQs<br>(purple)</p>         | <p>Displays the buyer's number of request for quote events in Awarded status.</p><p>If you drill into this value, you can review and download a summary of events included. This includes the RFQ ID (with Link), Request ID, Created at Date, Status, Title, Requester Title, and Full Name.</p>  |
| <p>Total Canceled RFQs<br>(gray)</p>          | <p>Displays the buyer's number of request for quote events in Canceled status.</p><p>If you drill into this value, you can review and download a summary of events included. This includes the RFQ ID (with Link), Request ID, Created at Date, Status, Title, Requester Title, and Full Name.</p> |
| <p>Total Archived RFQs<br>(red)</p>           | <p>Displays the buyer's number of request for quote events in Archived status.</p><p>If you drill into this value, you can review and download a summary of events included. This includes the RFQ ID (with Link), Request ID, Created at Date, Status, Title, Requester Title, and Full Name.</p> |


---

# 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.fairmarkit.com/buyers/analytics/buyer-analytics/total-rfqs-by-status-per-buyer.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.
