Zero Information Points: When the Cricket Sheet Came Back Empty and the Ledger Had to Speak

Eleven fields. Nine of them empty. The file that was supposed to arrive at my desk in the first week of February 2026 — the first read-through of a cricket report — did arrive, but it did not contain a match. It contained the outline of a match. Title: not available. Source: not available. One-sentence summary: blank. Information points: none. And at the bottom, where a healthy file says whether the piece is a Test or a T20, there was one word — cricket_world. That is not a cricket category. It is a claim to be one.

I read the file twice, then a third time upside down. In nine years I have kept the receipt for every crore and every quiet over — the 2026 value-per-crore sheet with 1,140 domestic players coded by hand, the 2026 chart of 2,412 deliveries tagged for control, the 2026 auction ledger that stayed open in front of 217,000 people. After all of that, a file arrived in which nine answers out of eleven were "not available."

And something strange happened. I felt relief. Had all eleven fields been filled, I would have had to trust them, and then ask readers to trust them too. An empty file does not need trust. It needs honesty.

This is the postmortem of that empty file. There is no team here, no player, no score, no projection. There is only what a data desk owes its readers on a day when it has nothing to say — work that, however small it looks, matters more than yet another review of somebody's middle order.

First, what a hand-off actually is

Digital cricket coverage runs on two floors. The first floor catches the story — the headline, the source, the date, and the hard facts inside it. The second floor moves those facts, sets them against history, and pulls out something the reader did not see.

This is a relay race, and in a relay race the dropped baton is the great hazard. The rule on the first floor is explicit: every conclusion must state which information point it derives from. If there are no points, what exactly is the conclusion a conclusion about?

The file I received had a count of zero. That shut all eight doors on the second floor — format and match shape, player technique, squad depth, league commerce, governance, risk, public narrative, industry transmission. Ring any one of the eight bells and the same voice answers from inside: evidence unavailable.

In the regular season, this wound is expensive

Look at what this part of the calendar demands. The reader is watching every match. He does not need the score; the score is on his screen. He needs what is not yet a headline — the two kilometres per hour missing from a fast bowler's first spell, a captain quietly holding a spinner back from the death, a batsman who slows down in the powerplay to speed up through the middle. That layer is the entire pleasure of a regular season.

Showing that layer needs three things: a format, a team, and a ball-by-ball record. With none of the three, you can write about cricket, but you cannot write cricket. That distinction is the whole of my job.

The file had none of the three. No format, no team, no ball. Had I written that "this team's PPDA has dropped across three matches," that would not have been a finding. It would have been upholstery. And the defining property of upholstery is that nobody can check it — because the thing you would need to check it is missing from the sentence.

The weakness of my trade is not that we print wrong numbers. It is that we print numbers nobody can check.

What this feels like at the ground

In November 2026 I booked a hall in Andheri and watched the Melbourne Test with three hundred people. That evening gave me something no spreadsheet has ever given me. When a big shot lands, three hundred people inhale at once — and that sound does not appear anywhere in a figure of 4-0-32-0.

I bring it up because that memory arrived while I sat in front of this empty file. Three hundred people breathing did not come from an information point. It came from the ground. I have the ground, the hall, the three hundred people — and no reliable number. When the number is missing, you have to learn to admit you do not know.

The real story of the eleven fields

Look at them one at a time, because emptiness has a structure too, and the structure is itself informative.

No title. No source. Article type: unclassified. The one-sentence summary blank. No author stance. No stated purpose. The information-point array empty. Entities — team, player, board, league — never extracted. Time sensitivity not assessed. Source quality not assessed.

The eleventh field was the category: cricket_world. It was the only populated field in the document, and it was populated with a value that does not exist in the framework's allowed enum, which expects Cricket.

A document in which everything is blank except the label is not a match report. It is a machine's own statement that it read nothing but has decided this is cricket.

Three causes, and a fourth that is worse

This failure signature — correct schema, empty arrays, "not available" in every free-text field, one wrong label — has three ordinary causes. First, the body was never fetched: paywall, JavaScript-rendered page, blocked crawler. Second, the body arrived and the language or encoding broke the parser, which still happens routinely with Devanagari and Urdu script. Third, most simply, the script was run against a null document.

None of the three gives me a cricket story. All three give me a photocopy of a cricket story with no ink on it.

