FYTT's metrics hub allows you to create metrics for anything you might want to track—one-rep maxes, heart rate thresholds, nutrition data, wellness factors, readiness indicators, testing protocols, sprint profiles, surveys, and more. Everything you track can be managed in one place, and the metrics can be seamlessly integrated into your programming to provide data-driven training to your athletes.

At the heart of the metrics hub is the overview grid, which utilizes our unique "power grid" functionality for displaying and managing measurement data. The overview grid is laid out with a column for each metric utilized by the team and a row for each athlete on the team. By default, the overview grid includes the built-in metrics for athlete height and weight.

Each cell in the overview grid displays the most recent measurement within the time frame defined in the grid filter, which defaults to 45 days from today.

Changing the value of a cell will create a new measurement for the given athlete and metric as of the filter date, or update the existing measurement if one already exists for the given date.

The grid filter, located at the top of the grid, allows you to quickly search for and isolate athletes, as well as adjust the parameters used for displaying data on the grid. Click on the "filter" icon to open and adjust the filter parameters. You can change the "as of" date and the number of days to look back. You can also filter the athletes in the grid by group membership and coach assignment.

The power grid has a summary view that can be accessed by right clicking on a grid cell, which will display a summary of data for the given athlete and metric.

This view shows you all the athlete measurements within the filter's specified timeframe in both graphical and tabular format. You can click on a measurement row to edit it. If you hover over the graph and click the "add" icon, you can add a new measurement.

Within the summary view for custom metrics (not the built-in height and weight), you have the ability to enter an override value for the athlete, as well as a reason for the override.

This can be used to override an athlete's working measurement for a given metric. This can be useful in situations where a coach wants to prescribe individualized exercises from the metric using a specific value without recording a measurement. For example, when an athlete is returning to play from an injury or sickness.

When an override is in effect, the overview grid will display the override value in orange with the most recent value crossed out to indicate that the override is being used for exercise prescriptions.

A metric is a fundamentally simple object that allows you to track athlete measurements for a key measure of health or performance over time. Metrics can be used to track virtually anything, ranging from 1RMs to joint range of motion to subjective factors like fatigue and motivation.

Since data is useless unless it leads to action, metrics in FYTT were designed with the end goal of using measurements to drive data-driven training. See the the workouts guide and the automations guide for more information on incorporating metrics into the design and delivery of athlete training.

A metric's measurement type defines the primary dimension for which the measurement is being made. For example, a lift metric like Back Squat 1RM should have a measurement type of "weight," a vertical jump metric should have a measurement type of "height," and so on.

The measurement type definition has a few key implications for how it is used throughout the platform:

For metrics that fall outside the standard set of measurement types, you can set the measurement type to custom and use a custom unit. However, as of right now, custom metric types cannot be used for exercise prescriptions, though they can be used in conditional logic and workout modifiers.

The exercise definition for a metric is optional, but you should define it if there is a specific exercise performed when an athlete tests for the metric. This not only adds clarity to the metric definition, but it will also speed up workout building by telling FYTT how to prescribe an exercise attribute for a given exercise when the metric selection is left to "auto."

Use the measurement specifications to spell out any additional parameters that need to be communicated for the test. For example, a metric for a Bench Press estimated one rep max would specify weight as a measurement parameter, because weight is the primary dimension being measured. It would also have reps specified as a measurement parameter, because the number of reps is one of the testing inputs.

The main goal with the measurement specifications is to spell out for coaches and athletes exactly what parameters make up the metric testing protocol.

Metrics can have a custom formula option that allows you to input a formula to calculate a derived output.

Formula inputs are limited to numbers, equation operators, and the standard measurement parameters (calories, heart rate, distance, etc.). For example, if we wanted to write the Epley equation to calculate an estimated 1 rep max based on a 3 rep maximal effort, we would use the following inputs:

See the formula field guide for more info on building custom formulas.

Each metric has a "Track percentile" setting that allows you to turn percentile tracking on or off for the metric.

With percentile tracking on, every athlete's percentile rank is automatically calculated for the metric. Percentiles are calculated using the most recent 1,000 measurements for all athletes at the institution.

An athlete's percentile rank for a metric can be viewed in one of two ways.

In the summary view:

Within group reports, athlete reports, and the athlete dashboard: