The Conflicts page shows the players that are scheduled to play in two or more events at the same time, which would cause conflict for overall scheduling. The page will also show conflicts that are created due to "Constraints", either through approved bracket feedback or when manually entered by a TO.

Constraints are essentially a “blocker”, that will create a conflict if the bracket does not meet the constraints set. You can use constraints to set up a conflict so that players can be avoided for various reasons, or to prevent them from being placed in certain waves due to a schedule issue. Conflicts are then resolved within the “Conflicts” tab.

Players can also submit their own feedback and bracket change requests through the Bracket Feedback system. To learn more about this feature, check out our article here.

Some scheduling conflicts can be generated without player feedback by assigning your pools/brackets to waves. To learn more on assigning waves, visit the Setting up your brackets and the Using Waves in the “Scheduling” Tab articles.

Player Conflicts

The conflicts section shows the conflicts based on your constraints, as well as schedule conflicts tied to your bracket/pool times.

  • Click on “Resolve” to solve the conflicts.
  • The modal that appears will suggest swaps to resolve the conflict. Click on “Swap” to apply the change.


Here you can create constraints manually for players.

Creating a Constraint

  • Click on “Create Constraint”
  • A modal will appear, then choose a “Player Constraint” or “Schedule Constraint”

Player Constraint

  • In the first “Player” section, search for the player this constraint applies to.
  • In the “Player Constraint” section, enter the player that needs to be avoided.
  • Select the event that this constraint applies to.
  • Enter a short description for the constraint (reasoning behind it).
  • This is allows you to set up a constraint in order to avoid matching up players from the same region, relatives, training partners, etc.

Schedule Constraint

  • In the “Player” section, search for the tag of the player that this constraint applies to.
  • Select the event.
  • Select the waves that the player is able to attend.
  • Any wave unchecked means that the player is unavailable during those times.
  • Enter a short description for the constraint.
  • This is allows you to manually enter a constraint for a player that has a volunteering shift, a commentary shift, etc.
Did this answer your question?