The Empty Column and the Full Corridor: The Cricket Truth No Spreadsheet Records

Five days into a pre-season camp at the Rajiv Gandhi International Stadium, I found the analytics kid sitting at the edge of the practice grid with his laptop open. On the screen was a column headed "expected wickets per ten overs." Against one bowler's name, three characters sloped sideways: N/A. Two rows down, the bowling coach was explaining wrist position to a nineteen-year-old left-arm spinner — the ball that holds its line, then skids, and the half-second that buys before a batsman's feet settle. That half-second had no column.

Four forty in the afternoon. A drinks break that no scoreboard records. After seventeen years on this beat, I was standing there because I wanted to see what teams are actually deciding on this season. The answer was not on the laptop. It was in the coach's unfinished sentence, which he repeated three times, as if convincing himself.

The scorecard says 41. The corridor says everything else. The biggest fact of this season is not who scored how many. It is that a large share of the numbers we hang decisions on was never recorded at all — and when something goes unrecorded, our systems quietly file it as zero.

A franchise decision passes through four rooms. First, the scouting network — what zonal selectors once did, now done by forty-odd stringers and three regional heads. Second, the data desk, holding ball-by-ball files from three seasons, venue splits and matchup matrices. Third, the coaching staff, who carry the daily ledger of the nets and whose sleep is dictated by the travel schedule. Fourth, the auction table, where purse arithmetic and a man's life get written on the same sheet.

My understanding of that four-room structure comes from standing inside it, not from reading about it. In 2026, at twenty-four, I joined Sportskeeda as a junior cricket writer and was assigned to Hyderabad's Ranji Trophy campaign. I spent the season at the Rajiv Gandhi International Stadium, watching Mohammed Siraj's seam position at the nets, and I wrote up his 41 wickets. A support-staff member on that team used to say the same thing every evening: counting wickets is easy, counting the overs bowled before those wickets is hard.

I see the bigger version of that sentence now, only the scale has changed. Every broadcaster, every fantasy platform, every agency runs a two-stage pipeline. The first stage pulls facts out of a match report or a team update — score, player, stat, ruling. The second builds the analysis on top. When the first stage returns empty, the second has two routes: state plainly that the information is insufficient and no assessment is possible, or dress a guess as a finding.

This cycle I was handed a report where the first stage had failed badly. Blank title, blank source, an empty list of information points, no entities named — a schema had come back, not a substance. Reading that empty frame taught me the industry's most expensive blind spot. An empty column looks like a zero, but it is not a zero — it is a failure nobody measured.

Hold that distinction. There is a case where we looked and found nothing happened. There is another where we never looked, and therefore wrote that nothing happened. The first is a conclusion. The second is a fault. Dashboards paint both the same colour, and that colour travels all the way to the auction table.

Siraj's seam position

The 2026 season was a laboratory for me. Siraj was twenty-four and carried the whole weight of Hyderabad's pace attack. The scorecard says 41 wickets. What it does not say is that behind those 41 sit the overs bowled in April and May heat in which no wicket came. I watched him bowl nineteen overs in thirty-eight degrees in one innings. In the third spell his follow-through had shortened by five or six centimetres — a shift I could catch only because I had spent four years in biomechanics classrooms before I ever held a press pass.

That evening the team physio counted ice baths. That number went nowhere. No analytics desk carries a column called "third-spell over and follow-through length," because measuring it requires a person standing at the edge of the grid.

My piece that season, in which I predicted his India call-up, was read fifty thousand times. But the lesson in those fifty thousand reads was not the number. It was that I built a WhatsApp group of thirty fans and asked them what they saw in his bowling. Twelve said, "He takes wickets, that's why." Eighteen said, "The ball moves off the pitch, that's why." That second group gave me the language to explain reverse swing to a lay reader, and that language doubled the engagement on the piece.

Here is the first lesson. A fan's choice of words is data, and it never reaches a spreadsheet. Teams today have a dashboard for fan emotion but no record of fan vocabulary — and vocabulary is what tells you why a player is liked, which connects directly to shirt sales and stadium seats.

Auction arithmetic and the fourteenth man

In 2026 I covered the IPL auction in Bengaluru for Sunrisers Hyderabad. I live-tweeted it and correctly called Rashid Khan's retention at nine crore. What I learned that day is that the fastest man in the room does not win the auction; the one with the best-prepared sacrifice does. The number that speaks loudest in a retention call is not the nine crore — it is what remains for the other ten players once that nine is spent.

The same day I interviewed twenty fans outside the venue and wrote about the team's family atmosphere. That piece went viral. But another page of my notebook was full: the fourteenth man, undrafted, base price twenty lakh, whose sister was sitting in a hotel lobby outside Bengaluru that evening.

This is where purse arithmetic stops being arithmetic. Bidding is theatre — good for television, good for ticket sales, excellent for Twitter. The real question is what the money changes once the hammer falls. A player bought at a twenty-lakh base can open a coaching camp in his village next year. A player who goes unsold will spend next year explaining to his father that nine years on the right path were not wasted.

