The Empty File: Why Indian Club Football Keeps Hiring Coaches Without Analysts

The file opened and there was nothing inside. Last June, at the first pre-season meeting of an ISL club, the new head coach was handed a video folder containing ninety-minute files of twenty matches from the previous season — and not a single tag. No timestamps, no line-break markers, no zone codes. The folder was called "2026-25 REVIEW". Volume: 34.2 GB. Information: zero.

In April 2026 I had sent a different kind of file — ninety minutes of a Delhi Dynamos under-18 match, cut into forty-one clips, each tagged with the line-breaking pass that produced a goal. That file had five goals, five line-breaks and an argument. That is the difference: 34 gigabytes versus a forty-one-clip file. Indian club football's analytics crisis is not about cameras or software. It is about the step that converts footage into evidence, and that step is often simply not taken here.

An analyst's job splits three ways: opponent preparation, own-team load, and a match-by-match record of evidence. All three share one condition — a person who spends hours each week watching footage and naming it. In India that person is often absent, and when present, his contract is shorter than the coach's. The 2026-21 ISL season was played behind closed doors across three Goa venues — Fatorda, Tilak Maidan and the GMC Athletic Stadium in Bambolim. Sitting in those three empty stands, I logged the build-up of fourteen matches, because with no crowd noise Sergio Lobera's touchline instructions recorded directly. Ahmed Jahouh's instructions could be heard verbatim. Mumbai City finished that season with the Shield, forty points from twenty games. It was no coincidence that the club with the cleanest touchline communication also had the cleanest pivot system.

In this transfer window most discussion centres on contracts, release clauses and agent claims. The real question sits in the room where the new coach is asked how he will win the first four matches. He has a two-week pre-season, three fit centre-backs, a calendar running from the Durand Cup into the ISL, and a video folder with nothing tagged in it.

The analytics supply chain at Indian clubs breaks at four points, and all four breaks are organisational decisions, not technical ones.

The first break is at intake — who cuts the tape. My forty-one-clip file was also cut with a thesis; I made it because I believed the error lay in defensive transition. Had someone else cut it, it might have contained set-pieces and no transitions. Indian clubs never write down this selection rule. Nobody says why eleven of forty clips were chosen and twenty-nine dropped. When there is no rule, the cutter becomes a carrier of his own bias, and the new coach inherits that bias.

The second break is capacity. An ISL season — twenty league games plus the Durand Cup, Super Cup and possibly AFC competition — runs past thirty matches. Opponent preparation means watching at least three recent matches of every incoming rival, roughly two hundred and seventy minutes of footage a week just to watch. Then tagging, cutting and presenting to the coaching staff. That is one person's full-time job. In India it is often dumped on the assistant coach, who already has training sessions, travel and player management. The result is that tagging shrinks to goals and big chances — the very things already on the scoresheet. Footage that repeats the scoresheet is not evidence.

The third break is translation. The analyst's language and the coach's language are not the same. I built my eighteen-zone grid during the 2026 World Cup, in a Delhi studio where the shift began at 5.30 p.m. and ran till dawn. In that tournament I logged all twenty-nine penalties — the first VAR World Cup — and watched the France-Australia award three times to understand the decision protocol. On 6 July in Kazan I diagrammed Roberto Martínez's in-game switch to a 3-4-2-1 against Brazil and called Nacer Chadli's overload on the left before it produced the winner. All of that I did on the grid. But a coach does not ask for the grid. He asks: who goes up for the first set-piece? If the analyst cannot connect that question to a timestamp and a repetition count, his work becomes a report that stays in a drawer.

The fourth break is the costliest — knowledge accumulation. When Indian clubs change coaches, the entire analytics archive leaves with him. The next coach starts from zero again. The club has no continuous player-load data across three seasons, so it does not know how many minutes a player logged across the four months from the Durand Cup into the ISL, or in which week his hamstring had been loaded before. At a European club this data is institutional property. Here it remains a person's private file, and the person is on a short contract.

The calendar enlarges this fourth break every year. The Durand Cup begins in August, the ISL follows immediately, and in between sit away days involving four-hour flights. If four away weeks land back-to-back in a twenty-match league, squad depth stops being a theoretical debate and becomes arithmetic. The coach must know whom to rest in the third away game. That decision comes from minutes data, not experience. Where there is no load data, rotation happens on guesswork, and guesswork always falls on the player who logged the most minutes last season. This is why the national team has long resided in the 100-130 ranking band and why the striker's slot looks empty after Sunil Chhetri — this is an output of the supply chain, not of will.

I watched fifty-two matches across six host cities at the 2026 under-17 World Cup and built a three-hundred-clip library. That experience settled one point: footage availability was never the problem. Every ISL match in India is recorded in high definition. The problem is that nobody is employed to read that tape.

Now the angle that cuts against this whole argument. Hiring a data analyst is not a solution in itself, and this is where Indian clubs deceive themselves most easily. Appointing an analyst gives a club the illusion that it has a process. There will be files, presentations, meetings — and the decisions will remain the old ones, because recruitment authority still sits with the man who picks players off a DVD sent by an agent. In Indian football the largest input into player selection is an agent's phone call, and that variable appears on no spreadsheet. I say it plainly: this is an unmeasured variable, and if in any single season it proves decisive, my whole model is wrong.

The second angle: the habit of measurement is itself a trap. Once you start counting everything, what cannot be counted quietly drops out of the model — a dressing-room fracture, agent politics, a player's family stress. In twelve years of reporting I have seen clubs with the cleanest spreadsheets sometimes unravel fastest. The analyst's job is not to prosecute the coach. In my own file, when a coach was removed, the question was not whether he made the wrong substitution in the seventieth minute — it was how many support staff the club gave him, how long the pre-season was, and who controlled recruitment. The employer must be audited on the same evidence standard as the coach. Indian clubs sack on results and never on process, which is why the same failure gets re-signed by the next club in the next window.

This file is not closed. Three things can be checked in the next transfer window, and all three are public. First, whether the club appointed an analyst before or after announcing the coach. Second, how many days of pre-season were announced. Third, whether the club's website lists a single technical staff name whose sole job is reading footage. The day all three answer yes, the empty-file day will not return.