The Blank Column: What Cricket Analysis Owes to Absence

The report reached my desk in Kolkata at 1:40 a.m. I have been reading reports for fifty years, and for the first time one of them handed me nothing. Title: N/A. Summary: an empty bracket. Information points: a list with no points in it. Author stance: N/A. Purpose: N/A. One field was filled — a tag reading cricket_world. So much is settled: the subject is cricket. Beyond that, nothing is settled at all.

I thought of Eden Gardens, 2026. Thirty-one years old, my eleventh first-class season, left-arm spin, forty-two overs against Bombay, three wickets for ninety-four, and an innings defeat. What I owned after that match was a written record of three hundred and eighteen deliveries — entered in a spiral notebook, every ball marked on a hand-drawn field. I had numbers and I had a loss, and I still did not sleep. Tonight the arrangement is inverted: a loss or a win is entirely possible, and there is not one number to argue with. An empty column speaks more loudly than a scoreboard. It only needs someone willing to hear it.

The factory of numbers and its assembly line

Cricket coverage has spent fifteen years becoming a factory. Every ball becomes a data point, every data point becomes a graphic within minutes, every graphic becomes a verdict by morning. The first machine on that line is the one that pulls 'information points' out of the raw match — atomic facts sturdy enough to carry an argument. The second sorts them into categories: player, team, rule, market. The third assigns meaning.

The report on my desk showed the first machine returning empty-handed. That does not mean the match never happened, or the story did not exist; it means something broke at the first station. The likeliest reading is that the source text never reached the machine, or reached it and was zeroed out by a parsing or language-detection error. That conclusion belongs to process, not to cricket. The distinction is not small for anyone who writes.

An old condition returns here, one I have repeated in every meeting for thirty years: no cricket number means anything without its format context. A Test average, an ODI average and a T20 average are citizens of three different countries; seating them on one page is not analysis, it is upholstery. A report stating that Test, ODI or T20 could not be determined has, in fact, said a great deal. It has said that no comparison here is valid, and therefore none should be attempted. The industry reads that as weakness. I read it as discipline.

Two ledgers: one for runs, one for reasons

My method has not changed in fifty years. I keep two ledgers: one for runs, one for reasons. The public ledger prints averages, strike rates, economy rates, auction prices. The private one sits in my drawer: who was rested when, who was put on an international flight the morning after a domestic match, who was denied an over because his economy rate embarrassed someone in a boardroom, and who was never picked at all across three seasons.

A report with empty information points is the cleanest specimen of that private ledger I have seen. The public ledger says nothing — not because nothing happened, but because what happened never entered a column. When non-entry itself becomes a pattern, the reader has to look at the margin of the page.

I learned this in 2026, and the lesson came from geometry rather than from the result. Bombay's No. 4 scored seventy-one of his ninety-six runs square of the wicket. I charted three hundred and eighteen deliveries across three days, marking each one on a hand-drawn field. In the second innings I moved the sweeper twelve yards finer, and the same batsman was caught at deep point for nine. We still lost the match. From that week my copy has gone to the desk with a field map attached. Editors tolerated it, then demanded it, because a reader could see the argument instead of taking my word.

The Ranji audit: the page no data desk ever visited

What has happened to domestic cricket is the larger sibling of this empty report. In twenty years the data factory has covered the international calendar and the auction circuit completely. Every ball of every T20 league sits in a database. The Ranji Trophy — the layer that produced Zaheer Khan, Sunil Joshi and Anil Kumble — still barely gets its deliveries logged anywhere. A six-month season runs, no form graph is built, no fourth-stump map is drawn.

The consequence is direct. When a young cricketer carries the record of five thousand first-class deliveries, that record should weigh more than three excellent T20 overs at nineteen. The system does not weigh it that way, because the ledger that decides does not contain those five thousand deliveries. Red-ball economy has no column, so it is treated as risk; league economy has a column, so it is treated as investment. That is accounting, not cricket judgement.

My position on youth development comes out of the same ledger. In a satellite-club model, large clubs step around their homegrown rules. A prodigy from a small league becomes a satellite asset: his value is recorded not in his own soil but on the balance sheet of whichever club borrowed him. The Ranji Trophy hollowed out along identical lines. The domestic tier was an asset; it became an asset that gets rented out and forgotten.

The 1 a.m. batting order

2026 Ranji quarterfinal, Bengal against Railways. Forty-five years old, in the coach's chair. I spent the night watching three seasons of tape on Railways' left-arm spinner — two hundred and forty deliveries, sixty-two per cent of them on a fourth-stump line to right-handers. Our No. 6 averaged eighteen against that angle. At 1 a.m., the batting order becomes a confession.

