The Scorebook With Empty Columns: Where Cricket's Information Chain Drops the Truth

The crate behind the Eden Gardens nets was still turned over, eighteen years on, so I sat where the game had been. January 2026, the eve of the Ranji final. Wasim Jaffer had scored more than a thousand first-class runs that season and that evening he left 31 balls outside off stump in forty minutes. I opened my match report with the leaves, not the winning runs. My editor cut it to one line. I kept the notebook.

There was no bowler behind the crate this time. There was a file. At six in the morning a report landed on the desk with eight columns — format, player, team, league, rules, risk, public narrative, industry transmission — every heading intact, every row ruled, and in every substantive cell the same sentence: insufficient information. The field called information points was entirely empty. No title, no source, no date, no named player, no venue, no format. The page had lines drawn across it and not one drop of ink.

In thirty-six years on the beat I had not seen a scorebook like that. And I had not felt the pressure to fill one.

The season when rumour is cheapest

This is transfer-window weather. Retention lists, trade talk, an agent's afternoon call, a franchise's wage bill, the arithmetic of a bid — all at once. In the press building in Mumbai one rule applies this season that never makes the scoreboard: the faster a rumour travels, the hungrier the reader becomes for verification. He is not asking for the name of the eleventh man. He is asking which story came from which source, and who checked it.

Cricket's information chain is longer than it used to be and every link now runs on data. At the bottom, district scoring; above it, domestic tournament feeds; then the selection committee's comparison sheet, the franchise's valuation model, the broadcast graphic, the fantasy platform, and finally the analysis market itself. If any link returns empty and does not tell the link above that it is empty, the man at the top reads the silence as 'no news'. The distance between 'no news' and 'the news was never read' is where the whole trade lives.

My own notebook has an old example. After sixteen flights, the 2026 IPL final finished in Hyderabad — Mumbai Indians defended 129 for 8 and beat Rising Pune Supergiant by one run, Krunal Pandya's 47 the difference. The new digital desk wanted 400 words in twenty minutes. I wanted the three net sessions before the final, where Mitchell Johnson bowled for an hour to a field with one slip and no cover. I filed twice that night: the fast piece for the app before the bus left, a 2,000-word travel notebook by six. The notebook, not the match report, was what got read.

So the empty column that morning was not a technical glitch to me. It was the weakest link in the chain my whole trade stands on.

The signature of an empty cell

What looks at first like 'analysis unavailable' is in fact the fingerprint of a very specific failure. All the labels are present. All the values are absent. Had the source article genuinely contained no cricket, the system would have said so. Instead it said the article was about cricket and yielded not a single factual point. That is not a conclusion; it is half a conclusion — it says the document could not be read, or that its body text fell out somewhere in transit. It happens outside the paper too. A co-writer's byline disappears, an editorial box goes missing, and a section that cannot find its place gets treated as empty.

I learned the wicket from pitch reports, and I taught it too. But the first thing I learned was that knowing which end a pitch report was written from matters more than knowing how much grass it mentions. A report saying 'green top' may be green from the Pavilion End and brown from the Far End — true both ways, incomplete both ways. A report that does not say which end it was written from is worth nothing. The file with the empty information points was that report: it said the ground was a cricket ground, and never said which end the observer stood at.

The difference between a filled report and a label-filled report is this: the first contains facts, the second contains their placeholders.

Format is the first gate, and it was shut

The greatest loss in that file was not the names of players. It was the format. Test, ODI, T20 and The Hundred — four different games under one banner. Metrics are not transferable between them, and that is the first condition of the entire exercise.

Take the number that has bothered me for thirty years. An average of 40. In Test cricket, 40 is the mark of a good middle-order batsman who lasts. In T20 it means something else entirely — it tells you how often a player stayed not out, not how useful he was. Pair that 40 with a strike rate of 118 and he can be lethal or a liability, depending on where his team is in the fifth over. Average is a number, not a utility. Reading an average without a fixed format is reading a book's introduction and claiming to know its ending.

Bowling makes it plainer. An economy rate of 7.00 is respectable in T20; in Test cricket the same rate is expensive, and in a four-day game economy is not even the right measure — strike rate is, the balls per wicket. An analyst who judges a Test bowler by economy is sizing a fish by its sense of smell.

And the benchmark for bowling strike rate shifts again between a fourth-day Australian roller and a second-day subcontinental turner. The venue missing from that file was not geographic trivia; it was the grammar of the number. Duckworth-Lewis-Stern, a black cloud on day three, dew, a wet ball in the second innings — all of it lives behind that one gate. Without a format you cannot even say whether the match ended at 180 or 480.

No role, no metric: Jaffer's 31 balls

Not one player was named in that file. That is bigger than a technical gap. A cricketer is evaluated against his role, and if the role is undetermined then even the right statistic answers the wrong question. The opener's benchmark, the anchor's, the finisher's, the keeper-batsman's — four different things. Judging a finisher on average is the same category error as judging a fast bowler on run-out conversion.

At Eden Gardens that evening I watched Jaffer leave 31 balls in forty minutes. A data desk logging that session would record 31 dot balls. Thirty-one dot balls look like the least valuable passage of an innings. On the ground those 31 balls were a statement — that the pitch was slow, and that he would play nothing outside off stump. Mumbai won the title and the first sentence of that statement never entered the scorebook.

