Skip to content

Readiness

The Readiness screen brings together, for each player, today’s readiness and the reason for that colour. It crosses two sources: the subjective input (the daily check-in) and the load actually absorbed.

Two tabs:

  • Today: the whole squad’s readiness for the day, sorted from most at risk to most ready.
  • Evolution: a player- and metrics-oriented tab where you see each player’s load and readiness over the period at a glance, correlated with sessions and matches, with a detailed per-player zoom.
  • Subjective comes from the check-in: fatigue (out of 5), hours of sleep, motivation (out of 5) and pain (yes / no).
  • Load comes from the session reviews: every training or match produces an sRPE load.

Each session produces a load equal to duration (min) × RPE (1 to 10 scale). A match counts a bit more: minutes played × RPE × 1.2. The detail and the formula are managed on the Training load page.

ACWR compares recent load to habitual load:

  • Acute load = sum of load over the last 7 days (the week).
  • Chronic load = sum of load over the last 28 days.
  • ACWR = acute load (7 d) ÷ (chronic load (28 d) ÷ 4), i.e. the week’s load relative to the average weekly load over the last 4 weeks.

An ACWR around 1 means the player is absorbing what they are used to. The balance zone shown on the chart is 0.8 to 1.3: above it, overload risk; below 0.8, undertraining.

The colour combines the subjective input and the ACWR. With the default (football) thresholds:

ColourConditions (any one is enough)
Redpain and fatigue ≥ 4/5 · or fatigue ≥ 5/5 · or ACWR > 1.5
Amberfatigue = 4/5 · or sleep < 6 h · or ACWR between 1.3 and 1.5
Greenall other cases

If a player has done their check-in but no load is logged yet for the day, the colour relies on the subjective input alone (pain, fatigue ≥ 4 or motivation ≤ 1 → red; fatigue = 3 or motivation = 2 → amber).

The readiness percentage turns the colour into a number so it can be averaged across the team: red = 30%, amber = 65%, green = 100%. The “average readiness” shown at the top of the Evolution tab is the average of these scores.

A strip of cards summarises the squad over the period: average readiness, % of players ready, average ACWR and load over the last 7 days.

Each row shows the player, today’s readiness, their ACWR and its trend, plus a sparkline: daily load bars topped by the readiness line. The most at-risk players rise to the top. A click opens the detailed zoom.

The zoom details one player over 14, 28 or 56 days:

  • Daily readiness: one cell per day, green / amber / red. An empty cell means no check-in that day.
  • Markers: a triangle marks a match, a dot marks a training session.
  • Load & ACWR: the bars give the day’s load (a taller bar capped in white = a match, the fainter bars = training); the bright line tracks the ACWR; the green band is the safe zone (0.8 to 1.3).
  • Next event and recent check-ins round out the context.

A measured state comes from a real check-in. Between check-ins, STRIVN does not let readiness go stale: the model projects fatigue day by day from the last check-in (each session or match pushes it up by intensity, rest brings it down). Only fatigue is estimated; load and ACWR are always measured.

Every estimate carries a confidence (the “Estimated · X%”). It drops the older the last check-in gets, and when sessions happened without their load (RPE, duration) being logged. Below 50%, the player moves to “To re-check”: no firm colour is shown and they are not counted among at-risk players. A new check-in validates the estimate and corrects the preceding days. On the chart, estimated days are hatched, measured days are solid.