Three Numbers Beyond the Scorecard: The Real Work of Cricket Data Verification

On the morning of 11 August, nine o'clock sharp, the tea had gone cold in the small analysts' room beside the county ground's indoor school. On the table lay the Stage-1 packet: twenty pages, three lines circled in red ink on the first. All three were numbers. All three were written in a way that invites no doubt on a first read, and that is precisely the problem. One: a fielder covered 11.4 kilometres in a 50-over match. Two: a young quick bowled forty overs in a week. Three: the pre-season fielding circuit ran six sessions. All three look clean. All three are incomplete, and two are simply wrong. The work began where the scorecard stops.

Modern cricket coverage supplies numbers faster than it verifies them. GPS vests, catapults, sprint trackers: after every match comes a flood, and the flood gets packaged as 'effort'. Twenty years beside the boundary rope have taught me that covering ground and working hard are not the same thing. A fielder at deep cover who walks through an afternoon banks eleven kilometres. A man at slip who stands there for forty overs does not register three, and yet the two dives that decide the game happen at slip.

My apprenticeship was in football, at Cobham, in August 2026. After the 3-2 opening-day defeat to Burnley, Antonio Conte went back to a three-at-the-back shape, and I spent fourteen consecutive sessions logging Álvaro Morata's No. 9 movement and talking defensive shape with two youth coaches. The 3,200 words I filed were about how Morata's running freed space for Eden Hazard, not about his eleven Premier League goals. At Cobham, the shape was less a tactic than a daily habit, and logging that habit taught me that drills and match data do not speak the same language. Ruben Loftus-Cheek's 22 minutes. One career. Watch the runs: that lesson started there.

In cricket the gap is wider. A bowler's work cannot be measured in distance; it is measured in overs, spell length, and how much pace falls away in the day's last spell. A keeper's work lives in the squat. A fielder's work lives in the first five metres. A transfer fee is only the first beat; the rest is how a squad learns to breathe. A data packet is the same: a first beat, nothing more, until it is verified.

Take the first circled line. 11.4 kilometres in 50 overs may well be true, because it is true. What the packet omits is how many high-intensity sprints sit inside those eleven kilometres. The ground log showed four efforts over 25 metres and the rest jogging and repositioning. The same eleven kilometres, for a different fielder, might break into forty-eight sprints. Distance is the packaging; intensity is the contents, and you cannot identify a medicine by its box. Scorecards cannot hold that difference, because a scorecard counts destinations, not velocities.

The second number. A club thread claimed the young quick had bowled forty overs in a week. The thread's language was emotional; the number was accurate. Cross-checking the scorecards gave twenty-six competitive overs and fourteen in the nets. Net overs and match overs are not the same currency: in the nets a bowler searches for rhythm, in a match he tries to beat a batsman. The difference between twenty-six and forty is not fourteen overs; it is who is carrying how much risk. This error is most common in diaspora club chatter, where affection is close at hand and the scorecard is not.

The third number looked harmless and was the slyest. Six sessions on the fielding circuit, except the session log listed morning and afternoon separately while the same coach ran both groups on the same drill plan. One piece of work, counted twice. Two independent confirmations: that threshold earns its keep here. The scorecard is one source, the coach's drill log is the second, and when they disagree the number gets dropped, not softened.

The method is not complicated, only laborious. Set a source threshold for every piece: two independent confirmations. One claim from a forum, one line from a scorecard, one moment of direct ground access. Anything outside those three does not get written, or gets written with the doubt attached.

The outside reading runs the other way. Readers assume the number is the story; analysts assume the number is the proof. Neither assumes that the number is often the explanation that arrives after a decision has already been made. On 14 July 2026 at Lord's the World Cup final tied, and the result was settled on boundary count, 26 to 17. Nobody came down from that evening arguing about the rule. A metric can produce a result; it cannot explain the game.

Another misreading: reading fitness off a session count. Six sessions are not six sessions, because drill type, rest intervals and ground temperature are absent from the figure. The coach who kept two fielders back for ten extra minutes of diving after the circuit put work into a place no packet records, and that is where matches are decided.

The third misreading is the most dangerous for a reporter: rotation equals workload management. Often rotation is a selection committee avoiding reputational risk, resting a tired quick by dropping him so that a comeback story can be written later. The scorecard shows both identically, which is why the distinction is my job to write.

Over the next three weeks I will watch something other than the distance figure: how far sprint counts drop in the day's final session, and whether a fielder still attacks the first five metres once they have dropped. The packet will come again. The red ink will come again. The question stays: are we writing the team's story, or only the packaging?