> For the complete documentation index, see [llms.txt](https://help.horsespot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.horsespot.com/product-docs/show-day-tools/entries/show-scratches.md).

# Show Scratches

{% embed url="<https://www.loom.com/share/8303131d6a5d42edaa700f5e39666c1d>" %}

## **Requesting and Reviewing Show Scratches**

Exhibitors can request and submit show scratches from their exhibitor account, sending them directly to the show secretary after their entry has already been submitted online.

## **Requesting a Scratch as an Exhibitor**

Every entry on the exhibitor side has an option to request a show scratch. Once an exhibitor submits one, they'll see that the scratch is being requested and is awaiting review by the show secretary.

## **Reviewing a Scratch as a Secretary**

On the secretary side, any entry with a pending scratch request will show up as updated to reflect that a show scratch has been requested. From there, the secretary can accept or reject the scratch based on the conditions of the horse show.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.horsespot.com/product-docs/show-day-tools/entries/show-scratches.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
