The Empty File, No Timecode: What Evidence Indian Football Actually Writes Its Verdicts On

1. The file that came back empty

On Monday afternoon a case file landed on my desk. It carried nine printed headings — tactical analysis, club finance, results cycle, league landscape, rules compliance, management, risk, media narrative, industry transmission. Under all nine was a single line: insufficient information. N/A where the title should have been, N/A where the source should have been, zero entries in the list of information points. No club, no player, no competition, no date, no number, no quote.

A file like that leaves two roads open. The first is to fill the blanks — assume a club, pick a formation, invent a storyline and call it analysis. The second is to write that the file is empty. The first road is fast. The second is honest. I pulled every clip before I said a single word, and this time there was nothing to pull. That is the most useful finding of the week.

2. The scaffold of evidence, and the day it was first built

A dispute in football is not settled by feeling. An incident log holds four things — the clip, the timecode, the law citation, the threshold. The fifth thing is the verdict, and the verdict always comes last, never first.

In 2026, while at a pre-university college in Bangalore, I built that scaffold by hand for the first time. It was the Karnataka State Football Association U-18 final, Bengaluru FC Academy against Kickstart FC. In the 78th minute a penalty appeal went up and the pitch broke into argument. I was the video logger, working off one borrowed camera. I cut 42 clips from that single appeal, tagged 14 handball and offside incidents, and sent a one-page timeline to the district referee coordinator. He used it in a weekly referees' review. Later I wrote a 900-word handball-law explainer for the college magazine and refused to include a single clip without a timecode.

What I understood that year still underpins everything I write: the shortage in Indian football is not a shortage of controversy, it is a shortage of documentation. An incident with no timecode lives forever in argument and never once enters the record.

I started that log at U-18 level deliberately. Half the boys in that final had a body still under construction and a scoresheet that declared them ready. Early-maturing players get pushed into senior rhythms before their frames have finished, and nobody keeps a column for biological age. That is a record failure too — what we do not measure, we cannot correct.

3. Sixty-four matches, 1,247 clips, three labels

In 2026, during the Russia World Cup, I turned that one-page timeline into a database. Sixty-four matches, 1,247 clips, 38 reusable review templates. Among them was the moment that bent the tournament — the 38th-minute penalty to Antoine Griezmann in France's 4-2 final win over Croatia, awarded after a video review of Ivan Perisic's handball.

I wrote that single incident five different ways and kept the same sequence every time: incident, camera angle, law, threshold, outcome. Later I compressed the sequence into a one-page "clear and obvious error" flowchart. It drew 12,000 reads and a message from a Bangalore sports-data vendor looking for part-time loggers.

That is where my writing changed. I stopped filing video reviews as drama and started filing them as decision trees. I also made a demand that remains unmet: every review should carry one of three labels — checked, overturned, or no clear error. Until those labels are public, a spectator cannot compare two decisions, and where there is no comparison there is no trust, only opinion.

4. The audio column from the bio-bubble

In 2026-21 that vendor hired me remotely to log the ISL's 115-match season inside the Goa bio-bubble. The stadiums were empty, which meant no crowd noise — whatever happened on the pitch arrived straight down the microphone. I added a new column to my template: audio cue. Whistles, shouts, the conversation between referee and player. Across that season I tagged 1,046 set-piece delays and 78 on-field consultations.

After Mumbai City's 2-1 final win over ATK Mohun Bagan, I built a 12-page crisis-review template for broadcasters covering disputed calls where crowd context does not exist. One producer wanted speculation folded in. I refused and kept the template evidence-only. We argued. The template did not change.

It had four sections: the incident, the available audio, the missing angles, the referee's likely communication. I logged it from a bio-bubble, and the pattern still held — under deadline, file the short "what we know" box first, then the full analysis.

5. A null return is also a result

Back to the file that came back empty on Monday. The easy reaction is to treat it as a failure and bin it. For a logger, zero is data too. Nine dimensions each returning "insufficient information" tells us something specific: the failure sits in the collection layer, not the analysis layer.

