The Silent Ledger: The Discipline of Missing Data in Cricket Analysis

Hook

The first thing I do when I open a match file is the same every time — count the numbers. Runs over by over, the line and length inside the powerplay, the phase-splitting of an innings, the drift of fielding positions, the placement of yorkers in the death overs. But that day the ledger held nothing. Empty cells, empty columns, and one quiet question — the match was played, so where is the accounting?

Since 2026 I have been used to sitting beside the pitch and counting recoveries. After joining Bengaluru FC as a performance analyst, I learned that every claim must sit on a tracked number. In the 2026-18 ISL semifinal against FC Goa I logged 47 recoveries in the middle third — not to tell a story, but to prove a claim. That night I understood something: without numbers, there is no difference between analysis and rumour. So when the ledger is empty, my body registers it — something here has gone wrong.

The hard moment, honestly, is never the controversial DRS call. The hard moment is the one where there is nothing to count. The numbers did not shout; they waited until the tape confessed.

Context

Modern cricket analysis is a supply chain. From the ground, cameras, scorers, sensors and tracking systems lift raw information; it then reaches the analyst in refined form. I call this the data chain of custody. Just as a ledger remembers the origin of every entry, every tactical claim should have an origin you can trace. A claim without an origin is a forged entry in the ledger — it may survive a week, but it will never survive a tournament cycle.

When nothing arrives from the layer above, the analyst faces two paths. One: fill the gap with guesswork — easy, popular, dangerous. Two: admit honestly that there is no information, and therefore no assessment. The second path is hard, cold, and precisely for that reason professional. Because the reader's memory is long. The analyst who delivers a confident wrong verdict today will find that verdict attached to their name tomorrow.

I cover cricket for the Indian market, but my core training is in performance science. That double world taught me one thing — separate the format and the metric separates too. A Test batting average, an ODI strike rate and a T20 economy can never be placed on one straight line. In Tests the ball ages, the seam moves, the batter endures; in T20 the ball is new, fielders are inside the ring, and every dot ball builds pressure. Dragging one format's data into another format's decision is a false entry in the ledger.

So when a report arrives with no format tag, empty information points, and no named team or player, the honest output is never a verdict — it is a diagnosis.

Core

1. An empty ledger is itself a finding.

We are addicted to verdicts. After every match the social feed fills with rulings — who won, who lost, whose tactics failed. But there is a truth we rarely state: missing information is also information. When the first stage of an analysis pipeline returns completely empty, that is a signal — somewhere in the system there is a leak: at the raw-capture layer, the refinement layer, or the handover layer.

I call this systemic silence. And here cricket reminds me of my own training — what you cannot see is still part of the match. In football the camera often misses the run a striker made before receiving the ball. In cricket the camera misses the fielding shift that happened before the catch. Missing information does not mean the event did not occur; it means we failed to capture it. That distinction is small, but it is the analyst's moral foundation. Under tournament pressure it erases fastest — flags and stories fill the air, everyone wants an answer immediately, and the easy path is to fill the empty cell with a guess.

2. The chain of custody — traceability.

I have one rule, learned in 2026. After Spain vs Russia at the World Cup (1-1, 3-4 on penalties) I charted Spain's 1,029 passes and Russia's 5-3-2 low block. What stood out: Spain completed only 7 passes into the penalty area. My piece, "The 1,029 Passes That Went Nowhere," was later cited by Indian coaches. But what nobody noticed — I waited 48 hours before publishing, to verify the data.

Those 48 hours are the greatest asset of my career. A number without an origin is not a number — it is a rumour. If the ledger says "1,029 passes," I need to know who counted, on which system, in which version, and how that version treats deflections. Pass counts shift system to system — a deflected pass is counted in one place and not in another. In cricket this is even sharper: two systems can show different strike rates for the same innings simply by defining dot balls differently.

A pass map is a confession, not a compass. It tells you where the team went, never why. And "why" requires an unbroken chain of custody. The day the chain breaks, the greatest knowledge available is admitting that we do not know.

3. The courage to write "N/A."

The hardest sentence of my professional life is short: "Insufficient information; cannot assess." Writing it requires managing your own ego. Readers want a verdict; analysts want evidence. Tournament time is the peak of pressure — and saying "I do not know" right then means standing against the crowd.

But my 19 years of watching from the ground tell me the analyst who is quick to rule will one day make a large error; the analyst who rules late may be slow, but coaches believe them. I have seen coaches who, before asking me for an answer, asked, "What is your source?" Asking for the source is the real respect.

