An assessment groups several metrics into a single testing or screening protocol — a CMJ, a pro agility drill, a neck strength test, a DEXA scan — so you can record every input for that test in one place instead of hunting down separate metrics one at a time. You can also build a custom formula from an assessment's metrics to calculate a derived score automatically.
[Screenshot: the New Metric drawer showing the Assessment type option]
Building an assessment
Assessments are created from the same place as any other metric: choose Assessment as the type, then give it a name, a measurement type, and — if you want one — a unit. From there, an assessment is really just a shell until you add the metrics that make up its testing protocol.
You can also add a description explaining the purpose of the assessment and how it's conducted, and attach an instructional video — useful if other coaches or staff will be the ones running it, or if athletes need a reference for how the test should be performed.
Adding metrics to an assessment
There are two ways to add a metric to an assessment:
Create a new metric — build a metric from scratch that belongs to the assessment, the same way you'd build any other metric.
Insert an existing metric — pull an existing metric into the assessment as one of its inputs.
Inserting removes a metric from the main list
Inserting an existing metric into an assessment associates it with the assessment as part of the testing protocol and removes it from your main metrics list. It's still a fully functional metric — it can be used for reporting, conditional logic, and everything else a metric can do — it just now lives under the assessment.
[Screenshot: adding metrics to an assessment, showing both the create and insert options]
Tracking percentile
Turn on Track percentile if you want FYTT to calculate where each athlete's result ranks against the rest of the group as a percentile, in addition to the raw value.
Calculating a score with a formula
If a test protocol should produce its own derived result — a composite score, an index, a pass/fail threshold — give the assessment a custom formula. The assessment's own metrics become available as inputs, and once every input has a value for an athlete, FYTT calculates the assessment's output automatically and stores it as its own measurement.
Running an assessment
An assessment is comprised of one or more metrics that define its protocol. Once it's built out, you can collect results for it in two ways.
The assessment grid
Every assessment has its own grid — a spreadsheet-style view with a row for each athlete and a column for every metric in the assessment, plus a column for the assessment's own output if it uses a custom formula. Changing a cell's value creates or updates a measurement as of the date set in the grid's filter. If the assessment has a formula, FYTT recalculates its output in the background as soon as the inputs it depends on are updated.
You can right-click a cell to bring up a summary view for that athlete and metric, showing past measurements and letting you add or edit values without leaving the grid.
[Screenshot: the assessment grid with metric columns and a calculated output column]
Adding an assessment to a workout
You can also add an assessment directly to a workout as part of an athlete's training. When the workout is delivered, the athlete is able to record values for all of the metrics included in the assessment themselves, rather than a coach entering results through the grid.
Like any metric, an assessment can be marked athlete-facing if you want athletes to be able to see their own results outside of a workout as well.
Where results go
An assessment doesn't create its own separate data store — every value recorded for it, including a calculated output, is saved as a regular measurement on the underlying metric. That means assessment results show up everywhere metric measurements do: on athlete and group reports, in leaderboards, as conditions in automations, and as inputs to other formulas.
See the metrics guide for more on how measurements behave once they're recorded. Assessment data can also be exported to CSV from the metrics export tool if you need it outside of FYTT.
[Screenshot: an assessment's metric measurements appearing in an athlete report]
Assessments vs. surveys
Assessments and surveys are both ways of grouping metrics together, but they serve different purposes. An assessment is built for objective testing you or your staff administer — a CMJ, an agility test, a body composition scan — and results are typically entered by a coach through the grid or captured during a workout.
A survey, by contrast, is built to collect subjective, self-reported data directly from athletes — readiness, wellbeing, soreness, sleep quality, nutrition, or hydration — and can be pushed out through a workout on the phone or tablet apps, or delivered on its own through automations. Because both are metric types under the hood, results from either one flow into the same reports, leaderboards, and formulas as any other metric.