A trend follows one metric you already record and works out a value for every athlete, every day, from their own readings of it: their recent normal, how far today sits from it, how much they've changed, how fast they're moving, or their best lately. Nobody enters these values. This guide covers when to use a trend, creating one, reading its values, and changing or deleting it.

Use a trend for a metric that doesn't add up into a total: a 1RM, bodyweight, jump height, sprint times, wellness and readiness scores, or Session RPE, where a 7-day average shows each athlete's typical session rating (see Session RPE & load). A week of readiness scores means something averaged; added up, it means nothing. For a metric that does add up, such as distance, minutes, or tonnage, use a Training load, which totals it over a period and compares that total with a longer baseline.

On the Metrics tab, click Add metric, then choose Trend (1).

Or start from the metric itself: on its page, open Trends and loads (1) and choose New trend (2), which fills that metric in for you. The menu also lists the trends and training loads already built on the metric. It shows only on a metric a trend can follow, to staff who can edit it.

In New trend:

FYTT then works out the last 90 days for every athlete. The data page shows Calculating the last 90 days while it runs, usually a few minutes.

Once a metric is chosen, the name suggests itself from the metric and the formula, such as "Countermovement Jump · 28-day change", with a Suggested badge. It follows your choices until you type your own.

Any metric you record can be the Metric to follow, including a survey question, a metric you test inside an assessment, Session RPE, and the built-in Height and Weight, which a trend reads in your organization's measurement system. An assessment, a sprint profile, or a survey as a whole can't, and neither can a training load or another trend.

Each formula has one setting in days, from 1 to 365, and skips days without a reading rather than counting them as zero. An athlete with fewer readings than a formula needs has no value.

Use Change from baseline (1) to see whether an athlete's jump or readiness is trending down: a negative value means their latest reading sits below their own normal. Set the Baseline, in days (2), and choose z-score under Shown as (3) to put every athlete on one scale, where −1.5 is unusually low whatever the metric's units.

Under Settings, add a Description, or turn on Visible to athletes so athletes see their own value in the app; it's off until you turn it on. There's no ranking setting: a trend ranks the way its metric does, so for a lower-is-better metric such as a sprint time, a negative change is the improvement.

Click View data beside the trend on the Metrics tab, or in its panel. Each athlete's row shows their Latest reading of the metric with its date, and the trend's value (1) as of the date in the toolbar (4), which reads Today until you pick another. A change carries its sign, + or −, and the athletes with the lowest change come first, so whoever is furthest below their normal sits at the top.

Hover a value (2) to see the readings behind it. The rail restates the setup, and its About section (3), closed until you open it, explains what each value means, which sign is better, and the name the trend goes by in charts, reports, and automations.

An athlete without enough readings in the window has no value, not a zero. Change from baseline and Rate of change need 3, Percent change 2, and the others 1. Hover the blank to see what's missing, such as "Needs 3 readings · has 1".

When an athlete stops testing, the trend keeps their last value rather than dropping it, so reports, leaderboards, and automations still use it. Once their latest reading is older than the window (for Change from baseline, the baseline), the value fades beside a clock, and hovering it says when it was last updated. It updates with their next reading.

Trend values are calculated, not recorded, so nothing on the data page can be edited, and the trend's column on the Data tab is read-only. An import doesn't write to a trend either: a CSV column with a trend's name creates a new metric. To change a value, correct the reading behind it, or change how the trend is worked out.

A trend updates whenever its metric is recorded, and FYTT recalculates every trend's last 7 days each night, so averages and bests move as old readings leave the window.

A trend works like any other metric in Reports, Leaderboards, and Automations, so an automation can act when an athlete's change from baseline drops below a value you choose. Flex reads a trend's values and knows how it's worked out. A trend can't be prescribed in a workout, and a transfer doesn't copy it. A formula can't look back over time; a trend can. For metrics in general, see Metrics.

Click the trend's row on the Metrics tab, or Edit at the top of the Info rail on its data page, make your changes, and click Save changes. A new Metric to follow, formula, or setting asks first: Recalculate 90 days of history? lists each change, old to new, and Save and recalculate replaces the last 90 days of values for every athlete. A new name, color, description, or visibility saves without asking. A name that's still the suggested one follows your new choices.

To delete a trend, click Delete in its panel and confirm with Delete trend. Its values are removed, and charts, reports, leaderboards, and automations stop showing it. Readings of the metric it follows aren't touched.

If you delete the metric a trend follows, FYTT warns you first that the trend will stop updating. Its values are kept and reports still use them, and its data page says Source metric deleted. To start it again, click Edit and choose another Metric to follow.