The Empty Payload: When Cricket's Data Stories Get Published Without a Story

The Empty Payload: When Cricket's Data Stories Get Published Without a Story

Last Tuesday, at my desk in Delhi, my producer sent me a file. Eighty-four pages. Eight major sections, twelve tables, and at the end of every section separate headings for "Analytical Conclusions", "Evidence" and "Hidden Information". I turned to page one. Where the title should have been: N/A. Source: N/A. Article type: unclassified. The information-points list was empty. And through the next eighty pages, every cell repeated one sentence — "N/A — insufficient information."

I read it twice. The first time hoping I had missed a fact, a date, a score, a name. The second time because I could not understand how a document could be eighty-four pages long and contain not one verifiable sentence. Then it struck me: this was the most honest cricket document I had read in forty-six years in the trade. And possibly the most frightening.

Honest, because it did not lie. Where there was no information, it said there was no information. Frightening, because it was completely finished — formatting, structure, confidence, all of it. There was simply no story in it. And I know what our industry does with a document that is completely finished and has no story in it. We publish it.

I remember the night of June 2026. The Oval, Champions Trophy final. Jasprit Bumrah's front-foot no-ball reprieved Fakhar Zaman on 3; Fakhar made 114, Pakistan posted 338/4, India were 158 all out, and a 180-run defeat became the most argued-about result of my career. I filed a 2,000-word post-mortem within six hours, frame-checking the no-ball, the field placement and the commentary clichés, and woke to 40,000 angry replies. That night I had a frame. I had a screen. I had a system that could attach evidence to a claim.

This Tuesday, in that unfinished document, there was no frame at all. That difference is the whole argument.

The template arrives before the story

When I joined The Times of India's sports desk in 2026, the match report had a fixed skeleton: toss, pitch, first innings, turning point, captain's quote, and a connective line at the end. Those slots had to be filled; nobody argued about that. If nothing had actually happened in the match, the slots were still filled — with adjectives. "Gritty", "superb fightback", "composure under pressure". No reader could tell that the desk had nothing worth analysing that day.

Today those slots are JSON fields. The headings changed: "turning point" became "key-phase performance", "captain's quote" became "player technique and data analysis". The bigger change is that the filling is now done by a two-stage system. Stage one extracts — title, source, date, format, teams, players, facts, entities. Stage two builds analysis on top of that extraction.

The file on my desk was stage two. Its stage one had come back empty.

The report itself flagged the reason, and this is the spine of the whole affair. Because every field — even the title and the source, which any genuine article possesses — was blank or default, it was almost certainly an upstream extraction failure, not a real article that happened to contain no information. It stamped that inference "High confidence". Rightly.

But the real question is not where the system broke. It is why the system kept running after it broke.

Eight sections, one truth in each

The first section was called "Format and Match Analysis". Its opening line: format N/A, insufficient information. Immediately after came the sentence I had to read several times — because no format can be established, no tactical interpretation is admissible, since Test, ODI and T20 metrics and game-plans are not interchangeable.

That refusal is the most valuable thing in the document. I know how easy the alternative was. The system could have assumed T20, talked about a four-over spell and death-overs economy, and no reader would have caught it. "The spinner built pressure through the middle overs" — who challenges that sentence? Nobody. It is the safest sentence in our trade.

Walk the eight sections. No format in the first. No player in the second, so role, batting position, recent trend and age-curve position cannot be assigned. No team in the third, so no ICC table can even be selected, because Test and T20 tables are separate and the format is undetermined. No league in the fourth — IPL, BBL, The Hundred, PSL, SA20, ILT20, MLC are all indistinguishable. No governance question in the fifth. No risk item in the sixth. No narrative in the seventh. No event in the eighth to transmit through the value chain.

Every section is empty, and every section states why it is empty. That is the report's achievement, and it should embarrass the profession I belong to — how many of us write "I do not have evidence for this claim"? Our entire training is the opposite. We are taught that news is what gets printed, and what gets printed must be complete.

Thirty-two nights in Russia taught me to steal expected goals for cricket. June–July 2026, sixty-four matches, 169 goals, twelve own goals, and an ugly shot-quality spreadsheet. The football desk's biggest lesson was that "I watched them play well" is a breakable sentence. You break it by stating what "well" was measured against. This document did that eight times. It asked what the benchmark was, and found the preconditions for a benchmark did not exist.

It also refused to spare itself. The "Information Value Rating" put all four dimensions — sporting, industry, timeliness, reference — at one star out of five. No cricket outlet I know has ever printed a one-star information-value rating on its own page. We count our stories in terms of importance, never in terms of price.

Unknown is never the same as clear

On page four, one line went into my notebook. In the governance section: "No integrity signal — positive or negative — is present. This is not an integrity clearance; it is an absence of data. Any reader must not interpret 'no flag' here as 'no issue'."

That is the oldest lie in cricket journalism, and I watched it being built. By 2026, when the match-fixing investigation opened, no scorecard carried a flag. No stadium report said something was wrong. What existed was a phone record and a very calm man. Had we run on "no flag, no problem", that story never gets printed. The 2026 Pakistan spot-fixing case, the 2026 IPL case — in none of them was the first signal in an official document. The first signal was an inconsistency: a no-ball that arrived three deliveries early, an over that had a price.

Unknown and clear are not variants of the same word; they decide an entire moral economy. If I write that a player "faces no disciplinary action", the sentence is true and dishonest, because it omits that I never checked. The report wrote "unknown" and never once wrote "clear".

