Groups allow you to organize your athletes so you can easily create multiple concurrent training paths. You can manually add athletes to groups from the roster, or you can add conditions to a group that will cause athletes to be automatically added or removed based on whether or not those conditions are met.

DEFAULT GROUP

Every team has a "default" group labeled "Team." All new athletes are added to this group by default. The purpose of the default group is to provide a way to assign programs to the entire team. You can add and remove athletes from the default group like normal, but all athletes belong to the group at the beginning. (Example use case: you assign a program to everyone on the team, but an athlete gets injured, so you need to move them to their own separate track.)

CREATING GROUPS

To create a group, use the team's main menu to navigate to the "Groups" page. The only required attribute for a group is a name, but you can optionally add a description, category, and conditions.

CATEGORY

The category is intended to be used in conjunction with conditions (explained below) to create a hierarchy of groups. For example, suppose you have three groups: Ankle Corrective, Knee Corrective, and Hip Corrective. Each of these groups has conditions to automatically add athletes, but you only want athletes to be part of one of these three groups at any given time.

To accomplish this, you would simply add each group to the same category, then assign the priority of each group. Let's say you added all three of the groups to the "Corrective" category, and your priorities are assigned as follows:

  1. Ankle Corrective
  2. Knee Corrective
  3. Hip Corrective

Now suppose we have an athlete that meets the conditions for both the Knee Corrective and Hip Corrective groups. The athlete will only be added to the Knee Corrective group, because it has the higher priority within the "Corrective" category.

If membership within a group is not mutually exclusive (athletes can belong to other groups as well), then simply leave the category section blank.

CONDITIONS

Group conditions allow you to define the criteria used to automatically add or remove athletes from the group. These conditions follow a simple "if this and/or that" style of logic. Below are a few examples.

Single Condition

Suppose you had a "Conditioning" group that you wanted athletes to follow if their body fat percentage was above a certain threshold. You can easily add a condition for this scenario. (The following example assumes that a KPA of "Bodyfat %" has already been created. See the KPAs guide for more info on creating KPAs.)

With this condition in place, athletes will be added to the group anytime their "Bodyfat %" KPA is updated with a value above 25%. If their value falls below 25%, they will be removed.

Multiple Conditions

Stringing conditions together is pretty straightforward, and you have the flexibility to create rather sophisticated logic.

Once you've added your first condition, there's two options for adding more conditions. The first is to use the "Add Condition" button, which adds another "group" of conditions. Think of each group of conditions as being enclosed in parentheses.

The second option is to use the "+" button at the bottom of a condition group. This is like adding another condition within the parenthetical group.

Thinking in more "spreadsheet-like" language, the above logic is equivalent to the following:

(BF% >= 25% and BF% < 35%) or (BW >= 250 and BW < 300)

MANAGING GROUP ASSIGNMENTS

Athlete group assignments can be managed in one of two ways: 1) you can manually add and remove group assignments from the roster, or 2) group assignments can automatically be managed based on the group's conditions.

MANUAL GROUP ASSIGNMENTS

You can use the roster to quickly add and remove group assignments manually. (For more info on using the roster to manage groups, see the Roster guide.)

AUTOMATIC GROUP ASSIGNMENTS

When a group has conditions, there are three events that will trigger the evaluation of those triggers and cause athletes to be added or removed:

  1. When KPIs or KPAs are changed from the roster
  2. When a KPI is assessed and recorded by an athlete from a mobile device
  3. When a KPI is assessed and recorded by a coach from the whiteboard

USING GROUPS IN PLANS

The practical application of groups with conditional logic is ultimately realized in the plans tool. Once all your logic is setup, you can build out separate programming for each group in the plan, along with scheduled assessments to trigger the evaluation of group logic and the automatic assignment of athletes.

For example, suppose you have a four-week training block, and you want to divide athletes into one of three different tracks based on a series of KPI tests. You would first create your groups with their respective logic and category / priority pairs.

Next, on the plan, you would create a testing track for the entire team in week 1. This could be a very simple program that only has a single session containing the assessment protocols.

You would also out the programs for each of the different groups on the plan.

With this in place, after the assessments are recorded on day one, the logic will be evaluated for all the groups, and the athletes will automatically be added to the appropriate group based on the results of their assessments and the hierarchy of the groups. (See the Plans guide for more info on building out programs within plans.)

Theoretically, you could test every single day, and athletes would switch groups based on the daily testing results. How often you want to trigger group changes through assessments is up to you.

Did this answer your question?