What Development Means Here
Match reports and practice reports tell you what happened in a single session. Development is the layer above that - what is happening over weeks and months, and what it means for every person involved.
FIS develops four things. Not just one.
Players
Individual growth, tracked over time
Weekly and monthly reports show each player their own arc - kick velocity, decision speed, foot balance, physical load. Self-comparison only. No rankings.
Teams
What the group is telling us
Team-level patterns visible across a full squad: skills that are growing, skills that are stalling, practice-to-match transfer gaps. The coaching staff sees what they can't see while running the session.
Coaches
Which approaches are actually working
As data accumulates, FIS correlates specific drill designs with metric improvement rates. Coaches learn not just what players are doing - but which of their own training decisions are producing results.
Programs
Consistent data across all sites and teams
A program director looking across all sites and skill bands - Purple through White - gets a cross-team view that has never existed before. Placement decisions informed by a full season of data. Quiet standouts noticed. Sites compared fairly.
All of this data already exists in FIS as a natural output of per-session event logs. The development layer reprocesses accumulated session data, computes derived metrics, and produces reports on a weekly, monthly, and seasonal cadence.
Developing Players
Every player gets a development record that builds automatically from session data. Reports arrive without anyone asking for them - weekly on Monday morning, monthly on the first of the month, and once per season as a full arc summary. All metrics compare a player only to their own prior performance. No rankings, no comparisons to teammates.
A player report says "your kick velocity this week was 14.2 m/s vs. your recent average of 13.8 m/s" - not "you ranked 4th in the group." Development is personal. Comparisons are the coach's job.
Weekly Report
Delivered Monday morning covering the prior week. Sessions attended, distance covered, sprint count, touch count, kick events with foot preference, and three key metrics vs. the player's own 4-week rolling average - each with a trending up / stable / down indicator. One positive observation. One focus area for next week.
Monthly Report
A fuller picture: technique progression curves over time, consistency trend (is variance decreasing as skills consolidate?), drill-by-drill improvement breakdown, and a practice-to-match transfer comparison. Metrics consistent across both contexts suggest solid skill transfer; metrics strong in practice but lower in matches suggest the skill is developing but not yet automatic under full-game pressure.
The monthly report also includes a range band showing where the player sits relative to the team median on key metrics - not a rank, just context for the coach to understand relative development needs across the squad.
Seasonal Summary
Once per season, a full-arc report covering where each player started, where they ended up, and what the data suggests for next season. Full-season progression curves for all key metrics. Peak performance moments. Practice-to-match transfer delta. A positional profile weighted by role - what matters for a midfielder is different from what matters for a forward. It arrives as a PDF, covers every tracked metric from the first session to the last, and is written to be understood by a player and their family - not just their coach. The report a family keeps.
Developing Teams and Coaches
The team development report is a separate monthly email digest delivered to the coaching staff only - not to parents or the player portal. Its purpose is twofold: to surface squad-wide patterns that are hard to see when you're on the pitch running the session, and to help coaches understand which of their own training decisions are actually producing results.
Everything in this report is framed as an observation and an opportunity. Coaching staff are professionals - they decide what to do with the information. But the data gives them something they've never had: a mirror on their own practice design, not just their players' performance.
Strengths to reinforce
What's going well
Skill areas where the group is improving consistently. Named specifically: "kick velocity across the squad has improved an average of 8% over the last 6 weeks, with 9 of 12 players showing positive trends." Things worth protecting in the schedule.
Development opportunities
Where adjustment could help
Skill areas that haven't moved despite repeated practice. Not because players aren't working - there may be an opportunity to adjust drill design, volume, cues, or focus. Example: "Weak foot usage in 1v1 drills has not changed across the squad over 8 weeks despite the drill design leaving both feet available."
Transfer gaps
Practice vs. match patterns
Skills present in practice data but not showing up in match data - skills the players have but haven't automatized under full-game conditions. Helps target which drills need more game-speed or game-pressure simulation.
Drill effectiveness
Which approaches are working
As data accumulates, FIS correlates drill types with metric improvement rates. Sessions with more 1v1 reps show faster decision-speed gains. Kick velocity improving in shooting drills but flat in crossing drills. A coach who sees this has a basis for adjusting session design that didn't exist before.
Team shape trends
How the squad's shape is developing
Compactness, pressing intensity, and passing patterns tracked across weeks, not just one game. A team getting tighter defensively or pressing faster over a month is a development signal at the squad level, the same way kick velocity is at the individual level.
The report only surfaces drill effectiveness observations once enough sessions have accumulated to make them reliable. Every observation is labelled with how many sessions it draws on — so a coach knows whether they’re looking at a solid pattern or an early signal worth watching.
Game patterns and practice design
As data accumulates across games, the sequence log surfaces which named plays the team is running, how often each one appears, and what it produces. The coaching insights digest includes a pattern summary drawn from this data. It is not a prescription - it is a mirror. What the coach does with it is their call.
What the team is running
Which play sequences appear most frequently, which ones are producing shots and goals, and which ones are ending in turnovers or going nowhere. Over a season the picture sharpens: a play that works once is luck; a play that works in six of eight games is a weapon worth protecting. A play that runs frequently but never produces is a different kind of signal.
What opponents are running
The sequence log records patterns from both teams in every game FIS is deployed at. After playing the same club twice, the coaching report can show which plays that club favoured, how often they ran them, and what outcomes they produced against your team. Patterns observed against one opponent stay in the library - so when a different team runs the same play, it already has a name.
Plays travel fast
Teams in the same competitive environment play each other, share training staff, and watch each other's games. A sequence that worked against one team spreads. FIS does not track opponents you have not played - but when you have played a team, you know what they ran. By the time a play appears for the third time across different opponents, it is no longer a surprise. It has a name in the library and a clip in the archive.
Specificity is the value. Not "we struggled with crosses" but "wide carry and cross appeared six times in the last two games against us, resulting in four shots on target." That is the kind of observation that can anchor a conversation about what to work on - without the system telling anyone what to do about it.
Developing the Program
A program director overseeing one or more age groups across all three sites - Academy, Oldham, Shelby - is responsible for some of the most consequential decisions in a youth player's development arc: promotion and relegation between skill bands (Purple, Black, Grey, White). Those decisions benefit from a consistent longitudinal record. FIS builds one automatically: session data for every player, collected the same way regardless of site or coach, accumulating across a full season.
When FIS is deployed across all sites, the director sees a cross-team, cross-site development view built from consistent data across every session. After one season the picture starts to form. After two it becomes a genuine foundation for the complex decisions program leadership already makes.
What the director can see
- All 12 teams in an age group (3 sites × 4 skill bands) on a single dashboard
- Individual player development trajectories across every team - sorted by any metric
- Players whose trend is running ahead of their current band placement
- Players whose metrics are declining or stalled - early flags before problems surface on the pitch
- Site-level comparisons: is Academy Purple developing differently than Shelby Purple?
- Injury watch flags across all 12 teams - bilateral asymmetry outliers by site, band, and position
What becomes possible
- Placement decisions informed by longitudinal data alongside the observations coaches already bring
- Identifying the quiet standout at Shelby White whose trajectory is ahead of players currently in Black
- Distinguishing a player struggling because of skill from one struggling because of load or bilateral imbalance
- Evaluating whether coaching approaches at different sites produce comparable development outcomes
- Building an age-group benchmark: what does healthy development look like for a U11 midfielder at each skill band?
| Band | Sites | Director view |
|---|---|---|
| Purple - most skilled | Academy, Oldham, Shelby | Are top-band players across all three sites developing at comparable rates? Is one site's Purple producing outliers? |
| Black | Academy, Oldham, Shelby | Which Black players are trending toward Purple? Which Purple players' metrics suggest they need a different environment? |
| Grey | Academy, Oldham, Shelby | Grey-to-Black transitions: who is developing fastest? Is the gap between Grey and Black consistent across sites? |
| White - developing | Academy, Oldham, Shelby | Early identification: which White players are on trajectories that warrant attention and investment now? |
Cross-Band Rostering Report
Generated on request before tryouts, mid-season reviews, or end-of-season placement decisions. Aggregates longitudinal data across all teams in an age group and surfaces four things: promotion candidates (players trending above their band, ranked by trajectory strength not snapshot performance), players needing attention (stalled or declining, skill stalls separated from load concerns), site comparisons (are the bands actually equivalent across sites?), and quiet standouts (players in lower bands whose development rate is among the highest in the age group).
️ One season builds the picture. Two seasons builds the tool. After one season, the director has a baseline for every player and a sense of band-level norms. After two, the system distinguishes typical development variance from meaningful trends - and cross-season comparisons reveal which players transferred growth from one year to the next.
️ FIS surfaces data. It does not make roster decisions. The director sees trajectories, flags, and comparisons - they decide what to do with them. The goal is not to automate judgment; it is to make sure the people making those decisions have as much quality information as possible to work with.
Expansion Path
The derived metrics schema and S3 structure support program-level aggregation without changes to the per-team pipeline. Expansion is a query change, not an architecture change.
What becomes possible with full program data
- Age-group benchmarks across all three sites: what does healthy U11 development look like in this program at each band?
- Cross-age development pathways: following a player's arc from U9 through U13 and beyond
- Program-level skill gap identification: are all U9 teams struggling with weak foot usage, or is it specific to one site?
- Cross-program benchmarking: as FIS is adopted by other clubs, the derived metrics format is portable
Data requirements before enabling
- Minimum: one full season of data from at least 3 teams in the same age group
- Consistent session tagging across sites - shared drill vocabulary
- Player identity persistence across seasons (same player_id carries forward year to year)
- Privacy: program-level reports give each coach visibility into their own team only — cross-site aggregation is available to the program director, not to individual coaches
Report Delivery and Cadence
| Report | Cadence | Trigger | Recipients | Format |
|---|---|---|---|---|
| Weekly player development | Weekly | Auto - Monday morning covering prior week | Coach + parent portal | PDF via email + portal |
| Monthly player development | Monthly | Auto - 1st of month covering prior month | Coach + parent portal | PDF via email + portal |
| Seasonal summary | Once per season | Manual - coach or director triggers end-of-season run | Coach + parent portal | PDF via email + portal |
| Team development insights | Monthly | Auto - 1st of month, same run as player reports | Coaching staff only | PDF via email |
| Cross-band rostering report | On request | Manual - director triggers before placement decisions | Program director only | PDF via email + director portal |
️ Minimum session requirement: Weekly reports require at least 2 sessions in the reporting week. Monthly reports require at least 4 sessions. If a player misses significant time, the report notes the gap rather than computing trends from insufficient data. The cross-band rostering report requires at least 6 weeks of data per player to include them in trajectory analysis.
Data Model
Longitudinal reporting reads from a flat derived metrics layer computed once per session at Pass 2 completion — not from raw event logs on every run. Per-session derived metrics are stored in S3 keyed by program, site, team, player, and session.
Compute Model
Weekly and monthly reports are lightweight Lambda jobs reading from the derived metrics layer. The heavy computation happens once at Pass 2. Total longitudinal reporting cost for a full season runs under $20 per team.
Open Items
- Implement per-session derived metrics write step at end of Pass 2 Lambda job - include program_id, site_id, team_id fields from day one
- Design and build weekly and monthly PDF report templates - player version and team insights version
- Build report generation Lambda functions triggered on Monday AM (weekly) and 1st of month (monthly)
- Build cross-band rostering report: aggregation query across all site/team paths in an age group, PDF output, director portal delivery
- Add manual seasonal summary trigger and cross-band report trigger to director portal or CLI
- Define position weighting coefficients for midfielder, forward, defender at U9/U11 age groups
- Implement practice-to-match transfer delta calculation
- Define minimum data thresholds per report type and implement graceful handling when thresholds aren't met
- Parent portal: design the report delivery and storage UX - PDF accessible per player, organized by date and report type
- Director portal: design cross-band view - 12-team age group dashboard, promotion candidate list, injury watch flags across sites
- Validate injury watch flag thresholds against this specific player population before surfacing them in the director view
- Define player identity persistence across seasons and team transfers - same player_id must survive roster moves between sites and bands
- Program-level S3 path design: confirm multi-site path structure is adopted consistently across all three sites from first deployment