One counterfactual, at one decision point, and no more — that is my rule. If this empty payload had been handed to the next stage, the one that fills slots, the one that infers and extrapolates and fills blank space with the rhythm of language, what would have happened? An eighty-four page analysis, beautifully written, entirely fluent, entirely certain, containing not one true fact. And nobody would have doubted it, because the frightening thing about false analysis is that it reads better than true analysis. True analysis hesitates. False analysis does not.

Cricket_world versus Cricket

The document contains a technical error most readers will skip, and I could not put it down four pages later. The domain label was filled as "cricket_world" while the schema expects "Cricket". The report called it non-conforming and noted that an unvalidated label degrades routing and query precision downstream.

One underscore. A line between two words. Cricket has a direct parallel. If a player's format label is wrong, his entire record sits in the wrong table. A Test average of 45 dropped into a T20 table becomes a dangerous number, because 45 means different things in the two formats. When a selection committee is looking at three format tables at once, a wrong label does not stay in its place — it changes the direction of a career.

The Next XI Index I built on my channel rests entirely on this problem. The index cannot tell you who is playing best in the country if it does not know which format each player played in. And the larger problem is that the index only sees matches whose scorecards reached a digital database.

This is where a technical report suddenly collides with a very old argument. The report warns that a whole class of documents may be silently failing at extraction — paywalled sources, image-rendered PDFs, and non-Latin scripts.

Non-Latin scripts. Three words that are a death knell for the generation that watched Ranji Trophy cricket played out on newspaper pages. A Ranji scorecard printed in Marathi, a domestic match report in Bengali, an off-season note in Tamil, a trial match story in Hindi — all invisible to a system that can only think in English. And matches that were never digitised never happened, as far as any model is concerned.

I covered that domestic beat on a print desk when Ranji still had a footprint. There was no model then, but there was a man who knew which batsman had technique and which had only numbers. The 2026 auction economy made that pyramid invisible. Twenty years on we are discussing the same pyramid and we do not even have its data. That is not a technical failure to me. It is a cultural one, and it stands inside the system as an empty cell — exactly like the cells in these eighty-four pages.

The gate principle

The report's top recommendation is written in technical language but is, in substance, the oldest selection principle there is: stage two must be hard-gated and refused execution unless the title is not N/A and at least one information point exists. Every request that fails the condition is rejected, logged and alerted.

Read that in cricket's language. It is a gate. A filter that says: until this condition is met, nothing proceeds. And I remember December 2026. December 19, Adelaide: India bowled out for 36, Australia won by eight wickets, and my channel nearly died because I had called it a system failure rather than a one-off. January 19, 2026, Brisbane: India chased 328, finished 329/7, won by three wickets and took the series 2-1. The Gabba week saved the channel and gave me the thesis I still use — India's bench strength is a selection problem, not a talent problem.

What that thesis really says is that the system needed a gate: a filter that screens a player on format, role, recent trend and domestic record before passing him forward. When a committee has no criterion, it picks names. When a pipeline has no gate, it fills templates. They are two forms of the same error, and the damage lands in the same place: where the reader's trust sits.

The risk table rated exactly one entry "High", and it was not a cricket entry. It read: "Empty or defective stage-one payload propagated into stage two." Likelihood: observed. Impact: high, because downstream decisions would rest on nothing. That sentence reminds me of a truth we do not like printing: a bad selection follows a team for four years, and no scorecard ever records its name.

Where I could be wrong

First, and most important: this is one document. One. And I am building an industry verdict from it. That is precisely the mistake I warn others against — a systemic verdict from a single frame. So I put the sample size in the same sentence as the claim: one empty payload, one desk, one Tuesday. This is not a trend. It is a signal. The difference is that I will not print it as a trend; I will say that if it happens again it becomes one, and I will log the day.

Second, a reading that reverses my conclusion. Maybe the system is not broken. Maybe it did exactly what it should — it declined to work on a document it could not read. That is honesty, not failure. And if so, this empty document is a census, not a bug. It is telling us how much of cricket was never digitised and therefore never counted. In that reading the indictment is not of the pipeline. It is of us.

Third, the most uncomfortable one for my own trade. The strength of "do not fill the blanks" is a luxury that belongs to a well-staffed desk. The lone digital reporter in Patna or Coimbatore has no gate. He has a deadline. He has ten stories to file by eleven at night, and if his extraction fails him he fills from his own understanding — as I did in 2026, as all of us have. Before preaching at that man I have to admit he does not have my cushion. So the real reform is not the slogan. It is putting the gate on his desk too.

A twelve-month ledger

I am running this the way I ran things after the Gabba — a rolling twelve-month tracking table, and only claims that can be checked later. Three lines for this empty payload.

Line one: within the next twelve months, Indian cricket media will publish at least one data-driven story whose root is an unvalidated extraction, and no correction will follow. That prediction is checkable. I wrote it for myself, not for the reader.

Line two: automated coverage of domestic cricket will overtake reporter-based coverage — especially in states whose languages are not in the script the score-reading system recognises. When that happens, nobody will notice, because stories will still be appearing.

Line three: it is time to decide how we write "no flag" into a report. My suggestion is unambiguous — never "clear", always "unknown". And if we did not have time to check, we should write that too: "we did not check."

One question has been sitting with me since Tuesday. Those eighty-four pages, containing not one fact, were technically flawless — right structure, right tone, right restraint. If I sent it to a publisher, it might well get printed. So the question is not why the document was empty. The question is why our system is so ready to print it.