Three Numbers That Would Not Reconcile: Cricket's Verification Gap

The number appeared on the big screen and, within seconds, three people on the next row offered three different versions of it. One said nineteen, another twenty-two, the third seventeen. None carried a date, none carried a venue, none said which format it belonged to. In a press box at an English ground I opened my notebook — date, venue, format written across the top of the page. For more than twenty years I have written those three things before I write anything about the cricket itself. The ground had a heartbeat before the first ball, and I wrote it down; later that page is what tells me whether the number on the screen is right or wrong. That afternoon nobody had written the number down. Three journalists, three figures, zero evidence — and every one of them certain.

10 January 2026, MA Aziz Stadium, Chittagong. A 226-run win over Zimbabwe — Bangladesh's first Test victory. The press box that day had almost no reliable live score; the scorers' books and handwritten notes were the only places to stand. By evening three outlets printed three different margins. One matched the scorers' book. The other two matched only each other. From that night came the habit: the scorecard is a claim, and the notebook is the proof. Twenty-one years later the technology has moved on enormously, but the distance between claim and proof has not closed. It has widened.

Cricket information now reaches the reader through a supply chain. First the scorer, then the board's match official, then the data provider, then the broadcast graphic, then the social clip, then the pundit, then the reader. Something drops out at every handover. Sometimes the format tag drops, sometimes the date, sometimes the sample size. Football has less room for this, because there is one league, one format, one season structure. Cricket gives the same player three separate lives — Test, ODI, T20 — each with different rules, different ball counts, different field restrictions. Lose one tag and a true fact becomes a false one.

The growth of franchise leagues over the past decade has multiplied the number of matches, but the verification layer has not grown at the same rate. A batter's career average can now be a blend of a dozen competitions — BPL, PSL, IPL, The Hundred, county cricket, internationals. Into that single figure go different balls, different grounds, different opponents, different weather. When someone says a bowler's economy has risen over his last three matches, my first question is: in which format, in which phase, on which ground?

From thirty-six years of watching from the stands and the press box I have learned one thing: cricket's numbers do not speak for themselves. They need context to open their mouths. The bowler who takes 3 for 40 on a damp Chittagong surface will not repeat that spell on a dry Mirpur turner. The two scorecards will look identical. Seeing the difference takes an eye, not a spreadsheet.

So verification is not simply asking whether a number is true. It is asking five questions at once: which format, which window, how big a sample, which venue, and who compiled it. In a recent analysis packet, three claims failed those five questions. That is not a failure of any individual's honesty; it is a failure of method — and it is the least discussed risk in cricket journalism today.

First failure: format conflation. T20 death overs allow four fielders outside the circle; the last ten overs of an ODI allow five. That one fielder changes a bowler's entire method — the ratio of yorkers to slower balls, the risk of guarding the boundary, the batter's shot selection. A bowler holding a 7.2 economy in T20 death overs has to be judged on a separate calculation and a separate sample in ODI overs 41 to 50. Yet it is the blended number that gets quoted most.

Second failure: hiding the window and the sample. Since 2026 — that one phrase can prove any player in any direction. If a batter's career average is 38 and his last eleven innings average 52, the second number is not a trend, it is a coincidence. One or two large innings lift an eleven-innings average, and six failures disappear from view. Fourth-innings averages are more dangerous still: many batters have fewer than ten such innings, and that is precisely the number paraded as proof of temperament.

Third failure is the subtlest: data that crosses a rule change. From October 2026, ODIs began using two new balls, one from each end. A bowler's ODI record before and after that date is close to two separate careers. With less reverse swing available, spin in the middle overs became a different job, and so did the state of the ball at the death. When someone sets a 2026 average beside a 2026 average and draws a conclusion, he is comparing two different games without saying so.

