Shanto’s Failed Review, Sadman’s Fifty and 110/3: Three Questions on Bangladesh’s Scoreboard, and the Clause That Answers Them
**मुख्य उत्तर:** बांग्लादेश ने लंच के बाद पांचवें ओवर में 110/3 पर तीसरा विकेट खोया, जब नजमुल हुसैन शांतो जोमेल वॉरिकन की गेंद पर एलबीडब्ल्यू आउट हुए और उनका रिव्यू असफल रहा। सादमान इस्लाम ने टेस्ट करियर का 10वां अर्धशतक पूरा किया। **मुख्य तथ्य:** - स्कोर: 110/3, लंच के बाद पांचवां ओवर। - शांतो एलबीडब्ल्यू आउट, वॉरिकन की गेंद, रिव्यू से मदद नहीं। - सादमान इस्लाम का 10वां टेस्ट अर्धशतक। - रिपोर्ट में मैदान, श्रृंखला, दिन और रिव्यू का कारण नहीं दिया गया। **स्रोत:** मैच लाइव स्कोर फ़ीड; प्रकाशन तिथि उपलब्ध नहीं। **संबंधित प्रश्न-उत्तर:** प्रश्न: शांतो का रिव्यू क्यों असफल रहा? उत्तर: उपलब्ध रिकॉर्ड में रिव्यू के कारण का उल्लेख नहीं है; केवल इतना दर्ज है कि रिव्यू से मदद नहीं मिली। प्रश्न: सादमान इस्लाम का यह कौन सा टेस्ट अर्धशतक था? उत्तर: यह उनका 10वां टेस्ट अर्धशतक था। प्रश्न: बांग्लादेश का स्कोर क्या था? उत्तर: बांग्लादेश का स्कोर 110/3 था, लंच के बाद पांचवें ओवर में।
The scoreboard read 110 for 3. It was the fifth over after lunch. Najmul Hossain Shanto was out LBW to Jomel Warrican, and the review did not save him. Sadman Islam had completed his tenth Test half-century in the same innings. One lead carried three things: a milestone, a captain’s wicket, and a spent review. The headline gave the loudest voice to the third: ‘Shanto could not survive even with review.’
I have watched matches for years with a scorebook open, logging each ball before I trust the memory of it. My habit is to read what is written first, then what has been left out. This report says: Sadman’s fifty, Shanto’s ‘shaky’ batting, LBW off Warrican, the review did not help, 110 for 3, fifth over after lunch. What is missing is longer: venue, series, day, innings, Sadman’s score, Shanto’s score, the reason the review failed, Warrican’s over, the pitch, the toss, the team sheet. In journalism that gap matters. A scorebook is a document; a headline is an opinion.
I keep the originals. Memory argues; paper testifies. The paper evidence here begins with three figures: 110 for 3, a tenth fifty, the fifth over after lunch. None of them, by itself, proves a collapse or a recovery. They need a fourth figure — the over, the pitch, the bowler. That fourth figure is absent. So the first task is to decide which question we are answering: was Shanto out, or was the review right? They are not the same question.
The clause before the story
Nobody reads the playing conditions until the rain starts. Then everyone does. The same is true of the review protocol. No captain opens Appendix 2 until an LBW appeal arrives, and by then the third umpire is already on screen and the captain has three seconds. The rule exists in advance; the decision is made at the last moment.
Law 36 of the Laws of Cricket sets the basic LBW conditions. The ball must not be a no-ball; it must hit the pad and would have hit the stumps; it must not pitch outside leg stump, and the impact must not be outside leg. Whether the batsman played a shot changes some conditions, but the core question remains: would the ball have hit the wicket? The on-field umpire judges that. The third umpire checks it with ball-tracking.
The review is not a re-appointment of the umpire. The ICC Test playing conditions, Appendix 2, set out the player review protocol: the on-field decision stands unless the third umpire has clear evidence to overturn it. In legal language, the appellant does not have to prove innocence; the question is whether the original decision was clearly wrong. That is the detail the phrase ‘even with review’ erases.
A review is not a shield. It is a challenge. A challenge works only when the evidence is clear. If ball-tracking shows Umpire’s Call, there is no reason to change the on-field decision. Calling that a lost review is fair. Calling it a batsman’s failure is premature. A review has three outcomes — out, not out, or Umpire’s Call — and the third is not a verdict on the player but on the margin.
The economics of a review at 110 for 3
A Test team gets two reviews per innings. A successful review is retained; a failed one is burned. It is a shared resource, the team’s, not the captain’s. At 110 for 3 the third wicket has fallen. It is the captain’s wicket. And the captain reviewed his own dismissal. There is a structural conflict here that no clause forbids and no captaincy manual solves.
Shanto is captain and batsman. When he is given LBW, the review decision concerns his own wicket. If he reviews and succeeds, he saves the team. If he fails, the team loses a review and he stays out. That is a double loss. It is easy to call it greed. It is more accurate to call it a missing protocol.

