The Empty Column: The Silence That Cricket's Data Never Records

The ball dropped on the pitch. The batter shifted weight onto the back foot, rolled the bat towards cover, and the scorecard stayed silent.

That is not a hypothetical. A Ranji Trophy fixture lost its live feed for two full sessions and nobody outside the ground felt a thing. Overs kept ticking on the scoring app. Wickets kept falling. Updates kept arriving — all of them generated by an engine that was not on the ground, a template filled half an hour earlier that no one was refreshing. By the time the real feed returned, three wickets had fallen for which there was no footage, no ball-tracking, no catch-map. Nobody complained. The score was correct, and in this game nothing outranks a correct score.

Twenty-eight years of writing this sport from its margins has taught me one thing: the largest lies are told in places where the paperwork looks complete.

The room cricket data now lives in

When I started, we had a teleprinter, a scorebook, and a phone line that collapsed every monsoon. From the groundstaff in Kanpur to the scorer in Mohali, everyone was a link in a chain — and if a link snapped, the next morning's newspaper carried a visible hole. Error showed. Silence did not.

Today that chain is invisible. Cricket coverage flows through four layers: the scorer at the ground, the broadcaster's tracking rig, the aggregation engines that scrape it all, and then the layer of language — us. The first three are machines. The fourth is human. And the human layer instinctively fills every gap between the machines, on the assumption that a number which has arrived must also be true.

That assumption is the story. Data is not truth. Data is a record — and every record, like everything else a human wrote down, carries the blanks its author left behind.

The Oval, 18 June 2026 — a scorecard that knew everything

I was thirty-five, filing from a rented desk in Hyderabad while a colleague in London fed me the room.

Pakistan made 338/4. Fakhar Zaman struck 114 off 106 balls. Mohammad Amir removed Rohit Sharma, Virat Kohli and Shikhar Dhawan inside seven overs, finishing with 3-16. India were 158 all out in 30.3 overs — a 180-run defeat, the heaviest margin in Champions Trophy final history.

Every one of those numbers sat openly on the scorecard. Nobody hid them. And still, of the roughly 26,000 people in that ground, almost all of them Indian, the actual event of that afternoon is recorded nowhere. What I remember is not the scoreboard but the sound of it changing. The stadium went dark section by section, like lights switched off room by room. When the fourth wicket fell, an old man was still clapping — slow, arrhythmic, as though he had forgotten what clapping was for.

I stopped writing defeats as autopsies that afternoon. My column moved from 'why India lost' to 'what the ground felt like at 5:40 pm.' I now keep a separate notebook for ambient detail — a dropped flag, a man still clapping, the fourth-wicket silence — so that every match piece carries at least three things a scorecard cannot hold.

The pitch keeps the score; the silence keeps the story.

Where the pipeline quietly breaks

Now to what pushed me into this column.

A data record reached me recently with its title field empty. Its source field empty. Its summary empty. Its list of 'information points' empty — entirely empty. But its domain label was populated: cricket_asia. Whatever built that record knew the thing was about cricket. It knew nothing else.

That reads like a technical fault. It is actually a journalism crisis, and here is the mechanism.

Inside that pipeline, the layer that extracts article text failed — the page was JavaScript-rendered, or paywalled, or its markup had changed. Then came the real damage. Nobody labelled that failure a failure. It was labelled 'not available.' The blank was accepted as a default, and a meaning was inferred from the default: 'this article contains no clear position.'

Absence of data had been converted into a data point. The pipeline turned its own breakdown into a conclusion, and that conclusion travelled downstream as fact.

This happens in cricket journalism every single day. The only difference is that here we do not call it an empty record. We call it statistics.

Ranji's lost eyes

My generation carries a delusion: that if no shot was recorded, no shot was played.

What actually happens is this. The shot was played. The machine that could have witnessed it was not at the ground.

Most Ranji Trophy venues carry no permanent camera. There is a scorer, working twelve hours, logging every ball, often alone, often without a second pair of eyes to check the count. His handwritten record travels upward, reaches an aggregator, appears on an app, and becomes the single version of truth. If he did not log a catch as a catch, that catch exits history. If he misread the line and called it a wide, that bowler's economy is altered permanently.

