Empty Columns, Loaded Story: When Cricket's Record Goes Silent

The file lay open on the Pune desk and it had exactly one thing in it: a label, cricket_world. In the title field, N/A. In the source field, N/A. In the list of information points, zero. A cricket article existed — the label said so. Which player, which match, which date, none of it was there.

I have been opening files like this for more than thirty years, and my first move has never changed: paperwork first, opinion afterwards. The first thing I packed for Pune was not a pen; it was patience. Patience has earned its keep across three decades on this beat. It is useless against an empty page, because patience is built to wait and an empty page refuses to wait — it asks you a question.

That evening I declined to answer. If the file was about a match, I did not know the score; if it was about a player, I did not know the name. Anything written on it would not have been cricket. But the empty file contained a story anyway, and the story belonged not to a match but to a record. When something goes unrecorded in cricket, the question is never what was lost. The question is who will fill the space.

Cricket's record is made on paper before it is made on a server. Two scorers at the boundary's edge, two separate books, a cross-check at the tea interval. Six deliveries an over, a result for each, a mark for every result. The work is tedious, which is exactly why it can be trusted. John Wisden's Almanack, from 1864, derived its authority from printing everything that happened, however small. When CricInfo began in 2026, it was fed by the same sheet of paper arriving from the ground. The technology changed; the source never did.

Today almost every ball of a Test match sits in some database. The Ranji Trophy has been played since 2026-35, and a large share of its ninety years of scorebooks survives only as arithmetic — who made how many, who took how many. How those runs were made, off which ball, on which day, is not on those pages. Nobody misses a column that has never existed, because the count looks complete.

My own cupboard holds one bound notebook per season. Dates, weather, net times, who bowled which line, who arrived early and who arrived late. No score comes out of those notebooks. What comes out is the condition in which the score was made. The rule is single and severe: no tactical claim reaches print without three separate sightings. Paying for three sightings costs you. In 2026 the rule cost me two quick scoops. That same year it saved me from a viral claim about Steve Smith's captaincy that collapsed inside a week.

In the summer of 2026 I watched all sixteen matches and logged forty-four of forty-seven net sessions at the Gahunje practice square. I wrote thirty-eight pieces that season; twenty-one were built on detail no press conference produced. One of them concerned the powerplay lengths of a seventeen-year-old named Washington Sundar — lengths he bowled in the nets and which the scorecard later reduced to '0/28'. The scorecard tells you what happened; the session tells you why. Neither is whole without the other, and cricket writing keeps treating the first as complete and discarding the second.

That is why what I did after the 2026 England tour was not really newspaper work. Edgbaston, lost by thirty-one. Lord's, bowled out for 107 and 130. Trent Bridge, won by 203. Southampton, lost by 60. The Oval, lost by 118. I came back to Pune and re-watched all five Tests ball by ball. One thousand four hundred and twelve deliveries logged. The report ran six weeks after the series ended, six thousand words, and it was not about winning or losing. It was about the balls left alone outside off stump.

The 107 at Lord's is remembered for swing and seam, and nothing else. The delivery map says a large part of that day was not what happened to the pitch but what was declined off it. Leaving a ball is a decision, and across that tour India's batsmen took that decision wrongly again and again over sixty hours. A left ball has no column on a scorecard, which makes it the largest invisible labour in the game — and it settled that series. The scorebook recorded the defeat. The delivery map recorded the reason.

By the same logic I refused to file in December 2026. India were bowled out for 36 in Adelaide and I watched it at 4:30 a.m. in Pune while every portal on earth published a reaction. I wrote nothing. The 36 all out was more than a number; it was a silence with a clock, and anything driven by a clock cannot be understood without watching the clock. Thirty-one days later at the Gabba, Mohammed Siraj, Washington Sundar and Shardul Thakur won that match — the three names sitting in my domestic file every week while no preview printed them.

This is all a matter of records, and records come in two kinds. One is made and then lost. The other is never made at all, because somebody decided it was not worth writing down. An empty column is not neutral. An empty column is a loan, and the next reader pays it back whether or not he has the facts to service it. I watched that debt settle in February 2026 at the mega auction in Bengaluru: two days, ten teams, a shortlist of 590, and eleven weeks of preparation before it. Those eleven weeks produced a 212-page file — three seasons of Ranji, Vijay Hazare and Syed Mushtaq Ali numbers for every name on the list.

The file earned its keep in the noise. When Gujarat Titans bought Hardik Pandya, Rashid Khan and Shubman Gill, I wrote that afternoon that the real value lay in domestic middle-order batting rather than marquee names. Titans won the title in May. That was not prophecy. It was filling a column nobody else had bothered to fill — the coverage chasing big names had no domestic data, so it printed the easiest story available.

An outsider will call all this a technical matter. A headline came back blank, the information points came back blank, so an engineer has a bug and a pipeline will be re-run. Look at it as cricket and the failure is elsewhere. A gap in cricket never stays empty. It gets filled by the loudest voice in the room, and in India that voice usually belongs to the most famous name. A wrong score can be corrected. A wrong story cannot, because nobody asks a story for evidence.

This is the machinery behind milestone journalism. A hundred is easy to count; the sixty-six overs it took to build are not. The scorebook gives us what can be counted, and what can be counted becomes the agenda. Somewhere in a scorer's book is the afternoon a batsman left forty-one deliveries in two hours and the match was drawn. There is no aggression column on that page, so the innings never reaches the highlights. No column, no story.

Back to the empty file. If the source turns up tomorrow — title, date, information points restored — I will work on it. The real question is not whether the source will be recovered. It is whether anyone noticed it went missing. The day a desk stops at a blank column is the day cricket's record does not stop being written; it simply changes hands. Thirty years on this beat taught me one habit: read every full scorebook once as though it were empty. Often the biggest story is not on the page. It is in the page's absence.