N/A — Insufficient Information: The Cricket Report That Had No Match Inside It

On 19 November 2026, two screens were running. In Ahmedabad, hard afternoon light sat on the Narendra Modi Stadium roof, India had been bowled out for 240, and Travis Head was in the last stretch of his 137 — that walk between wickets he repeated all tournament, feet straight, bat late, as if buying time on his own terms. The same evening, a few time zones ahead, Seoul hosted the League of Legends World Championship final: T1 against Weibo Gaming. I walked out of the Okhla booth that night and stood on the roadside thinking about how one date can leave the same bruise on two different sports.

Months later, a document arrived in my inbox. Eight sections. Tables. In every table a column headed "Confidence". And inside those eight sections, every populated cell, every conclusion, every assessment, carried the same two characters: N/A — insufficient information. I read it twice. The first time to check whether I had opened the wrong file. The second time because that was the story. A report so clean, so structured, so trustworthy in appearance — and inside it no match at all. No player, no ground, no pitch report, no date. Only the frame.

This piece is about that document, and about how cricket's data economy slips at exactly this point — where the format is empty, and the format is so handsome that someone mistakes it for a finding.

What the case was: a pipeline, two floors, and a hole in between

Modern sports data work happens on two floors. On the first floor, someone breaks down source material into information points — scores, spells, selection news, figures, quotes, dates, teams, players. On the second floor, an analyst hangs an expert framework on those points. The second floor can never produce evidence the first floor did not extract. That sounds obvious, and it is the most violated rule in the business.

The document that reached me carried an empty set from the first floor. No title, no source, no summary, no information points. The second floor did the honest thing and declared it could say nothing. I want to record that the bravest page in that file was its first — the one stating plainly: this is not analysis, it is a null return.

What happened after that is cricket's older disease.

Format first, judgement later

The first condition of any cricket report is: which cricket? Test, ODI, T20, or The Hundred? That is not a technicality; it is the door without which no other room opens. A powerplay means nothing in a Test. New-ball shine is a three-over story in T20 and a five-session story in a Test. Strike rate is the number everyone quotes and whose meaning changes with every format.

23 June 2026, Southampton. The World Test Championship final. Kyle Jamieson took 5/31 in India's first innings — high release, seam upright, and that length where the ball moves an inch more than the batsman's bat does. That figure lives only in the Test column. Move it into the middle overs of a T20 and it becomes meaningless. Likewise 17 September 2026 in Colombo: Mohammed Siraj's 6/21 in the Asia Cup final as Sri Lanka folded for 50. That was fifty-over cricket, with that pitch's moisture and that day's air. Put the same Siraj on a fourth-day Chepauk surface and you get a different bowler with different numbers.

No technical or data judgement can be made before the format is fixed — that is not opinion, it is cricket's structural rule.

And this is where the thing that bothers me most begins. Because in a document where the format is undetermined, whatever number gets filled in later will almost certainly be cross-contaminated. Virat Kohli scored 765 runs at the 2026 World Cup — a record inside a single ODI tournament. I will bet that number walks into a Test argument within a few years without disclosing which window it came from. That is the exact point where data analysis turns into religion: the numbers survive, their addresses are lost.

Eight boxes, eight zeros, one seductive beauty

The report had eight dimensions. Format and match. Player technique and data. Team landscape and rankings. League and commercial structure. Rules and governance. Risk. Public narrative. Industry transmission.

All eight were populated. There were tables and sub-tables, a risk matrix, scenario projections — the flimsiest, most foundational, most attractive of inferences. Every entry read the same: insufficient information.

The first instinct is that the document is incomplete. For me it was not incomplete, it was a mirror. Because this is the disease afflicting a great deal of cricket writing: a handsome frame with no evidence under it.

The risk section logged four checks — injury, schedule overload, fixing suspicion, financial crisis — and against each wrote insufficient information. That is the most dangerous slippage in the whole file. It does not mean none of these exist. It means nobody checked. N/A never means "no risk"; it means only "unknown". When a newspaper prints that table the next morning, zero becomes assurance. A clean record. Nobody even asks who asked.

The other early tell: the domain label read cricket_asia. That is geography. Not format, not competition, not team. It is like calling a match "a Delhi match" and therefore a Ranji match because it happened at Feroz Shah Kotla. Labels are conveniences; they can never serve as evidence.

I made this mistake, and I hold the receipt

October 2026, Shanghai. A six-team cross-region invitational. Three days before the bracket I published a 3,000-word coronation of one roster — five players, one coach, and a number somebody told me secondhand: 14–2 in scrims. I made that number the spine of the argument.

