> 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/events/review-supplier-responses/response-quickview.md).

# Response QuickView

With Response QuickView you can automatically receive an email with AI-generated summaries of supplier responses when your request for proposal and request for information events close. Additionally, you can easily generate and download these summaries in PDF format directly from your event page.

{% hint style="info" %} <mark style="color:purple;">Contact your Fairmarkit Customer Success Manager to enable this feature.</mark>
{% endhint %}

<figure><img src="https://1711751134-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F95QWDcOsKn95Me8sE2RP%2Fuploads%2Fv0oDXkIaBGAtE6YhnsLl%2FScreenshot%202026-08-25%20at%208.29.57%E2%80%AFAM.png?alt=media&amp;token=f5bed10c-72c3-43f9-8662-9e7c411b500c" alt=""><figcaption></figcaption></figure>

<figure><img src="https://docs.fairmarkit.com/content/buyers/images/event-quick-view_thumb_0_0.png" alt=""><figcaption></figcaption></figure>

### How does it work? <a href="#howdoesitwork" id="howdoesitwork"></a>

Response QuickView uses AI to automatically generate a summary of supplier responses for an event. Based on the structure of your event, the process provides a summary of each supplier's response to each section of your event. Additionally, if the supplier provides any text-based attachments, they will be included in the section summary.

### How can I optimize my event? <a href="#howcanioptimizemyevent" id="howcanioptimizemyevent"></a>

To ensure the best summary of supplier responses, use the following best practices:

#### Use Fairmarkit Structure

Build your event using the event sections, questions, and sub-questions in Fairmarkit. The process uses your event structure to build and generate the summary of supplier responses. Information added via attachments and outside of this framework will likely not be included in the summary.

#### Organize your questions

Arrange your questions so that each section can stand alone. Avoid referencing questions or information in other sections.

#### Write detailed questions

Make questions specific and descriptive, preferably in the form of questions that suppliers can easily respond to.

#### Text-based attachments

Recommend suppliers to only attach text-based file formats (e.g., .txt, .pdf, .docx, etc.). Non-text-based files will not be included in the summary.

### When will I receive my summary? <a href="#whenwillireceivemysummary" id="whenwillireceivemysummary"></a>

When a request for information or request for proposal event with supplier responses closes, Response QuickView is automatically generated and emailed to the event owner.

### Can I manually run Response QuickView? <a href="#canimanuallyrunresponsequickview" id="canimanuallyrunresponsequickview"></a>

Yes, from the Events list or the event Details screen, you can generate Response QuickView (if it wasn't automatically generated) or you can download a copy of the PDF file.

<figure><img src="https://1711751134-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F95QWDcOsKn95Me8sE2RP%2Fuploads%2FjbdCXNVsClergU0MZ3m9%2FScreenshot%202026-08-25%20at%208.30.47%E2%80%AFAM.png?alt=media&amp;token=8659025d-61cb-4c5a-9e90-a7e6430e5c93" alt=""><figcaption></figcaption></figure>

#### Generate summary

<figure><img src="https://1711751134-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F95QWDcOsKn95Me8sE2RP%2Fuploads%2F3JahjLmbTC94824WHJP2%2FScreenshot%202026-08-25%20at%208.27.51%E2%80%AFAM.png?alt=media&amp;token=2d30ec55-378f-4ace-bf01-d8d58029ea34" alt=""><figcaption></figcaption></figure>

* From the Events list or the event Details screen, select **Actions > Generate Summary**.\
  A message displays, letting you know that the file will be emailed after it is generated.

#### Download summary

<figure><img src="https://1711751134-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F95QWDcOsKn95Me8sE2RP%2Fuploads%2FDnEjfgKQq8KR0oAcMruq%2FScreenshot%202026-08-25%20at%208.31.20%E2%80%AFAM.png?alt=media&amp;token=3844150a-c4ef-41a1-a9a1-8d69bd8e7c1d" alt=""><figcaption></figcaption></figure>

* From the Events list or the event Details screen, select **Actions > Download Summary**.

<br>


---

# 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/events/review-supplier-responses/response-quickview.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.