> For the complete documentation index, see [llms.txt](https://uspa-wpr.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uspa-wpr.gitbook.io/docs/getting-started/getting-started.md).

# TMS Guide

> **Audience:** Tournament Directors (TDs) and club staff using the **Tournated Tournament Management Software (TMS)** in partnership with **WPR** and the **USPA**.

## Quick‑Start

* [ ] Submit your tournament poster to <info@padelusa.org>, following guidelines <http://www.padelusa.org/flier>: 1200 x 1700 (horizontal x vertical) with 100 pixel border zone at top & bottom, required USPA sponsor logos, etc.
* [ ] Connect Stripe (required only once, for the first tournament you run).
* [ ] Verify your tournament appears on the USPA Calendar.
* [ ] Maximize registrations by reviewing & completing the Club Tournament Marketing Guide - Strategies, Ideas & Promotion Timeline for USPA-Sanctioned Events (e.g. "Section 6: Suggested Marketing Timeline" of checklist tasks from 12 weeks out thru to tournament completion): (\[<https://drive.google.com/file/d/1aEpVs8yHZwCojDJ0eT2wlfHve\\_IMEX\\_8/view>] (<https://drive.google.com/file/d/1aEpVs8yHZwCojDJ0eT2wlfHve\\_IMEX\\_8/view>)).
* [ ] Registration opens.
* [ ] Receive login credentials to your club's **TMS** ([https://manager.tournated.com](https://manager.tournated.com/)).
* [ ] Review **this document's Instructions Step 3-7**, and also familiarize with USPA Rules & Regulations (<https://padelusa.org/competition/rules-and-regulations/>).
* [ ] At deadline, **review Entry List** from USPA (includes seeding), and make changes if any needed. (\*IMPORTANT Note: If any late entries and/or any teams changing divisions and/or partner changes, seedings may resultingly change -- add the entries, make changes, and determine seedings by consulting a team's combined USPA rankings points. See Instructions Step 5 below for details.)
* [ ] **Create draws & schedule** in TMS. Publish by 3pm local time on Monday (Tuesday for USPA 100s).
* [ ] Manage **in‑tournament scoring** in TMS.
* [ ] Use **Stripe** to issue any necessary refunds for withdrawals.

3min video on "Tracking Tournament Entries in Tournated and Stripe": <https://www.loom.com/share/76745f58307f450f83fd0e6e525ae6be>

## Overview

The USPA, in partnership with WPR, uses **Tournated TMS** for the end‑to‑end tournament flow: listing, player entry and payment, draws, schedules, and scores. This improves the experience for players, clubs, and TDs.

* **Players enter and pay** at [https://uspa-tournaments.worldpadelrating.com](https://github.com/marasco/gitbook-wpr-tournated/blob/main/getting-started/\[https:/uspa-tournaments.worldpadelrating.com]).
* **Entry fees** are paid **directly to the club** via the club's **Stripe** connected to the TMS (real‑time). *Note: Stripe fees will be applied.*
* **TDs** are responsible for learning and operating the TMS; **WPR** and **USPA** provide support and oversight.

## Key Contacts & Links

**Support**

* General TD queries: <tduspa@worldpadelrating.com>
* Technical/TMS issues: <hello@tournated.com>

**Portals**

* Player portal: <https://uspa-tournaments.worldpadelrating.com>
* Manager portal (TMS): <https://manager.tournated.com>


---

# 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://uspa-wpr.gitbook.io/docs/getting-started/getting-started.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.