N/A: The Cricket Report That Had Every Field Filled Except the Fact

It was 2:47 a.m. The cooler in the Delhi room ran on one steady note, and on the laptop screen a document was open whose title was: N/A.

I closed it. Opened it. Closed it again. The third time, I started counting the fields, the way you search a rain-washed scorecard for one surviving line. Title: N/A. Source: N/A. Article type: unclassified. Information points: empty. Core viewpoints: empty — summary blank, stance blank, purpose blank. Time sensitivity: not assessed. Source quality: not assessed. I stopped counting at the thirteenth N/A.

One field in the entire document was filled. Domain label: cricket_asia.

The machine did not lie. It refused. Everyone who writes on cricket in this country — me included — puts something into the space where the fact should be. A turn of phrase, a hunch, a memory. The machine wrote N/A and went quiet.

What the machine was actually doing

This was not a match report. It was the second link in an analysis chain. The first link reads an article and pulls out facts: format, team, player, number, date. The second link builds on those facts — tactics, bowling combinations, auction arithmetic, board politics.

The first link came back empty. The second had two roads. Fill the blanks with inference and confidence. Or raise its hands.

It raised its hands. It hung a warning at the top — an upstream data integrity alert — and then, across eight sections, wrote down everything it did not know. It built a risk matrix, applied confidence tags, created a section called “Hidden Information,” and inside that section admitted it could only guess, and only at low confidence.

At one point it wrote: Confidence: High — and the sentence was that it had no information at all.

The machine was entirely confident about its own ignorance. I have never been that confident about my own knowledge.

The 2026 blog and the forty-one readers

June 18, 2026. A hostel room at Delhi University, a second-year sociology student, and the Champions Trophy final. Pakistan beat India by 180 runs at The Oval. Fakhar Zaman made 114.

That night I wrote 900 words. Not about Fakhar Zaman. About the silence in the corridor between rooms after the match ended. I posted it on a Blogspot page called Third Man. Forty-one people read it. One was a Sportskeeda editor who emailed the next day.

The hostel room was quiet. The 180 runs were not.

After that night I stopped writing scorecards. Every piece began with a sensory image and only then moved to the cricket.

Three years later, September to November 2026, the IPL in the UAE. Empty stadiums, canned applause piped into the broadcast. I wrote three thousand words on it — “The Silence of the Stands” — and dragged Durkheim's collective effervescence into it. The argument was that cricket's real text is the crowd, not the pitch.

And on January 19, 2026, at 4:12 a.m., I filed from a Delhi desk — not on the win, but on the bench: Rishabh Pant's unbeaten 89, the Shardul Thakur–Washington Sundar stand of 123 that rescued the innings.

At 4 a.m., the Gabba was less a ground than a held breath.

The habit of writing into the blank

For nine years my work has rested on one thing: writing about what the scorecard does not show. The third seamer. The debutant. The net bowler. The spell that does not look economical because it was bowled on the fourth afternoon when the match was already gone.

I keep a notebook of everything the broadcast camera forgives.

So when that document opened with nothing inside, it did not feel strange. It felt familiar. It was the thing I had been doing for nine years, from the other side. I fill blanks with words. The machine left the blanks blank and gave them names.

The frame that stands after the fact dies

The document had eight large sections. Format and match analysis. Player technique and data. Team landscape and rankings. League and commercial ecosystem. Rules and governance. Risk. Public narrative and expectation. Industry transmission. Each with subheadings, tables, bolded conclusions, evidence lines, risk colours, and signals to keep tracking.

It was a building with a lock on every door and no rooms inside.

The disease of cricket journalism is not that machines are lying. It is that the frame stays standing long after the fact has disappeared, and the reader, having read it, believes he has learned something.

You read this disease every day. The match preview that says “Team A will look to continue their momentum” — a sentence that survives any result. The talking-points graphic with three bullets, none of which is about this match. The projected score that runs across the screen with no error bar.