They were out in 41 minutes, 0–2. In game two the opposition went 13–0 in kills. I did not delete the piece. I walked the Yamuna barrage at dawn for five days and came back to write the correction myself.

The lesson from that is the key to the empty report. 14–2 was not a lie. It was a true number, and it had nothing to do with the thing I used it to prove. I did not know which patch those scrims were on, against whom, on which server, on what day. I had a figure and none of the air around it.

The great error of cricket analytics is not that the numbers lie — it is that true numbers get used to prove the wrong thing.

Read the empty report in that light. It told no lie. It said, everywhere, I don't know. But the form in which it was born — eight sections, a risk matrix, confidence ratings — is itself a claim. The form says analysis happened. That is the fraud. The envelope is sealed; nobody could write the letter inside.

The auction lesson: real number, real money, half a story

Put that thinking into Indian cricket's most expensive market. 24 November 2026, Jeddah. At the IPL auction Rishabh Pant went to Lucknow Super Giants for ₹27 crore — the highest bid in auction history. The same day Shreyas Iyer went to Punjab Kings for ₹26.75 crore.

Those numbers are real. I am not in the business of denying them. But the story built around them is nearly always larger than they are. A wicketkeeper-batsman's age, the old knee trouble, his strike rate in major tournaments, the size of his home ground, and which language he holds a dressing room in — without joining those to the figure, 27 crore is just noise.

And this is where I think the young-player premium is slowly being asked to pay its real price. Bidding three or four times the odds on a batsman with fewer than fifty first-class games is not faith in rare talent — it is fear money. Fear that somebody else might have bought him tomorrow. Converting that fear into analysis is like writing N/A into those eight boxes, only more expensive.

The second XI ledger, and one night

I spent my first career on Ranji scorebooks — 118 match days, two IPL auctions, four years on a desk. When I reached a studio in Okhla Phase II in 2026 on an ₹18,000-a-month casting contract, there was a cricket scorebook in my bag. My first broadcast was an eight-team college League of Legends invitational: three days, 26 matches, peaking at 2,400 concurrent viewers on a single YouTube channel. I called a gold lead "the required rate". The clip travelled to 40,000 views and got me the summer.

That one clip taught me the method that still runs before every piece I file: hard numbers on the left, myth on the right, and no empty space between them. Because the reader fills empty space with assumption, and assumption's worst quality is how assured it looks.

In the summer of 2026, while Russia 2026 played on every screen in the building, I cast 32 consecutive nights of the EA SPORTS FIFA 18 India qualifiers from a Delhi studio — 226 matches, one microphone, a fan pointed at the console. Somewhere in those nights a 19-year-old from Pune went past me with a 27–5 record and lost the final 2–3 to a 118th-minute counter. I filed 32 instalments, 21,000 words. Before every one I built a twelve-page player dossier: three verified data points, one recorded conversation, one contradiction. I have not written a rising-star story on vibes since.

I say all this to be clear that I am not against data. I traded a cricket desk for Summoner's Rift, but cricket gave me the rhythm and esports gave me a second language for the crowd. The problem is not data. The problem is the moment data mistakes itself for judgement.

The contrarian angle: the empty report is more honest than a full one

Now the paragraph I am required to write into every prediction — what would have to be true for this to fail.

The fastest failure here is that the source material did contain match information and the extraction floor dropped it. If so, my entire argument is aimed at a clerical error rather than an epistemology. One data entry missed, and I built a philosophy on it. That possibility is real and I am not hiding it. The uncertainty is live and dated to the day this piece is written.

But suppose it was not an error — suppose the material really was hollow. Even then the question stands: is an empty report that announces its emptiness better than a full one that borrows its content from memory?

My answer is yes, but only if the announcement is in the first line, not the last. The eight-dimension document got that right. It said up front: this is not analysis. That distinction matters, because in our trade the damage is done less by information that is wrong than by information that looks right.

And here is where I suspect my own craft. Because if a machine can produce a confident eight-section frame on zero input, what about the thousands of reports humans write with one tweet, one team source and one hurried evening behind them?

Forward

The image I want to end on is not on the field. It is a closed laptop. On its screen are eight boxes, all filled, and not one scorecard ever opened.

The next time a report with a risk matrix, confidence ratings and scenario projections lands in front of you, ask one question. Which match was it? Which format? What date? If those three cannot be answered, the rest is decoration.

Because a batting average is not a character. A KDA is not a character. A strike rate is not fate. They are all just accounts of the time a ball was bowled — and if we do not know in which format, on which ground, on which day, we have an account and not a story.

The best casters do not call the play; they call the room before it breaks. Tonight the room was empty. And I think we should learn to say the most honest call of all: I have nothing yet.