Zero Information Points, Eight Dimensions: The Cleanest Lie in Cricket Analysis

1:12 a.m., Mumbai. A cricket analysis document sat open on my laptop, and it was so complete that you would have assumed three days of work had gone into it. All eight dimensions were present: format and match analysis, player technique and data, team landscape and rankings, league and commercial ecosystem, rules and governance, risk matrix, public narrative, industry transmission. Under each dimension a table, inside each table columns, inside each column one word — N/A.

At the top, Article Title was N/A. Source N/A. Article Type, Unclassified. Core Viewpoints summary blank, stance N/A, purpose N/A. And the Entities Involved field read: 'identify from the information points above.' There were no information points above. The list was empty. The one thing the whole system was built on had gone missing first.

My first reaction was to close the file and move to the next job. I came back to it the next day, because under all that emptiness was something more honest than any prime-time studio I have sat in front of. Across eight dimensions and seven risk categories, there was not a single sentence claiming anything without evidence. Every cell carried the same stamp: insufficient information, cannot assess.

I have not seen a more honest document in cricket coverage in years, and I have not seen a more frightening one either. Not frightening because it was empty. Frightening because it was alone. Everything else is filled in.

You know the consensus. Cricket is now a data product. Win-probability bars crawl across the screen, graphics carry a 'pressure index', somebody in the commentary box says 160 will defend on this pitch, and the next morning every portal carries the same scorecard. Everything looks measured. Nothing is measured.

I have spent sixteen years in this industry, and for the last several my job has been to find out which question was registered before those graphics were built. The answer is almost always the same: none. The team making the graphic already knew the result; the question was attached afterwards. That is not research, it is reverse engineering, and in reverse engineering you always find exactly what you went looking for.

The pipeline that produced that empty document was not a cricket pipeline. It was a machine that pulls an article out of a feed and then breaks it into eight analytical dimensions. Stage one, extraction, returned no title, no source, no facts. Stage two, analysis, went ahead without a gate and started building an eight-storey structure on that emptiness. And then it correctly labelled every missing brick.

This was not a technical glitch. It was a scale model of the industry I work in. The only difference is that the document admitted its own emptiness, and we never have.

Here is the uncomfortable part. It was not a report on a single failure, it was a pattern. Every independent field — title, source, type, summary, stance, entity — was null in the same way. When every door opens in the same direction, the building is fine and the key is broken. The source existed. It simply was not captured. Paywall, geo-block, JavaScript render, or rate limit — one of the four. And the pipeline converted that silence into a blank cell instead of returning an explicit error.

Which is why I keep arguing for an evidence gate, something cricket journalism also lacks. A check that asks, before anything goes forward: does this claim rest on at least one fact with an actor, an action and a context? If not, nothing gets built. The pipeline had no gate. In broadcast the gate is a producer; in digital it is an editor; in the forty-five-minute cycle the gate is the clock, and the clock has no memory.

I find the DRS comparison cleanest. A review without ball-tracking is a huddle. Eleven players form a circle, the captain says something, the commentator says it looked out — but until three trajectories and an impact point arrive, the huddle is only theatre. In cricket we understand this difference. We call it a bad review and we laugh about it.

In data analysis that same huddle runs daily with a microphone and a chyron attached. An analysis built without an information point is that huddle with a number bolted on to make it feel trustworthy. Which is why I hold one hard rule in my own work: a question I did not write down before I started counting is not a question I am allowed to answer.

In July 2026 I was twenty-three, three months into a junior video desk job in Mumbai, when Harmanpreet Kaur made 171 not out off 115 balls against Australia in the World Cup semifinal at Derby. The innings had twenty fours and seven sixes, and a 137-run stand with Deepti Sharma. My editor killed the pitch in one line: nobody watches women's cricket. I posted the breakdown myself at 1 a.m. — phase-wise strike-rate splits, the four and six counts, the partnership. It did 2.4 million impressions. Four days later the final at Lord's went to England by 9 runs, and my follower count had tripled.

Since that night I have kept a receipts file. Every take time-stamped, every prediction logged, every correction published in the same thread. Because I learned that being doubted is a filing problem, not an argument problem. The person with the file does not shout. She shows.

By the summer of 2026 I had a statistics degree, a laptop and a grudge. India lost the five-Test series in England 4-1 and the consensus was uniform: the bowling had been exposed. I hand-coded 1,240 deliveries and charted Jasprit Bumrah's 48 Test wickets that calendar year. Thirty-one came from balls on a fourth-stump line. Fourteen catches went down in the slip cordon. My four-minute video argued the attack was already world-class and the slip cordon was the story. A broadcaster booked me onto a panel that week.

On that panel the host introduced me as 'our numbers girl'. I corrected him live — by name, politely, immovably. That correction settled into my on-camera persona the way coding rules settle into a spreadsheet. The spreadsheet was never the story; it was the torch I aimed at the story.

