Team Placement Overview

Team Placement and Roster Building Options

Byga provides several ways to place players onto teams, allowing clubs to choose the workflow that best fits how they build and manage their rosters. Players can be placed during the tryout process, directly from a team roster, from the Player Profile, through Program Registration, or through a player upload.

The appropriate method depends on how the club is forming teams, whether players are coming from a tryout or registration, and whether the program allows a player to be rostered on one team or multiple teams.

Placing Players Through Tryouts

For competitive programs that use Byga Tryouts, players can be placed onto teams directly from the Tryout workflow.

After evaluations are complete and roster decisions have been made, administrators can use the +TEAM option to place a player onto the appropriate team.

For example, after reviewing evaluations, a club may determine that a player belongs on the U15 Blue team. The administrator can place that player directly onto the team rather than first moving to another area of Byga to complete the roster placement.

Tryout information can also be mapped to Player Profile fields, and Player Pools can be used to organize players based on information collected during the Tryout. This can help administrators organize and review players as they work through team formation.

Once a player is placed on a team through the Tryout workflow, the player can continue into the club's registration process when the club is using a registration workflow connected to team placement.

Placing Players Directly From a Team Roster

Players can also be managed directly from the Team Roster.

From a team's roster, administrators with the appropriate permissions can add a player to the roster. Existing rostered players can also be moved to another team or removed from the roster.

This method is particularly useful when teams are already established and an administrator is making individual roster adjustments.

For example, if a player is initially placed on U14 White and the club later determines that the player should be on U14 Blue, the administrator can use Move to another team from the player's roster controls rather than rebuilding the player's placement from another workflow.

The Team Roster also includes tools for importing a roster from another team, when permitted, which can be useful when reorganizing existing teams.

Placing Players From the Player Profile

A player can also be managed from the Player Profile.

This approach is useful when the administrator is already working with a specific player and wants to manage that player's team relationship without first navigating to a particular team's roster.

The Player Profile provides a central place to review the player's information and team relationship. Player activity can also provide useful history when reviewing how a player has moved through club workflows, including roster-related activity and Tryout activity.

This can be especially useful when an administrator is making an individual placement decision or reviewing a player's history before changing their team assignment.

Placing Players Through Program Registration With One Team Per Player

For a Program Registration configured so that each player can be placed on one team, Byga provides the graphical Roster Workspace.

The Roster Workspace is designed specifically for team placement. It provides an Unassigned Group containing players who have not yet been placed, along with the teams being used in the workspace.

Players can be dragged from the Unassigned Group onto a team or moved between teams.

This makes the Roster Workspace particularly useful when an administrator is forming several teams at once and wants to see the player pool and teams together.

Using Player Information While Building Rosters

The Roster Workspace can display selected form fields and player information directly with the players being placed. Administrators can also filter players based on the information available in the workspace.

For example, a club could use information collected during registration to help organize the player pool before placing players onto teams.

Each player also has options to open the Player Profile or view the player's form response, allowing administrators to review additional information without leaving the roster-building workflow.

Changes made in the Roster Workspace are automatically saved, including changes to the player pool, teams, and form filters.

Multi-Team Placement Must Be Disabled

The graphical Roster Workspace is available when the program is configured for one team per player.

If Multi-team placement allowed is selected in the Program Settings, the drag-and-drop Roster Workspace is not available.

This distinction is important when deciding which roster-building workflow to use.

Placing Players Through Program Registration With Multiple Teams Allowed

When a program allows players to be placed on multiple teams, the graphical drag-and-drop Roster Workspace is not used.

Instead, players can be assigned to teams individually using the team placement controls, including +TEAM.

This workflow allows a player to remain on one team while also being added to another team when the program's structure requires multiple team assignments.

For example, a player participating in a program that requires placement on both a primary team and an additional team can be assigned to both teams without replacing the original team assignment.

The important distinction is that Multi-team placement allowed changes how roster placement is managed within the Program Registration. With the setting enabled, administrators use the multi-team placement controls rather than the graphical one-team-per-player workspace.

