> 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/evaluation-and-scoring/evaluate-a-scorecard.md).
# Evaluate a scorecard
After the evaluation period ends, you can evaluate a summary of responses from all invited evaluators to help you award your event. If an evaluator did not complete their scores, they are not included in the final score calculation.
### Access scorecard
1. Open your event, and select the **Details** page.
2. At the top of the page, click **View Scorecard**.
### Review scorecard
From the Scorecard window, you can view a **summary of scores** from all evaluators. For each section, you can expand to view how each evaluator responded to the section and line items (if enabled) and review any notes they added. The highest score overall and for each section is highlighted in green. Additionally, the top three responses will be marked.
Scoring scale
| Score name | Score value |
| ----------- | ------------ |
| 5 Excellent | 5 |
| 4 Good | 4 |
| 3 Average | 3 |
| 2 Fair | 2 |
| 1 Poor | 1 |
| Decline | Not included |
#### Section score
The section score is calculated as *Total evaluator score SUM / total available points*.
#### Total supplier score
The total supplier score is calculated as *Section weight x total section score*.
### Download scorecard to PDF
* From the Scorecard window, click **Download PDF**.\
A summary of your scorecard is generated and opened in PDF format.
---
# 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/evaluation-and-scoring/evaluate-a-scorecard.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.
