Clutchat
Sign inGet started

Guide · Organizers

How to run a 16-team bracket in Discord

The short version: From the announcement post to the grand final: how to size, schedule and run a sixteen-team bracket without a spreadsheet.

Who this is for: Tournament organizers, and the moderators who help them on the day.

Last updated October 16, 2026

Why sixteen is a good size

Sixteen entries is the most forgiving bracket a community can run. It fills four clean rounds of single elimination (eight matches, then four, then two, then the final), it fits comfortably into one evening if matches are short, and it is small enough that an organizer can keep an eye on every match without a team of helpers. It is also a power of two, so nobody gets a bye in round one when every slot is filled, and nobody can complain that the draw handed a rival a free pass.

This guide walks through running one in a Discord server with the Clutchat bot, from the first announcement to the final result. The same steps work for solo players or for teams; where they differ, it says so.

1. Decide the format before you announce anything

Players decide whether to sign up based on what they are signing up for, so settle the basics first and put them in the announcement:

  • Bracket type. Clutchat supports single elimination, double elimination, round robin and Swiss. For a one-evening event with sixteen teams, single elimination is the practical choice. Double elimination roughly doubles the number of matches and needs a second evening or very short games. Round robin with sixteen entries is 120 matches, which is a league, not a tournament night.
  • Team size. 1v1, 2v2, 3v3 or full squads. If players sign up alone and you want teams, the bot can form teams from solo signups for you (more on that below).
  • Match length. Best of one for the early rounds and best of three for the semi-finals and final is a common compromise. Write it down in the rules so nobody argues about it at 11pm.
  • Start time and time zone. State the time in your server's time zone, and set that time zone in the bot with /config timezone so the times the bot shows match the ones you announce.

2. Create the tournament

Run /tournament-admin create in your server. You need the organizer role your server admin bound during /setup, or administrator permissions. Set the maximum to 16 participants. The bot posts the tournament with a registration button, so players can sign up with one click or with /tournament register.

Decide whether every signup should count immediately. If your event is open to anyone, leave approvals off. If you need to check ranks, server membership or team eligibility first, turn on Require approval in the create flow; signups then wait until you approve them under Approvals in /tournament-admin manage. Approval adds work for you, so only use it when you would actually turn people away.

Want specific people in the event? Invite player in /tournament-admin manage sends a player a direct message invitation. Players can check what they have joined with /tournament browse, and anyone can see the field on the Participants tab of /tournament view.

3. Build the teams

For team events there are two ways to get to sixteen rosters. Captains can register their team and add players, with substitutes added through /tournament team. Or, if your community signs up as individuals, /tournament-admin start forms the teams once registration has closed. It offers two modes: automatic, which shuffles the pool into random teams, and manual, where you pick the players for each team yourself. Manual takes longer but lets you balance teams by skill; automatic is quicker and nobody can accuse you of favouritism.

The bot will not quietly drop players who do not fit into a team when the event starts. Form the teams first, then start.

4. Run check-in

The single biggest cause of a late start is teams that registered days ago and are not online when the bracket opens. A check-in window solves it: players confirm they are present with the check-in button, and anyone who has not checked in when the window closes is removed from the field and told so by DM. Open check-in 30 to 60 minutes before the start. Our guide to check-in that stops no-shows covers the details, including what to do with the empty slots.

5. Seed and start

Before you start, decide how the bracket should be seeded. Seeding decides who meets whom in round one, and with sixteen entries a bad draw can knock out two of the strongest teams before the quarter-finals. If you have duel ratings, clan Elo or past results to go on, use them; the seeding guide explains how.

When the field is final, run /tournament-admin start. The bot generates the bracket, reports the format, number of rounds and number of matches, and sends round-one match messages to every participant by DM. /tournament bracket shows the current state as an image at any point, which is worth posting in your announcements channel after every round.

6. Keep the rounds moving

Players report their own results: the winner (or loser) presses a button in their DM, and the opponent is asked to confirm. When both sides agree, the result is recorded and the winner advances automatically. Players can check where they stand with /tournament report, which shows their current match.

For a one-evening event, set a time limit per round with Round time limit in /tournament-admin manage. When the deadline passes, matches that have not been reported are advanced automatically, with the higher-seeded side going through. It sounds harsh, but it is announced in advance and it is the only way to stop one slow match holding up seven others. If you need to close a round by hand, Force-advance round in /tournament-admin manage forfeits the unreported matches and moves the bracket on.

If a match message did not reach someone (closed DMs are the usual cause), Re-send match DMs in /tournament-admin manage re-sends it to both sides of every match that is ready. Announce in /tournament-admin manage posts a message to the tournament thread, which is the right place for "round two starts in ten minutes".

7. Handle problems calmly

Expect at least one dispute in a sixteen-team event. When the two sides report different winners, the match is marked disputed and sent to your log channel with buttons to award either side or void the match. You can also settle it with Resolve dispute in /tournament-admin manage. If a result was entered wrongly, Revert match in /tournament-admin manage puts a played match back to pending. A player who breaks the rules can be removed with Remove participant in /tournament-admin manage, which counts as a disqualification once the event is live. The dispute guide covers how to decide fairly.

8. The final, and afterwards

Give the final its own announcement and, if your community streams, its own stream. When the last result is confirmed, the bracket shows the winner. Once the tournament is complete, its results feed the server's tournament leaderboard (/leaderboard) and players' records (/player profile). Post the final bracket image, thank the field, and announce the date of the next one while people are still in the channel.

If the event went well, make it a fixture: the monthly Repeat option in /tournament-admin create sets up a recurring monthly tournament on a day of the month you choose, with registration and check-in windows handled for you. You can pause, resume or delete a schedule at any time. See tournament features for the full list of tools.

A sample timeline

  1. One week before: create the tournament and announce the format, time and rules.
  2. Two hours before: registration closes; form teams if players signed up solo.
  3. One hour before: check-in opens.
  4. Start time: check-in closes, seed, run /tournament-admin start.
  5. Every 30 to 45 minutes: a new round, with a round deadline set.
  6. About three hours in: the final.

More guides