The File That Came Back Empty: Excavating N/A in Cricket's Record

I. The Empty Cell

It was close to two in the morning when I opened the file. The Mumbai rain had stopped and the only light in the room came off the laptop. The file had an unremarkable name: a cricket analysis report, stage two of a pipeline, divided into eight dimensions. Format and match reading. Player technique and data. Team landscape and ranking. League and commercial ecosystem. Rules and governance. Risk. Public narrative and expectation. Industry transmission. Eight cells, exactly the way my own ledger sheets are laid out. I opened the first, then the second, then the third. My hand stopped at the fourth.

Every cell carried the same sentence, phrased slightly differently, meaning exactly the same thing: N/A, insufficient information, cannot assess. Four thousand words of document and not one fact in it. Not a player's name, not a score, not a date, not a ground. Only the frame, complete and clean, and inside the frame that three-letter marker everywhere. My first thought was that I had opened the wrong file. My second was that it had half-downloaded. My third was the one that actually frightened me — the file was whole, there had simply been nothing to put in it.

I have been digging through cricket's paperwork for nine years. First on weekends away from an analytics job in Andheri, logging every Mumbai under-19 club fixture at Shivaji Park by hand. By the close of the 2026-18 Cooch Behar Trophy I had built 412 player files — bowling workloads, dismissal types, school and club lineage, coach names, and the one column that mattered most: who had actually watched the kid bowl. I pitched the database cold to a digital cricket desk. The editor ran it and offered me a contract. I was twenty-nine, took roughly a forty percent pay cut, and kept the spreadsheet as the actual job.

Looking at that empty file on that night, an old habit returned. An archaeologist does not call the soil in a trench rubbish. The soil is what tells you what is buried beneath. I did not shut the laptop. I made tea and started reading the emptiness as a document. Because the thing I have written about most in nine years is not achievement. It is absence. The matches that were never played, the forms never filled, the certificates never requested, the seasons that fell out of the scorecards. The empty cell is an old host of mine.

II. Context: The Shape of the Pipeline

Every serious cricket desk now thinks in two stages, whether or not it uses those words. Stage one is extraction — pulling facts out of a raw source: a match report, a scorecard, a board statement, two lines in a vernacular paper, a coach's WhatsApp message. Stage two is the analysis built on those facts: what the format was, which phase decided it, which player's number survives comparison with the benchmark, how deep the squad is, where the league's money is moving, whom the rules favour, what the crowd believes.

This time stage one came back empty. Blank title, blank source, blank list of information points, blank core viewpoint. The only populated field was a domain label: Asian cricket. A label is not a fact. It is a yellow sticky note on the outside of the file saying that something Asian is inside. It cannot tell you whether that something is a Test match or a T20 league, Bangladesh or Afghanistan, an under-19 fixture or a franchise auction.

What stage two did next is an example of professional honesty and is rare in this industry. It did not guess. It did not say that since the label says Asian cricket, the subject was probably an Asia Cup match and India probably won. It built the architecture of all eight dimensions, marked insufficient information in each, and stated plainly at the bottom that this was not analysis but a null-input condition. Reading that document gave me an odd kind of relief. In twenty years I have read hundreds of reports in which a blank was filled with confidence. This was the first time a system had called its own blank a blank.

But my job is not to feel relief. My job is to ask why the blank was there. And one distinction has to be made cleanly at the start, because the whole piece rests on it: there are two reasons for an empty field and they look identical. First, the source contained no information. Second, the source contained information and the pipeline could not read it. In the first case we learn something about the source. In the second we learn something about the pipeline. In both cases the screen prints the same three letters.

That is the central insight of this affair — a blank cell in a record is never itself a fact, it is a question, and the answer to that question lives outside the cell. The day you accept a blank as a fact is the day you have destroyed your most valuable clue.

I found the ledger first; the season only made sense afterward — that is the old habit, and it had to be applied here too. I began looking around the file the way you look at the soil layers around a trench. When was this file built? From what source? Did that source have a title that never made it into the file? Did it have a date that survives only in a system log? Is this emptiness alone, or did the other files in the same batch come back empty too? These are not facts but questions about questions, and in cricket the things I have learned most from arrived exactly this way.

This is also where the industry repeats its oldest habit: filling the blank. An editor will say the match must have happened, just write something plausible. An analyst will say the label says Asia, so it was probably India-Pakistan. A scout will say the boy is good, so what if the numbers are missing. In this trade the pressure to fill a blank is as sharp as any deadline. And the man who refuses is called slow, stubborn, difficult. I have been called all three for twenty-two years.

III. The Core: The Life Cycle of N/A

1. Two kinds of empty cells, and how to separate them

The first question in front of any blank is not what should have gone in it. It is whether anyone tried to fill it. On paper that distinction looks small. On a career it is enormous.

Years ago I added a third column to my own sheet instead of two. First: the number. Second: the source of the number. Third: refusal or absence. If a boy's bowling workload was missing because the scorecard never recorded overs, that is absence. If I asked the state association in writing and it declined, that is refusal. A refusal is, ironically, a better datum than an absence. A refusal carries information about intent. An absence carries only air.

