> 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/managing-digital-signature-requests.md). # Managing Digital Signature Requests {% embed url="" %} ## **Sending and Tracking Signature Requests** ### Sending Requests in Bulk Once you have entries accepted into your horse show, select those entries and use Bulk Actions to send signature requests to everyone involved on each entry. Each person receives an email prompting them to sign wherever a signature is needed on any entry they're part of. There's also a button at the top of the entries screen to quickly send signature requests to anyone on an entry who hasn't received one yet. ### Managing Requests from the Verifications Pop-Up After requests go out, use the verifications pop-up to manage their status. Signature requests appear as missing until the individual completes them. Hover over any status bubble to see the email it was sent to and its current status. From this same pop-up, you can resend a request or even update the email address it was sent to. ### What Exhibitors See When someone receives a signature request, they'll get an email letting them know documents need their signature for an upcoming horse show. Clicking the link takes them to a Horse Spot page where they can review and sign everything, using a single button at the top to sign all documents in one flow. Exhibitors can also access their signature requests directly from their Horse Spot account by going to their shows, selecting the relevant horse show, and opening the entry. This gets them to the same signature requests, whether they arrived there from the email link or from their account. ### Tracking Completion As people complete their signature requests, their status updates in the verifications pop-up. Once everyone required on an entry has signed, that entry shows a green checkmark, both in the verifications pop-up and on the main entries screen, letting you know at a glance that it's ready for competition. {% embed url="" %} ## **Setting Up Your Signature Requirements** ### Choosing Your Document Type Before sending any requests, configure your digital signature settings for each horse show. Go to Settings > Public Experience and scroll down to the signature documents section. You'll see two options: liability waiver, recommended for most horse shows since it collects a single waiver per participant rather than repeat signatures across every entry, and entry agreement, only needed if you're running a USEF-licensed show that requires signatures on an official USEF entry blank. If you open this dropdown and don't see any options available, reach out to the Horse Spot team so we can get your waivers uploaded on the back end. ### Sending Signature Requests Once your settings are saved, sending signature requests works the same way for every horse show: use Bulk Actions > Send Signature Requests to send them to all entries at once, or open an individual entry's verification pop-up to send or manage a request on a single entry. Hovering over a pending request shows the exact date and time it was sent, and who it was sent to. ### The Exhibitor Experience On the exhibitor side, the experience is the same regardless of which document type you've configured: they'll receive an email with a link to sign, or they can access the same signature request through their Horse Spot account. Once they finish signing, the request clears from their queue, and as the secretary, you'll see the exact date and time it was completed. ### Where Completed Documents Live Completed documents are saved to the Files tab on the entry, alongside any horse health documents, where you can download and review them anytime. --- # 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/managing-digital-signature-requests.md?ask=&goal= ``` `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.