Fourth failure: attribution. First Bangladeshi to score a century at Lord's — true, but only if you say Test cricket, May 2026, Tamim Iqbal. Remove the tag and the sentence becomes false. Likewise 2 March 2026 at Chittagong, a two-run ODI win over England on a World Cup stage. And January 2026 at Mount Maunganui, Bangladesh's first Test win on New Zealand soil, built on Ebadot Hossain's 6 for 46. Each of those events carries a date, a venue and a format together; without them, history slowly becomes rumour.

There is another missing layer nobody mentions: pitch classification. No scorecard records whether a surface turned, seamed or sat flat. So a phrase like his average in Asia lumps Mirpur's turner together with Kandy's belter. For a spinner or a seamer, the success rate on those two grounds is not close. No number fills that gap, because the number was built without being able to see the gap.

So what is the fix? My notebook has four boxes. One, the primary scorecard — not the newspaper report, the match official's sheet. Two, the format and the innings number. Three, the sample size and the time window. Four, who compiled the figure and when. If those four boxes are empty, I do not write the number and I do not say it on air. Readers will never notice which number was dropped, but year after year the analysis keeps its weight — and that weight is the real asset.

Here is the uncomfortable part. A number that passes the verification gate can still be entirely meaningless. Take a batter's strike rate against spin. The figure is certainly accurate. But if most of those innings came at home, what does it tell us about a turning pitch in the subcontinent? Nothing. Accuracy and relevance are two separate tests — the first needs a scorer, the second needs an eye.

Let me offer a case where the number and the eye worked together. The ODI middle overs, 11 to 40, are the least discussed passage in the game. Run rates dip, yet wickets fall least often there. The side that squeezes those thirty overs with spin keeps two wickets in hand for the last ten — and those two wickets are worth roughly twenty extra runs at the death. Statistics show this as middle-overs economy; on the ground it shows as fielders two steps closer, as a batter's patience being tested, as catching positions being moved. Numbers show outcomes. They do not show process.

And the largest gap sits where no database exists. Standing in a team's physio room, I have seen the same thing again and again: injuries are not caused only by a bad ball or a bad fall. They are caused by the schedule. Two matches in a week, a flight from one country to another, six hours at an airport, arrival at the hotel at three in the morning, training the next morning. No medical team beats that schedule — they simply see the damage a little later. Yet none of it, not the hours of sleep nor the miles flown, appears on a scorecard. Analysis stops where reality begins.

Now consider the reverse. We assume more data means more certainty. In cricket it is often the opposite. Writing an average as 47.32 creates an impression of precision that hides the six innings behind it. The decimal places multiply, confidence multiplies, knowledge does not. When an analyst quotes an x-factor of 1.8, I suspect we are measuring something whose unit we have not yet agreed on. False precision is more damaging than error, because error gets caught and precision does not.

The second discomfort: the verification gate is itself an instrument of power. Whoever owns the calculation decides which numbers are worth verifying. So what flows is often not wrong information but correct, one-sided information. Coutinho left in a blur, Van Dijk arrived like a metronome — that line works in the football market because the replacement can be measured directly. In cricket it cannot. An opener leaves and another opener arrives, but the team's tempo shifts for entirely different reasons: the pitch, the weather, the opposition spinner, the light. An analysis that sees only the individual never hears the team's rhythm.

One more thing belongs in the record, because it is also data. The pulse of a ground never enters a database, yet it enters results. When the Chittagong stands rise, an opposing young seamer's hand shakes — no app records that. When South Asian crowds in London, Leicester and Birmingham carry the memory of their own cities onto the grass, the tempo of the match changes. The analyst who reads only the scorecard misses that tempo; the analyst who reads only the tempo gets the number wrong. You need both.

Looking ahead, one thing is clear. The franchise calendar will get denser, the matches will multiply, the information chain will get longer. In that world, the team or the newsroom that keeps a small verification desk — one person, one notebook, four boxes — will have decisions that hold. The rest will publish faster and get it wrong. The question is no longer who has more data. The question is: the next time a record flashes on the screen, who in the room can open the scorer's book?