There is a subtlety here. "There is no information" and "I did not see" are different. The information may exist but never reached me — or it may truly not exist. In the first case the fault is mine; in the second, the system's. Without separating these two faults, analysis never matures.

4. Separate format, separate language.

Cricket's three main formats are really three different games played on the same ground. In Tests, time is the resource, and time means room to change tactics. Losing a session does not mean losing the match — that patience is the Test's architecture. Holding the shine, balancing pace and spin on the same pitch — these are day-by-day, session-by-session decisions.

In ODIs the middle overs rotate; a side 150 for 3 at 30 overs hopes for 150 more in the last 20, but that depends on the rate of wickets falling. It is a wicket-budget calculation, not merely run-rate. Whoever watches only run-rate cannot price the set batter.

T20 is harder still, because a single over can turn a match. Here the powerplay is not just about runs — it is about wides and dots. If a bowler concedes 8 in two powerplay overs but bowls four dot balls, the economy looks fine, yet those dots built pressure on the next batter. This is why a T20 economy can never be read alone; it must sit beside dot-ball percentage and boundary-prevention. In a tournament cycle this mistake is the most expensive, because one match's decision fixes the whole campaign.

5. Reading silence.

In 2026, in the ISL bio-bubble in Goa, I was performance analyst with Hyderabad FC. Empty stadiums. I recorded 12 matches and found the defensive line had pushed roughly 4.2 metres higher — because the coach's instructions were audible. Nobody expected an empty stadium to change tactics.

That experience gave me a new language. I now read pressing not only as a response to sight but as a response to sound. Without crowd roar, player communication is clear, and the opponent's instructions are clear too — so the pressing trigger moves a step later. Silence is not absence; it is the pressing trigger moved one step later. An empty ledger should be read the same way: an empty field does not mean we are lazy; it means some layer of our machinery has gone silent. When I cannot hear a sound, I do not say "there is no sound" — I say "my hearing has a problem." The game whispers its pattern; the analyst writes it down only after the third replay.

6. Empty input, big picture.

And here is the real tournament reading. In a tournament cycle every match, every innings, every over is part of one large data flow. When input is lost somewhere, it is not merely a damaged report — it signals weak communication between the selection system, the scouting system and the analysis system.

Comparing Bangladesh and Indian cricket cultures, I see this difference repeatedly. In Bangladesh selection often runs on immediate emotion; in India it runs on market demand and big-league arithmetic. Both share one thing — even when data exists, it often does not reach the decision. So the problem is not only the absence of data, but the absence of a chain from data to decision. An empty ledger is the small version of that broken chain.

7. The chain of verification.

The toss and dew are cricket's least-acknowledged yet most influential factors. In a night match, dew makes the ball come off the hand quicker, costs the spinner grip, and eases batting in the second innings. If the analyst has no dew data, the entire second-innings reading stands on a false foundation. DRS is similar. Whether a review succeeds is not only a skill question — it is also a question of the ball-tracking system's margin. Wicket line, impact height, stump projection — a system error in any one of them changes the verdict. An analyst who treats a review result as direct evidence of a player's judgement turns an uncertain machine into a final judge. So the chain of verification means not only matching numbers, but knowing each number's limits.

Contrarian angle

Here I want to say something uncomfortable. We assume the enemy of analysis is a lack of information. My experience says the opposite — the bigger enemy is a surplus of information. A tournament throws up thousands of data points; if someone lays them out without filtering, the reader believes analysis has happened, when what happened was a heap of information.

My 47-recovery piece succeeded not because of the number — because I knew which recoveries were real turnovers and which were merely touches. I counted the recoveries before I trusted the shape, but counting alone does not reveal tactics. After counting I had to ask: in which phase did these recoveries occur, what was the opponent attempting then, was the pitch wet? Without those three answers the recovery count is like a trophy — handsome, but no proof of function.

So before lamenting an empty ledger, ask one question — do we truly lack information, or do we lack the discipline to filter it? If the answer is the second, the fault is not the analyst's but the system's. And pointing at the system is far more uncomfortable, because pointing at the system puts a finger on your own house too.

Takeaway

Next match, when you open the scorecard, do one thing. Beside every large claim, write down where the source is, which format, and what tracked number stands behind it. If you find a gap, that is not your ignorance; that is your first real discovery. The analyst who learns to recognise the gap is the one who can later fill it — and that very gap becomes the most valuable question of the next match.