Eight Empty Columns: When the Cricket Report Answered Every Question With 'Insufficient Information'

Eight columns were open on the screen, more than forty rows beneath them, and every single row said the same thing: "Insufficient information." Format unknown. Match type unknown. Player unknown. Team unknown. League unknown. Governance level unknown. Risk level unknown. Narrative phase unknown. The only living word left in the entire document was cricket_asia. The paper was about cricket; cricket was not in it.

That evening took me back to an April night in 2026. Homework lay open in a Bangalore bedroom and the television carried Eden Gardens. Royal Challengers Bangalore were bowled out for 49 in 9.4 overs; Kolkata Knight Riders won by 82 runs. Forty thousand people did not speak. No booing, no whistling — a hollow hush, as if the ground had held its breath. I wrote nine hundred words that night and refused to begin with the score. I wrote the silence, the white ball, Virat Kohli walking back. The crowd stopped, and I heard what was missing.

Seven years later that same feeling returned inside a professional analysis file, this time without a stadium. It was the second stage of the two-tier system that now underpins serious cricket coverage: the first stage decomposes an article into information points, viewpoints and entities; the second applies an eight-dimension frame — format, player technique, team landscape, league commerce, governance, risk, public narrative, industry transmission. That day the first stage returned nothing. Zero information points, zero entities, zero headline, zero source, zero date.

The interesting question is what a machine does when it has nothing. The easiest route — and the most common — is to fill the empty template with beautiful speculation about Asian cricket. A stale Asia Cup narrative, a ready-made India–Pakistan frame, an auction rumour. This report did not. It wrote "insufficient information" on every line and listed four probable causes: an empty or truncated source body, a non-textual source such as video or a paywalled page, an article outside the classifier's known taxonomy, or a serialisation fault inside the pipeline. None could be confirmed, so all four were tagged low-confidence.

That discipline is rare. In the nine years I have spent around cricket coverage, filling a gap is treated as a professional skill. Dashboards are not allowed to look empty. Projection models must return a number, even if the number comes from twenty overs of a single innings. It has long bothered me that cricket borrowed football's expected-goals logic and handed it jobs it cannot do — explaining decisions taken inside a match, proving a player's form, grading an umpire's standard. A model can describe the ball's path. It cannot describe what was in the batter's head a second before.

The same gap shows up elsewhere in the game. DRS arrived, the third umpire arrived, the big screen arrived — and the spectator in the stand is still never told what "umpire's call" actually means. The person who bought the ticket is the largest stakeholder in the decision and the least informed about it. Transparency speeches are delivered every season; the translation never reaches the scoreboard.

The most honest line in that report was not technical, it was a warning: a blank risk matrix must never be circulated as "no risks found." That sentence applies to cricket journalism as much as to data pipelines. The integrity row was empty because there was no information, not because the sport was clean. There was no signal of abnormal betting movement because there was no report at all. Absence of data is not absence of risk. The day an institution forgets that difference, every "all clear" it issues becomes suspect.

Apply the same logic to players and it sharpens. In January 2026 I watched the Under-19 World Cup final from Bay Oval. India beat Australia by eight wickets; Manjot Kalra made 101 not out off 96 balls; Prithvi Shaw captained. The win was so clean that nobody felt the need to look at the bench. I looked. Three months later I began assembling the first-class minutes of those eleven boys. By 2026 only four of them had played a single Ranji Trophy match. The other seven do not appear in any record the way members of a trophy-winning team ought to.

Some boys lift the trophy; others become a question. And the question stops exactly where the data stops. A player who never gets a match will always have "insufficient information" against his name — and to the next analyst, insufficient information quietly becomes no case at all. This is Indian cricket's least examined inheritance. The hardest place in world sport is not India's first XI; it is India's second XI — and the cost of that surplus is paid by players who were never given a match to be measured by. Selection debates always ask who should play. They never ask who was never measured.

The crowd suffers the same erasure. March 2026, Melbourne Cricket Ground. The Women's T20 World Cup final, 86,174 people — then the largest crowd for any women's cricket match. Australia made 184 for 4, Alyssa Healy struck 75, India were bowled out for 99, Australia won by 85. I was in a hostel room watching a noise no scorecard has a column for. Within weeks a pandemic emptied every ground. I was nineteen when eighty-six thousand one hundred and seventy-four became zero. Afterwards I spoke to two Bangalore club players who had gone from three hundred spectators to none. What they remembered was not the applause but a PA announcement that cut out mid-sentence.

All three stories share one architecture. In 2026 the score was recorded and the hush was not. In 2026 the trophy was recorded and seven futures were not. In 2026 the crowd was recorded and the silence after it was not. Our archive keeps what is easy to count, and then we form opinions about the whole sport from that partial file.

Here is where consensus breaks. The common view is that more data produces better coverage, and that a null report proves the system is honest. My objection is not to its honesty but to its self-regard. A null result validates the schema, not the sport. A pipeline that found nothing in forty rows could not even establish whether the article it was reading existed. And the moment it travels downstream, some summarising layer reads it as "no risks found" — absence of data becomes a clean bill of health by default.

The same system has another habit cricket has never challenged: format discipline. No honest analysis can mix Test, ODI and T20 numbers, because averages, strike rates and economy rates are not comparable. The report stated that rule in its first line. At the auction floor the opposite happens: a T20 strike rate prices a red-ball future, one good short-format season becomes a valuation of a long career. The discipline an analyst writes first is the discipline the market breaks first.

And one last thing, the one that stings. The record fills itself for those who get measured. A star's columns are always full — every innings, every ball, every away tour. The bench's column stays blank, so the bench's story is never written, and a story that is never written is not present in the next argument. My habit of writing away from the franchise press box comes from that fear: the stories most easily available there are usually the ones the board and the team are happy to tell.

So the next time a dashboard claims everything is recorded, ask one question: recorded for whom? The next report needs only four things — a format tag, a name, a number, a date. Four things, and the empty column fills. It has taken us nine years to admit it was empty.

I write the echo, not the final whistle — and the echo begins exactly where the record ends.