Cross-system athlete availability status board
Problem
Whether an athlete is safe to train tomorrow depends on three separate logins: the GPS and wearable tracking platform for yesterday's load, the wellness survey tool for this morning's soreness and sleep scores, and the medical and injury records system for anything flagged by the physiotherapist. The strength and conditioning coach checks one, the sports scientist checks another, and a medical hold often reaches the training group as a message rather than a system flag. On a busy morning nobody has time to open all three before the session starts, so the call gets made on memory and whichever number was checked last. A load spike or an unresolved medical hold can slip through simply because the three screens were never open at once.
Product idea
A single status board, one row per athlete, pulling together yesterday's load against their own rolling average, this morning's wellness flag, and whether medical has placed a hold — nothing else. Each row shows green, amber or red with the reason stated in one line, not a score to interpret. Thresholds are configured per squad or per athlete by the Head of Performance: a load spike over an agreed level, two consecutive red wellness days, or any open medical hold triggers an alert to a named person by a set cut-off before the next session. It does not decide who plays or trains — it stops a flag from being missed because nobody had the three tabs open.
Who it is for
Strength and conditioning coaches and sports scientists checking status before a session, and the Head of Performance who sets thresholds and is the escalation point when a flag is missed.
Possible first version
A single web dashboard fed by daily CSV or spreadsheet upload — load figures exported from the GPS platform, wellness scores exported from the survey tool, and a manually entered medical hold flag. One row per athlete with a red/amber/green status and the reason. Configurable thresholds per squad. Email alert to a named recipient when a threshold is crossed, sent by an agreed cut-off time each morning. Out of scope for version one: live API integration with any GPS, wellness or medical system, SMS alerting, and any automated return-to-play recommendation.
- Build classification
- Workflow application
- Rough effort
- 4-6 week first release
- Roles involved
- Head of Performance, Strength & conditioning coach, Sports scientist
- Relevant to
- Professional club, Collegiate athletics, Academy & youth, Women's league
- Systems in play
- GPS and wearable tracking platforms, Wellness survey tools, Medical and injury records, Spreadsheets
- Product framing
- Monitor
Questions we get asked
What do we need to have in place before this is worth building?
Three things you likely already produce daily: an exportable load figure per athlete from your GPS platform, a wellness score from whatever survey tool you use, and a way for medical staff to flag a hold — even a shared note is enough to start. Version one reads these from a daily upload rather than live feeds, so nothing needs to change in how those systems are used before a first version can be tested.
Does this replace our GPS platform or wellness survey tool?
No. Those stay exactly as they are and remain the systems of record for load and wellness data. This sits above them as a single view of the flags that matter, built from what those systems already export. If you decommissioned it tomorrow, none of your underlying performance data would be affected — you would simply be back to checking three screens.
Our coaches already glance at a spreadsheet each morning. Why would this be different?
A spreadsheet someone updates by hand only works while that person is available and the squad is small. This adds two things a spreadsheet does not: a defined threshold that triggers an alert automatically, and a named person who is on the hook if it is missed. If your current spreadsheet already does that reliably, you do not need this.
Who is responsible for it once it exists, and what happens if an alert turns out to be wrong?
The Head of Performance typically owns the thresholds and reviews them as the squad's baseline shifts over a season. A wrong or noisy alert is a configuration problem, not a data problem — it usually means a threshold was set too tight for that athlete or group, and it should be adjusted rather than tolerated, or staff will start ignoring the board entirely.
Is this your workflow?
Tell us one sports workflow that still runs on paper, spreadsheets, WhatsApp or an outdated system. We will map it and show you what a simpler product looks like.
Tell us about itMore in Athlete performance & sports science
- Daily wellness survey completion monitorA single board showing which athletes have not yet submitted today's readiness survey, with one alert to a named coach before the missing responses become a training-load blind spot.
- Force plate baseline deviation monitorA live board that compares each new force plate result to an athlete's own rolling baseline and alerts a named performance staff member the moment asymmetry or output drifts, instead of waiting for a week-old spreadsheet review.
- GPS and wearable unit issuance and condition logA mobile checklist that replaces the whiteboard and group chat used to track which athlete has which GPS or wearable unit, capturing condition, charge and return sign-off for every session.