Scale it up. A tournament of 100-plus matches a season, most without video, most without independent reporting, covered inside a national newspaper by four hundred words on an inside page. And from that same data we decide who gets an India A call-up next season.

Selection here is not a talent question. It is a visibility question. Whoever has a record gets seen. Whoever is seen gets picked. Whoever is picked builds a better record. It is a closed loop, and it has no room in it for anyone's quiet merit.

The IPL did not kill Test cricket. It killed the domestic pyramid's visibility — and it was such a silent killing that nobody held a wake. When money and cameras migrated upward, what stayed behind was memory. A Ranji fast bowler who loses a season to injury in May has no insurance payout, no broadcast fee, no heatmap. His entire career rests on a spreadsheet nobody scrolls past three months later.

The laundering of 'not available'

That empty record showed me something I had been ignoring for four years.

When we journalists open a player's record, we do not see the blanks. We see the filled cells. If a spinner's tracking sheet covers nine matches and misses three, we average the nine and forget the three — without ever asking why they are missing. Washed out by rain? No camera installed? Tour cancelled? The data vendor never bought the series?

Every blank is a statement. The question is not why it is blank. The question is whose side the blank is arguing for.

Take a fast bowler's death-overs economy. The number looks excellent. Nobody asks which grounds produced it. Small boundaries, high altitude, sea-level air — all dissolved into the figure, none of it visible. When he bowls a final at a large ground and gets hit in the sixteenth over, we say his form deserted him. It did not. It was the same number — except this time its hidden conditions stepped onto the field with him.

I call this the quote-floor. When numbers are separated from the ground they were built on, the floor does not travel with them. The reader takes the number as a line carved in stone.

Heatmaps: the new tea leaves

Now the part that looks most like science and says the least.

Every major broadcast now carries a red-yellow-green map. Where a batter scored, how often, at what angle. It looks empirical. I treat it as augury.

A heatmap tells you where the ball went. It does not tell you what the batter was instructed to do. It does not tell you what field was set, and whether that field made him deliberately choose a different direction. It does not tell you what he survived in the two overs before.

A batter who rarely hits to midwicket is not necessarily failing. He may have been given the job of driving the ball to cover, because the spinner was turning it in the air and midwicket was deep. The heatmap renders both men in the same colour. And every analyst in the room reads that colour into a story — the same story the bowler's tracking data quietly suggested.

A heatmap is not what the player did. It is what the bowler allowed him to do. The distance between those two things is enormous, and it never appears in a blotch of colour.

I once spent three months with a team that pinned its own heatmaps to the dressing-room wall. The coach would arrive with paper, point at the blotches, and say, 'runs leaked here.' One morning a senior batter asked, mid-meeting, 'against which bowler?' Silence. That information was not in the map. The machine had shown direction, not cause.

He went out that afternoon and scored off that same shot, because he had not watched the map. He had watched the match.

The dot-ball deception

In football, possession percentage does the lying. In cricket, dot-ball percentage does it. Both measure everything and explain nothing.

A batter faces forty balls. Thirty are dots. Sounds like a controlled innings. It could equally be three other things: he is respecting a spinner who is not turning it; he has forgotten how to rotate strike; or he is deliberately leaving the ball so a new bowler comes on and the ball stays where his team needs it. The third is the most valuable and the least visible.

In the 1990s I heard a domestic opener explain himself over the phone. 'I don't count runs,' he said. 'I count how many yorkers that bowler has bowled in four overs, and how many full tosses he's already spent. If he's spent the full toss, I won't attack. I'll push him back into the blockhole.' His career strike rate sat near sixty-two. His dot-ball sheet must have looked appalling.

In this game, a dot ball is a sentence that can be spoken three ways and is only ever read one way.

This is where insight separates from the chart. The chart compiles a list. Insight knows the intention behind the list. And intention is never written into a log file. It never has been.

Pre-season tours and the unpaid body bill

A different flank now.

Every May and June we read that a team has announced a foreign tour: three countries, eight cities, twelve days, four matches. The report never states what the announcement is actually paid for out of.

The payment arrives in August and September. Out of a hamstring that spent twelve hours on a bench in April crossing eleven time zones. Out of a spinner's knee from five thousand square metres of airport shuffling. Out of a fast bowler's lower back from squatting on hotel gym flooring laid in three different tile sizes.

