Umpiring & DRS

icyman

ICC Chairman
India
The Boys
Joined
May 17, 2004
Location
Hong Kong
Profile Flag
India
We've seen a lot of howlers, haven't we?

Well, the DRS was supposed to alleviate these instances, however, what we see nowadays are more 'basic howlers' from the cricket umpires.

The reason I wanted to start this thread was to get your views on:

  1. How can we improve the umpiring standards?
  2. Should the DRS be limited to 2 calls per innings? Why can't we look at unlimited calls?
  3. Role of the 4th umpire/ Match Referee (useful in instances like the overthrows during the WC Final)
 

Willoughby63

User Title Purchaser
ENG....
Mumbai Indians
RCB...
PlanetCricket Award Winner
Sydney Sixers
Joined
Jul 29, 2019
Profile Flag
England
We've seen a lot of howlers, haven't we?

Well, the DRS was supposed to alleviate these instances, however, what we see nowadays are more 'basic howlers' from the cricket umpires.

The reason I wanted to start this thread was to get your views on:

  1. How can we improve the umpiring standards?
  2. Should the DRS be limited to 2 calls per innings? Why can't we look at unlimited calls?
  3. Role of the 4th umpire/ Match Referee (useful in instances like the overthrows during the WC Final)
Personally I think that every decision should be checked, creating a consistency that must be achieved in a high level sport like this
 

asprin

Administrator
Admin
India
PlanetCricket Award Winner
Joined
Sep 3, 2012
Online Cricket Games Owned
  1. Don Bradman Cricket 14 - Steam PC
You couldn't give the teams unlimited reviews though
I've a different take on that. We can very well try out unlimited reviews. More on that below.

