friendflickrelvlt Browse the notes

Section 05

The scorecard is a summary, and summaries leave things out

Cricket keeps a more detailed public record than almost any other sport, and that abundance creates its own problem. A scorecard tells you what happened without telling you why, and the standard statistics were designed for a game that had one format. Reading both well is mostly a matter of knowing what each number is blind to.

Illustration of a hand-ruled cricket scorebook open beside a pencil, showing columns for runs, overs and wickets with a wagon-wheel diagram in the margin
The scorer's book is the source document. Every statistic anyone argues about is a compression of these columns.

Start with the dismissal notation

Each batter's line records how the innings ended, in a shorthand that is stable across the world:

  • b — bowled: the ball hit the stumps.
  • c … b … — caught, naming the fielder then the bowler.
  • lbw b … — leg before wicket.
  • st … b … — stumped by the wicketkeeper.
  • run out — often naming the fielders involved.
  • not out — the batter was still in when the innings closed.

Extras, and why they matter more than they look

Runs credited to the team rather than to a batter appear as extras: wides, no-balls, byes and leg byes. In a close limited-overs finish these are often decisive, and they are the one part of the scorecard that reflects bowling discipline directly rather than through the filter of how well the batters played. A long extras line in a tight defeat is usually a more honest explanation than anything in the batting column.

Bowling figures

A bowler's line is conventionally read as overs, maidens, runs, wickets. A maiden over is one in which no runs are scored off the bat. The order is fixed, so a figure with four entries can be read at a glance once you know the sequence. What the line does not show is who the bowler dismissed or when — a spell that removed the two most dangerous batters early is compressed into the same shape as one that collected wickets from a settled position at the end.

Average, strike rate, economy

Three rates do most of the analytical work, and each answers a different question.

  • Batting average — runs divided by completed innings. It measures how much a batter tends to score before being dismissed. It is blind to how quickly, and it treats not-out innings in a way that reasonable people disagree about.
  • Batting strike rate — runs relative to balls faced. It measures speed, and it is the number that changes most in importance between formats: near-decisive in the shortest, secondary in a Test.
  • Bowling average — runs conceded per wicket taken. It captures cost of a wicket.
  • Bowling strike rate — balls bowled per wicket. It captures how quickly a bowler breaks partnerships, which is the more relevant question in Test cricket.
  • Economy rate — runs conceded relative to overs bowled. Central in limited-overs cricket, close to irrelevant as a standalone judgement in a Test.

The general rule is that averages travel badly between formats and between eras, because the surrounding conditions differ. Comparing two figures without knowing where and when they were compiled is the most common mistake in cricket argument, and it is committed as often by people quoting numbers as by people ignoring them.

Interrupted matches and adjusted targets

Weather is part of cricket, and limited-overs matches shortened by rain need a fair revised target. The method in general use, developed by Frank Duckworth and Tony Lewis and later revised by Steven Stern, adjusts the target according to the overs and wickets remaining rather than by simple proportion. The reasoning is that a batting side's remaining resources depend on both — a side with all its wickets intact can score faster over a short remainder than a side that has lost most of them.

The consequence for a viewer is that a revised target can look arithmetically odd while being internally consistent. The method's critics note that it can produce awkward outcomes in matches heavily truncated at unusual points, and that a batting side's strategy may become known only after the interruption. There is no method free of that problem, which is why the debate is about which distortions are acceptable rather than whether distortion can be removed.

Following play across time zones

Because international cricket follows the weather rather than a season, a large share of the fixtures a UK-based follower cares about start outside UK waking hours. A few habits make that manageable.

  1. Note the local start time and convert once, rather than repeatedly during a day. Session breaks — lunch, tea and drinks in Test cricket — give natural points to check in.
  2. Use ball-by-ball text coverage where video is unavailable; it preserves the sequence of a spell in a way a highlights package cannot.
  3. For a multi-day match, read the day's report before the highlights. The report gives you the passages of play that mattered, which is what the highlights, selected for incident, will not.
  4. Treat searchable statistical archives, such as the one maintained by ESPNcricinfo, as a way to test an impression rather than to form one.

Reading a match report sceptically

A good report explains a result; a weak one narrates it. The useful test is whether the piece identifies a mechanism — a surface that changed, a bowling plan that a batting order was not built to absorb, a phase of overs where the run rate was allowed to drift — or whether it reaches straight for character and momentum. Character explanations are unfalsifiable and therefore comfortable, which is exactly why they are so common. Where an account cannot be checked, it is worth holding it loosely.

Back to the beginning of the argument: Formats, or the structures that surround it in Competitions.