Ten Overs of Law, Eleven of Complaint: In Muscat, the Scorer’s Pencil Stood Alone as Witness

An over in a scorebook is six small boxes — ball, run, wicket, and underneath them a number that assigns responsibility to a name. The entire dispute from the Bangladesh Under-19 versus Afghanistan Under-19 one-day series in Muscat rests on one of those boxes: the eleventh over. In 50-over cricket no bowler may deliver more than ten overs. This is a hard playing condition, not advice. Bangladesh’s board alleges that Afghanistan captain Sohail Khan bowled an eleventh. The official scorer’s book has him stopped at ten. The scorecard says ten; the story keeps running at eleven.

What is actually documented is this. The series finished 2-2, which means all four matches carried consequence. Bangladesh lost the third ODI — the match in which the over-count dispute arose. The grievance travelled from the ground to the board: two rounds of discussion with match referee Yasir Latifzai, then a formal letter from the Bangladesh Cricket Board to the Afghanistan Cricket Board, accompanied by a warning that Afghanistan should be ‘more careful’. After the fourth match the two coaching staffs argued over LBW and caught-behind decisions, an exchange that ended in a handshake and a conversation. None of these facts on its own proves a rule was broken. Together they describe a contest in which the question is not only about umpiring but about record-keeping.

The root of the whole affair is the moment the bowling cap passes from one hand to another and the scorer fails to catch the change. According to the report’s own detail, the official scorer credited one over to a teammate who was not bowling in that match at all. The dispute therefore splits into two different claims: Bangladesh says Sohail Khan delivered the ball; the official record says the over was attributed to the wrong name. These are not the same claim, and merging them would be the easiest mistake in the file.

Three records were running in parallel. Bangladesh’s analyst had counted ten overs already bowled. A team member opened the Cricinfo scorecard on a phone and the count was reconciled from there. And the official scorer’s terminal — the legal document of the match — stayed at ten because one over sat against the wrong name. Three separate records, none of them looking at the others. That is the quietest revelation here: the complaining team had no access to the official scorer’s feed. When a side must verify its own bowling count against a public website, the problem is not the umpire’s intent but the match-day administrative window.

The controversy is format-anchored. T20 caps a bowler at four overs, Test cricket caps nothing; the ten-over line exists only in the fifty-over game, at twenty per cent of the innings. Dragging this into T20 or Test arguments would be meaningless — the rule allegedly breached lives in one format alone. And because the series ended 2-2, the contested match was no dead rubber; the side that lost it is the side complaining, which pushes the matter toward competitive fairness. One caution belongs here: even if an eleventh over was genuinely bowled, it does not follow that the extra over changed the result. Probability and proof are different animals.

Sohail Khan’s role thickens the knot. He is captain and, in the report, the main bowler — a concentration of duty in which an over-count slip is easiest to miss. When a captain plans his own spell, moves his own field and also keeps his own tally, an error at eighteen or nineteen is human, not conspiratorial. And here the record goes blank: the available material contains not one performance figure for Sohail Khan — no wickets, no economy, no split of the spell. Any judgment of his bowling would be speculation. The only data in play is the over count itself, swinging between three records.

The neutral venue matters because neither side carried home pressure; both boards sit in the developing tier of the game. In such fixtures the third umpire’s chair, the replay facility and the double-check on over counts are often weaker than at senior international level. In my experience the frailest link at development level is rarely the player and usually the administrative table. In 2026, when the stands in Abu Dhabi were empty, the loudest thing in the ground was the dugout; I suspect that afternoon in Muscat the loudest thing was a scorer’s pencil, and no second witness stood beside it.

My other ledger opens here, the one I carried from Colombo. Twenty-one years of reading scorecards have taught me that in school and club cricket the old book is the last court of appeal — rubbered-out figures, a pencil note in the margin reading ‘over changed’, a signature at the bottom. No video sits behind that book. When the book is wrong, no second version of the truth exists. Sri Lanka has also taught us what happens when an institution is placed before a team: records stay correct on paper and hollow on the ground. I write that as a warning to Indian readers who assume money and coverage will shield a system from error. They do not. Muscat is the same lesson in a smaller currency.

From the Indian side another layer shows. The platform that kept this story alive is the same website whose scorecard a Bangladesh player opened on his phone — the medium that helped create the dispute then broadcast it. The market decides which controversies are remembered, and this one cleared a filter that dozens of comparable scoring errors at the same level never clear. The coaching-staff argument over LBW and caught-behind, which ended in a handshake, proves that de-escalation channels were open, and that the tension was real.

Now the part where collective memory misleads. Two years from now the series will survive as one sentence: Afghanistan’s captain bowled eleven overs. Yet the report’s own detail suggests the event was an over credited to the wrong account — a less inflammatory, less shareable, truer story. The real blind spot is not umpiring but recording; and the larger blind spot is assuming a one-sided allegation becomes an established fact. The report carries no Afghanistan board statement and no officials’ account. Where one side is silent, there is not a court, only a testimony.

That caution should not become an amnesty. An administrative slip does not make a breached rule acceptable. The ten-over cap is structural: it decides how much influence one bowler can have on a whole match. If an eleventh over was bowled and nobody stopped it, the failure sits in three places — the bowler’s own count, the umpire’s oversight, the scorer’s terminal. Silence in two of the three lifts this above an administrative slip into a systemic one.

Cricket also does not amend results retrospectively. Even a successful formal protest — rare — leaves the third ODI’s scoreboard where it stands. The letter’s real target is therefore probably not that match but the appointment list for the next series. Some columns are unwanted because they arrive earlier than anyone asked for them; this is one.

What to watch is specific. The match referee’s formal finding: does it name an eleventh over, or close the file as a scoring error? The Afghanistan Cricket Board’s reply: denial, concession or silence, each with its own political weight. And above all, the appointments for the next Under-19 series at a neutral venue — repeat the scorer and third-umpire arrangement and the error repeats. My position is stated: this is not a verdict on Afghan cricket’s honesty, it is a verdict on how carelessly development cricket keeps its records. The cure is not a press release. It is a second witness.

I was not at that ground in Muscat. I have only what any reader could hold: a scorecard, a letter, and a count written three ways in three places. On the afternoon Sohail Khan’s tenth over ended, somebody’s pencil lifted and somebody’s name settled into the wrong box. The book is still open. The question is not whether it says eleven or ten — it is how long the pages will stand without a second witness behind them.