Squad rotation load risk simulator for fixture congestion
Problem
When three fixtures fall inside eight or nine days, the rotation plan gets worked out in a meeting, a spreadsheet of matches on one screen, last week's GPS peak numbers pulled up on someone's laptop, and a series of judgement calls about who played heavy minutes last time out. Nobody in the room can see the cumulative effect of a proposed rotation across the whole squad at once, only individual numbers recalled from memory or a quick scroll through the athlete management system. A plan gets agreed, the fixtures are played, and only afterwards, when an athlete goes down or wellness scores fall off a cliff, does anyone go back and calculate what the accumulated load actually was.
Product idea
The tool takes a fixture list and a proposed rotation pattern, who starts, who is rested, who plays a reduced number of minutes, and calculates the projected cumulative load per athlete against their own rolling baseline and any current wellness or medical flags. Staff can build two or three rotation scenarios side by side and see which athletes would cross an internal load threshold under each one before a lineup is confirmed. It does not select a team or recommend a rotation, it shows the consequence of a plan already under discussion so the conversation in the room has numbers behind it instead of recollection. Nothing in it decides who plays; it only says what the projected load would be if they did.
Who it is for
Head coaches and strength and conditioning coaches working out rotation plans ahead of a congested run of fixtures, sponsored by the Head of Performance who owns the internal load thresholds the tool checks against.
Possible first version
A web tool where staff enter the upcoming fixture list and, for each match, tick which athletes are proposed to start, rest or play reduced minutes. Load history comes from a CSV export of the existing GPS platform rather than a live feed. The tool calculates projected cumulative load per athlete per scenario and flags anyone crossing a configurable threshold, with two scenarios comparable side by side. Out of scope for version one: any live integration with the GPS or athlete management system, automatic rotation recommendations, and wellness or medical data beyond a manually entered hold flag.
- Build classification
- Workflow application
- Rough effort
- 4-6 week first release
- Roles involved
- Head coach, Head of Performance, Strength & conditioning coach, Performance analyst
- Relevant to
- Professional club, Collegiate athletics, Women's league
- Systems in play
- GPS and wearable tracking platforms, Athlete management systems, Spreadsheets
- Product framing
- Test or simulate
Questions we get asked
We already work this out in a meeting with fixtures on a spreadsheet. What does this actually change?
The meeting does not go away, and it should not. What changes is what is on the table when it happens. Today the numbers in the room are whatever someone remembers or can find quickly, one athlete at a time. This tool calculates the cumulative projected load for every athlete under a proposed rotation before the meeting starts, so the discussion is about which scenario to choose rather than about reconstructing last week's figures from memory. If your group already argues from solid numbers, this adds little. If it argues from recollection, it changes what the argument is about.
What data do we need before this is any use?
A fixture list for the period you are planning, your squad roster, and a load history export from your existing GPS platform, typically the last several weeks per athlete so a rolling baseline can be calculated. Wellness and medical status are limited in version one to a manual hold flag rather than a live feed. If that export is not something your staff already pull for another purpose, the tool will feel like extra work rather than less, and that is worth checking before committing to a build.
Who ends up maintaining this once it exists?
Someone, usually a performance analyst or the same person who currently builds the fixture spreadsheet, has to keep the load export current and re-run it before each planning meeting. The load thresholds also need periodic review by the Head of Performance as the squad's baselines shift over a season. Neither task is large, but if nobody is assigned to it, the export goes stale and the scenarios stop matching reality within a few weeks, which is worse than not having the tool at all.
Does it tell us who should actually play?
No, and that is deliberate. It shows the projected load consequence of a rotation plan you propose, not a recommended team. Selection stays a coaching decision made on form, tactics and availability, none of which this tool has any view of. Turning a load model into an automatic lineup recommendation would hand a decision that has to stay with the coaching staff to a spreadsheet, and it would be wrong the first time a tactical factor outside load mattered more.
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
- Cross-system athlete availability status boardA live status board that pulls load, wellness and medical hold flags for each athlete into one view and alerts a named person when a threshold is crossed before the next session.
- 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.