My quarrel is not with data but with its single-dimension reading: the same 31 balls are waste in one model and strategy in another. The difference is whether anyone asked why he did it.

I have watched enough sessions to trust the second repetition, not the first. The first drill wakes the body; the second shows its habit. A player's technique is revealed not by the first ball but by the eleventh, when he is carrying the tenth and the foot still stops where it always stopped. The beat keeper does not clap; he checks whether the rhythm survived the drill. That file had no rhythm, so there was nothing to clap for.

The pressure to fill: where corruption begins

Now to the real danger, which sat in that file as a single warning and which I regard as the oldest disease of my trade. An empty template invites completion by virtue of its own tidiness. When seven of eight sections are blank, the mind insists on writing something. That is the moment a reporter begins the climb towards storyteller, and the staircase goes down, not up.

Cricket's most expensive verification failures were born at that moment. In February 2026 Delhi Police exposed the alleged match-fixing syndicate around Hansie Cronje; whatever the investigations proved, they showed that the conversation came first and the evidence afterwards. In August 2026, after the News of the World sting around the Lord's Test, Salman Butt, Mohammad Asif and Mohammad Amir were banned; one video changed three careers. In the 2026 IPL, arrests in Mumbai over spot-fixing included Sreesanth, Ajit Chandila and Ankit Chavan.

All three share one foundation: a piece of information accepted as true because it sounded true. In the betting world, 'it seems' was never currency; 'I asked X' was. In analysis, 'the data says' is not currency either; 'which data, from which format, on what sample' is. The ICC's Anti-Corruption Unit rests on that single principle — information's first duty is verification, its second is distribution.

The oldest red flag on the file I was sitting with was not attached to a reputable institution. It was attached to an empty cell. And the pressure on that cell was strongest precisely because filling it required no one to lie. It required only the most probable name. Verification's greatest enemy is not falsehood. It is plausibility.

The institution's empty cell

One broader context belongs here, the one commercial cricket coverage keeps skipping. In April 2026 the ICC approved the financial model and governance restructuring that the sport calls the Big Three — disproportionate weight for India, England and Australia in revenue distribution and decision-making.

The most dangerous part was not that three boards got more. It was that those numbers were handled like an empty cell — what was not disclosed was assumed to continue as before. The game's money decides how many domestic matches are played, how many scouts are hired, how many physios a state association can keep. When that cell is contested, the effect lands first on the margin, which is where players come from. The margin was never romance to me. It is the place the eleventh man comes from.

Some matches are remembered in the travel receipts before the scoreboard, and some crises are remembered in the red flags a file raised rather than in the numbers. That morning's file did not carry six risks. It carried a seventh — 'downstream decision-making on a null-evidence brief, level: high'. It was the one entry that needed no suppression, because it was already buried.

What I did not write

I read the rules-and-governance rows twice and left them as they were. The 2026, 2026 and 2026 cases sat there as reference, not accusation. That distinction is not small. When a reporter keeps old cases as context he hands the reader a tool. When he pastes them onto a fresh case he takes the tool away and hands over his verdict instead.

I spent forty minutes on how I could fill that file. Every route ended at the same hazard — assigning a ranking tier to a team that had never been named, out of my own experience. Cricket's home-away differential is among the largest in professional sport, and it becomes perfectly useless when you do not know whose home it is. I dropped the route. Dropping it took ten minutes; writing this took longer.

The misreading we call a complete report

Here is where I have to disagree with my own market.

Cricket media wants a full, populated, well-sourced report. 'Insufficient information' reads as a failed assignment, not a finding. That morning nobody said the file was empty; somebody asked why the file was short. That is the question inverted, and we have spent two decades inverting it.

My disagreement is plain: the most honest cell in that document was the one with nothing in it. An eight-dimension report filled with plausible-sounding detail would read ten times better on first pass and do a hundred times more damage. An empty cell is a warning; a filled wrong cell is a trap.

The person setting that trap is not a reporter with bad intent. He is a tired man like me with a bus to catch and two thousand words of space. I say this because I have fallen into it. In 2026, watching the IPL from a quarantine hotel room in Dubai, when Mumbai Indians beat Delhi Capitals by five wickets in the final and Trent Boult took 3 for 30, I wrote about the sound of a wicket with nobody there to answer it. The weakest sentence in that piece was the one where I described the stadium's atmosphere, because I was not in it. That same year I started my quiet file, on one condition: use it to explain selection and workload, never to expose anyone.

The empty stand taught me that absence has a tempo too. That morning's file was that tempo, and it was not mine to play.

The next signal

This story ends not on a scoreboard but at a gate. Whatever pipeline sent that empty file needs one condition attached: if there are fewer than three discrete information points, the payload does not travel upward — it goes back. That check takes five minutes and could have prevented five years of error.

My notebook carries a rule I made sitting behind that crate, one my editors still cut: reach the ground two hours before the first ball, watch the nets before reading the team sheet, and open every report from a place where nobody else was standing. Thirty-two years on, the rule applies to an empty column as well. The question is not how many words a report contains. It is whether anyone was standing behind them — and if nobody was, when that gets admitted.