Placing Players Through a Spreadsheet Upload

For larger roster movements, Byga also provides a player upload workflow.

Rather than adding players individually, a club can prepare player information in a spreadsheet and upload the players in bulk. This can be useful when a club already has a finalized roster list outside of Byga and needs to bring a large number of players into the appropriate teams.

This approach can save significant time when forming multiple teams or making a large roster update. Byga's Program Registration documentation also identifies Upload players as an available workflow from the Players area of a program.

For large roster imports, review the spreadsheet carefully before uploading to make sure the player information and intended team assignments are correct.

Choosing the Appropriate Placement Method

The different placement methods are designed to support different roster-building situations.

Tryout +TEAM is useful when team decisions are being made as part of the Tryout process.

Team Roster placement is useful when an administrator is already working from an established team and needs to add, move, or reorganize individual players.

Player Profile placement is useful when the administrator is already working with a specific player and needs to manage that player's team relationship.

Program Registration Roster Workspace is useful for visually building rosters from a registration player pool when the program uses one team per player.

Program Registration +TEAM is used when the program allows players to be placed on multiple teams.

Spreadsheet upload is useful when a club needs to place or update a larger number of players at once.

These workflows can also be used at different points during the season. A club might initially build teams through Tryouts, make individual adjustments from Team Rosters or Player Profiles, and later use roster imports or Program Registration tools as additional players are added.

Teams Do Not Always Have to Be Tied to a Registration

A team in Byga does not necessarily exist only for the purpose of collecting registration information or payment.

Some teams are used as part of a competitive registration workflow. In this situation, the team can function as the roster or invitation group associated with that registration.

Other teams may primarily exist for communication and scheduling. For example, a club may create a team so that players, families, coaches, and staff can receive team communication and access the appropriate schedule, even when that team is not being used as part of a particular registration.

This means that placing a player onto a team can serve a purpose beyond registration. The team assignment can establish the player's ongoing relationship with that team's schedule and communication.

Team Placement and Registration Workflows

Once players have been placed onto teams, the club can determine how, or whether, the player proceeds through registration.

For competitive programs using Invite Based Registration, the team can be used as the invitation list for the registration. This allows the club to build the roster first and then use that team relationship as part of the registration workflow.

Byga also supports registration workflows where registration is used primarily to collect player information rather than simply to collect payment.

The important distinction is that team placement and registration are separate decisions. First determine how the player should be organized within the club. Then determine which registration workflow, if any, should follow that placement.

Placement Acceptance as an Optional Step

Clubs using a competitive placement and registration workflow can also choose whether to use Placement Acceptance.

Placement Acceptance can be useful when the club wants a player or family to formally accept a roster offer before completing registration. Depending on how the club configures its workflow, acceptance can also include a deposit.

However, Placement Acceptance does not have to be part of every club's process.

A club may choose to use Placement Acceptance when it wants an explicit acceptance step between team placement and registration. Another club may choose to move players directly into the Registration phase when the player is already expected to proceed with registration.

Placement Acceptance can also be configured around the club's preferred approach to communicating the team assignment. In some workflows, a specific team is part of the acceptance process; in others, the club may use Acceptance without relying on the acceptance step to communicate the final team details.

The important point is that Placement Acceptance is an option within the overall workflow, not a requirement for building a roster.

Maintaining Rosters After Initial Placement

Team placement does not have to be a one-time action.

As the season develops, administrators may need to move players between teams, add players to existing rosters, remove players, or reorganize teams. The Team Roster provides controls for these ongoing changes, including Move to another team, Remove player from roster, and roster import tools.

This allows clubs to continue managing team formation after the initial placement process is complete.

Once rosters are established, the club can then determine whether those teams will be used for registration, invitations, communication and scheduling, or a combination of those functions.

Review this document on Teams Directory Management for help with the team management process. You also have options to review documents on Team Invite-Based Registrations or Program Registrations.