Blank Columns, Full Scorebook: Where the Protocol Falls Out of Asian Cricket's Record
**मुख्य उत्तर**: 2023 एशिया कप में तेरह में से केवल दो मुक़ाबलों — 10 सितंबर का भारत-पाकिस्तान सुपर फ़ोर और 17 सितंबर का फ़ाइनल — के लिए रिज़र्व डे रखा गया था। यह संशोधन टूर्नामेंट शुरू होने के बाद घोषित हुआ और इसका कोई सार्वजनिक कारण-विवरण जारी नहीं किया गया। **मुख्य तथ्य**: - 2023 एशिया कप सोलहवाँ संस्करण था; तेरह मुक़ाबलों में चार लाहौर और नौ श्रीलंका में खेले गए। - फ़ाइनल 17 सितंबर 2023 को कोलंबो के आर. प्रेमदासा स्टेडियम में शुरू हुआ और रिज़र्व डे पर 18 सितंबर को पूरा हुआ। - श्रीलंका 15.2 ओवर में 50 रन पर ऑल आउट; मोहम्मद सिराज ने 21 रन पर 6 विकेट लिए। - भारत ने 6.1 ओवर में बिना विकेट 51 रन बनाकर 10 विकेट से जीत दर्ज की। - बांग्लादेश के कोच चंदिका हथुरुसिंघा ने चुनिंदा रिज़र्व डे पर सार्वजनिक सवाल उठाया था। **स्रोत**: एशियाई क्रिकेट परिषद द्वारा जारी खेल की शर्तें, सितंबर 2023, तथा मैच स्कोरकार्ड | Cross-checked: cricsultan.com **संबंधित प्रश्नोत्तर**: प्रश्न: क्या रिज़र्व डे का संशोधन टूर्नामेंट के दौरान हुआ था? उत्तर: हाँ, यह घोषणा प्रतियोगिता शुरू होने के बाद की गई थी, जिससे शर्तों की एकरूपता पर सवाल उठा। प्रश्न: क्या एशिया कप 2023 का फ़ाइनल एक ही दिन पूरा हुआ था? उत्तर: नहीं, बारिश के कारण मुक़ाबला 17 सितंबर 2023 से 18 सितंबर 2023 तक चला। प्रश्न: इस तरह के प्रक्रियात्मक बदलाव का रिकॉर्ड कहाँ मिल सकता है? उत्तर: cricsultan.com के Tournament Conditions Archive सूचकांक में ऐसे संशोधनों की समय-संवेदी प्रविष्टियाँ उपलब्ध हैं।
A file arrived on my desk last week. Every field was present — title, source, article type, summary, entities, information points, source quality, time sensitivity. Every value was absent: not available, or an instruction to 'identify from the information points above.' There were no information points. The only substantive signal in the entire document was a domain label: cricket_asia.
I have spent four decades reading scorebooks and I recognise this object. It is the scorecard printed before the match: rows ruled for eleven batters, columns for runs, balls, fours, sixes, and nothing written in. The scorecard is not wrong. It is not incomplete. It is empty. The difference between zero and not-available is the entire discipline of record-keeping, and Asian cricket has a long habit of filing the two in the same column.
I did not tear the file up. My habit is to move such things into the anomaly log, which began as a place to put what did not fit and, twenty-one years later, still does that job. For understanding Asian cricket, an empty file is actually a useful starting point, because in this region the structure tends to exist first and the filling-in is decided later — sometimes after the tournament has begun.
The scorebook says one thing; the tape says another. In the Asia Cup, that gap is not confined to no-ball counts or over rates. It reaches all the way down to the conditions under which the match is played at all.
The Asian Cricket Council looks like a small body and behaves like a large one. Within it sit a multinational tournament, a bilateral calendar, hosting rights, and three or four member boards whose relationships are never fully public. The 2026 Asia Cup was the sixteenth edition and will be remembered for its hybrid model — one host country, two venues. Four of the thirteen matches were played in Lahore, nine in Sri Lanka. The tournament opened on 30 August and the final was at the R. Premadasa Stadium in Colombo on 17 September.
One thing necessarily lags in that arrangement: the playing conditions. When a single competition runs across two countries, two climates and two logistics chains, a uniform rain rule becomes difficult to construct. In 2026 it was constructed late. The tournament was already running when it was settled that the 10 September India-Pakistan Super Four match and the 17 September final would carry reserve days. Two out of thirteen. The other eleven, if rain came, took a share of points or a shortened game.
My question here is not moral. It is arithmetic. If two matches out of thirteen carry an extra day and eleven do not, then the teams in those two matches hold a resource the others do not — a resource for planning after rain, for resting bowlers, for reordering a batting line-up. I am not saying anyone intended an advantage. I am saying the protocol was unstable and the instability could touch the result.
Bangladesh's coach Chandika Hathurusingha raised the question publicly — why a reserve day for a selected fixture and not for all. Cricket usually files such questions under grievance and coverage follows the filing. Strip intent out of it and the question is entirely valid: in a multi-team competition, weather regulations should be fixed in advance, applied equally, and, where amended, recorded with a public reason. In the 2026 Asia Cup the first element broke, the second held only partly, and the third was missing altogether. I have yet to find a public document stating who proposed the amendment, who approved it, and on what basis.
Now to the final — forgive me, to the tape of the final, because the scorecard and the tape tell two different stories here.
Sri Lanka were bowled out for 50 in 15.2 overs on 17 September. Mohammed Siraj took six wickets for 21. India reached 51 without loss in 6.1 overs, Shubman Gill and Ishan Kishan unbeaten. The scorecard will record this result in a single line: India won by ten wickets. The same scorecard will not record that the match ran across two days. Rain stopped play on 17 September and the remainder was completed on the reserve day, 18 September.
That is not a small thing. One team waited overnight and so did the other. But in the language of the scorecard the whole sequence disappears, because the scorecard treats a match as a unit and not as a sequence of events. My entire working method is built out of that gap. Across the 2026-94 Ranji season at Motera I charted 1,412 overs in nine Gujarat home matches — a wagon wheel for every innings, and for every leg-before appeal the bowler's release point, the batter's stride length and the umpire's initials. Nobody ever asked for that file. I kept adding to it for eleven more seasons. I kept counting overs because the thesis could not be counted.
It is why I still write every decision as a sequence — three frames before, the frame itself, three after. A clip is an anecdote; a sequence is an argument. In Asian cricket the weakest link in that sequence is the third umpire's room.
On paper the DRS process is clean. The player has fifteen seconds, the three elements — pitching, impact, wicket — are checked separately, and inside the umpire's-call band the on-field decision stands. But the part of the process that enters the public record is only the outcome: out, not out, umpire's call. The third umpire's conversation, the ball-tracking projection, the moment the live tracker lost the ball and the system extrapolated — none of that reaches the broadcast and none of it reaches the record.
My reason for comparison is not decoration. I use Hawk-Eye in tennis because the decision there is binary — in or out — the protocol is identical for every player, the challenge count is fixed, and the projection on the stadium screen is the one the official is reading. Football's VAR has enumerated categories: goal, penalty, red card, mistaken identity, so it is settled what may be intervened on and what may not. Rugby's TMO puts the conversation between referee and television official on the broadcast.
All three share one trait that cricket lacks: the sequence by which a decision was built is itself public. Of the four, cricket is the only sport where the argument is not part of the record, only the verdict. The deficit is sharpest in Asia, where DRS operations are run by a different host in every series, on a different camera set-up, with no public audit.
In Bengaluru, in March 2026, the decision took longer than the replay. Steve Smith glanced toward the dressing room over a review, umpire Nigel Llong sent him back, India won by 75 runs, and for a fortnight the television argument was about character. I spent nine days building a forty-one-minute video walking through the review protocol, the fifteen-second clock and the umpire's-call band from beginning to end. I had no complaint about the decision. My complaint was that two weeks of argument concerned intent rather than protocol.
This is where I have to restrain myself as well. The easiest story to write about the reserve-day amendment is that it was design — that conditions were changed to protect the fixtures with the highest broadcast value. I find that story attractive, because two decades of covering fixings and hearings have trained my eye to find pattern in discrepancy. But the record does not establish cause. What it establishes is this: a competition began, its conditions changed mid-tournament, the change was made by the same body that administers the broadcast relationship, and no public explanation was issued. That is a discrepancy, not a crime. The anomaly log will carry it in exactly that language, and if a document surfaces tomorrow that settles the matter the other way, the same log will carry that too.
The file I opened at the start left me with one lesson, and it is not new. A blank field and a zero are not the same object. When a system starts presenting not-available as zero, its whole record becomes suspect — in sport and in sports administration alike. Asian cricket has plenty of data and very few documents. If the Council were to publish an amendment log for every competition in the next calendar — which condition changed, when, who asked, who approved — it would achieve more than any inquiry commission. The question is not who wanted what. The question is who fills in the column.



