TS
Tournament Suite
TS
Tournament Suite
Help CenterPlatform OverviewProducts, Roles, and How They Fit TogetherWhat Is Tournament SuiteCreate Your AccountQuick-Start: Your First TournamentCreate a ProjectProject DashboardProject Settings: General and AppearanceManage Team and RolesCircuits and SeasonsCreate a TournamentTournament Settings OverviewRegistration SettingsParticipant and Match RulesSet up tournament structure and formatsSeed and place participantsSchedule matchesPublish and Go LiveDuplicate a tournamentUse and manage tournament templatesManage RegistrationsCheck-InCustom FieldsExport ParticipantsMonitor and Control a Live TournamentApply Interventions to a MatchTrack and Resolve Issues During a Live EventHandle Officiating and Formal DisputesSet Up Streams and the Broadcast CenterSet Up Branding and SponsorsReview your project's financial activityConfigure prize pools and disburse winningsSet up your payout methodHold prize funds in escrowManage project communications from the hubCreate and send campaigns to participantsCreate and manage API keysReceive real-time event notifications with webhooksConnect Tournament Suite to a Discord serverManage Tournament Permissions and Staff AccessReview and Resolve Participant AppealsConfigure Wellness Settings for Your ProgramProjects, Workspaces, and Team ManagementTournament Creation, Settings, and StructuresLive Operations, Broadcast, Streams, and MediaGovernance, Support, Integrations, and Organization ControlsPublic Discovery and Viewer Experience

Review and Resolve Participant Appeals

Use the Appeals queue to formally review disputes and deliver rulings that participants are notified of automatically.

The appeals system gives participants a structured way to dispute match results, moderation decisions, or other rulings made during your tournament. When a participant submits an appeal through the player-facing site, it lands in your Governance → Appeals queue. Your team reviews the evidence, adds internal notes, and issues a binding ruling. The participant is notified automatically when the decision is submitted.

Where to find it

Projects → [Your Project] → Governance → Appeals

(projects/[id]/governance/appeals/)

Individual appeal: projects/[id]/governance/appeals/[id]

Step by step

  1. Navigate to Governance → Appeals.
  2. Click on an appeal to open it.
  3. Review the submitted reason, any evidence attached, and the linked match or event.
  4. Add internal notes to document your reasoning (these are not shown to the participant).
  5. Make a decision:
    • Uphold — accept the appeal and change the outcome.
    • Reject — keep the original outcome.
  6. Submit your ruling.
  7. The participant is notified of the decision automatically.

Setting governance policies

Clear, pre-published rules make appeals easier to resolve and harder to dispute. Navigate to Governance → Charter (projects/[id]/governance/charter) to define your tournament's rules and the standards you apply when reviewing appeals. Referencing the charter in your ruling notes keeps decisions consistent and defensible.

Escalation

If an appeal requires a higher-level review — for example, a match result that needs a replay verified by a referee — it can be escalated to the officiating workspace.

What happens next

  • Upheld appeals may trigger result changes, score corrections, or participant status updates depending on the scope of the ruling.
  • Rejected appeals are closed and archived in the queue.
  • All rulings remain in the Appeals history for audit purposes.

For handling disputes during live play, see Officiating and disputes. To control which staff members can access the appeals queue, see Permissions and admins.

Manage Tournament Permissions and Staff Access

Assign granular permissions to staff members so each person has exactly the access they need inside a tournament.

Configure Wellness Settings for Your Program

Set play time limits, break reminders, and guardian rules to create a safer competition environment for your participants.

On this page

Where to find itStep by stepSetting governance policiesEscalationWhat happens next