The Chain of Verification: Empty Data, Template Traps and Naming the Mechanism in Cricket Analysis

Last month, moments before the studio lights went down after a T20 match, the commentator said, “This collapse is simply inexplicable.” I was looking at my notebook — stopwatch beside it, over-by-over run flow written down, and a spreadsheet open on the laptop. One column of that spreadsheet was completely blank. To me, the real story that day was not the collapse — it was the empty column.

An empty column does not mean a lack of information; an empty column means responsibility. An analyst who fills the empty column with his own imagination is not analysing — he is telling a story. And the more cricket values stories, the less courage it has to name the mechanism. That is today's subject — an empty column, a template, and a chain that binds every claim of information to verification.

After joining a Delhi digital platform as a senior tactical analyst in 2026, I built a habit — arranging every match piece in three fixed sections: defensive shape, transition geometry, and coaching adjustments. That year I wrote a 2,800-word piece on Real Madrid's 4-1 win over Juventus, centred on Casemiro's screening role and Juventus's second-half spatial collapse against Zidane's 4-3-1-2. Hand-drawn passing lanes filled the pages. It became the platform's most-read piece that month, and the editor asked for the same format across the next ten matches. For me that was a relief — because I want to write process, not guesswork.

In 2026, covering the Russia World Cup remotely, I wrote a data-backed preview arguing France's 4-2 win would hinge on set-piece deliveries and Mbappé's transition runs, not possession. France scored from a set piece and a counter; I set Croatia's 61 per cent possession beside their mere three shots on target. The piece was shared 12,000 times. It taught me to add xG and set-piece conversion rates to previews — four extra hours of preparation per match, but fewer errors.

In 2026, when the Bundesliga restarted after the COVID break, I refused to speculate. Starting with Borussia Dortmund's 4-0 win over Schalke, I reviewed all ten matches — logging pressing intensity, defensive line height, and verbal communication incidents. Without crowds, home teams' pressing intensity dropped 12 per cent. I wrote “The Silence of the Stands” for a Delhi sports magazine and added an “environmental variables” section to my template.

In 2026 I published my first memoir of a life in cricket journalism — a journey from the daily desk to reflective writing. It taught me that the rush of daily news and the patience of long-form analysis cannot be held in the same hand; each needs a separate clock.

These experiences converge in one place: before reaching a conclusion, I look for the mechanism. Not the winner, the process. From my years of watching matches, I have learned one thing — every cricket event has a specific cause behind it, and that cause often happens off-camera, in a corner of the field or in the angle of a bowler's wrist.

By 2026, the cricket information market is saturated. Every ball's speed, every shot's angle, every fielder's position — all recorded within seconds. But abundance of information combined with a lack of verification is dangerous: numbers rise, understanding falls. Someone quotes a strike rate, someone an economy rate, but nobody says which over, which pitch, which opposition. That gap is the centre of my writing.

Now to the core. I read T20 death overs like football set-pieces — but carefully. The shared mechanic, in one line: a pre-decided delivery plan and a pre-set field, where each ball is part of a pre-planned frame. The limit, in the next line: cricket has no whistle like football's corner restart, no fixed position from which to run the routine. The bowler's execution variance and the batsman's freedom mean the death-over “set-piece” is not choreography — it is probability.

Still, the part that is genuinely prepared in advance is field setting and the delivery menu. From overs 17 to 20, five fielders can be placed outside; where those five stand is decided two overs earlier, based on the opponent's strike zones and their weakness against the slower ball. The real death-over preparation is not before the ball is bowled but at the moment the field is set — that is the invisible set-piece the camera never catches. Just as France's 2026 corner routine had a designated blocker and a runner, cricket pre-fixes long-off and fine leg for the yorker. The difference is one thing: in football the ball goes to a fixed point, in cricket it goes wherever the bowler's hand sends it.

The second mechanism is the phase script. How many fielders a captain keeps inside during the powerplay, who sits just outside the circle — that is a script. But real skill shows in the bowling change, often decided two overs earlier. I write over by over in my notebook — which bowler in which over, where his field shifted in the over before. I reconstruct how a single field shift cascades across the next four overs, rather than summarising it as a result.

Suppose, in the 12th over, the fielding captain brings mid-off in and sends long-off out. A small change to the eye. But in the next over the batsman stops relying on cover and starts playing square, having changed his line. Two overs later the bowler shortens his length, it becomes a boundary, and the captain is forced to change the field again. One decision in four overs produced four decisions. This is the chain I write — and here it becomes clear that there is no such thing as an “inexplicable collapse”; there is only a chain nobody wrote down.