In three decades of watching and filing, I have seen this pattern: when the captain is also the batsman, the review becomes emotional. The ball-tracking data sits with an analyst in the dressing room; the captain has two seconds. He sees the ball hit the pad and assumes it was missing. That is human. It is also the team’s resource.
The sanction is never the point. The point is what the rule was protecting. Here the rule protects the team from clear errors by giving it two challenges. It does not say challenge every 50-50 ball. When a captain challenges his own wicket, he may be protecting his emotion rather than the rule. That is where captaincy begins.
Warrican’s angle and the geometry of the sweep
Jomel Warrican is a left-arm orthodox spinner. Shanto is a left-handed batsman. That angle carries a geometry. A left-arm spinner’s stock ball turns away from a left-hander, so the ball is moving away from the bat. The sweep goes against that turn. The bat comes across the pad, the body dips, and the balance goes outside the line of the stumps. If the ball is not to the pitch, the pad is in front and the bat is behind. That is the oldest LBW story in the book.
Not every sweep is wrong. If the ball has pitched, if the batsman has covered the line, the sweep can be the safest scoring shot. The problem is the premeditated sweep. The fifth over after lunch is a specific window. The spinner has reset his rhythm during the break, the pitch has had forty minutes to dry or sweat, and the batsman’s feet have not yet settled into the new session. In that window the spinner tries to put the ball on the stumps, because the batsman’s review count is finite.
The report does not say why the review failed. That is the largest omission. If ball-tracking showed the ball hitting the stumps, the question is shot selection. If it showed Umpire’s Call, the question is margin. If the ball hit the pad before the bat, the question is footwork. Three different answers, one headline. That is the convenience of the headline and the loss of the report.
Sadman’s tenth fifty: milestone or platform?
Sadman Islam’s tenth Test half-century is a number. It shows career continuity. But a fifty at 110 for 3 does not mean what a fifty at 300 for 3 means. At 110 for 3 it is the team’s anchor. The batsman is expected to stay, wear down the bowling, and give the next man time. At 300 for 3 the same fifty would mean accelerating. The number is the same; the role is different.
The report gave Sadman’s fifty one line and Shanto’s wicket a full paragraph. That is an editorial choice. The reader is not told how Sadman reached fifty — how many balls, against which bowler, at what stage of the innings. Without those questions a fifty is news, not analysis. And if we want it to be analysis, we need the price: balls faced, boundaries, beats, struggles against a particular bowler. None of that is in the report.
A milestone is not a milestone until we say what the match required. Sadman’s tenth fifty is a document of his career. The match’s document is 110 for 3. Putting both in one sentence tells the reader that the fifty and the wicket are parts of the same story. In fact they are two stories: one batsman’s continuity, one team’s instability.
The ‘shaky’ adjective
The report contains one word of opinion: Shanto’s batting was ‘shaky’. That is a judgement, not a statistic. If I were signing the match report, I would not print it without one of three pieces of evidence: the play-and-miss count, the proportion of balls beaten, or the time spent at the crease. None is present.
‘Shaky’ can also mean the batsman looked short of confidence. Confidence is a psychological state, not a scorebook column. Journalism often links confidence to shot selection. But a batsman who makes 15 off 30 balls may be slow, not shaky. A batsman who makes 20 off 10 and then gets out may be aggressive, not reckless. The word should come from the data, not from the mood.
I read the order twice. The second time I read what it left out. Here the order is the report. The first reading shows Shanto’s wicket. The second shows the questions the report did not ask: Did Shanto sweep? Was the ball there to defend? Did he consult the analyst? Did the captain use the team’s review protocol? None of these questions appears. That is the real problem with ‘shaky’ — it takes the place of the questions.
What the report does not contain: venue, series, day
A Test score of 110 for 3 tells us very little on its own. If it is the first session of the first day, it may be a fair start. If it is the second session of the third day, it is a crisis. If it is a fourth-innings chase, it is a target. The report has no venue, no day, no innings. The word ‘hosts’ implies Bangladesh at home. Warrican’s name implies West Indies. But the series is unnamed, the ground is unnamed, the toss is unnamed.
For a reporter that is the biggest omission. A scorebook contains more than runs and wickets; it contains date, place, toss, pitch report, and team sheet. Without them 110 for 3 is an incomplete sentence. You cannot call it a collapse before completing the sentence. You cannot call it a strong start either. You can say only this: three wickets fell, 110 runs were scored, and one review was spent. That is honest reporting.
I follow one rule in my own work: one figure, one argument. 110 for 3 is one argument — the team lost three wickets. The tenth fifty is a second argument — one batsman showed continuity. The fifth over is a third argument — this is the early part of the session. Stuffing all three into one paragraph does not make an argument; it makes a pile of information. The reader cannot pull a story out of the pile.
Two officials, one rulebook, and a decision nobody wanted to sign
The third umpire makes the review decision, but the responsibility is not his alone. The on-field umpire gave it out. The third umpire checked the evidence. The match referee records it. The captain challenged it. Four people, one clause, one ball. None of them says the decision was wrong. All of them say it was according to process. That is modern cricket’s greatest strength and its greatest weakness.
Two officials, one rulebook, and a decision nobody wanted to sign. The sentence applies to every controversial review. Apply it to Shanto. The on-field umpire raised the finger. Shanto raised his hand. The third umpire looked at the screen. The decision stood. Now the question: was the error the umpire’s, the batsman’s, or the system’s? The report does not say. So we must keep the three separate.
The umpire errs when he gives a clear out not out. The batsman errs when he reviews a clear not out. The system errs when it does not give the batsman enough information. The third umpire sees everything on a screen; the captain sees nothing. That inequality is the biggest blind spot in the review process.
The headline’s ‘even’: a small word, a large legal difference
‘Shanto could not survive even with review.’ The sentence suggests the review is a safety net and Shanto fell through it. In fact the review is not a safety net. It is a question: was the on-field decision clearly wrong? If the answer is no, the review fails, however innocent the batsman. The phrase ‘even with review’ erases that distinction.
In law, the appellant does not say he is innocent; he says the decision is wrong. The same applies to a review. Shanto appealed, but the appeal did not mean the ball was missing the stumps. It meant he believed the decision was wrong. The third umpire looked at the evidence, not the belief. The evidence did not support the belief. Calling that ‘even with review’ is linguistic laziness, not legal reasoning.
The captain’s review: challenging himself
Shanto’s review was a personal decision, but the team paid for it. That is captaincy. When the captain is a batsman, he has two interests: saving his wicket and saving the team’s review. They do not always point the same way. At 110 for 3 the team’s review may be more valuable, because the batsmen to come will need it. But the captain values his own wicket most. That is human.
The problem is that the laws do not recognise the conflict. Appendix 2 says the captain may review. It does not say the captain may not review his own dismissal. The captain fills the silence of the rule with his own convenience. That is where reform begins. A team should adopt a review protocol: for the captain’s own wicket, the vice-captain, wicketkeeper and analyst decide. The captain has no veto. This is not democracy; it is practical governance.
What 110 for 3 means: three wickets or a hinge?
110 for 3 is a number, not a direction. After three wickets there are two paths. One: Sadman stays and takes the innings to 250 or 300. Two: Warrican takes another wicket and Bangladesh are bowled out for under 150. What happens in between is decided in the next ten overs. The fifth over after lunch is the start of that ten-over window. It is the spell in which the spinner bowls long and the captain changes the field.
The report has no pitch report. So we cannot say whether 110 for 3 is a collapse or a solid start. We can say the third wicket is the captain’s, and a captain’s wicket is always heavier than an ordinary wicket. His dismissal weakens not only the batting but the fielding and the strategy. If Shanto were not captain, this would be just a wicket. Because he is captain, it is an event.
Three review outcomes, three meanings
First: ball-tracking showed the ball missing the stumps. Then the review was right, but the third umpire did not regard it as clear evidence. That is a model limitation, not a batsman’s error. Second: ball-tracking showed Umpire’s Call. The on-field decision stood. That is a verdict on the margin, not on justice. Third: the ball hit the pad before the bat and was going on to hit the stumps. Then the review was doomed from the start. That is the batsman’s error.
The report contains none of these. So ‘the review did not help’ is an incomplete sentence. It tells us what happened, not why. The reader naturally asks: did Shanto review badly? To answer, we need the third umpire’s screen, which we do not have. The honest answer is: we do not know.
Auditing the source: live score feed versus headline
The report names no source. There is no official scorecard citation, no agency attribution, no byline. The facts look as if they came from a live score feed: 110 for 3, the tenth fifty, Warrican’s wicket, the fifth over. The opinion — ‘shaky’ — is of a different quality. A score feed can be checked against an official scorecard. ‘Shaky’ cannot be checked against anything.
My sourcing standard is simple: a figure I cannot footnote is a figure I do not print. I can print 110 for 3 because the scoreboard can be checked. I cannot print ‘shaky’ because there is no measure behind it. That difference is the reader’s trust. If we put opinion and fact in the same paragraph, the reader will treat them as the same. That is the cardinal sin of the trade.
Contrarian: the real story is the review, not Shanto
The headline says Shanto could not survive even with review. That is a story about a person. The real story is about process. A captain gambled a shared resource on his own wicket. He could have won, lost, or drawn the gamble. He lost. Now the team has one review fewer. That loss may be larger than the wicket, because the batsmen to come need the same resource.
The real cost of a review is not the wicket; it is the next review that is no longer there. That is the angle the headline misses. Shanto’s dismissal is an event. Shanto’s spent review is a process. Events attract readers immediately. Processes shape the next session. If Bangladesh need a review for a clear LBW later and have only one left, the root of that will be this fifth over after lunch.
The fix: a review protocol
The solution is not to change the law. The law is fine. The solution is inside the team. Every team should have a review committee: vice-captain, wicketkeeper, senior bowler, analyst. For the captain’s own wicket, that committee decides. The captain has only a veto, to be used when he has specific information about the ball. This protocol protects the team’s resource and the captain from emotional decisions.
A second fix: a review audit after every session. How many reviews were taken, how many succeeded, how many were Umpire’s Call, how many were burned by batsman error. That audit belongs to the coach and the analyst, not the captain. The captain should see only the result in the next match, not the process. That is how professional sport works.
Takeaway
The next ten overs will tell us whether 110 for 3 was a hinge or a collapse. If Sadman’s fifty takes the innings to 250, it will be not just a tenth fifty but the turning point. If Warrican takes another wicket, Shanto’s review will be a footnote. The match story is not written yet. But one question can be asked now: when the next LBW appeal comes, who will decide — the captain, the analyst, or the clause?
