Load ratio

Load ratio

ForCoachesViewersClub adminsPlayers

The load ratio compares what a player did in the last 7 days with what they are used to. It answers one question: is there too big a jump somewhere?

Acute and chronic

Two numbers go into the ratio:

  • Acute load: the total load of the last 7 days, today included. What the body has just done.
  • Chronic load: the total of the 21 days before those 7, divided by three. That is the player's usual week: what the body is used to.

Load ratio = acute ÷ chronic. If a player usually does 1,600 a week and did 2,100 in the last 7 days, the ratio is 2,100 ÷ 1,600 = 1.31.

Load ratio, worked out Try it — nothing is saved

Days 22–28 ago

1,500 AU

Days 15–21 ago

1,650 AU

Days 8–14 ago

1,650 AU

Last 7 days

2,100 AU

21-day weekly average 1,6002,100 ÷ 1,600 =1.31Rising — keep an eye on it

Clearly more than usual. Fine now and then, but keep an eye on it.

Each week is the sum of RPE × minutes for every session in it. A day without a session adds zero.

What the numbers mean

RatioColourThe app saysWhat it means
above 0.8 and below 1.3GreenOn targetAbout as much as usual.
1.3 or moreAmberRising — keep an eye on itClearly more than usual. Fine now and then, not week after week.
1.5 or moreRedBig jumpMuch more than the body is used to.
0.8 or lessBlueBelow usualLess than usual: rest, an injury, or missing answers.
–GreyNot enough history yetNo sessions in the 21 days before, so nothing to compare with.

Why these thresholds

Bodies adapt to the work they get used to. Trouble tends to come from sudden change rather than from hard work as such. In sports science, a ratio between about 0.8 and 1.3 is the commonly cited "sweet spot". Above 1.5 the risk of injury is reported to climb steeply. Far below 0.8, the player is losing the fitness the usual load keeps up, and the next normal week will feel like a jump.

The ratio is a prompt to look and talk, not a diagnosis. It knows nothing about a player's history, illness or the kind of session. Use it together with what the player tells you.

Rest days count as zero

A day without a session adds zero load. That is on purpose: a rest day is real information. A player who rests a lot this week gets a low ratio; a player coming back from two quiet weeks gets a high one when normal training starts.

The other side of this: a session the player forgot to log also counts as zero. A ratio that looks too low is often missing answers. The week view shows the gaps.

The Load ratio page

Where to find it
Where
Load ratio under Team in the menu.
Who
Coaches (their teams), viewers and admins (every team).
Load ratio
On targetFrom 1.30: risingFrom 1.50: big jumpUp to 0.80: below usualReadiness and sleep compare averages: from 0.90 falling, from 0.80 a big fall.
Readiness to trainLoad
PlayerReadinessSleep (h)Sleep qualityLoadMinutesDistanceHigh-speed runningStrain points
Aleksi HeinoFWD0.790.890.811.621.311.411.651.27
Eetu MäkeläMID0.940.990.971.341.161.181.271.16
Leo KarjalainenMID0.790.950.931.121.091.040.98–
Joona LehtinenDEF1.031.011.031.051.051.051.051.02
Ville RantanenGK0.991.011.010.950.970.960.880.94
Oskari NieminenDEF0.970.970.990.920.900.740.700.78

Totals (load, minutes, GPS) compare the last 7 days with the weekly average of the 21 days before; readiness and sleep compare averages, and a fall is what is flagged.

Readiness to train on the left, load on the right. Hover a ratio to see its two numbers. Players with an alert come first.
  • One row per player, with the players who have an alert first.
  • One column per measure, in two groups. Readiness to train comes first: readiness, recovery before sessions, sleep hours and sleep quality. Then Load: load and minutes, then the GPS measures (distance, high-speed running, strain points, sprint distance, sprints, accelerations, decelerations).
  • A measure no player has any history for, such as GPS before the first vest import, gets no column.
  • Hover a ratio to see its two numbers: the 7 days and the 21-day weekly average.
  • As of picks the day the 7 days end on. Use it to look back, for example at the day before an injury.
  • A dash means not enough history for that measure yet.

Wellness: a fall is what counts

For readiness, recovery before sessions and sleep, more is not a risk. Here the app compares the average of the last 7 days with the average of the 21 days before, and flags a fall:

  • 0.9 or less (amber): the player feels clearly worse than usual.
  • 0.8 or less (red): a big fall. For readiness, sleep hours and sleep quality, this puts a tag such as "Readiness falling 0.79" on the board's Needs attention list.

Days without a morning check-in are left out of these averages. A missing answer is not a zero.

On the readiness and sleep columns amber and red mean a fall, and the badge says so ("Falling — keep an eye on it", "Big fall"); the legend above the table gives their thresholds.

The ratio over time

On the player page, a line shows the load ratio for every day of the period, with the green band from 0.8 to 1.3 and a red line at 1.5. With GPS data, you can switch the line to distance, high-speed running or strain points. A player's own My stats has no line: it shows today's ratio of every measure as a badge instead.

Load ratio over time
0.511.518/924/930/96/1012/1018/1024/10

The last 7 days’ total against the weekly average of the 21 days before. The green band (0.8–1.3) is the usual target; above 1.5 the jump is large.

A quiet fortnight, then a fast build-up: the line leaves the green band and crosses 1.5 for a few days.

The morning alert

Early every morning (07:00 Finnish time in winter, 08:00 in summer) the app checks each team. If any player's load ratio for yesterday is 1.5 or more, the team's coaches get one notification listing them, for example "Aleksi Heino 1.62". Yesterday, because today's sessions have not happened yet. See Inbox, reminders and alerts.

Other measures

Minutes and the GPS measures work exactly like load: a 7-day total against the 21-day weekly average. The board flags distance, high-speed running and strain points the same way as load, from 1.3 and 1.5. GPS measures need imported vest files; see GPS import.