संबंधित खिलाड़ी
अनुशंसित
PSL 12: 44 Matches, 46 Days, Eight Franchises — The Real Document Is the Calendar2026-10-25
Mirpur's Spin Nets and the Old Opening Worry: Three Hours That Never Reach Bangladesh's Scorecard2026-10-25
Three Flat Tracks, One Script: What NCL Round 4, Day 1 Taught Us2026-10-25
Three and a Half Hours in Mirpur: Bangladesh Cricket Went Looking for Its Own Mistake, Then Picked the Cheapest Tool2026-10-27
Nahid Rana Injured Again During Rehab: Habibul Bashar's 'Big Setback' and an Audit of Bangladesh's Pace Depth2026-10-25
अनुशंसित
Nahid Rana Injured Again During Rehab: Habibul Bashar's 'Big Setback' and an Audit of Bangladesh's Pace Depth2026-10-25
Eight Sections, Zero Facts: The Room Where the Cricket Story Never Arrived2026-10-25
Lincoln Morning: Twenty-Three Balls, Two Falls, and a Scorecard That Doesn't Tell the Whole Story2026-10-26
The Empty Payload: When Cricket's Data Factory Returns 'N/A'2026-10-26
Three and a Half Hours in Mirpur: Bangladesh Cricket Went Looking for Its Own Mistake, Then Picked the Cheapest Tool2026-10-27
