> 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/basic-show-setup/creating-and-managing-show-names.md). # Creating & Managing Show Names ## **Give Your Show a Name!** **Here are some bullet points to get your creative juices flowing:** * Add the season to your name. Example: Kentucky Spring Fling * Add the discipline to your name if you'd like! Example: Run O' the Mill Pony Club Hunter/Jumper Show. This isn't necessary. Horse Spot already filters shows by discipline type, so this is just a nice-to-have, not a requirement. * Add your show management name, association acronym, or farm name to your show. Example: ECRA Spring Fiesta * Get creative with it! Use catchy phrases that will grab exhibitors' attention. Example: Marigold's Summer On My Mind Show * Hosting a rated or schooling show? Make that a part of the name. Example: Oaklawn Farm May Schooling Show or The Ridge Week 12: USEF Jumpers & Equitation * Have an official sponsor? Make sure to include them in the name! Example: Defender Kentucky Three-Day Event * Hosting a charitable show? Add the word "Charity" to it to let exhibitors know. * Still stuck? Ask ChatGPT for help or reach out to Horse Spot's team of creatives! ### **What Not to Add** **You don't have to add the following to your show name, since Horse Spot already displays this information.** * You don't have to add the venue name to your show name (e.g., Kentucky Horse Park) as Horse Spot will display your venue name right next to your show name. * It's not required to add the city or state to your name, unless it's a part of your show name (e.g., Lexington, Kentucky). You may want to name your show "The Kentucky Showdown," for example, but it's not required to include location details if you don't want to. Users will see the proper venue, city, and state displayed for them automatically. * Do not add specific dates to show names (e.g., May 11th-13th). You may still want to include the year if it's part of an official annual event's title. For example, NCEA's "National Collegiate Equestrian Association National Championship 2025" includes the year, but not the specific dates, since Horse Spot already displays those. {% hint style="info" %} Avoid naming your show something like "Summer Sweetness August 9th-11th," which creates redundancies in the user experience with dates already being automatically displayed. Use something simpler and shorter, like "Summer Sweetness." {% endhint %} ### **Have a Series?** Consider adding numbers to the end of your show name to help users track which show they're attending. You can use any of the naming conventions below. We recommend sticking to one type of naming convention throughout your series, so users understand the pattern you've set up. For example, don't name one show "Plantation Spring Horse Show I" and the next one "Plantation Spring Horse Show Week 2." Consistency is key! * Plantation Spring Horse Show I * Plantation Spring Horse Show II * Charleston Spring Fling: Week 1 * Charleston Spring Fling: Week 2 --- # 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/basic-show-setup/creating-and-managing-show-names.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.