Nobody asks. I know why nobody asks — the tour schedule was drawn from a corporate calendar, and cricket's calendar was drawn three weeks after it. The cloth was woven first. Health had no room left in the pattern.

The market counts the fee; the player counts the rooms he leaves. Every tour adds one more memory he will not keep for a trophy's sake — a runway in some city, a hotel window showing another hotel, a room-service tray untouched at dawn.

This is not sentiment. It is accounting. And it appears in no financial statement.

Valuing a nineteen-year-old

Kazan Arena, 30 June 2026. I was thirty-six, covering my first World Cup on site after a decade on Indian cricket desks. France 4-2 Argentina. Kylian Mbappé, nineteen years and 192 days old, scored twice — 64th and 68th minutes — won the penalty Griezmann converted, and ran sixty metres to draw the foul. Around 41,000 people changed their minds about one teenager in eleven minutes.

He was nineteen, and the future had already learned his name.

I changed my method after that night. I stopped writing emerging players as ratings and started writing them as value propositions — what a nineteen-year-old promises a sport, and what the sport will then demand of him.

This is why my pieces on India's age-group cricketers read as warnings as much as celebrations. Everyone sees the first hundred by a boy who scores five hundred runs at nineteen. Nobody sees the machine behind him: eighteen domestic matches, six flights, two rehab centres and one coach whose language he does not speak, delivered across twenty-four months.

We recognise players by their numbers and watch them destroyed by their machinery. Those are two different screens, and we keep our eyes fixed on the first.

The document of a promise

In 2026 the Women's Premier League began. The broadcast deal it signed is a paper I keep in a separate folder. Five years, ₹951 crore. Against the men's IPL cycle of ₹40,800 crore, the figure looks small — a comparison that was never the point to begin with.

In November 2026, when India's women won the World Cup, every column called it 'the next 2026.' I did not, because the two sentences rest on different foundations.

In 2026, no structure followed the win for fifteen years. That was the tragedy of the era — and it happened because there was no broadcast contract committed to showing the players play.

Today the contract exists. Priced at ₹951 crore. The question is not whether India's women won the title; that is true, hard-earned, and belongs to nobody else to dilute. The question is whether over the next three seasons WPL matches reach more homes, whether more city grounds get cameras, and whether more domestic women's cricketers are covered by injury insurance.

If within a year those matches are aired in the same two languages, on the same slots, with the same camera quality, then 2026 was a beginning. If the only way the price gets recovered is a trophy-celebrity package sold annually, then that title ends up in the same cupboard as 2026.

Some scorelines are not numbers but rooms people enter and never leave.

The other side: more data does not mean less truth — it means more confident lies

Now the section that earns me the most abuse.

The received wisdom is that more data produces better journalism. It gets repeated at every panel where an executive puts a chart on a screen.

I will not say the opposite. I will say something further: increasing the volume of data does not improve the quality of the conclusion. It only increases the volume of the conclusion.

The reason is simple. With three data points, you stay uncertain. You write 'it seems.' With three thousand, you write 'it is.' But three thousand points do not answer the question three points also failed to answer — the conditions under which each point was produced.

That empty record taught me this. It contained no contradiction. No wrong number. No falsehood. Only a place where nothing existed, and that place was never called nothing. It was called 'not available' — and 'not available' is a laundering process in which a breakdown becomes a conclusion.

Here is the difference. When a scorer makes a mistake, it gets caught the next day, because something is written on the page and written things can be audited. When a pipeline makes a mistake, the page is blank — and a blank page forms no basis for an audit, because there is nothing on it to audit. Zero conceals itself. Error does not.

Which is why the next big story in cricket journalism is hiding not in a scandal but in an empty column.

The real danger is not that we will be handed wrong numbers. It is that we will never be told the missing numbers are missing — and that we will read that silence as 'no match took place' and look away.

Forward

Next time I open a heatmap, I will not ask it where the runs went. I will ask which ground produced it, whether that ground had a camera, and whose server holds the data for the ball behind that blotch.

My generation granted data the status of reverence. I want to grant it only the status of memory — something that must be re-read every time, re-checked every time, and whose empty spaces must be explained every time.

The ball lands on the pitch. The batter plays. The crowd goes quiet. That last thing has no file format.

Which may be why writing it still requires a human being.