The Russia World Cup was running that same month, and I compared auction bidding to a football transfer window. One part of that comparison still holds: just as football inflates the fee of a goalkeeper who can kick long over one whose shot-stopping is declining, cricket lets a showy metric lift a player's price above his actual work. A bowler conceding above seven an over carries a "death-overs specialist" tag that pulls a twenty-lakh premium — and no column records who built the tag.

What the bubble never logged

In 2026 I travelled to the UAE to cover Sunrisers Hyderabad inside the IPL bubble. The team stayed in the hotel; so did I. SRH reached Qualifier 2 and lost to Delhi Capitals. Afterwards I wrote a long piece on mental health, having spoken to eight players and three staff members.

One thing kept returning in those conversations: how many days had passed since they last saw home. No spreadsheet has that column. Nor does it record that one player had not cut his hair in three weeks because his mother used to cut it. Nor that a staff member watched his child's birthday on a video call and then sat alone in his room for two hours.

Empty stadiums don't lie. They only tell you that the noise was coming from somewhere else. That season I started a support group for beat reporters inside the bubble, where we traded isolation tips every evening. The most-read thing in that group was not a tip. It was a line from a photographer: "Nobody spoke to me today, and that's fine."

This is where the data desk goes entirely silent. A workload model can tell you a bowler sent down a certain number of balls in fourteen days. It cannot tell you how many of those nights he spent awake. And when it cannot, the space on the dashboard stays blank — and whoever reads the blank treats it as fine.

The silence of ten wickets

In 2026 I covered India's T20 World Cup campaign in Australia. In the semi-final at Adelaide, England beat India by ten wickets. The scorecard's language is clean: no excuse, no near miss. I stayed in the dressing-room area that evening, where voices arrive and then stop.

Inside that silence was something no scorecard can carry. Players were looking at their phones, and nobody was in a hurry to speak to anybody. One senior player picked up a water bottle twice and put it back twice. I spoke to fifteen fans in different cities that night and wrote down their words. Not one mentioned a bowling error. All of them mentioned the same thing — that the team had conceded the match to itself in the first over.

That may be a fan's illusion, but for a beat reporter it is a measurable signal. After that night I added a Fan Voice section to every match report. The effect was that podcasts began calling and a regular column followed.

My point here is the least comfortable truth about my own trade. That silence was a data point, but recording it required somebody standing outside a dressing room — and that location does not exist in any extraction pipeline. On the day the spot stayed empty, the report said no signal was found.

What an empty column really means

Now the part most of the industry will reject.

Our entire trade runs on the belief that more data means better decisions. Analytics desks are growing, files are getting heavier, models are getting better. My experience says otherwise. The sharpest teams I have watched at an auction table were not the ones with the most columns. They were the ones carrying a separate sheet titled "what we could not measure." On that sheet: we have seen this bowler's temperament under pressure in three matches, the sample is thin; we do not know the true severity of this batsman's injury, we are relying on a team statement; this young player's domestic record comes on different pitches, comparison would be dishonest.

A team that keeps an account of its own blanks makes fewer auction mistakes, because it does not buy its own guesswork at the price of fact. I learned that at the 2026 table, when one franchise passed on a player because his numbers came from an inadequate sample, and the following season he was winning matches for somebody else. That team made an error, but its reasoning was not wrong. The sample was wrong, not the direction.

The second common misreading is that analytics is replacing the corridor. The opposite is true. The corridor decides which numbers get collected. A data desk never decides whether follow-through length matters — that call belongs to the coaching staff, and it is usually made at three in the afternoon at the nets, unwritten, unlogged. The entire data structure rests on blind decisions that are never audited.

The third thing bothers me most. When a report returns blank fields, downstream reads it as no signal. The space looks empty on a dashboard, and a month later a trend line has been drawn through it. That is an error that never reports itself. If a pipeline cannot say it extracted nothing, it must at least say it extracted nothing — the two are worlds apart.

And the last point, on which nobody will agree with me. Just as I watched a team concede a semi-final to itself in the first over in 2026, I think several teams this season are losing to the size of their own data rather than to the opposition. When you have a hundred metrics and must decide on three, the biggest risk is choosing the three that are easiest to show rather than the three that matter.

Seam position is hard to show. There is no slot for it. So it does not get chosen. And when it does not get chosen, the next time a bowler shortens his follow-through in a third spell and buys a wicket, the desk simply updates a column.

What to watch next

Three things after this season. First, whether any franchise appoints an analyst whose only job is to record what was not measured. Second, whether boards and broadcasters accept that data pipelines need public audit, the way pitch reports and DRS calls are accounted for. Third, whether the Women's Premier League's broadcast revenue reaches grassroots spend or stops at the press release.

The next time a spreadsheet comes back empty in front of you, ask one question. Is it empty because nothing happened — or because nobody was standing at the edge of the grid to see what did?