Empty Dataset, Loud Notebook: The Discipline of Verification in Cricket Analysis

Thirteen Vests, Twenty-Three Players

Mumbai, a practice ground, a seven o'clock session last November. Twenty-three GPS vests were supposed to come back. Thirteen did. The other ten players' data never reached the server. One of the coaching staff said, "We'll look at today's numbers tomorrow."

I opened the notebook. Which bowler bowled how many overs, whose boot noise went soft in the last twenty minutes, who looked towards third man and asked for the field to shift, which young player started walking during the final warm-up round — all of it went down. The report that came out that evening contains not a single GPS number. It is still the most reliable document from that week, because I saw every line of it myself; and where I did not see, I wrote, plainly, "did not see."

That is the first lesson cricket writing taught me: when the number is absent, the blank has to stay blank. Filling a blank with a guess is not analysis. It is invention.

Context: A Sport That Got Its Numbers Late

Cricket is going through the quietest data revolution of the decade. Hawk-Eye, Snickometer, wagon wheels, reverse-swing maps, bowling-load monitoring — every delivery now fragments into dozens of data points. The problem is not a shortage of data. The problem is that abundance does not generate interpretation by itself, and both readers and editors want interpretation — quickly.

My English-language commentary debut came in 2026, in the Bangladesh women's ODI series against India, after I came up through social-media analysis videos. The first thing that box teaches you is the pressure of time. You have forty seconds to commit to a judgement. The faster the judgement, the smaller the sample.

At the 2026 Qatar World Cup I attended nine matches as a student stringer. I tracked Morocco's 5-4-1 low block across five knockout matches — only three goals conceded, two Bono penalty saves, an average of 42 percent possession. When the tournament ended, the world wrote that this was the new meta. I did not. One tournament is not a twenty-match sample; it is a question, not a verdict.

In a regular season this distinction shows up most clearly. Tournament heat makes everyone declare a trend; the long rhythm of a league rewards patience, because the next fixture is already testing your previous opinion.

Core: How the Load Ledger Started

I started writing down loads because nobody else was.

1. I was a volunteer data logger with Mumbai City FC's Under-18 side. I was seventeen, with a notebook. Forty-two training sessions, twenty-three players. Every day I recorded three things — RPE, sprint counts, sleep hours. The coach did not read my first report. He handed it back without a comment.

So I re-watched every session tape. I found that one specific build-up shape — 3-2-4-1 — had produced seventeen turnovers across two matches. The cause was not in any tactics manual; it was in positional habit. The two central midfielders were drifting onto the same line, which closed the half-space, which pushed the wing-backs back to receive. The three-second error before each turnover is invisible on a broadcast camera. It is obvious on tape.

I rewrote the report as a one-page table: session, shape, consequence. No introduction, no adjectives. The coach read it that time. That is where a permanent habit formed: every report opens with a verified training-ground number before it opens with an opinion. It makes deciding harder and writing easier, because you are holding something nobody can dismiss as "just your view."

In the 2026-21 ISL season, inside the Goa bubble, I was a remote data intern with Mumbai City FC. The notebook had become a spreadsheet. I logged all twenty matches: eleven clean sheets, twenty-four goals, an average of 62 percent possession under Sergio Lobera. Almost nobody needed those numbers at the time, because the stadiums were empty.

And that is exactly when something else became audible. The stadium was empty, so the notebook got loud. Bench communication, ball-boy delays, the sound of boots on wet turf — those three things became my primary sources. Who was telling whom to cover, what instruction came from the bench before a delivery, which bowler's rhythm broke when a ball-boy delayed — none of it reaches the scorecard, and all of it shapes the match.

There is a trap here. An empty stadium becomes romantic very easily. I have fallen into it more than once — built a beautiful sentence that turned silence into character when there was no material cause behind it. So the rule has to stay simple: every acoustic observation needs a material cause — schedule, crowd restrictions, travel load, or a card. Silence without a cause is not evidence. It is decoration.

I learned one more thing in that bubble, and it remains my most contested habit. Four of those twenty-three players were young but physically early-maturing. The staff wanted to run them on senior rhythms because they were producing results immediately. I wrote down sleep, RPE, and the sprint drop-off across the previous two sessions. By the end of the season, one of them was out with a hamstring injury. The numbers nobody asked for were the only warning that existed. The early-maturing player's body is spent early — and that only shows up in a load ledger.

This is also why I learned to write timelines. I attend almost every training session, and I keep names against absences — who is walking, who is only on the bike, who is doing separate drills with the physio. None of that is a one-day story. It is a pattern, and the pattern breaks before the scoreline does. The rhythm broke before the scoreline did — you never see it in the table. You see it in the session.

Contrarian: Where Data Is Richest, Analysis Is Weakest

The biggest misconception of our time is that more data means better analysis. The reality is close to the opposite. In abundance, numbers travel fast, and travelled numbers slowly become "facts." Take one example.

For two months I have read the same sentence about European football: mid-table sides have "solved" gegenpressing by buying fast, physically strong players. The fact is true. The explanation is half-true. The cause is not strategy; it is physical limit. When both teams press relentlessly across thirty-five metres, the game drifts towards athletics and away from intelligence. Statistics will show more successful pressing. Matches will show more indecision.

Cricket carries the same mould. When powerplay scores rise, we are told this is "a new attacking era." Nobody checks what the same batter does with the same shot outside T20. Conflating formats is the most common offence in this analysis, and the social feed rewards it daily.

So my method carries two thumb-rules.

First: the two-source threshold. I will write a transfer rumour, a selection rumour, or a "dressing-room unrest" story only when two independent sources exist. One source is not news; it is a possibility — and possibilities can be discussed, not asserted.

Second: sample-size scepticism. I will not call a tactical trend a trend after one tournament unless I have comparative data from at least ten previous matches and I state the counter-evidence plainly. It slows the deadline copy. It makes the long-form reliable.

There is a professional cost here, and it should be admitted. Restrained writers are read less. Columnists who hand out instant verdicts go viral more often. But the value of a ledger is that old entries cannot be quietly rewritten. If you recorded in 2026 that a boy's sleep had dropped below six hours, and in 2026 he tears a hamstring, you become a witness against yourself — and that is the only way an opinion ever learns anything.

I read the medical before I read the highlight reel. The highlight tells you what happened. The medical tells you what is about to.

Takeaway: What to Watch in a Regular Season

The most important information in a regular season sits outside the table. How far a side's PPDA has dropped across three matches, which bowler is carrying the same spell load for a fourth straight fixture, which young batter has stopped playing the pull for six innings — none of it becomes a headline, and all of it makes the next headline.

Since July I have kept a plain notebook. Three columns only: session count, travel miles, sleep hours. No story has come out of it yet. It will. And when it does, I want the evidence in hand rather than a guess.

You cannot write from an empty dataset. But you can be honest about an empty dataset — and in the long run, that honesty is the only asset you have.