18 October 2026, Sharjah. Rahul Tewatia hit five sixes off Sheldon Cottrell in the 18th over. I had no calendar left — two-thirds of my shifts had gone, the studios were shut, and I was making sixty-second verticals from a bedroom in Mumbai. My tactical breakdown was out in 41 minutes: why Rajasthan targeted the short boundary and why Cottrell's hard length got sold. It reached 3.4 million views and the channel went from 4,000 to 210,000 subscribers by the final, where Mumbai Indians beat Delhi Capitals by 5 wickets. That week I wrote down the forty-five-minute rule: a take published outside the news cycle is a think-piece, not a take.

June 2026, Southampton. India lost the World Test Championship final to New Zealand by 8 wickets, and I said on camera what the studio would not — that the side had been selected to draw, not to win. 24 October 2026, Dubai. Pakistan beat India by 10 wickets, Babar Azam 68 not out and Mohammad Rizwan 79 not out chasing 152. India's 151 was a 2026 total. I had published my pre-mortem two hours before the toss naming that exact score as the losing scenario. The abuse was loud; followers went from 200,000 to 800,000.

So I institutionalised the pre-mortem. Before a marquee match I publish the specific number that loses it, on the record, in advance. It forces me to argue forward instead of explaining backwards. And every risk call now carries two things: an explicit probability and a falsifier date, plus a visible ledger of the pre-mortems that never came true.

What has any of this to do with an empty document? Everything. That document did what took me seven years to learn — it declared its sample size, and the sample size was zero. It was the first analysis in cricket history to disclose its own sample size. Everything else hides the number and moves on.

Go dimension by dimension and the pattern sharpens. Format could not be established, so every tactical model — powerplay, middle overs, death overs, new-ball milestones — stayed shut. No venue meant home-ground bias and luck-stripping were impossible. No toss or DLS information meant result and process could not be separated. No player name meant no role could be assigned, and without a role you cannot even decide which metric matters. Strike rate for an opener, balls per dismissal for a finisher, economy for a spinner — none of these carries meaning on its own.

In the league and commercial dimension the document said it plainly: no league named, so broadcast-rights value, franchise valuation and player salaries cannot be tabulated. In governance one line stuck with me: 'silence here is not evidence of clean governance, merely of absent input.' Every cricket board spokesperson should have that sentence framed on their desk.

The risk matrix carried seven categories — sporting, personnel, commercial, rules and integrity, public opinion, systemic, and an eighth sitting above them: analytical. All seven rated N/A because every row needed at least one named player, team, league, fixture or governance event. The eighth rated HIGH: the risk of analysing on an empty evidence base. That is a species of honesty you do not get on a talk show.

Now the hardest part, because my whole brand runs on disagreement and disagreement is the easiest trap there is.

Let me argue the mainstream case at full strength. Maybe that empty document was not wrong but exactly right. A system that says 'I don't know' is worth far more than one that guesses and proceeds. Perhaps my anger was misplaced. Perhaps the real problem is the expectation we readers carry — we open a 1 a.m. thread looking for certainty, and the pundit's job is to compress uncertainty into one clean sentence. A pundit who will not do that is of no use.

Second, and this is the fastest cut at my own method. I coded 1,240 deliveries — but I coded them, not some blind process. I already had a thesis: the bowling was world-class, the slip cordon was the problem. In hand-coding, selection bias lives in the coder, not the code. Had I spent that summer proving the slip was fine and the bowling raw, I would probably have found deliveries in those 1,240 that said so. Publishing the sample size is not enough. You have to publish the coding rules. And pre-registration is a promise, and promises break, especially at 1 a.m.

Third, the eye is not always lying. Momentum can be measured in a lab and cannot be measured on the fourth afternoon at Mirpur. People who have watched 300 first-class matches on bad pitches carry information no coding rule captures — which batsman pushes his front pad forward under pressure, which spinner shortens his flight in his third spell. The commentary box is not the data desk's enemy. It is an archive nobody has coded.

Fourth, and I say this publicly. Sometimes the consensus is simply correct. The commentator who says the body language was poor is not always wrong. Some defeats really are shot selection, some really are the pitch, and some happen because the other side played better. If I start hunting for an analytical flaw behind every result, I am doing exactly what I accuse the commentary box of — result first, evidence later.

So let us put that document back where it belongs. It was not a revolution. It was a feed failure that accidentally performed integrity. The only thing worth learning from it is this: the gate missing from that pipeline is missing from our newsrooms too. We do not build eight dimensions on zero information points. We build 800 words on zero information points and call it a match report.

I am staying with my forty-five-minute rule. But I am adding an amendment: any post containing a number gets a twenty-minute cooling window. If I get it wrong I do not delete — I publish the correction in the same thread, and I treat the correction as content. My curiosity has no bedtime, but my conclusions have to earn morning.

And here is the prediction you can use against me, with dates. First: before 31 December 2027, at least one major Indian cricket outlet will publicly adopt an evidence gate — a rule that rejects any claim without a cited source. My estimate, 55 percent. Second: in the next twelve months, an Indian television cricket broadcast will run a win-probability graphic without naming the model behind it at least once. My estimate, 85 percent, and you can check that yourself in the next match.

The question is not whether that empty document will return. It will, in some form, on some channel. The question is whether, the next time a 1 a.m. thread lands in your feed and tells you it has settled everything, you will ask for the screenshot — or the sample size.