I translated that file's four risk flags into football's language, and all four are alive in Indian football reporting:

One, fabrication risk. When the pressure is to deliver something, a club, a formation and a storyline assemble themselves. This is the most common and least caught offence in Indian football coverage. Writing "the team switched to a 4-2-3-1 at half-time" is easy; proving the switch happened in the 46th minute rather than the 58th is not.

Two, downstream contamination. Any report built on an empty scaffold carries its invented premise forward. One number printed without a source gets quoted for six months by everyone. Indian football has no shortage of airborne statistics — attendance, academy spend, viewership.

Three, source-tier blindness. When the source itself is unrecorded, the tool for grading credibility disappears. This is the hardest block for me. Printing a claim without its source is the same act as printing a clip without its timecode.

Four, circular extraction. "Identify the entities from the information points above" — when there are no information points above, the instruction stands on its own foot. Indian football's administrative reporting reproduces this shape constantly: a committee is formed, its report is referred back to the committee, and the public receives a sentence nobody verified.

6. "The standard is poor" is an unfalsifiable sentence

Refereeing debate in India stalls at the same point every time — the standard is poor, bring in foreign referees. My objection is not that this is wrong. My objection is that it cannot be tested.

Testing requires a graded clip log from a single matchweek: handball threshold, DOGSO, positioning, advantage played. It requires a count of appeals, of correct decisions, of errors, and the category each error falls into. It requires naming the law applied — Law 12 handball, Law 12 denial of an obvious goal-scoring opportunity, Law 5 advantage.

My experience is that most ISL and I-League flashpoints are law-application and positioning failures, not bias, and both of those are fixable provided somebody counts them. Until the AIFF referees committee publishes a graded log instead of a press release, every argument stays a personal opinion.

One comparison helps. The barefoot 2026 London Olympics, the 2026 and 2026 Asian Games golds, the 131,781 at Salt Lake in 2026 — these are not emotional memories but administrative evidence about what Indian football chose to fund. A refereeing error is the same kind of fact. It belongs in a ledger, not in a weekly mood.

7. The pyramid's arithmetic is the same blank

The double standard is clearer at institutional level. Punjab FC in 2026-24 and Mohammedan Sporting in 2026-25 were sold as fairy tales. I treat them as data points. One promotion slot a season against a fourteen-club top tier. An I-League whose fixture list and broadcast coverage can be counted. An Indian Women's League that has existed since 2026 without becoming professional.

The slogan and the record are two different documents, and only one of them is falsifiable. A pyramid is a throughput number, and the number is one. Until it moves, every promotion story is a rounding error.

8. The contrarian angle: the real dispute is not the referee's mistake

Here is the uncomfortable part. In most of the viral refereeing controversies of recent years, the problem was not the decision that was given. The problem was that the decision had no immutable record.

I don't argue with the crowd. I argue with the timecode. And the timecode usually shows that the clip which travelled was the weakest frame of the incident. Here is the frame that decided it, not the frame that trended. The broadcast cut away. That is usually where the story was — in the cut, in the second camera, in the three seconds after the whistle that never aired.

There is a trap here I have fallen into myself: treating referee error as the explanation for everything. Officials are my beat, so their mistakes are the most legible thing on the page. Not every defeat is a refereeing defeat. Decision error has to be separated from performance variance, and what happened on the pitch has to be named — fitness, selection, or simply a bad day.

And the largest point: an empty file is more honest than a filled one. A report that says "insufficient information" nine times is at least not lying. Indian sports journalism needs the habit of publishing null results, because a null result is still a result.

9. Takeaway

The way forward is procedural, not technical. The AIFF referees committee should publish a graded log every matchweek — how many appeals, which law, which threshold, which label. Clubs should attach an audio-cue column to their broadcast feeds. And those of us who write should normalise saying, when the evidence is absent, that the evidence is absent.

The question is not how many controversies the next season will produce. It is how many of them we will hold a timecode for.