Looking at that empty file, I could not determine which kind of empty it was. That was the document's most honest quality — it gave both the same name. But for an archaeologist it leaves the case unfinished. If a layer is missing from a trench, you do not say nothing was here. You say something was here and someone removed it, or something never arrived. Either way the history of the ground changes.

The greatest power of the empty cell is that it does not choose for you — you choose how to read it, and that choice is your real bias.

2. The propagation of nulls

There is a rule in data work I learned through labour rather than from a book: a blank cell never stays where it is. It travels. A blank at stage one becomes cannot assess at stage two. Cannot assess at stage two becomes no data available on this player at stage three. That sentence becomes limited information in a scout's report. And at stage four the player drops off the very list a state selector looks at before the monsoon.

In four steps, a technical failure becomes a player's disappearance. And nobody decided anything. Nobody called the boy poor. A cell simply stayed empty and the emptiness chose the rest of the road.

This is why I count blanks in my own sheet. At the end of every season I check how many columns are empty for how many players and why. If a column is empty for twenty percent of the boys, the fault is not in the boys. The fault is in the question I asked, which nobody could answer. In 2026 the emptiest column in my sheet was how the boy's age was verified. Thirty-one of 412 files had it filled. Seven and a half percent. Chasing that blank is what eventually took me down the bone-age alley where the refusals, not the records, showed me the way.

3. Six refusals out of fourteen

In January 2026 I was in New Zealand. On 3 February at Bay Oval in Mount Maunganui, India beat Australia by eight wickets. Manjot Kalra made 101 not out and Shubman Gill finished the tournament's best player with 372 runs. I wrote the match report the way everyone wrote it.

By the time I was back in Mumbai it was June. The World Cup was on in Russia and Indian cricket had gone quiet. The desk wanted a feature. I filed information requests to fourteen state associations for their TW3 bone-age verification records for age-group entries. Six refused. Eight gave something, half of it unusable. I published the refusals instead of the rumours. It became the most-read investigation the desk ran that year.

The first lesson from that exercise was that the bone-age blind spot was not a gap in data but a gap in asking. The second lesson was more devious: a refusal, if recorded with a name and a date, becomes data itself. Six refusals can be named. Nine estimates cannot.

That is why my first question about the empty file was not a guess but this: had anyone asked? If someone asked and got nothing back, this report is the first page of an investigation. If nobody asked, this report is an illustration of an old habit.

4. Who pays for an empty cell

Here I have to stop myself. My worst instinct is finding the ledger more interesting than the match. Reconciliation is where I feel competent, and a player's difficulty tends to slide behind it. So a person has to be named here, even with the name changed, because the story belongs to a cohort I recorded in my own sheet.

A left-handed opener, Mumbai, 2026 Cooch Behar season, six innings, two fifties. In my sheet his age-verification column was blank. I put him on that year's list of probable under-19s with a note: verification incomplete. The following year, in the state association's trimming, his name went first onto the list of players flagged for incomplete paperwork. Nobody applied the flag. It applied itself, because the cell was empty. He did not make the under-19 side. His under-19 career ended without a single match and without a single missing number.

Two years later I saw him in a club game. Still batting, still batting well, still in no file anywhere. Once the age-group door closes in the year it closes, it does not open again. The price of an empty cell is paid by the person whose cell was empty — and he never learns that his cell was ever full.

5. A map of the lost season

In March 2026 Indian cricket shut. The board cancelled the 2026-21 Ranji Trophy outright. For fourteen months I did not watch a live match.

What I did then became the most useful skill I now have for reading an empty file. I built a six-variable coding sheet and persuaded forty-one club and academy coaches in Mumbai, Delhi and Chennai to send phone footage. Thirty-nine did. I coded 340 young players off that footage — bowling axis, foot position, arm height, ball-to-ball consistency, pace variation within an over. Then I wrote The Lost Season and published it.

In it I put one count that still stings. Of those 340, seventy-one had their entire age-group season cancelled outright. Seventy-one boys lost a full cycle — sixty-five to seventy match appearances, four or five coaching camps, one selection window — that never existed on paper. Nineteen of them aged out of under-19 eligibility that year. Nineteen children who, across their whole youth career, never played a single age-group match for a reason no calendar records.

There is a lost season under every official calendar, and it still leaves marks. It is easy to make that mark romantic. I do not want it romantic. It is a three-digit count: seventy-one players, nineteen of them aged out, one cycle. Numbers do not want ornament. They simply stand there.

6. The twelve-innings rule, applied in reverse

When I sold that database in 2026, one rule went with it, and it gave me a byline and gave editors a permanent scheduling problem: no talent claim without at least twelve logged innings. The rule did not come from the ground. It came from paper. In cricket a brilliant innings is noise; twelve innings is paper. I speak after the paper.

That empty file forced me to apply the same rule backwards. If I cannot assess a player until I have twelve innings, I cannot form a view on a report until I have one information point. This document had zero. So the honest headline of my own piece should have been: nothing can be said. I hold that higher than whether I like it.

Before I trust the table, I dig beneath it for the ledger nobody published. Here nothing was published beneath it at all. That became the real finding.

7. What a label can and cannot carry