Environmental variables are a separate section in my template, because in this region's conditions they often decide the outcome. When dew falls, a spinner's grip drops in the death overs, and that alters a bowling change calculated two overs earlier. Square dimensions fix the value of the cut and the pull. Travel load fixes how sharp a fast bowler's four-over quota can stay. And toss history says which side has historically gained the advantage at this ground. Without these variables, any strike rate or economy rate is just an incomplete sound.

As an example, consider a template decision — not a claim about a specific match, but a point that recurs in every match. In the 15th over the captain has two open paths: bring the frontline seamer back now against the set batsman, or save him for the 18th-19th against the finisher. The second looks reasonable, but it has a price — if the middle overs leak runs, that bowler must be forced to bowl the last two overs when the batsman's eye is set. No outcome is written in advance here; both options were genuinely open, and the decision shaped the tempo of the remaining five overs. This is how to avoid hindsight determinism — by admitting the alternative was genuinely available.

I hold a standing view on football's five-substitute rule, and it casts a shadow over cricket too. Deep squads can turn the final twenty minutes into a war of attrition — but cricket has no direct substitutions. So here the analogy stops halfway. The nearest equivalent in T20 is a bowler's four-over quota: he will bowl four overs regardless, but deciding in advance which overs sharpens his edge. The friction that squad rotation creates on a long tour is like football's substitutions — but the limit is that in cricket a bowler's fatigue is measured in overs, not minutes, and that measure returns every match.

The third layer is financial, and here my second standing view comes in. Paying a huge sum for a player with fewer than fifty top-flight games is not analysis, it is gambling. When auction numbers become headlines, the analyst's job is to set phase, opposition quality, pitch age, and match state beside that number. A strike rate alone says nothing — without which over, which pitch, which bowler, the number is merely a sound. A young player who is best against spin in a domestic league sees his price rise; but how far he endures on a fast away pitch is a separate column, and it usually stays empty.

And the fourth layer, the one most important to me: the empty column. When no information is available, the analyst has two paths — leave the column empty, or fill it with imagination. I choose the first. I follow a chain of verification: every claim is like a block, with a verifiable source behind it. If a block is missing, the chain breaks, and you cannot advance on a broken chain. This is where it meets blockchain — an immutable, traceable chain of information. Cricket analysis needs exactly such a chain: who said it, when they said it, from which number — without answers to these three questions, no claim joins the chain.

Why this chain matters so much becomes clear when you look at formats. Test, ODI and T20 — their tactical logic differs, so their metrics are not directly comparable either. Test is about patience and attrition, ODI about middle-over rotation, T20 about risk and reward. Dropping one format's strike rate into another is placing a block of the chain in the wrong slot.

One more thing I deliberately avoid: vibes-first verdicts. “Brave captain” or “inexplicable collapse” — these words are not analysis, they are feeling. If there is bravery, it must be shown in which decision, which over, at the cost of which alternative. If there is a collapse, it must be shown from which over it began, after which field shift. The softer the words, the weaker the analysis.

Now the section that goes against my own template. I built a three-part template, then watched the match break it beautifully. The problem is never a lack of information; the problem is the confidence that covers the lack. While an analyst is busy filling the template's three boxes, the match may be saying something else — something that does not fit those three boxes. In that moment the honest act is to break the template, and to draft the “template broke” section first.

The second trap is overreach of the cross-sport analogy. The France 2026 set-piece frame does not always fit T20 death overs. When the limit of the analogy grows larger than its mechanic, the analogy should be dropped. The tape does not lie; it just waits for the right question. For the death over, the right question is — was the field set before the ball was bowled? And if not, then it is not a football corner, it is just a delivery.

The third trap, one my ISTJ instinct keeps creating: the verification spiral. Re-checking information again and again burns the clock, and the live insight goes stale. The fix — time-box verification, and publish the process with a clear “confirming” flag rather than holding the piece.

And one word about myself: I often lean toward the template, because it has worked five times, it is fast, and readers now expect it. But a cricket match does not obey a template. So my first task now is to listen to the match, then decide which structure is genuinely today's story. Readers want to reconstruct the passage of play themselves, not be told how to feel about it.

In the next match I will verify one thing: the name of the mechanism. Who set the field, when the bowling changed, in which over the delivery menu shifted. Not the name of the winner, the name of the process. A good prediction names the mechanism, not just the winner.

And the question remains: when information is absent, will you accept the empty column as truth, or fill it with your own story? The faster cricket becomes, the more urgent the answer.