A guide for Tournament Directors — from "I have a date and a park" to results published. Fifteen minutes to read; most of it you'll never need, because the product does the remembering. <!-- REVIEWER NOTE (delete before merge): drafted from specs per #422's verification rule. Screen-level details (button names, menu locations) are marked ⚠️ VERIFY and need one pass against the running app. Sections marked COMING describe committed but unshipped work and render hidden until their features land. -->
Before you start
You need three things:
- A team count (or a realistic guess — you can adjust until you publish)
- Your fields — how many, and their names
- Your time window — first pull to hard stop, each day
That's it. You do not need to know tournament formats. That's our job.
Your dashboard keeps a checklist. Once you run an organization or have created an event, Getting started on your dashboard lists what stands between you and publishing, in order: attach an organization, verify its name, connect Stripe payouts, set a price, build the event, publish. It is the publish button's own list, so a step marked done is one the button will not refuse you for, and each step links to where you fix it. It disappears once your event is published.
Creating your tournament
Every event belongs to an organization, so that comes first. If you don't have one yet, starting a tournament takes you to New Organization; if none of yours is verified yet, it takes you to your organization's page. Either way the page shows what publishing still needs from the organization — name verification and Stripe payouts, each linked to the panel that does it — and Start your tournament takes you on. Neither one has to finish before you build.
Create a competition, add your division(s), and set the basics: dates, location, fields. Your event stays in draft — invisible to the public — until you publish it, so seed, argue, and rearrange freely. Nothing leaks while you work.
Check the time zone on Event Info. It starts as your own zone, which is wrong if you are setting up an event somewhere else. Every game time is in the event's zone, and while yours differs, setup and the schedule say so above the times. Change it before you schedule anything: once a game has a time, the zone is locked, because every time already given out would move with it.
Each division has a limit, and it is yours to set: Ulti HQ has no cap of its own. A division entered by whole teams has a Team limit: how many teams you can add, and how many places registration sells before later teams join the waitlist. Enter the number your fields can hold, or leave it blank for no limit, which suits a league or an event that takes however many come. Choose Change limit beside the division to raise it at any time, or lower it as far as the teams already holding a place. A division entered by individual players, like a hat tournament, has a Player limit instead, or none if you leave it blank. With a player limit, it can also reserve places for women-matching players: open players fill the rest, women-matching players can take any free place, and once the limit is reached everyone joins the waitlist. Its teams are the ones you draft people onto, and there is no limit on how many you create, so make them once you know how many people signed up.
On the Teams step, pick a division to see its count and its teams, with their seeds, under the form. A team you typed in can be renamed or removed there. A team that came in through registration can't be: its name is its captain's, and removing it would skip the withdrawal and refund the registrant agreed to, so it links to Applications instead. Teams in a division people enter one by one come from the draft, so they're listed without either button. Removing a team always asks first. Once pools or games exist, the question lists that team's games, which are deleted with it, and you regenerate pools, games, bracket and schedule afterwards, just as after adding one. Removal never erases anything that happened. A team with a played game, a reported score, spirit scores or results in the standings can't be removed, and neither can any team once the event is live. If a team has left, record its departure instead: its remaining games are forfeited and every result stays.
Fields are named once and reused everywhere — schedules, live views, players' phones. Rename a field and every game on it updates instantly, because games point at the field rather than copying its name. A field with games on it can't be removed. The step names each of those games, so you know what to move first.
To put a photo at the top of your public event page, open Settings and choose Upload hero image. A wide photo works best, and it saves as soon as you choose it. Without one, the page uses your event's color.
Choosing a format
Tell the wizard your team count, days, and how many teams advance (for standalone tournaments, "advance" just means how precisely you want final places settled). It answers with a recommended format and alternates, each showing:
- The structure — "two pools of five, then an eight-team bracket, four advance"
- A USAU label where the structure matches the USAU Formats Manual —
"Format 10.3" means this is *the* format the manual prescribes, the one sectional coordinators are required to use. If you're running a sanctioned event, pick the labeled one and you're compliant by construction
- A feasibility verdict — fits / tight / doesn't fit your fields and time
window, with the limiting factor named ("needs 7 rounds; your window fits 6"). Options that don't fit are shown disabled with the reason — never hidden — so you can see what adding a field or an hour would buy you
You can ignore all of it. Manual configuration is always available: build your own pools, pick your own bracket, set your own advancement. The recommendation is a default, not a decision.
Where we differ from the USAU manual
Transcribing the manual's brackets, we found a handful of misprints in the document itself — games lettered wrong, one table misprinted. Every place we differ is published on the manual departures page, with the evidence, so you can check our reasoning rather than trust it. ⚠️ VERIFY in-app location of the departures page link.
Seeding
Seeding is yours — drag teams into order. If suggestions are available for your event (club teams with ranking data or platform history), a suggest option can pre-fill an order which you then adjust and approve; nothing is ever seeded for you. ⚠️ VERIFY current suggestion sources exposed in UI.
Unseeded events, like a hat tournament: leave Seed blank for every team in the division. On the Format step, tick draw the order at random before you generate. The draw is saved as the teams' seeds, so generating again keeps it. Nothing is drawn unless you tick it — teams that registered themselves arrive without seeds too, and a field you have not ranked yet is not shuffled for you. A division where some teams are seeded and some are not is refused, with the unseeded teams named, so seed the rest.
Two manual rules the engine enforces so you don't have to remember them: pool-play rematches are avoided in bracket placement where the manual allows opponent swaps, and byes always favor the higher seed.
The schedule
The time grid comes from Fields & Times: your fields, the day's start and end, the game length and the buffer. Saving it again with different numbers replaces that day's grid rather than adding to it. If a game is already sitting in a time the new settings remove, you're told which games before anything changes; continuing takes them off the schedule, and generating again places them on the new times. A game that has been played keeps its field and time.
Generate the schedule with one action. The engine places every game into your fields × time grid, validating as it goes: no team plays twice at once, no field double-booked — by any division, not just the one being scheduled — bracket games never scheduled before the games that feed them, rest windows respected, and no team parked on the far field all day.
Then edit anything. Drag games between slots — validation runs live and tells you specifically what an edit would break before it breaks. Generation is a starting point, not a cage.
Most of what validation flags you can override — a team with short rest, a rematch, a team in two places when you know one game will finish early. One thing you can't: two games on the same field at the same time, in any division. Moving a game onto a field that's in use tells you which game is there; move that game first. To swap two games, move one to an open slot, move the other into its place, then move the first into the gap.
Publish when ready. Players see schedules on their phones — including offline at fields with no signal — and every change you make after publishing reaches them automatically. No reposting PDFs, no version-three-final-FINAL.
Game day
The live control panel is your command post; captains are your data entry.
- Scores: captains report from the sideline; agreements post instantly,
conflicts come to you — and only conflicts. Standings, tiebreaks, and bracket advancement cascade automatically the moment a score lands
- Spirit: collected per game, tallied per the event's sanctioning rules
- Delays: when weather hits, delay or postpone from the panel — affected
players are notified without you texting anyone. ⚠️ VERIFY current delay controls scope
- Tiebreaks: the full USAU tie-breaker cascade (rules 2–9, with the
regrouping rule most software skips) runs automatically. When a tie is genuinely unbreakable, it comes to you — and only then
Your phone works at the fields even when the internet doesn't. So do your players'. That's not luck; it's built for the captive-portal WiFi and dead zones every tournament venue has.
After the final
Final placements resolve from the format automatically — including the manual's placement semantics (which games decide which places, which placement games are skippable under USAU's forfeit rules).
Where they don't — a bracket abandoned to weather, a forfeit you awarded on the court result, a team that withdrew after seeding — Final Placings on the season report lets you set a place by hand. Every team in the division gets a row, whether or not the event settled its placing, and each row says where its number came from: the bracket, the standings, a withdrawal, or you.
Setting one asks for a reason, and the reason is kept with the placing. That is deliberate: a hand-set number with nothing beside it is unreadable in two years, and these are the placings the results export carries. Change your mind and Use the result puts the computed placing back.
Reporting to USA Ultimate
If your event is USAU-sanctioned, the season report carries a USAU results link. It downloads every score, the finishing order, and your rosters with the membership numbers players gave us — tab-separated, so it pastes into a spreadsheet as columns and still reads as a list on screen.
Downloading it reports nothing. There is no submission API; you still type the scores into USAU's score reporter yourself, and the file says so in its own first lines. It exists to make that twenty minutes instead of an evening, not to stand in for it.
What you will see in it:
- Games, in typing order, one line each, grouped by division. Where the
division's stage names match the Formats Manual, the manual's format reference sits at the top of that division
- A count of games with no score yet, so you find them before you start
rather than half way down the form
- Placings, where the event decided them — and only those. A bracket still
running says what it has settled so far and tells you it is not a complete ladder. A placing you set by hand is marked as yours, with your reason
- Rosters, accepted players only, with each one's USAU number. A blank
means we were not given one — not that the player has no membership. The count is at the bottom
Unsanctioned events do not get the link. There is nobody to report to, and an invitation to file with a governing body you are not part of is noise.
Next year
Don't rebuild: roll the event over. Fields, settings, and structure carry forward; you update dates and go.
When something goes wrong
- A score was entered wrong: correct it; standings and brackets re-cascade
- A team no-shows: the manual's allowable-forfeit rules are built in
- You're stuck: every screen's help links land in this guide's matching section
*UltiHQ runs the formats in the USAU Tournament Formats Manual as printed, except where the printing is provably wrong — see the departures page. If you find a format we handle incorrectly, we want to know more than you want to tell us.*