> 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/divisions-and-classes/creating-new-divisions.md).

# Creating New Divisions

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

## **Creating Divisions in your Horse Show**

There are two ways to create new divisions in your horse show.

### **Finding the Divisions Settings**

Go to Settings on the left panel, then select Divisions and Classes. This page automatically opens to the Divisions tab.

{% stepper %}
{% step %}

### **Creating a Division Manually**

Click the blue New Division button in the top right corner. From here, you can name your division, set a division price, add a tag, and require full division entry (details as before).

Once you save, the division is created and ready for further setup.
{% endstep %}

{% step %}

### **Creating Divisions in Bulk**

Export your current settings to receive an Excel file with the same fields, fill it in, then import it back into Horse Spot to create your divisions in bulk.
{% 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 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/divisions-and-classes/creating-new-divisions.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.