None of these is a lie. All of them are empty. And empty things are more dangerous than lies, because a lie can be caught.

An archipelago, not a pyramid

Cricket's data is not a pyramid, as we are told — international cricket at the top, domestic below. Cricket's data is an archipelago: dense around the auction and the international fixture, open water everywhere else.

Look at the IPL auction. Every base price, every bid, every purse, on three screens at once. The auction's data is clean enough to build bots on, and bots are built on it.

Where does that same player's Ranji season live? In a PDF. Sometimes on a website where the scorecard takes two days to update. Sometimes on a one-camera stream with no commentary and a score graphic half an over behind.

The shape of that map is not an accident. The map was drawn by whoever pays the map's bill.

In September 2026 the BCCI raised domestic match fees sharply — first-class players from ₹35,000 to ₹60,000 a day, one-day from ₹20,000 to ₹40,000, T20 from ₹10,000 to ₹20,000. Real money, real relief.

Money is not data. The player now earning ₹60,000 a day still has no ball-by-ball record of that fourth-innings spell — which ball came in, which left, when the batsman's feet stopped moving.

This is where you understand that “insufficient information” is not a technical glitch. It is a system, and it has one advantage: what is not recorded cannot be questioned.

Ranji: the blank has a price

This is Ranji knockout fortnight. Somewhere in the country a left-arm spinner is bowling four maidens in the fourth innings, an opener is wearing out his shoes against the same ball for three days, a twenty-three-year-old is making the biggest hundred of his career, and no video of that hundred will exist.

I am not mourning an old memory. Ranji is not finished. It is running now, this week. This is present-tense neglect, not a lament for a lost past.

The BCCI cancelled the 2026-21 Ranji Trophy — the first time since the competition began in 2026 that it was not held at all. Hundreds of domestic players had not one competitive match that year, and no data emergency sounded for any of them.

Take Jalaj Saxena. A Kerala off-spinner who has played first-class cricket for two decades, done enough that his name returns every season in the “never got a chance” list — and every season that list is used for something else. Take Baba Indrajith, the Tamil Nadu batsman whose Ranji average has always been larger than the argument about his selection.

The blank has a price, and the market sets it, not the cricket. If a player's data is incomplete at an IPL auction, someone's phone rings within five minutes, because incomplete data there is a money error. If the same player's data is incomplete in a Ranji knockout, no phone rings, because incomplete data there is not an error.

Some transfers are not moves. They are small griefs with paperwork.

Going unsold at an auction is not an event — it is a screen on which a name turns red before the next bid starts two minutes later. For that boy it is the night he did not call his coach. There is no data for that night. No pipeline ever extracted it, because it is in no scorecard.

Women's cricket: “insufficient information” is the default

March 17, 2026, the WPL final. Mumbai Indians needed six off the last ball and Sajana Sajeevan hit it. That moment still floats through every feed — clip, graphic, a thousand retweets.

Now pull up Sajana Sajeevan's domestic season. How many of her overs have a ball-by-ball record? On what pitch, against which bowling, in what weather did she make those runs? The same “insufficient information” comes back that came back in that document.

In women's cricket, “insufficient information” is not an error state. It is the default state, and it has been the default for so long that it now passes judgment on the cricket rather than on the record-keeping.

Viacom18 bought the WPL's media rights for 2026 to 2027 for roughly ₹951 crore. The price came with a promise — every match, every ball. The question is whether the depth matched the cheque, or only the gloss of the broadcast did.

In November 2026 India won the home World Cup. The question afterwards is not about the trophy. It is about how deep the data frame behind the selection, preparation and replacement calls actually was. How often was a call made on a thirty-ball sample? Where is the wagon wheel for a left-arm spinner's rain-shortened four-over spell?

This is not a moral assignment. It is a question of selection, contracts and broadcast, and it deserves the same scepticism applied to the men's game.

4 a.m.: the vigil and the cron job

