The folder is named "verify_23m". It holds four files — a match sheet with a date and two team names; a scoresheet with nothing but the score; a text file reading "entry angle — N/A"; and a video folder containing zero clips. I looked at it for eleven minutes and closed it.

Before this, in October 2026, after the Asia Cup final in Dhaka, my hard drive carried 41 clips — every Malaysian circle entry, tagged with build-up shape. India won that match 2-1, and my first byline was built out of those 41, at thirty-two, in the video room at SAI Bengaluru where I was the junior video analyst on the national camp support staff.

Eight years later I have a folder with nothing to count. This piece is about that folder — and about the habit it taught me, which is that an empty file is not something to fill. It is something to record.

Context: nine headings, and N/A under every one

Last week an "analysis" reached me. It had nine sections — tactical and technical analysis, data and form, competition system and qualification path, global landscape, rules and governance, team management and talent pipeline, risk profile, public narrative, industry transmission. Every section had a table. Every table had rows. Every row said the same thing: "N/A – insufficient information."

I have read a great deal of bad hockey work. This document did not strike me as bad. It struck me as incomplete, and those are different failures.

The process behind it is simple to describe. Stage one is extraction — pulling title, source, date, information points and entities out of the source material. Stage two is analysis — laying a nine-dimension framework over those information points. When stage one returns empty, whatever stage two produces is not analysis. It is decoration.

The document left me exactly one usable line: "the only defensible conclusion is a process/integrity finding — the upstream pipeline failed." I read that line eleven times, because it was the only sentence I could have put in front of an editor and defended.

Core: three roads to an empty file, and a fourth

Three technical causes usually sit behind an empty file, and I have paid for all three in my own work.

First, the door to the content was shut — a paywall, a subscription, a page that handed a scraper nothing. Second, JavaScript rendering: the page opens, the headline appears, the body is empty because the text is assembled later in the browser. Third, truncation: half the file arrived and the system treated it as whole.

All three share one property. The system does not know it has lost anything. That is what makes an empty file dangerous. It does not complain. It quietly writes "N/A", and N/A looks honest, because it admits ignorance. The problem is that it does not know for the right reason.

The fourth road is different, and it is the one that stopped me. The source material may have arrived intact and the emptiness may be genuine — because the subject itself does not match the framework. In our sport that mismatch is so easy to produce that it needs its own section.

The word that names two sports at once

The document carried a warning I liked more than anything else in it: "field hockey versus ice hockey is unresolved and cannot be inferred."

That is not a bureaucratic line. It is the foundation of the entire structure. If the subject turns out to be ice hockey, then penalty-corner counts, drag-flick conversion, entries at the 23-metre line, green and yellow cards and the Pro League all go into the bin. Power play, penalty kill, line changes, the blue line and the draft system take their place. And the analysis already written would not be wrong analysis. It would be analysis of the wrong sport, which is worse.

I see this confusion daily in India. "Hockey" is one word and two sports here. When Winter Games coverage arrives, the same word is used on the same sports desk. A newsroom aggregator searching "hockey" returns both codes in one list. An NHL highlight sits directly under an FIH Pro League score in the same feed.

The result is borrowed vocabulary. "Power play" leaks into Indian field hockey commentary, and "penalty-corner conversion" gets written into ice hockey columns because nobody in the chain was positioned to stop it. Inside our own code the disease has a local variant: we compare a five-match HIL window to a fourteen-match international cycle without saying so out loud.

So when an analysis file reaches me, my first question is not what the conclusion is. My first question is who the governing body is. The FIH runs the World Cup, the Pro League and the world rankings. Ice hockey's international federation is a different body with a different championship structure and an entirely different club system. A document that has not settled the governing body is, to me, nine tables of formatting.

Core: three habits that fill the void

Now the part I have to write about myself. The real danger of an empty file is not its emptiness. The danger is that the writer sees a gap and wants to fill it.

The first habit is turning history into explanation. Berlin 2026, eight golds, Dhyan Chand's six goals. These are dates and comparison points. When they are lifted to explain a current result, they stop being comparison and become mood. I have made this error. After the 2026 World Cup quarterfinal in Bhubaneswar, where India lost 2-1 to the Netherlands, my first draft opened with history. The editor cut it and said the first paragraph should say where the goals came from. He was right. The 1-2 in Bhubaneswar is still open on my laptop, and the note at the top of it reads: entries first, story second.

