Football academy management software: what a junior club needs beyond fixtures

Youth football in England runs on four different formats: 5v5 at Under-7 and Under-8, 7v7 at Under-9 and Under-10, 9v9 at Under-11 and Under-12, and 11v11 from Under-13 up, as set out by England Football. A club with a team in every age group is therefore running four different games, four squad sizes, and four sets of parent expectations on the same Saturday morning, with volunteers. Fixtures software handles none of that.

What does a junior football academy actually manage in a week?

On paper, a club is a list of teams and a fixture list. In practice, a Tuesday looks like this.

Take Thornleigh Juniors FC in Warrington as a working example: 11 teams from Under-7 to Under-16, 168 registered players, 22 volunteer coaches, and a club secretary we will call Dawn Whittaker who works four days a week in a job that is not football. Across a 34-week season Dawn's teams train on two pitches on Tuesday and Thursday evenings and play on Saturday mornings and Sunday afternoons.

In a normal week the club has to know who trained, who is injured, who is away at a cousin's wedding on Sunday, which Under-11 has not been picked for three weeks, which coaches still need their safeguarding renewal, and which 168 families have read the note about the change of pitch.

None of that is a fixture list.

And crucially, only two of those questions have an answer anywhere. The fixtures app knows the kick-off time. The rest lives in 11 separate WhatsApp groups, a coach's notes app, and Dawn's memory.

Why is a fixtures app the wrong place to start?

Most committees shopping for "football academy management software" start with fixtures, registration, and subs, because that is the part of a club that looks like admin. We would argue that is the wrong end, for a specific reason rather than an ideological one.

Registration and subs are irritating but stable. A club that registers players in July and collects monthly subs by standing order has a process that survives being ugly. The league imposes deadlines and the club meets them, because the consequence of missing one is immediate and loud.

What is not stable is the Under-13 who trains every Thursday, plays eight minutes a week, says nothing, and does not re-register in July. Nothing in the club's software will flag that child, because from the fixtures app's point of view nothing went wrong: the game was played, the result was submitted, the subs were paid.

This matters more in football than in most sports because the sport is structurally over-supplied with substitutes. England Football's youth rules keep Under-7 to Under-11 football out of league tables precisely so that the development phase is not run on results, but the moment a coach is short of minutes to distribute, the child who is 20 months younger than the top of the age band gets fewer of them. It compounds week on week, invisibly.

Fix the register, the availability poll, and the minutes count first. Keep whatever the league already forces you to use. Clubs that do it in that order tend not to regret it.

How do you track playing time without publishing a table of minutes?

This is the decision that separates clubs that keep their teenagers from clubs that rebuild every summer.

Record minutes per player per fixture. That is the whole mechanism, and it takes a coach about 40 seconds after a game. Then look at the cumulative share of available minutes across the season, not at any individual Saturday.

The reason to use the season total is that every coach can defend one game. "He came on with fifteen to go because we were chasing it" is a true and reasonable sentence. What no coach can defend is a season they never added up, and the honest version of the problem is that most coaches genuinely do not know. A running total turns an argument about fairness into a number, in November, while there is still a season left to do something about it.

What you must not do is publish the table. A ranked list of minutes played, visible to the squad, is a public statement about who the coach rates, refreshed every week. The players at the bottom of it are the players closest to leaving, exactly as with any comparative list posted into a group.

So: the coaching staff see the whole squad's minutes. Each family sees their own child's. Nobody sees anybody else's.

Coaches we speak to describe the same conversation shift afterwards: "I stopped being asked why he didn't start, and started being asked what he needs to work on to start."

How should a club collect matchday availability?

One poll per fixture, posted by Monday evening, with a Thursday cut-off, in the squad's own group.

The reason a poll beats a chat thread is not tidiness. It is that a poll tells you who has not answered. Twenty replies scattered through a WhatsApp thread require a coach to reconstruct a list by scrolling on Friday night, which is why so many grassroots squads are selected on the touchline at 09:20 from whoever turned up.

Coaches who switch to a poll with a deadline stop chasing a whole squad and start chasing the four families who have not tapped anything. The same pattern works for anything that needs counting: tournament entries, kit sizes, the minibus, the end-of-season presentation night.

Selection itself is a different message. The meet time, pitch, and kit go to everyone. Who is starting goes to each family privately, or is simply not published at all before the game. This is the same rule that keeps a register useful rather than punitive: the group channel carries logistics, and anything comparative about a named child goes one to one.

What does a paperless football academy run on week to week?

Clubs that settle into a stable setup after a season or two converge on roughly the same shape.

One private group per squad, not per club and not per player. A single club-wide group means an Under-7 parent reads Under-16 cup logistics every week and stops reading anything at all. Per squad matches how the coaching actually happens, and it matches how the parents already think.

Training attendance marked in a few taps at the start of each session, with a standing club rule that a second consecutive absence triggers a private message to that family the same week. That single rule catches more drift than any dashboard.

Minutes recorded after each fixture. One development note per player, naming something specific and physical: "first touch out of the feet under pressure", "scanning before receiving", "defends the back post at set pieces". Reviewed at the halfway point of the season, visible only to that family and the coaching staff. Availability polls with a cut-off for every fixture and every extra session. Announcements for kit, pitch changes, and subs kept in their own lane so they do not scroll away under chat.

The part committees underestimate is the view across squads. Eleven squad groups in one dashboard means Dawn can sit down on a Sunday evening and see which registers were not marked, which squads have four unanswered availability polls, and which players have a development note more than three months old. Clubs working towards The FA's accreditation standards, with their requirements around qualified coaches, DBS checks, and a named welfare officer, will already be keeping records; a per-squad digital register is simply a cleaner place to keep them than a folder of paper and a phone gallery.

The software organises the club. The safeguarding duty, the coaching, and the Saturday morning stay exactly where they were.

Related reading: how a Halifax junior football academy used playing-time data to keep 91% of its players through the summer window, and how a Birmingham cricket academy replaced the coach's notebook with one cohort per squad.