On the morning of January 19, 2026, I checked Rishabh Pant's score four times, though it was already on the screen. We all do this. We look again at a number that is already safe, because looking feels like keeping.

That number was safe. It was already recorded in eleven places. What was not safe was the quiet of the room, the sound of the cooler, the knowledge of who else in Delhi was awake. None of them got a log.

A 4 a.m. vigil and a 4 a.m. cron job look identical in a log file. One is love and the other is a schedule. The next decade of cricket will be spent pretending they are the same, and the bill for that confusion will be paid by the man who still wakes up to check the score again.

The machine we feared refused

For three years every cricket conference has sold the same fear: machines will start writing cricket, they will sound like us, and we will not notice.

That fear is out of date. Machines are writing cricket. Previews, projected XIs, auction bots, talking points. And they do it with facts, because facts are given to them.

The new thing is refusal.

A machine that can say “I don't know” is the most disruptive object in a newsroom, because the newsroom's entire economy depends on never printing that sentence.

I have filled blanks too

I keep a file of my own errors. In a 2026 report I wrote of a Ranji fast bowler: “his numbers don't tell the story.”

That sentence was true and it was also an excuse. It meant I did not have the numbers. I filled a blank with literature and called it insight. My editor let it stand because it read well.

This is where cricket journalism's memory bends. We remember the moment and forget the conditions. We remember Pant's 89; we do not remember how many players were injured out of that series and which net bowler was suddenly handed a Test cap.

The document did the opposite. It forgot everything and kept the conditions. Domain label: cricket_asia. No player, no format, no result, no date. Only geography.

The machine remembered where the cricket was and forgot what it was. Indian cricket's own record-keeping has done something similar: it kept the ground, the attendance, the broadcast slot — and lost the left-arm spinner's fourth-innings spell that won the Ranji quarter-final.

Data is not killing the poetry. The claim of data is

One more thing goes the wrong way in this argument. We say data is killing cricket's poetry — xG, strike rate, match-ups, projections.

Look at that empty document. There was no data in it. What hollowed it out was not too much data but too little.

What kills the poetry is not the number but the claim of the number. The six-ball match-up that runs without an error bar. The projected score that vanishes when it rains and is called a prediction when it doesn't.

In one place the document said plainly that drawing conclusions without a format tag is the most common error in cricket research — Test, ODI and T20 numbers cannot be stacked on each other. Every analyst knows this. Every broadcast graphic forgets it.

The empty document at least was honest. It said: I don't know the format, so I will not give you a number. A human in its place would have given one, and it would have looked good.

A blank is also information

Here is what I understood that night. Cricket's record-keeping has never built a system for recording absence.

We have a record of every innings that was played. We have no record of the innings that was abandoned, washed out, left unscored, uncaptured.

A blank is also information, and cricket has never taken the trouble to record it.

If we had a column for what was not recorded, we would know how many domestic players lost a year in 2026-21. We would know how many women's domestic matches have no ball-by-ball record. We would know how many Ranji hundreds have no video.

We don't have those numbers because nobody counted. And nobody counted because nobody felt the need.

The document did what we don't. It counted absence. It listed every empty field and gave it a name.

The next eighteen months

In the next eighteen months someone will build a model that fills these blanks. It will have the venue, the weather, the team sheet, and it will generate an innings that sounds entirely plausible. It will be ninety-four per cent accurate. And in the places that matter — the third over of a fast bowler's fourth spell, an umpire's one call, a debutant's first Test wicket — it will be unfalsifiable.

That day you will have two kinds of cricket. The one that was played, and the one the database built. And no way to tell them apart, because they will be set in the same font.

The document gave me something no analysis has. It showed me that a system is at its most honest when it knows nothing and can say so. I have kept it in my notebook, between the pages where I keep everything the broadcast camera forgives.

The question is not when the machine will learn to fill the blanks. The question is whether, on the day it does, any of us will still remember what was supposed to be there.