The second habit is the saviour-or-scapegoat coach narrative. Charlesworth, Reid, Fulton. The foreign-coach churn gets written as a personality story when the actual material sits in boardrooms — contract lengths, who signed off, who called the review meeting, how many months before renewal the conversations began. Until the document carries that, the name does not go in. In my file, Graham Reid's tenure occupies two lines, and both lines are dates, not opinions.

The third habit is the unsourced scoreline memory. "Everyone knows", "it is well documented", "people forget that". I have a plain rule here, and it cost me money in 2026. If the clip, the match sheet or the dated report is not in front of me, the claim does not go into the copy. Between March and September 2026, with no live hockey in the country, I coded 640 penalty corners from 2026–2026 broadcast footage — by flicker, by injection angle, by rebound. That count returned a finding that India's knockout conversion had fallen from 21 percent in 2026 to 14 percent in 2026. That is a number I can still print without flinching, because I can walk back to 640 corners. A claim I cannot walk back to is not a claim. It is a habit.

Core: my own error, dated

Tokyo, played in 2026. Before the Games I argued India's penalty-corner dependence would break against Australia's rushers. India lost 1-7 in the group stage. The model looked right. Then India beat Germany 5-4 for bronze, and three of those five came off penalty-corner rebounds — a category my model had folded into a single conversion rate.

I published a correction within thirty-six hours and rebuilt the model. That correction cost me two commissions. It earned me a phone call from a national-team analyst. I added a permanent correction footer and a public error log to my columns, and I began writing models as versioned drafts rather than verdicts.

I am writing all this because an empty file takes me to the same place. When the input holds nothing, two honest routes remain: re-extract, or publish the null result. The third route, the popular one, is to dress your opinion as data. I know that route. I have walked it. It always ends somewhere like Tokyo.

Contrarian: the industry rewards the filled page, not the verified one

This is a problem of demand, not of documents.

An editor receives two drafts. The first runs fifteen hundred words, carries a clean conclusion, three quotes, and a reader who learns something. The second runs eight hundred words explaining that the source material could not be retrieved, so no conclusion is offered, and the piece will be filed when the material arrives. The first ships tomorrow. The second may never ship.

That gap is not produced by empty files. It is produced by a reward structure in which uncertainty reads as weakness. In hockey that structure is especially costly, because ours is a small-sample sport: short tournaments, thin public data, limited broadcast angles. The smaller the sample, the stronger the urge to conclude, because a conclusion is the only thing left to hand the reader.

My objection sits here, and it is where I part company with most of my own trade. Most analytical failures are not failures of opinion; they are failures of input dressed as opinion. And that failure surfaces a year later, when an analyst calls to ask where the rebound category went in your model.

At 0.25 speed, every team confesses. But before that, you have to admit you have footage to watch. And if you do not, the hardest sentence to write is the true one: nothing can be said from this file, and it has to be extracted again.

The second half of the contrarian point: N/A is discipline, not laziness

What that document did best was refuse to hide its emptiness. It wrote N/A in every table, and then it explained why — that stage one had failed, that the governing body was unsettled, that everything downstream was risky without domain confirmation.

We never print that kind of honest emptiness in the media. We fill the gap with adjectives. "Magnificent comeback", "disappointing display", "under the scanner". They all do the same work: they let the reader feel that something was said when nothing was.

I am keeping that document as an example. It is a report that recorded its own failure as a finding and declined to misinform. Journalism treats that as weakness. I do not.

Takeaway: three doors set for next time

I have written an expiry date on this file, because that is the rule I set myself: every open file gets an expiry the moment it is opened, and reopening requires a new document, a new clip or a new source — not a reread.

Three doors are set for this review, and until all three open, the file does not move. First, at least one countable information point from the source — a number, a date or a name. Second, explicit identification of the governing body, meaning the field hockey versus ice hockey question is settled. Third, source name, author and publication date, so source quality can be weighted.

On the day all three arrive, the nine-dimension framework runs at full depth, from penalty-corner entry-angle mapping to the talent pipeline. On the day they do not, I will write what that document wrote: nothing comes out of this file.

The whole subject reduces to one question for me, and it will return at the next tournament. When every circle entry in a match can be counted, why do we write about that match without counting?

I do not trust a system I cannot draw on a whiteboard in ninety seconds. And a file that arrives without a single clip is not something I will call a conclusion.

The tape does not lie, but it takes eleven days to stop lying. In the case of an empty file, those eleven days have not yet begun.

(Note: every number here comes from my personal clip index and public match sheets. This data cannot tell you why teams lost; it can only tell you where goals came from and where possession died. Where there is no footage, there is no conclusion — and this piece documents exactly that condition.)