Zero Information Points: When Cricket's Data Goes Silent

May 2026. The IPL final in Hyderabad: Rising Pune Supergiant stopped at 128 for 8, Mumbai Indians reached 129 for 8, one run apart. That night I did not watch the scoreboard, I watched the rings. Where deep point shifted in the twentieth over, which way the sixth bowler's release point tilted, and the gap the batter never filled. I keep a field map for the moments the scoreboard forgets. The next morning, re-plotting those 43 overs into a school notebook, I believed I had understood the match. I had understood its shape, not its mass.

Six weeks later came the Champions Trophy final at The Oval, and a new column appeared in my notebook: the angle of the ball. Two of Mohammad Amir's 3 for 16 came out of that column — Rohit Sharma for 0, Virat Kohli for 5. Different dismissals, one root: where the ball pitched had already decided the outcome before the field was set. That was the year I stopped writing match reports and started writing shapes.

Last week a document arrived on my desk with that same skeleton and nothing inside it. Title: N/A. Type: Unclassified. Information points: an empty list. The strangest line sat in the entities field — "identify from the information points above." The system was asking me to find things using things that were themselves empty. In cricket terms, this is a scorecard that reads "Overs: 50" with the runs column left blank. I turned the sheet over three times, assuming the error was mine. It was not.

One sentence first, clearly: an empty result is not a neutral result. In cricket, "no result" is a scored outcome — rain took the match, the event is recorded, points are split, net run rate shifts. In data, an empty cell is not a no-result; it is a not-read. The gap between those two things is the least examined crack in cricket coverage today.

Here is the structure. Every modern cricket analysis runs on a chain. At the top sits raw text: pitch report, toss, ball-by-ball log, run-rate curve, auction purse. In the middle sits what I call the information point — the atomic, citable fact with a unit, a date, an entity. At the bottom sits the analysis the reader consumes. My generation learned the bottom layer first, and it is now the weakest link. A scorecard that counts overs but not runs is a clock, not a match.

The real question was never what was missing from that document. The real question is how often we mistake silence for a clean report. Format comes first — this is my opening rule. Test, ODI, T20 and The Hundred each have different rules of evidence. In T20 the clock metaphor works, because the required rate is continuously visible and every over costs a decision. Apply that same lens to a Day Three Test session and I am lying. In red-ball cricket the draw, the follow-on and session context govern; time there is a resource, not pressure. That is the first line of my trap card, and it is exactly what the empty document broke: with no format tag, any conclusion can leak between formats and the reader never notices.

February 2026, the Under-19 World Cup in New Zealand. India beat Australia by eight wickets at Mount Maunganui and eighteen-year-old Shubman Gill finished with 372 runs and the Player of the Tournament award. I was in my first year of a BSc in Sports Science at Savitribai Phule Pune University. I logged Gill's scoring zones by hand across seven matches, then rebuilt the sheet in Excel. My hunch was that his cover driving was governed by where the ball pitched, not by where the fielder stood. For the first time a hunch had a cell. The spreadsheet was not the answer; it was the first question with cells. And that question would have been worthless if the cell held 372 without recording whether it was a Test 372, an ODI 372 or a junior T20 372. The same number is two different things in two formats. A strike rate of 135 is too high for a Test opener and too low for a T20 finisher. Without format, the number is a digit, not a fact.

That is why I could not treat last week's blank sheet as harmless. It had a column for fifty overs and an empty column for runs. The system returned "insufficient information." I took those two words and turned them over. Insufficient information does not mean information is absent; it means a pipeline died quietly somewhere in the middle and no alarm sounded.

December 2026, campus shut, home in Pune, nineteen years old. India's second innings at Adelaide ended at 36 all out in 21.2 overs — Josh Hazlewood 5 for 8, Pat Cummins 4 for 21. I did not react. I logged every dismissal by delivery type, length and trigger movement: ball 14, ball 31, ball 47. Through that autumn's empty-stadium IPL in the UAE I logged the commentary too, noting how often crowd silence was filled with narrative. The conclusion was clean: commentary is a secondary source; the stump mic and the wagon wheel are primary documents.

Later, on 19 January 2026 at Brisbane, India made 329 for 7, Rishabh Pant 89 not out, and won the series 2-1 — a side no model had priced. That day I wrote one line in my notebook: collapses are never explained by fate, they are explained by sequence. I repeated that line for the empty document. When information points are zero, only one cause can be assigned — system failure — and even that has to be explained as a sequence: one layer, one cell, one missing alarm.

Now the part that makes me slow to write and fast to argue. When I choose one variable, I must first write its failure condition. Take dot-ball rate. When does it lie? In a Test's second innings, when a session-end block is deliberate. In a T20, when the batter is targeting the bowler at the other end. Then the metric stops measuring performance and starts measuring compromise. An analysis without a stated failure condition is not analysis; it is advertising.

And this is where the empty document taught me the most. It told me nothing, but it showed me what I had been trusting. Cricket coverage daily carries claims that arrive as "the data shows," and we rarely ask when the layer above that data was last checked. A ball-by-ball log feels like the most reliable artifact in sport because it is as linear as an alphabet. A chain that can quietly return empty is the most dangerous kind, because its failure is not visible; it is only felt.

The biggest danger is not a report that is wrong. The biggest danger is a report with no fact behind it that nobody knows about.

A second dimension shows up most clearly in the India–Pakistan promotion cycle. I was born in Pakistan, live in India, and write about cricket. I am often asked about emotion — tension, pressure, history. My answer is that I do not write emotion, I write the calendar. An ICC-only fixture should be read as a nostalgia asset printed twice a cycle. The honest story is scheduling and broadcast rights, not inherited feeling. The day that series was lost, I went back to the date on the calendar and the number on the rights deal, and both proved steadier than any social media post. That is my first belief: a defined shape does not break under commentary.

