Organising Your First Tournament

Running a tournament is the most ambitious thing most HubMatch users will ever do on the platform. It is also one of the most rewarding - a well-organised event builds your reputation in the community, gives teams meaningful competition, and contributes directly to the health of the competitive scene. This guide walks through the full lifecycle of organising a tournament, from initial concept to post-event wrap-up.

Before You Start: Define the Event

Every successful tournament starts with a clear answer to four questions:

1. What is the prize? Money, in-game items, bragging rights, a qualifier slot for a bigger event. Whatever it is, name it clearly. Teams decide whether to enter based partly on what they get for winning.
2. What is the format? Single Elimination, Double Elimination, Swiss, group stage plus playoffs. Each format has different scheduling demands and different competitive characteristics - see the bracket types guide for the full rundown.
3. What is the size? 8 teams, 16 teams, 32 teams. The size determines the number of rounds, the total time budget, and the practical effort of running matches.
4. What is the schedule? A single day, a weekend, a multi-week ladder. The schedule has to fit both the format and the realistic availability of the teams you want to attract.

If you cannot answer all four cleanly, you are not ready to open registration. Tournaments that launch with vague details collapse mid-event when reality catches up.

Set the Rules in Writing

Tournament rules need to be written down and published before registration opens. Teams need to know what they are signing up for, and disputes during the event are dramatically easier to resolve when the rule is in writing rather than in your memory.

A minimal rule set covers:

• Eligibility. Region restrictions, skill ceilings or floors (ELO bands), age requirements, roster size limits.
• Roster lock. When does the roster you registered with become locked? Most events lock at registration close; some allow substitutions through the event.
• Match format. Per-round formats (BO1, BO3, BO5) - see the match formats guide.
• Check-in window. How long before each match do both teams have to check in? Typically 5-15 minutes.
• No-show policy. What happens if a team does not check in by the deadline? Standard is forfeit after a 10-15 minute grace period.
• Dispute process. Who resolves disputes, and within what time window?
• Conduct expectations. Reference the platform Code of Conduct and add any event-specific rules.
• Prize distribution. When and how is the prize delivered to winners?

Publish the rules on the event page and link them in your registration messaging. Do not change the rules mid-event unless you absolutely must - and if you must, communicate the change to every registered team in writing.

Open Registration

Set a registration window with a clear close date. The window should be long enough that teams can plan but short enough to create urgency - one to three weeks is typical for community events.

During registration:

• Confirm each team's roster meets eligibility.
• Track registration count daily. If you are well under target a week before close, push promotion harder.
• Watch for duplicate or suspect registrations - the same captain registering two teams with overlapping rosters is a red flag.
• Communicate regularly with registered captains. A pre-event briefing message 48 hours before kickoff helps set expectations.

Once registration closes, lock the bracket. From this point forward, no new entries are accepted; only the registered teams play.

Bracket Generation and Seeding

After registration closes, click Generate Bracket on the tournament page. The platform builds the bracket structure based on the seeding you provided - your job is to verify the seeding is correct before generating.

Seeding inputs:

