> 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/score-an-event.md).
# Score an event
If you're an evaluator on an event, you can view or edit the event, allowing you to review all of the invited suppliers' responses and then score the event on the Scoring page. You can only score your assigned sections, and you cannot view other evaluators' scores. You cannot submit scores after the event is awarded, and incomplete scores are not included in the final scoring. Once you submit your scores, you cannot edit them. The evaluation start and end dates display at the top of the Scoring page. You will receive an email reminder if you still need to score your event 24 hours before the event closes.
### Score a section
* In the **Score** field for a section (row) and a supplier (column), select if the response was *Poor*, *Fair*, *Average*, *Good*, or *Excellent*.
### Score line items in a section
Note: You can only **score** individual line items in a section if it was selected by the event owner.
{% stepper %}
{% step %}
For a section, click **Score line items**. A window with the section line items displays.
{% endstep %}
{% step %}
In the **Score** field for a line item (row) and a supplier (column), select if the response to the line item was *Poor*, *Fair*, *Average*, *Good*, or *Excellent*
{% endstep %}
{% step %}
Click **Close**.
{% endstep %}
{% endstepper %}
### Decline to score a section
* In the **Score** field for a section (row) and a supplier (column), select *Decline*.
### Add a section comment
For each section, you can add a comment to explain the reason for your score or provide additional details to the event owner.
{% stepper %}
{% step %}
For a section (row) click the Comment  button.\
The add comment window displays.
{% endstep %}
{% step %}
Enter your comment, and click **Save**.
{% endstep %}
{% endstepper %}
### Score all sections and items
* In the **Apply to all sections and items** field for a supplier (column), select if the overall response was *1 Poor*, *2 Fair*, *3 Average*, *4 Good*, or *5 Excellent*.
### Decline to score the event
* In the **Apply to all sections and items** field for a supplier (column), select *Decline*.
### Submit your scores
After you have completed scoring all sections for each supplier response, you will need to submit your scores and comments to the event owner.
{% stepper %}
{% step %}
Click **Submit Scores**. A confirmation message displays. Once you submit your scores, you cannot edit them.
{% endstep %}
{% step %}
Click **Yes, Submit Scores**.
{% endstep %}
{% endstepper %}
---
# 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/score-an-event.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.