It is said that DRS was introduced to get rid of howlers. That's fair enough. But what would you do when there is a bad decision after a team has used up their quota of reviews? Let's exclude close calls (like umpire's call in case of LBWs). DRS should not used as a tool to overturn those. So that's fine.

But let's say a batsman has clearly inside-edged a ball onto his pads and the umpire gave it out as LBW? The batting team has no reviews left.

OR

A batsman has clearly nicked a ball through to the keeper and the umpire did not give it out. The fielding team has no reviews left either.

Those two scenarios defeat the very purpose of having DRS in the first place. So how would you balance that out? Here's what I feel can executed on a trial basis.

(a) Remove the restriction on the number of DRS reviews a team can make.
(b) Now to make sure they are not abused, enforce a penalty in case the decision stays with the umpire after review (can exclude umpire's call since those are too close to call)
(c) Penalty should be in the form of runs being awarded to the opposite team (similar to the case where the ball hits the helmet placed behind the keeper)
(d) The amount of runs awarded should differ based on the format being played. For example: 6 runs for Tests, 4 runs for ODIs and 2 runs for T20Is.

What this will do is allow the captain to call for a review without having to worry about how many are left in the bank. And in case where the captain is using his reviews unnecessarily, it would cost his team extra runs that will keep getting added to the opposite team.
 

qpeedore

SOTM Winner - July 2014
Joined
Apr 5, 2009
Location
Trinidad and Tobago
I disagree. I think the current system works pretty okay.

Look at the use of DRS since its inception. Technically, a fielding captain can ask for DRS upon any query of dismissal. Now, we can exclude bowled, because that's rather blatant. Stumped and run out are umpires' reviews. So is obstruction. Timed out is a matter of the clock. Hit wicket is obvious, as is retired out. That's 7 of the current 9 ways to be out in cricket.

That leaves us with two dismissal types. LBW and caught. Now, caught is usually pretty easy. Ball hits bat, ball goes to a fielder, howzat, out. An extremely high percentage of DRS reviews for caught are for caught by the keeper or first slip. Occasionally you get a leg slip or short leg into the scenario. But by and large, it's the keeper or first slip. I don't think much people will disagree with that. A ball doesn't just go on its own to gully off of a good line and length without bat being involved. Maybe forearm, okay, but that's also rare. LBW, on the other hand, that's a different thing. You're appealing and relying on several scenarios. The umpire's assessment of the pitch, the way that pitch has been playing, your own ball trajectory, the pitch point, the line, the impact point, and so on and soforth.

So clearly there is a reason why most DRS reviews have been for LBW. And that takes into account that practically everyone has accepted HawkEye predictions as reliable. Which it is, I think I made a post here over 10 years ago when people were doubting its accuracy. I believe most cricket boards have also had UltraEdge integrated. That's therefore accepted as reliable. HotSpot is not common due to the financial issues, but it helps. I haven't heard or read of any cricket board not accepting HotSpot technology in reviews if it's available. So we have to agree that it's also accepted when it's available.

All I'm doing so far is making logical assumptions, but I don't think anyone will disagree that these assumptions are wrong. Feel free to discuss.

Now, the topic at hand. The use of the DRS system and howlers.

If we (logically) agree that it's mostly for LBW's, and to a slightly lesser extent for catches, then you have to also (logically) agree that you should only review when you're sure. This breaks it down into several scenarios, which I will outline below.

1. Batsman hit on pads, fielding team appeals, standing umpire gives not out. Fielding captain reviews.

Well that's clear enough. The fielding captain should consult with his wicketkeeper, he's the one who would really be in the best line to see the trajectory of the ball. Fielders in the slips will incur parallax error and no matter what they say, they really should not be involved in the decision to review. Mid off/mid on, provided they are not too wide, will also be subject to parallax error, but because they have the advantage of a front on sight (as they call it on TV now "front on spin view"), they are more likely to see potential edges and trajectories that the slips cannot. The bowler should be the next person consulted. He will be the best one to state where the ball pitched, where the batsman was hit, and which way the ball was going. A leg spinner who hits a right handed batsman right in front of the off stump but said he gave the ball a good rip is unlikely to see three reds, no matter what everyone else says. And this part is perhaps the biggest failure of captains in the DRS era. They do not ask the bowler what ball he delivered. Bowlers, to their credit, just want wickets, so they will agree with their captains, but you've just lost a review because you bowled an almighty spinning delivery and conveniently forgot to tell the captain in your excitement. There's a reason for a slightly bigger proportion of LBW DRS reviews asked for spin bowlers rather than seam bowlers.

2. Batsman hit on pads, fielding team appeals, standing umpire gives out. Batsman reviews.

There is no reason for a batsman to review an LBW decision by an umpire unless he is sure that he either hit the ball or he has taken such a huge stride that HawkEye gets screwed with the prediction. If you look back at the percentage of batsman LBW DRS reviews, it's going to come back mostly as "Umpire's call". Statistically speaking, you really should not review an LBW call. Yes, there are howlers. Those are the ones you review. Asking the non-striker is an asset, but is not without its own limitations. In limited overs matches, most non-strikers watch the bowler's run up and delivery stride. They are halfway down the pitch by the time the ball is delivered. They cannot tell you whether the ball was delivered wide of the crease, narrow, behind, in front, sideways, up, down, swinging in, out, diagonally, pitched to hit the third man halfway to the boundary, nothing. You're better off accepting the umpire's call.

3. Batsman plays a shot, catch is claimed, standing umpire gives not out. Fielding captain reviews.

This actually has one of the highest percentages of reversed decisions. Weird, because I thought cricket was a gentleman's game and batsmen walked. But in the teens and now the twenties, I guess batsmen have been trained differently. With the amount of padding in gloves these days, I do suppose that occasionally you really can't tell if you got a feather onto the ball, but really...batsmen should walk and the fielding side should not have to review. Fielding captains should ask for the review if they are sure, because more often than not, it's out.

4. Batsman plays a shot, catch is claimed, standing umpire gives out. Batsman reviews.


Again, a batsman usually knows if he had hit the ball or not. He should review this if he's sure. He's usually correct most times.


Captains need to use their reviews properly, and not just use it stupidly. I hate to see the last established batsman using a review just in the hope that he might be in and not out, only to see a good lower order batsman get out to a howler and cannot review it.

I will say that since DRS, the standard of umpiring has improved. We see much less howlers, but they do happen. I see no need to change the current system. I see a need for teams to use that system properly.

Just note that for an umpire to give a batsman out someone must appeal, and an appeal is valid at ANY point in time before the next ball is bowled, replays or not. It's in the Laws. Technically nobody can appeal, watch the replays on the big screen, and then appeal, and the umpire has to give it out if it is. Just saying.
 

Users who are viewing this thread

Top