> For the complete documentation index, see [llms.txt](https://docs.gymart.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gymart.org/competitions/choose-age-groups-vs-subdivisions.md).

# Choose age groups vs subdivisions

Choose the right structure for grouping gymnasts within a level.

## Prerequisites

* [Create a level](/levels/create-a-level.md) first.

## The Decision

When you set up a level you choose between two structures:

1. **Subdivisions only (2-layer)** - All gymnasts in the level compete and are ranked together. You split them into groups only for scheduling purposes.
2. **Age groups and subdivisions (3-layer)** - Gymnasts are separated by birth date and ranked within their own age group. You can then split each age group into subdivisions for scheduling.

## Do gymnasts of different ages need separate rankings?

**Yes** - Use age groups. A gymnast born in 2014 and a gymnast born in 2018 in the same level will be ranked only against others whose birth date falls in the same window.

**No** - Use subdivisions only. All gymnasts in the level are ranked together regardless of age.

## Do you have more gymnasts than can fit in one session?

**Yes** - Add subdivisions to split them across sessions. This applies to both structures.

**No** - A single subdivision (the default) is fine.

## Quick Reference

| Scenario                                                         | Structure                                  |
| ---------------------------------------------------------------- | ------------------------------------------ |
| Small meet, all ages compete together                            | Subdivisions only, 1 subdivision           |
| Large meet, all ages compete together, multiple sessions needed  | Subdivisions only, multiple subdivisions   |
| Age-specific rankings (e.g., 8-9, 10-11, 12+)                    | Age groups                                 |
| Age-specific rankings and large groups needing multiple sessions | Age groups with multiple subdivisions each |

## Examples

### Small recreational meet

Level 5 has 20 gymnasts ranging from age 7 to 12. They all compete in one session and are ranked together.

Use subdivisions only, 1 subdivision.

### Large invitational

Level 5 has 80 gymnasts. You want gymnasts born in 2014-2015 ranked separately from those born in 2016-2017. Each age group has 40 gymnasts, so you split each into two subdivisions for Saturday and Sunday sessions.

Use age groups (two birth date windows), 2 subdivisions per age group.

### Split sessions, single ranking

Level 7 has 50 gymnasts. You need two sessions (Saturday AM and PM) but want all 50 ranked together at the end.

Use subdivisions only, 2 subdivisions, all gymnasts ranked together.

## What's Next

* [How to create age groups](/competitions/create-age-groups.md)
* [How to create subdivisions](/competitions/create-subdivisions.md)

## Related

* [How do competitions, age groups, and subdivisions work?](/competitions/index.md)
* [How to configure individual score settings](/levels/individual-score-settings.md)


---

# 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:

```
GET https://docs.gymart.org/competitions/choose-age-groups-vs-subdivisions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.