Team Conflict Requests

In TeamSnap Tournaments tournament administrators have the ability to account for time and team conflicts so that the tournament administrator doesn’t have to manually schedule around these conflicts.

Note: If a coach manages more than one team entered in your event, the TeamSnap Tournaments software will automatically consider this a conflict and warn administrators when scheduling. Same coach conflicts in the same event do not need to be entered as time conflicts. The TeamSnap Tournaments system will automatically recognize and flag a coach conflict if the head coach profile on the rosters includes identical first name, last name and email address.

Conflicts Entered by the Coach or Team Manager  

When registration is used for teams, Tournament administrators can set up the registration to allow the coach to enter a time conflict request for the event at the time of registration.

To allow coaches to enter times that they are unable to play at the time of registration follow these steps: 

  1. Go to the Registration tab
  2. Click Manage below the event 
  3. Go to Settings > Conflict Settings
  4. Check the box that says allow registered teams to enter time conflicts.
  5. Enter the maximum number of time conflicts you will allow. (We suggest keeping this number low so that coaches don’t end up picking the exact times they would like to play each game.) 


Conflict Management by an Administrator

To view/manage existing time conflicts and to add conflicts manually as a Tournament administrator follow these steps:

  1. Go to the Tournaments tab
  2. Click Manage below the event 
  3. Go to the Teams tab
  4. Click the pencil icon next to the team for which you are entering a conflict 

  5. Go to the Conflicts Tab  
  6. Click the + Add Conflict button
  7. Enter the time conflict(s) 

  8. Click Close

You will now see the conflict icon in the Conflict column indicate that the conflict and the number of conflicts for the team. 

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.