At 1 a.m. I moved a nineteen-year-old to No. 3 and dropped the senior pro to six. The teenager made sixty-four off one hundred and twenty-one balls and Bengal won by three wickets. I never explained it to the senior pro. That night became the template for my writing — process instead of result, the count of deliveries off the tape, and the thing that did not happen. A batting order revised at 1 a.m. is just a theory with consequences. And a theory can only be tested one way: by naming the bowler, the over, and the angle it was built to neutralise. If you cannot name them, it is not a plan. It is a rumour.

The pause before the bid

20 February 2026, Mumbai. At the first IPL auction I sat in the media row with a calculator instead of a notebook. Eight franchises spent roughly $39.7 million on seventy-eight players in one afternoon. Mahendra Singh Dhoni went to Chennai for $1.5 million, Andrew Symonds to Hyderabad for $1.35 million, and an unproven Ishant Sharma to Kolkata for $950,000. Everyone around me wrote about the money. I wrote about what the money was buying: overs, wickets, and left-arm angle.

I built a crude value table — dollars per over bowled, dollars per run at a given strike rate — and filed it as a sidebar nobody had asked for. Two seasons later every auction preview in India carried a spreadsheet. Mine was still the only one that published its assumptions. On the auction desk, every price is a sentence someone did not finish. To finish it you must state which over, on which pitch, against which matchup the price was paid.

On the market's foundational error my view has not moved in twenty years: an auction price and international strength are different units. The day a boardroom balance sheet starts deciding a player's quality, evaluation of the sport stops and evaluation of the stock begins. And the most important information on an auction floor never enters the table. The pattern is never in the scoreboard; it is in the pause before the bid. Which franchise lifts the paddle and holds it, which one hesitates two seconds — that is the real data.

Wankhede 2026: a decision tree, not instinct

2 April 2026, Wankhede. India needed 275. I spent the chase watching the dressing-room corridor rather than the ball. In the twenty-second over, at 114 for 3, Mahendra Singh Dhoni walked out ahead of an in-form Yuvraj Singh and made 91 not out off 79 balls; India finished on 277 for 4 with ten balls unused.

By the next morning every paper had it that he trusted his instinct. That is wrong, and it has been repeated for fifteen years. The promotion was not instinct. It was a pre-agreed response to Sri Lanka's two off-spinners turning the ball into the right-hander's pads: a left-handed captain goes up, whatever the card says. When a decision comes out of tape and angle, calling it instinct is simply hiding its audit line.

Since then my copy reads like a decision tree. Who decided, when, and against which bowler — three questions. Journalism that cannot answer them is not writing cricket; it is writing cricket's advertising. Readers want to argue with the premises, not the adjectives.

The risk of the empty cell

The counter-intuitive part, and the part the industry will not enjoy. The industry fears incomplete numbers more than wrong ones, and it fears the lone empty cell most of all. A wrong number reaches three hundred websites in two hours because it is useful to somebody — a slide, a headline, a post. An honest blank bracket is useful to nobody, because nothing can be graphed from it. So when a pipeline returns a null, the institutional reflex is to fill it, and the filler is usually a hollow bridge: 'according to sources', 'those close to the camp'.

My reflex runs the other way. I treat the blank as a finding, not an embarrassment. A report that could not name a team, could not fix a format, could not establish a competition context has done its job at exactly the point where dishonesty would have entered. Had it cheerfully inserted a team, a player and a controversy, it would have looked as complete as a bureaucrat's file — and been just as empty.

Second, the television box is better than us at this, and conceding it is in my own interest. A live review under a dark sky, a field change as the wind turns, a spinner losing one and a half kilometres per hour — the box catches that better. Our databases receive it hours later, by which time it has become folklore. A desk that cannot admit this ends up naming its blind spot as its expertise.

Third, and most uncomfortable: the real risk in a null pipeline is not that bad data arrived. It is that no data arrived and nobody asked why. The most telling element of this report was not its emptiness but its tag — 'cricket_world' where the specified vocabulary says 'Cricket'. That is not a small slip. When the taxonomy itself does not sit correctly, every layer beneath it runs misaligned, and the most expensive error such a system can commit is not a wrong conclusion. It is an empty report forwarded downstream as 'no risks found'. Writing a zero in a risk column and having no risk are two different sentences. If you cannot tell them apart, you are not measuring risk. You are concealing it.

The next reader

For cricket, this whole episode carries one straightforward meaning. The next time a large number circulates — a fee, a double hundred, a record total — ask first: which format, which pitch, and of what exactly is this number evidence? A page without those three answers is still a blank page to me, whether or not a figure is printed on it. My own next step is modest: to hand-draw the bowling angles again through the next domestic season, so that no boardroom spreadsheet can collide with my map and claim it never existed. The ledger never lies; it only waits for the next reader. And that reader may be the one looking at an empty page from his own pipeline tonight.