> 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/supplier-diversity/buyer-diversity-performance.md).

# Buyer Diversity Performance

The Buyer Diversity Performance report summarizes how often your buyers invite diverse suppliers to their request for quote events.

<figure><img src="https://1711751134-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F95QWDcOsKn95Me8sE2RP%2Fuploads%2FWJU4tVHStVPUyxp1nUY4%2Fsd-buyer-div-perform_thumb_0_350.png?alt=media&amp;token=dbe220f2-7e9a-4201-a008-ecb61bd331c7" alt=""><figcaption></figcaption></figure>

Buyer Name: Displays the name of the buyer assigned to the event.

Total RFQs with Diverse Suppliers: Displays the total number of request for quote events where a diverse supplier was invited.

Total RFQs:Displays the total number of request for quote events that have been opened. This includes closed, awarded, and canceled events.If you drill into this value, you can review and download a summary of the buyer's included events. This includes the Full Name, Opened at Date, Lowest Bid, and Quotations.

% of RFQs with Diverse Suppliers: Displays the percentage of request for quote events where a diverse supplier was invited. This value is calculated for request for quote events as events with diverse *suppliers / total number of opened events.*


---

# 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/supplier-diversity/buyer-diversity-performance.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.