• Team Tournament ELO (the average of the players' individual Tournament ELO values).
• Previous tournament results, if you want to weight recent form.
• Manual overrides for teams you know are stronger than their ELO suggests (newly formed superteams, returning veteran rosters).

Standard seeding pairs highest seed against lowest in round 1, second-highest against second-lowest, and so on. Avoid pairing two top teams in round 1 by accident - review the bracket before publishing it.

If your bracket size is not a power of two, the platform assigns byes to the top seeds. Verify the bye placement is fair.

During the Event

The event itself is where good preparation pays off. Your job during play:

Monitor match progress. Watch the matches dashboard for stalled rounds. If both teams have checked in but no result has been reported 90 minutes in, intervene proactively - ask the captains what is happening.

Handle disputes promptly. Disputes block subsequent matches. Resolve them within a few hours, not days. Review screenshots, check the Team chat, make a call, and document the decision on the match page.

Communicate scheduling delays. If a round is running late, post a Discord announcement with the revised start time for the next round. Teams sitting around waiting without updates lose patience fast.

Enforce conduct. A toxic player or team poisons the event for everyone else. If you see clear conduct violations, issue warnings or disqualifications according to your published rules.

Stream or report on play. Many events benefit from a community stream of the featured match per round, or at minimum a text summary posted between rounds. Visibility builds the event's reputation.

After the Event

The final round ends, the champion is crowned, and the work is not quite finished.

Distribute the prize. Within the timeframe you promised. Late prize delivery is one of the fastest ways to destroy an organiser's reputation.

Update player and team records. The platform handles ELO updates automatically as matches verify, but if you ran a non-standard event you may need to manually adjust standings or award badges.

Publish a results summary. A brief recap on Discord - final standings, notable matches, statistical highlights - closes the event cleanly and helps teams reflect on their performance.

Solicit feedback. Ask captains what worked, what did not, and what they would want different next time. Most of the improvements in your second event come from feedback after your first.

Common First-Tournament Mistakes

• Underestimating time. A 16-team Double Elimination with BO3 throughout is not a single-day event. Build a realistic schedule before you announce one.
• Vague rules. "Reasonable conduct expected" is not a rule. Spell out what counts as a violation and what the consequence is.
• Bracket reseeding mid-event. Reseeding after registration closes erodes trust. Lock the bracket and live with it.
• Solo running. Organising alone burns out fast. Recruit at least one co-organiser to share match-monitoring and dispute resolution duties.
• No backup plan for no-shows. Decide in advance how you handle a team that does not show: standard forfeit, replacement from waitlist, or bracket restructure. Make the rule before you need it.

Scaling Up

Once you have run a successful small event, larger formats become accessible. The skills transfer: scheduling, rule-writing, dispute resolution, communication. The biggest tournaments on HubMatch - national championships, qualifier finals, prize circuits - all started somewhere. Most started with someone deciding to run an 8-team weekend cup and learning the operational realities from there.

You can be that someone.

Promotion and Pre-Event Outreach

A tournament with great rules and a generous prize pool still fails if no teams know it exists. Promotion is a real part of organising and deserves serious effort.

The first audience is your existing competitive network. Post the event in every active HubMatch-related Discord you participate in. Reach out directly to captains of strong teams you know - a personal message has dramatically higher conversion than a public announcement. Captains often decide whether to enter a tournament based on which other teams have already signed up; an early commitment from a known team validates the event for everyone considering registration.

The second audience is broader regional or skill-band communities. If your event targets EU mid-tier teams, reach into EU mid-tier Discord spaces specifically. Generic cross-region promotion is far less effective than targeted outreach to communities that match your event's eligibility criteria.

Consider partnering with a streamer or content creator who covers Rematch. A creator promoting your event to their audience for a small fee (or in exchange for streaming rights to the finals) can dramatically extend your reach. Build the partnership at least two weeks before registration opens so the promotion runs through the registration window.

Keep promotional messaging honest. Inflating prize pools, exaggerating expected team counts, or making promises you cannot keep ("featured on the official HubMatch stream") destroys credibility fast and ruins your second event before it starts.

Building a Co-Organiser Team

Running anything larger than an 8-team weekend cup alone is unrealistic. Build a small organising team with clearly divided responsibilities.

Typical role split for a 16-32 team event:

• Lead organiser. Owns the event vision, the prize pool, the published rules, and the final word on disputes.
• Scheduling lead. Owns the calendar, communicates round timing to teams, handles re-scheduling for delays.
• Dispute admin. Owns dispute review, evidence collection, and ruling delivery. Should be someone with strong rule-knowledge and even temperament.
• Community lead. Owns Discord communication, promotion, and the post-event recap.

A team of four handles most mid-sized events comfortably. Define each role's authority clearly - disputes about who owns what decision are the single most common reason organising teams fracture.

Long-Term Reputation as an Organiser

Each tournament you run adds to your organiser reputation. Teams remember the experience: was the event on time, were the rules clear, were disputes handled fairly, was the prize delivered when promised. A handful of well-run events establishes you as a trustworthy organiser, which makes the next event easier to fill and the one after that easier still.

The flip side is also true. A single badly-handled dispute, a single late prize payout, or a single mid-event rule change broadcasts through the community fast. Damaged organiser reputation is hard to recover.

Run events for the long term. Treat every captain and every player as a participant in your future tournaments. The community is smaller than it looks.