The only populated field in that file was the domain label. And the limits of a label need to be stated, because treating a label as analysis is an old disease in this trade.

A label can tell you the subject area. It can tell you which direction to walk if you are going to look for the source. It is the start of a search.

A label cannot tell you the format — the mandatory first-order context for any cricket judgement. The failed new-ball spell in a Test is one thing; the powerplay in a T20 another; a dip in the twenty-third over under the two-new-ball structure something else again. Without the format, every technical conclusion is an answer to a question that has not yet been asked.

A label cannot tell you the ground, the weather, the dew, the toss, Duckworth-Lewis. The things that account for luck's share of a result, which must be subtracted before the sport's share can be measured.

A label cannot tell you the team, the player, the opponent — the whole geography of the contest. Home advantage in domestic cricket is not small; pitches change with a spinner's age; a state selector's eye is slow to catch a player who is travelling.

The real danger of a label is that it gives the reader an excuse. It says: you know the direction. Knowing the direction is not arriving.

8. The only real fact in an empty file

If one thing is proven by that whole document, it is this: a system with eight dimensions that marked emptiness in all eight knows its own limits. And a system that knows its limits can be worked with, argued with, questioned. The system that fills all eight cells with it seems that is useless, however industrious it looks.

I did not sleep that night. I opened a new sheet and named the first column: was it asked? The second: who asked? The third: when? The fourth: what came back? The fifth: why did nothing come back? Into that sheet I entered the thirteen questions I would have put to the source. Not one of them was answered anywhere in the file.

It was not the first time I had built such a sheet. That sheet produced the 2026 audit. It produced the 340-player coding in 2026. Its absence is what allowed sentences into my early work that I now read with embarrassment — sentences where I patched an absence with a guess and settled a boy's future in an academy in a hurry.

IV. The Contrarian Angle: What Was Not Empty Was the Industry

The fastest and easiest conclusion to draw from that file is that the pipeline is lying. Several colleagues got there. One said the system is bluffing. Another said the data is fake. I sat quiet, and I want to put on record that their conclusion was as unearned as inventing a player's name in that document would have been.

The same scepticism I apply to the official record demands to be applied to the accusation. If I cannot prove what a record concealed, I cannot prove the pipeline concealed anything. What was provable was only this: the report arrived and it was empty. What was not provable: why. And the unprovable is not called a lie. It is called an open question.

The contrarian angle starts here and it is uncomfortable. An empty file is convenient for the industry. That sounds wrong, so stay with it. An empty cell cannot be quoted. It cannot be litigated. It cannot be argued over. It generates no ratings and no pointed fingers. In an environment where every statement is trolled, blankness becomes a kind of armour. The board that says nothing says nothing wrong.

That is why the document felt more honest than the industry's habits, and why it will not dissolve into them. A system that says I do not have the information is exposing its weakness. It is also displaying its strength: it knows the difference between fact and estimate.

The second contrarian angle is more uncomfortable and it applies to me. More dangerous than an empty file is the analyst who fills it so well that the reader cannot tell it was ever filled. This is the most common disease in my trade and it is mine too. A scouting report that reads keeper-batsman, sixteen, quick hands, sound batting technique tells nobody whether the boy was watched twice or twelve times. The same sentence prints either way. And a two-million-rupee contract gets built on that sentence.

Cricket has a long-standing addiction here: we keep the vocabulary of our conclusions very tight and the vocabulary of our sources very loose. Until every claim carries its sample size, the empty file will keep taunting us, because it is doing exactly what we ought to do — printing its sample. Its sample is zero and it is not hiding it.

Youth cricket hides its fossils in plain sight: birthdates, budgets, and borrowed birthdays. Having walked between those three for years, I still find that the biggest lies are told where nothing is written. A filled document is an opponent; it can fight you. An empty document becomes a friend, and friends are not watched carefully.

The pandemic did not erase the season; it reburied it under compressed fixtures and silence. What the industry did afterward is the warning. Some wrote off 2026-21 as a zero year, as though no child grew older in it. Every year ages everyone, and eligibility windows age with them. A boy who was seventeen that year turned eighteen the next, and a season's chance never came to him. Everything in this piece rests on one sentence: an empty space in a record behaves like an empty field of a farmer's land — it does not pause, it harvests.

V. Takeaway

I left that sheet open. Thirteen questions, zero answers. The first thing to watch in the next cycle will not be the document's reply but whether the file comes back populated at all. If it does, the emptiness was in the source and only the work was delayed. If the same file returns empty, the question stops being about the source and becomes a question about the pipeline. And a question about the pipeline becomes a question about the batch — every other article extracted that day may carry the same blind spot. That frightens me most, because one empty article is an accident and a whole empty batch is a rotten foundation.

Meanwhile one habit has to change. Every analysis should end with a list: what was asked, of whom, who refused, and where experience alone carried the work. The list will read as boring, will break deadlines, and will give editors a headache. It is also the only thing that can save some boy's career from the N/A that an analyst was in a hurry to fill at two in the morning.

The question is not anyone else's. It is mine: if I am not allowed to make a claim on a number until I have seen twelve innings, who gave me permission to fill a blank?