Concerns

Concerns is an automatic triage feed. Instead of reading every chart looking for problems, you open Concerns and the platform tells you which athletes to look at and why.

Who can use it: everyone can view the feed; admins and coaches can dismiss and restore concerns.

What gets flagged

Concerns are grouped into four categories. Use the filter tabs at the top to focus on one — tabs only appear for categories that currently have something in them.

• Injury risk — rising load (ACWR in the caution or high band), a spike in high-speed running or sprint volume, repeated near-maximal speed exposure (reaching ≥95% of MSS in several recent sessions — the "top-end reach" pattern from Speed Progress, flagged so recovery between top-end sessions can be managed), overdue for top speed (the opposite: a player who has been training but hasn't opened up to ≥90% of MSS in over two weeks — speed is use-it-or-lose-it, and the red chip on the Speed Progress exposure timeline), persistently low high-speed exposure (a deficit that has held across several weeks, not a single quiet week), or extra load from a second club.
• Fatigue — load that has dropped off after a heavy block, or a decline in jump output (CMJ or RSI) against the athlete's baseline.
• Engagement — patterns that suggest a player is dropping out of the routine.
• Data — data-quality issues worth a look (for example, a player who should be producing GPS data but isn't).

Jump-based concerns only appear if Jump testing is enabled, and gym concerns only if Gym is enabled. Injured or unavailable players are suppressed so the feed stays about actionable problems.

Working the feed

Each concern is a card with the athlete, the category, and an evidence panel you can expand to see the numbers behind the flag, the threshold it crossed, and — where the data supports it — a small trend sparkline of the recent weeks so you can tell a first-week blip from a signal that has been building. Concerns are ordered by urgency — the ones that warrant action first.

Where a flag is built on thin data — for example a high-speed ratio off a base that's barely there — the card says so and drops to a lower tier, so a big number off a small denominator doesn't read as an emergency. The platform describes and interprets; the call on what to do stays yours.

For each one you can:

• Dismiss — clears it. Use this when you've handled it or it's a known situation.
• Watch / snooze — quietens it for about a week, then it can resurface if the underlying signal persists.
• Restore — bring back something you dismissed.

Think of Concerns as a worklist: clear it regularly, and an empty feed is a good sign rather than a missing one.

Related

• Load management — the load data behind injury-risk flags.
• Wellness — subjective readiness, complementary to these flags.
• Jump testing — the source of CMJ/RSI decline flags.