The fourth cause, recorded in the audit and the one I take most seriously, is that this file looks complete. The schema is right. The headings sit where headings should sit. No warning, no red light. Put it on a website and no reader will ever know there was nothing inside, because emptiness does not look like anything.

The danger of an empty payload is not that it is empty. It is that it looks full.

What a real report carries and this one did not

Any serious cricket report opens with three questions. First, what is the format. It comes first because a Test average and a T20 average are different animals. A batsman with a T20 strike rate of 128 is a different person in a Test. Putting them on one scale is the same error as printing Sunday's score under Monday's name. Second, which phases are being read — powerplay, middle, death, or the first morning of a Test with the new ball. Each phase has its own benchmark, and a strike rate without a phase is a rough count, not an analysis. Third, venue and weather: dew, wind direction, pitch behaviour, and the rain probability that drags Duckworth-Lewis-Stern into the story. This file had no venue, so whose dew was I supposed to count?

And a fourth rule, the easiest to forget: strip out luck. The toss, rain revisions, DRS umpire's call, a dropped catch — all of it moves a result without any talent being involved. A responsible analysis separates them out. I could not separate them here because the data needed to separate them did not exist.

The real bug, the real lesson

Technically the most interesting thing in the whole exercise is that the entity instruction was circular. The template said: entities involved — identify from the information points above. There were no information points above.

In cricket terms, this is a scorecard whose batting column says "see scorecard." An answer derived by multiplying zero by zero. The fault belongs to the structure rather than to a person, and structural faults are the most expensive kind, because they repeat every single time.

The second bug is the label. The allowed enum says Cricket; the file said cricket_world. That is not cosmetic. The label is the rail the piece travels on to the next platform. Get the rail wrong and a Vijay Hazare score lands in the T20 tab, where the conclusion drawn from it will be technically correct and logically worthless — and the reader will never learn which format he was actually reading about.

Borrowed metrics are not lies; they are guests who must be introduced carefully.

I have made this mistake before, in a different costume

February 2026. The IPL auction in Bengaluru. I hand-coded 1,140 players from the 2026 Ranji, Vijay Hazare and Syed Mushtaq Ali seasons into a value-per-crore board. Rashid Khan — bought by Sunrisers Hyderabad for four crore — topped it as the buy of the day. I placed Ben Stokes 41st. He went to Rising Pune Supergiant for a then-record 14.5 crore.

My editor spiked the Stokes line. The piece ran. Twenty-three hundred comments arrived, most of them laughing.

That day I stopped writing for my editor and started writing for the comment thread. Every auction piece now carries a "where the model was wrong" section and a public corrections log. A player bought for 14.5 crore sat at number 41 — I still publish that, because there was no honest way to hide it.

The warning came, and I filed it in a drawer

At the February 2026 mega auction my ledger stayed open in front of 217,000 people — ten teams, 600 players, Ishan Kishan to Mumbai for 15.25 crore, Deepak Chahar to Chennai for 14 crore. The board did not shout; it simply rearranged the price of everyone.

My model had ranked India's death bowling seventh of sixteen. I published it, and then, after a hostile reply thread, I shelved it. Nine months later, on 10 November 2026 in Adelaide, England chased India's 168 without losing a wicket in sixteen overs.

That night I remembered the thing I should have printed in February. Since then the rule has been simple: uncomfortable model findings go out before the tournament, never after. My December column, "What I Got Wrong," is that rule's child. And I read the angriest replies first, because they arrive before the press releases do.

What could have been extracted from an empty file, and was not

There is one thing I deliberately did not do. With a little effort I could have built a beautiful piece out of this emptiness. The label cricket_world becomes "cricket's wider world." Article type unclassified becomes "the complexity of the subject." Information points unavailable becomes "the freedom of information." Three hours would have produced a column with rhythm, with language, and without one checkable sentence.

I am offered that power every week. It is the great catastrophe of my trade.

A spreadsheet is only a story that has agreed to show its working. A story that will not show its working is not a story; it is an educated guess read aloud in a good voice.

The conditions for a re-run

There is exactly one useful output in this whole audit, and it is the minimum-input list. I am printing it so that no other desk falls into the same hole.

First condition: at least three discrete, sourced facts. Those three are the key to all eight doors. Second: the actual title and the actual source — without them, narrative and transmission both sit in the dark. Third: the entities, meaning whichever of team, player, league or board applies. Those three fields alone open almost any report.

