> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ticketspotapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up sports event registration and tickets

> Configure spectator tickets or participant registration for a sports event, including capacity, custom questions, seating, and check-in.

Use **Sports Event** for spectator admission or participant registration that you manage through Ticket Spot. The starting template is one paid general-admission event. It does not create teams, fixtures, brackets, or race timing.

## Template starting point

| Setting | Initial choice |
| - | - |
| Schedule | One day |
| Admission | Paid tickets |
| First offer | General Admission · suggested price 25 in your site’s currency |
| Capacity | 100 |
| Attendees choose a time | Not enabled |

These are editable suggestions, not recommended prices or venue limits. Replace the dates, price, and capacity with your own. See [how onboarding works](./overview#complete-onboarding).

## Choose the onboarding answers

Open **Create Event** in the selected workspace.

1. Select **Sports Event** and name the fixture or activity.
2. Set **One day** with the actual start/end. Choose a repeating schedule for regular fixtures only when the dates follow that pattern.
3. Choose **Paid tickets**, **Free RSVP**, or **Assigned seating** to match how people attend. Replace the suggested capacity and price.

<Note>**Create my event** may publish immediately when the requirements are met. Use **Continue later** to finish setup as a draft. Review any plan or publishing message before sharing the event.</Note>

## Finish the event settings

| Where to go | What to configure |
| - | - |
| **Tickets** | Name separate spectator and participant ticket types clearly, and set their quantities and purchase limits. |
| **Additional Info** | Collect participant details with [ticket-specific questions](/event-management/additional-information); avoid requiring athlete information from spectators. |
| **Waivers** | If your activity uses an acknowledgment or signature, configure a [waiver question](/event-management/waivers) and its checkout/check-in requirement. |
| **Seating** | For a seated venue, connect a chart and ticket categories using the [assigned-seating guide](./assigned-seating). |
| **Memberships and check-in** | For season access, configure [memberships](/memberships/overview) and assigned events; prepare ticket or membership scanning. |

## Register each participant

A buyer purchasing several places may not be the person participating. Enable **Collect attendee details for each ticket** in the [widget checkout settings](/branding-and-design/checkout-settings) when you need each participant’s information. A Team Name question is a recorded answer, not automatic team or tournament management. Describe what each ticket includes and collect only the fields you need to run the activity.

## Check the attendee experience

* Test a spectator order and a participant order to verify question scope.
* For multiple participants in one order, check each attendee record and required answer.
* Check the correct fixture, seat if applicable, and admission rules on the ticket.

Review the event’s saved status and [publish/share controls](/event-management/manage-events) when it is ready. Return to [all event types](./overview) to compare starting points.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.