Decision Tree
Decision Tree
Lauke FC · Performance Suite
A decision guide across all 11 dashboards. Start from the question you are trying to answer, follow the branch, and land on the dashboard built for it — plus the ones to pair it with.
Tap a dashboard to highlight everywhere it appears ·
Readiness
Load & output
Injury risk
In-game performance
Integration
Fast router · one question, one dashboard
How does he feel today?
Subjective flags + yesterday's internal load.
Is he neuromuscularly fresh?
Objective fatigue you can't feel.
Can he play — one glance?
Readiness + recent load + flags, combined.
Did we load the week right?
Compliance vs plan + ACWR.
Is he at injury risk?
Hamstring/sprint-specific → HSRAS.
How did he do in the match?
Did he fade over 90' → xPO.
The full tree · six branches
Is this player ready to train or play today?
You want the subjective picture — sleep, soreness, stress, mood.
Read the daily flags and yesterday's session-RPE (internal load). Two or more red flags = confirm objectively before deciding.
pair with: CMJ · PSQ
You want an objective neuromuscular read — fatigue he can't feel.
Jump height / mRSI drop vs his own baseline. A clear drop with normal wellness = accumulated neuromuscular fatigue.
pair with: WEL · IR
You want one combined answer right now, no digging.
Snapshot that already folds in readiness, recent load and active risk flags. Your triage screen before training.
pair with: WEL · CMJ · IR
Context — it's MD-1 or matchday: readiness is the whole question.
Prioritise the freshest objective + subjective signals; PSQ resolves conflicts between them.
pair with: PSQ
Context — mid-week, deciding whether to push or hold load.
Readiness (CMJ) tells you if he can take load; ITCS tells you if the plan needs it.
pair with: ITCS
What load did he get, and are we loading correctly?
A single training day.
TD, HSR, Acc, Dec vs his personal best. A benchmark spike you don't like = jump to IR.
pair with: IR
A match.
External match load, sliceable by half and drill (half-sums only — never Entire Session). "Did he hold up?" = xPO.
pair with: xPO
The whole microcycle, measured against the plan.
Compliance vs each player's top-3 targets across MD-4 → MD+2, plus ACWR. Under 45' → MD+1 compensation targets.
pair with: IR · DR
Load relative to his own season match profile — did his output hold up.
In-game decay scored against his personal season curve, not a group average. Reads sub timing and position context.
pair with: GP
The player is a goalkeeper.
Dives L/R, GK load & power, average dive impact + running volume. Asymmetry or impact spikes = cross-check IR.
pair with: IR
Is he at risk, and why?
The signal is load-driven — ACWR, spikes, eccentric load, L/R asymmetry.
Integrated risk score from eccentric-load monitoring, load-spike detection and step-balance asymmetry. Your squad risk board.
pair with: DR · ITCS
The concern is hamstring / sprint-mechanics specific.
S-MAS sprint-mechanics faults from max-velocity video, weighted with sprint, HSR and neuromuscular load into a 0–100 index.
pair with: GP · IR
You suspect the week itself is overloading him — early warning.
ACWR climbing + compliance running hot flags a periodisation problem before it becomes a risk-board problem.
pair with: IR
A player flags red — now confirm the cause.
Load history → DR + ITCS · neuromuscular state → CMJ · full context before a decision → P360.
pair with: DR · ITCS · CMJ · P360
How did he perform in the game?
You want the raw external output — TD, HSR, Acc, Dec, max speed.
Per-game player table with % vs each player's max-game baseline. The what-happened layer.
pair with: xPO
You want to know if he faded over 90' vs his own norm.
Decay curve per 15-min block against his season profile — separates "slow starter" from "genuine drop-off".
pair with: GP
Sprint exposure & mechanics under match fatigue.
High sprint/HSR exposure combined with technical faults is the hamstring warning you act on next session.
pair with: GP
Post-match carry-over into the coming week.
Feed match load into MD+1/MD+2 planning; under-45' players get compensation targets in ITCS.
pair with: ITCS
The player is a goalkeeper.
Dive count/impact and GK power tell the match story that outfield GPS metrics miss.
pair with: IR
Tell me everything about this one player.
You need the right-now answer — fit to play, recent load, active flags.
The "now" rollup. Start here for a single player before a session or a selection call.
pair with: WEL · CMJ · IR
You need the season-long integrated profile.
One profile across load, risk, compliance, readiness and match output over the season. The staff-meeting view.
drills into: all specialist dashboards
From the profile, drill into whatever flags.
Readiness → WEL / CMJ · load → DR / ITCS · risk → IR / HSRAS · match → GP / xPO · keeper → GK.
P360 is the map; the specialist dashboards are the terrain.
Give me the whole group at once.
Today's group training load.
Whole-squad daily external load in one screen, each player vs his own best.
pair with: ITCS
Weekly compliance across the squad.
Who is under- or over-loaded against plan this microcycle, at a glance.
pair with: IR
Risk board across the squad.
Load-based risk ranking; add HSRAS for the hamstring-specific list.
pair with: HSRAS
Readiness board before training.
Subjective and objective readiness side by side; PSQ per player for the outliers.
pair with: PSQ
Fastest triage — who do I look at first.
Scan the snapshots, then open the specialist dashboard only for the players that flag.
pair with: P360
Every dashboard runs on the same StatSports data model and the same player/match identity, so a name means the same player everywhere and match days sum only the four halves (never Entire Session).
PSQ is the "now" rollup and P360 is the "season" rollup — neither replaces the specialist dashboards, they route you into them. The readiness pair (WEL, CMJ) and the load layer (DR, GP, GK, ITCS) feed both the risk layer (IR, HSRAS) and the performance layer (xPO), and all of it surfaces in PSQ and P360.
Rule of thumb: ask the question first, pick the layer, then the dashboard. Readiness before load, load before risk, and integration (PSQ / P360) whenever a single answer isn't enough.
Laurens Ebben · Head of S&C