Everything after that is priority ordering. A format tag — Test, ODI, T20, or "not a match" — which decides the benchmark. A date or a time-sensitivity stamp, without which no conclusion can be called fresh or stale. An article type, because news, analysis, opinion and rumour need different scales. And an author stance, so a reader can tell whether the source is inflating a story or dragging it down.

The most useful part is that the list is cheap. Add two tokens — a team name and a format — and one of the eight doors opens. Add three facts and all eight do. The cost is so low that the excuses start to look strange.

Where the risk actually sits

The audit carried six risk categories — sporting, personnel, commercial, rules and integrity, public opinion, systemic. Five were marked unassessable for lack of evidence. The sixth carried the same marking, but alongside it came the line I now treat as the hinge of this entire piece.

It said one risk could be rated with confidence, and it was the reader's: if this document were consumed as analysis, it would create the impression that due diligence had taken place. That risk spreads fastest precisely because it has no symptoms.

Cricket has an old name for it. Four overs bowled in the nets become a career's statistics. In the hurry to file a big number, this happens constantly, and nobody questions it, because the number is big.

The contrarian turn: our problem is not empty data

Here is where I have to stand against my own thesis. I am arguing that the empty file saved me. The other half of the truth is that empty data is not my industry's real disease. An empty number at least announces its own emptiness. The dangerous number is the one that looks full.

Most of the complete-looking analyses I read last month rested on a payload exactly as empty as mine. The only difference was that their authors never showed anyone the pipeline. Percentages appeared, trend lines appeared, and commentary was laid on top.

When the crowd went silent, the model started speaking in a softer voice. The problem is that a great many people say wrong things in that soft voice, and silence means nobody corrects them.

The second reversal, the one against me

Now the part I owe against myself. The discipline this article praises — if there is no evidence, do not publish — is also a hiding place. Any writer can say every week that the data is insufficient, and that writer will never be wrong. In a newsroom the name for that is cowardice, not analysis.

My trade has specialists at this game. Hiding behind a model is easy, because a model attracts exactly as much anger as a full bench, and none of it is directed at a named human. You do not name the selector, you do not date the coach's decision, you show a graph. I have had that habit too — Pakistan-born, Mumbai-based, covering the India beat, a writer whose access on any given day depends on somebody's goodwill. I am writing it into this piece here: my own soft pen is a cause too, and a cause belongs in the copy the same way an information point does.

The difference this time is that the story was not the model's. This time there was no score. And where there is no score, discipline is the only honest route left.

Who is accountable

This needs saying plainly, because blaming "the system" is the cheapest excuse available. The file named nobody, which means it did not even name the desk that sent it. But a decision was made somewhere: at some stage a person ran that script against a null document and forwarded the result.

My complaint is not with that person. My complaint is with the gate that was not there. Every data desk needs one question at the door — if information points equal zero, nothing passes. A floor without that gate will one day publish a piece in which everything is elegant and nothing is true.

What to watch next: three signals

For readers who treat this kind of transparency as useful rather than indulgent, I am making three signals public. They go into my notebook with dates, and I will answer for them at the next quarter.

First, this one. I am not claiming that only one piece came back empty on this day. I am claiming that whenever the information-point count is zero, I will publish the zero. If I do it more than twice in the next three months, assume my pipeline is broken and treat the whole ledger as suspect.

Second, Stokes at 41. A man ranked 41st went for 14.5 crore — that line is still on my ledger despite the spike. A writer with no receipt for his most embarrassing miss does not deserve your trust in his averages.

Third, seventh of sixteen. India's death bowling, ranked seventh, printed and then shelved. The rule now is that such a finding goes out before the tournament. If you ever read an uncomfortable finding of mine after a major tournament rather than before it, you will know I broke my own rule.

One line

The most useful column is often the one that admits what it cannot see. Today that column is blank, and I am printing it blank — because the only way I had to fill it was a lie.

If anything in this piece is wrong, the likeliest candidate is that the source file was in fact complete and the failure was entirely mine. In that case this article makes two errors rather than one: it defends me and it quietly indicts someone else. That correction will run in this space, with a date on it. The oldest tradition on my ledger is this one: the cut that stings most gets filed first.