From the Scorer's Book to the Coaching Box: The 214-Delivery Chart and the Cracks in Cricket Analysis

I counted 214 deliveries before the chart started counting me. It was 2026, and I was sitting in a small coaching room at Emirates Old Trafford in Manchester, a £40 camera and a spreadsheet in front of me. Six weeks of recording Lancashire's seam attack — 214 deliveries, each one's release point, crease position, length band. I found something no broadcast graphic had shown me: right-arm bowlers were standing on average 0.4 metres wider to left-handers. It was a 'tell', a habit that had cost 31 runs in the powerplay. I published those pitch maps on a new digital cricket desk. Three weeks later Lancashire's head coach offered me a formal assistant-analyst post — and the same week, a steward at a visiting ground redirected me to the family gate instead of the dressing-room corridor. That gate incident became my working rule: arrive with the data first, make the argument second.

This article starts from that rule, but on a different problem — one I have encountered repeatedly over the past few months. There is a major flaw in the world of cricket analysis, and it is not on the pitch, not in the boardroom, but in the place from which we see everything: the primary source of the data. When I recently received a 'deep analysis' report in which the title, source, type, core viewpoints, information points — everything — was 'N/A', I was not surprised. I was familiar. This is not an isolated incident. It is a systemic failure, and it marks the moment when cricket analysis begins to lose to its own tools.

Context: The scorer's book never lies — but the one reading it certainly can.

My career stands on 31 years of observation. When I came to England from India in the 1990s, I had playing experience — playing for Lancashire, a career ended by a shoulder injury at 31. But what started after that began with the scorer's book. I learned manual scoring, every ball's entry, every wide, every no-ball, every bye. I remember during my Rhodes Scholarship (2026–2026) I began a DPhil on the social history of Indian cricket — 'A Social History of Indian Cricket' — and completed it in March 2026. That research taught me that the real history of cricket is not in the scorebook but in those small entries no one reads. A run-out wrongly recorded as 'not out', an over mistakenly recorded as five balls instead of six — these 'trivial' errors can change the entire text of a match.

When I went to Russia in 2026, I was sent not as a football reporter but as a 'space writer' — 31 matches in 33 days, from the press tribune, a spreadsheet of 64 set-piece routines. I wrote a piece arguing that Iceland's 4-4-2 block and a T20 powerplay ring field obey the same geometry: deny the channel, force the low-percentage option, punish the second ball. That zonal-marking explainer reached 400,000 readers and was shared by two Premier League analysts. I returned and rewrote my cricket vocabulary in a week — 'the second line', 'the pressing trigger', 'the closed half of the ground'. This cross-sport grammar became a weapon for me, and it is what helps me recognise the flaws in that report filled with 'N/A'.

Core: The 2026 bubble and a new way of hearing sound, then the 2026 auction and the arithmetic of role scarcity.

When the pandemic hit in 2026, Emirates Old Trafford was one of England's two bio-secure venues. I spent eleven weeks inside the bubble on the support staff — England v West Indies, England v Pakistan, behind closed doors. There was no crowd, so the stump mics picked up everything: 12 matches of fielders calling, bat edges, bowler frustration. I logged 1,900 audible calls and found that mid-pitch communication errors fell by roughly a third in silence — and by the third match, fielding sides had begun switching to coded calls. That experience taught me that sound is a tactical variable, and broadcast audio is a primary source. Since I started transcribing stump mics before writing a word about a batting collapse, my copy has cooled: with no crowd to blame, there was only ever a decision to describe.

In 2026 I took a remote analytics contract with an IPL franchise — for the UAE leg. That winter I sat in on the mega auction in Bengaluru: 600 shortlisted players, a ₹90 crore purse, ten teams rebuilding from zero. I built a role-scarcity model instead of a best-player list; my franchise walked past the two biggest overseas names and bought three bowlers for ₹11.4 crore combined. That experience changed the shape of my auction coverage — I stopped ranking players and started pricing roles, publishing scarcity tables before every mini-auction.

This is why when I look at that hollow 'deep analysis' report, I see not only a technical failure but a professional negligence. A report that says 'N/A' to title, source, type — everything — is essentially admitting it did not do its job. But the real problem is that such reports often get published, because no one challenges them.

Contrarian angle: The real meaning of 'N/A' is not 'no information' but 'no accountability'.

In the 214-delivery chart I built in 2026, the most striking thing was this: when I shared it with Lancashire's coaching staff, no one asked 'How did you make this?' The first question was, 'Is this data reliable?' And I said, 'I watched every ball myself, I checked every frame myself.' That is my standard. But when a system produces 'N/A', it is rejecting that standard entirely. It is saying: 'We don't know, and we don't care.'

This is a problem that weakens the entire edifice of cricket analysis. When you analyse a match, you must know whether it is a Test, an ODI or a T20 — because powerplay structure, the use of two new balls, spin control in the middle overs, and session-by-session attrition are different frameworks that cannot be applied to one another. Without knowing the format, any tactical claim is invalid. And if you do not have venue and toss information, you cannot even perform a 'result vs. process' verification.

In my experience, the best analysts are those capable of saying 'I don't know'. When I was in the 2026 bubble, I logged 1,900 calls, but I also recorded how many times I could not understand who was saying what. I marked them as 'unclear', I did not guess. That is the difference between a scorer and a speculator.

Takeaway: The next time you read a 'deep analysis', first ask where its scorebook is.

The future of cricket analysis lies not in the volume of data but in its quality and verification. When I prepare for the next match, I always ask myself one question: 'Can I re-run this claim on video?' If the answer is no, I do not write it. That 'N/A' report taught me another question: 'Can I prove this information existed?' If not, I should reject that analysis entirely.

The next time you read any cricket analysis — whether from a major outlet or a small blog — ask: What is its source? Where did its data come from? Did the author count something themselves, or are they just repeating what others have said? Because if the answer is 'N/A', then you know what you are wasting your time on.

— From the scorer.