The same logic applies to pipeline integrity. An analytics system works like a calendar — it has dates, margins and fixed limits. When it goes quiet, the right response is not emotion, it is an audit. The whole Stage-2 method was built on this, and it did its job.

Now the part I consider my most harmful habit — letting the diagram become the argument. It strikes repeatedly. Once a clean field map exists, writing gets easy, and the illusion forms that the map is itself the proof. It is not. The map shows where the field was, never why the ball arrived there. So the rule: write the claim as one sentence first. If the map stands beside that sentence as evidence, keep it. If it starts looking like decoration, cut it.

The blank sheet taught the same lesson differently. It had plenty of cells — as if someone had drawn a map — but no sentence. A map without a claim. This is the most common disease of modern data journalism: the graphic arrives pre-drawn, the headline arrives pre-written, and nobody writes the middle sentence.

It amuses me that my first spreadsheet, the one on Gill's 372 runs, was also just a heap of cells. The difference was one sentence written above it — a sentence that could be proven false. That discipline is what separates analysis from bookkeeping.

Take a case I repeat constantly, because it is sequence rather than opinion. November 2026, the World Cup final in Ahmedabad. Many write emotional sentences about it. I read it over by over: the over where the required rate crossed the wicket-risk line, and the over where the field map shows the bowling side already knew. Those are two different things — one is a number, the other is an intention. Calling a collapse fate gives a fast answer but no understanding. Every collapse has an over behind it, a decision behind it, and one ball someone chose to bowl.

The same logic covers the World Test Championship finals of 2026 at Southampton and 2026 at The Oval. In both I used the same sheet: session-wise runs, the draw probability in the second innings, and the point where a team either took risk or stopped taking it. Those three things tell any cricket final's story, whichever side loses.

Now the place where I have to admit the limit of my own method. Isolate one variable and isolation flatters you into thinking you have captured the whole cause. You have not. Dot-ball rate does not cause wickets; it marks them. A purse figure does not describe a player's ability; it describes scarcity in a market. So I now write, in every piece, at least one line about where my metric will lie — and I include the counter-case, the match where the same metric said the opposite.

That missing discipline was clearest in the blank document. No team, no player, no date, no venue. Yet it carried a baseline: it refused, in writing, to build anything from insufficient information. That was its greatest achievement. It would have been easy for a system to name a plausible team, invent a venue, and convince a reader that a match happened, a winner existed, a hero emerged. It did not.

I call this a telegram bent the right way. A good telegram delivers news even when it is empty — it does not go silent. A bad pipeline fills the vacuum with narrative. That is the whole difference.

Draw the risk map and five categories appear: sporting, personnel, commercial, rules/integrity, and public opinion. With zero entities, four of them are unassessable. The fifth — public opinion — matters most, because filling vacuums is exactly what public opinion does. A rumour, a fabricated trade whisper, a "sources say" line: these do not fill the space information left, they cover it.

And here an older conviction of mine lands. Small clubs and small boards burn resources because every year they must finish a half-product for someone else, and what they get back is uncertainty. The information world behaves identically. A report built on someone else's data lives on someone else's terms.

One line from the Stage-2 audit I will not forget: the absence of an integrity signal is not always a clean bill of health. That applies to cricket as much as to a database. Do not ask why a report contains no dirt; ask whether the check ever reached that far. A scorecard that counts balls but not runs looks as trustworthy as a silent batter.

I will say without hesitation that this episode shook my own method. I have always believed that a field map, two numbers and a full clock let me tell any match's story. That is true, provided one small condition holds: I have the match's name. No name, no field map.

This is where my profession's weakness becomes visible. We analysts take pride in method and forget that substance precedes method. You can map an empty room in three colours; it will not become a room. A great deal of cricket "analysis" now belongs to this category: a fine map of a room, not the room.

The document did one positive thing — it named the verification stage. The difference between Stage 1 and Stage 2 is the difference between a scout and a coach. The scout finds the player; the coach makes him play. If the scout returns empty-handed and the coach still fields a team, the fault is the coach's. In analytics, this is the most common error, because a coach has to put a team on the field and a reader wants fresh copy every morning.

The fix is not a moral sermon. The fix is mechanical, and it sits inside the audit itself. Mandatory fields: format, match nature, date, source tier, and at least one entity. If any field is blank, the system must not emit. The rule is blunt: what is not identified will not be published. The dark cell does not go to print.

I will close with a cricket example. A batter plays the first ball defensively — no story forms. By the tenth over the rate holds — a review grows. In the fifteenth over the required rate crosses 9.5 and he plays a shot he does not own — the narrative completes and the charge is filed: could not handle pressure. False. He could not handle the over where the field had spread deep, the slot was shut, and only one bowler remained he could hit. That was not a lack of temperament; it was a lack of options.

The same happened with the blank document. It did not collapse; it had no over, no ball, no player at all. My job right now is not to write it a story. My job is to write that this time there was no story.

Next time I open that sheet — and I expect it to return intact in the next cycle — I will check three things at once. First, the format tag, because without format every judgement is void. Second, the entity list, because with no names there is no one to accuse. Third, the count of information points, because three points versus one is the difference between five overs and fifteen. And I will still ask the question I asked at sixteen: where did the ball pitch? The map comes after.

Maybe this is what experience means — the realisation that the discipline I am proud of can be learned not only from data but from its absence. Adelaide's 36 taught me that every dismissal has a length. The blank sheet taught me that every story has a presence, and that on the day that presence is missing, the most important work is to keep yourself quiet.