DRS needs to be reviewed: Here's how to do it

By Once Upon a Time on the Roar / Roar Guru

DRS was supposed to rid the game of the so-called ‘howler’ and it hasn’t done that.

We still get vital Test matches decided by howlers, such as Horrible Headingly a year ago. We can blame the players until the cows come home for using DRS speculatively, or even pure gambling with it, but I don’t believe that solves the imperfections in the system either because human nature gives rise to desperateness.

The teams that futilely burn reviews are almost always the one under the hammer in any given match. For example, we can say that an umpiring howler cost us at Edgbaston 2005 and DRS would have overturned it, but that is making a rather loose assumption that we would still have had a review left in any case.

At the end of the day, Test matches on an individual level (let alone, potentially, the result of a whole series) should never hinge on which side is more astute at challenging the umpire’s decision. Players should just play and umpire’s umpire; words spoken by Richie Benaud in an interview at the end of the victorious 1958-59 Ashes series.

I could ask why it is that we have three different systems of technology referrals for different modes of dismissal, but I won’t. I will merely briefly outline what those three different systems are before moving on to the main proposal that I want to put forward in respect to LBWs:

1. For run-outs and stumpings, the umpire has the option of referring the decision upstairs. They almost always do this even when the verdict is blatantly obvious to the untrained eye. In this case, the on-field umpire doesn’t have to make any decision whatsoever – they have the full prerogative to completely pass the buck upstairs.

2. For catches, when the issue is whether the ball has been caught cleanly or not (rather than whether or not the batsman has hit the ball) the umpire has no such prerogative. Rather, they’re required to stick their neck out somewhat by making a so-called ‘soft’ decision before reverting to the option of sending it upstairs.

3. For LBWs (as well as catches where the issue is contact with bat rather than carry to the fieldsman) the umpire has to make a complete decision. Either the batsman is given out or the fielding captain can appeal the decision to the higher authority upstairs. This depends on which way the on-field decision went.

With this third system, I have four major problems with it. Firstly, it has not worked in ridding the game of howlers. Secondly, kids watch their heroes on TV legally challenge the decision-maker in authority. When they’re successful it adds to the obnoxious perception that the umpire is always wrong.

Thirdly, I have never understood why it should make a difference whether a review is successful or not in terms of how many subsequent ones are available to a team. I think a team should get a capped number – whether successful or not.

(Ryan Pierse/Getty Images)

Finally, the umpire’s call epitomises the very inconsistency that DRS should surely be stamping out. Where is the fairness in an umpire ruling not out to an LBW shout, the fielding side reviewing, and it is shown to be clipping the outside of the top of leg stump so it stays not out, but then when their opponents bat, the decision is out, and the exact same scenario but it stays out.

I detest the idea that one batsman on one team gets to stay, while a counterpart on the opposition has to go based on what the original decision was in what was, at best, a line-ball call. At worst it was an umpire not concentrating enough to realise that there were, in both cases and using only the naked eye, enough doubts for the batsman at the wicket to benefit from.

I’m an umpire myself and I don’t consider saying not out with the naked eye to a ball that ball-tracking subsequently deems was hitting flush right at the top of leg stump to be a howler. If this technology was available in games I adjudicate, I would have no problem with such technology respectfully overturning my decision in the interests of fair play or natural justice (assuming it is 99.9997321% accurate).

The first part of my reform to the LBW part of DRS would be to abolish umpire’s call altogether. The decision on a percentage of the ball hitting a percentage of the relevant off-stump/leg stump/the bails and then everything that falls within that percentage is out, with the remainder not out. Depending on how reliable and accurate ball tracking is deemed to be, the aforementioned percentage may well be set at 100.

The second thing I would do is abolish the on-field challenge by players and have the third umpire review every LBW appeal and this will become clearer shortly.

The third and final thing I would do is alter the order in which LBW criteria is looked at (by the video umpire that is, not the on-field umpire making the initial decision). Currently, they look at the potential for a no-ball, followed by potential contact with the bat (whether before or after first contact with batsman’s person), followed by where the ball pitches, followed by whether the batsman was struck in line with the two sets of stumps, and then finally whether or not the ball would have hit the stumps had the ball not been intercepted by the batsman’s person.

How many people reading this have ever actually stopped to ask why the video umpire looks at things in this order? The answer is two-fold and it overlaps: this is, firstly, the order in which events occur. Secondly, this order is the way umpires without technology assistance are trained to assess the merits of an LBW appeal (with the naked eye in the split second or so in which events actually unfold).

This may sound totally obvious when spoken out loud but from the perspective of the umpire making the decision, a standard beginner’s umpiring coaching manual might say something along the lines of “too many inexperienced umpires ask themselves that last question first” (would the ball have hit the stumps?) with the inference being that the previous events have the potential to be quickly lost in the mind.

However, who’s to say that computer technology has to look at things in the same order that they occur, let alone the same order that the human brain processes things? Of those five LBW criteria outlined two paragraphs before now, three of them – where the ball pitches, whether struck inline or not, and whether the ball is hitting stumps or not – are literally ascertained in barely a split second, so why not do these three things first when using the technology?

So, let’s cut to the chase – here is my proposal.

There is an LBW appeal and the on-field umpire gives a decision. The video umpire immediately goes to ball tracking. If the on-field decision was not out, then ball-tracking can be completed before a spinner off a short run fully returns to their mark.

If at this point any of the three criteria covered by ball-tracking vindicate the on-field not-out decision, then the players simply get on with the game, the on-field umpire having received a covert signal from upstairs. As stated, this will happen within literally a second or two.

(Photo by Gareth Copley/Getty Images)

If, however, all three LBW criteria covered by ball-tracking are in contradiction to the on-field umpire’s decision, then the game pauses and they check for hotspot and legality of delivery. If it’s a fast bowler or medium-pacer, these last two criteria will also be pretty much completed by the time the bowler reaches their mark for the following delivery.

Given that well under 50 per cent of bowlers operate off run-ups of only a few paces, and 60 per cent of LBW criteria can be looked at in a split second, hold-ups to the game will be minimal.

If the on-field decision is out, then all five LBW criteria can be ascertained long before the batsman has left the field of play, and the incoming batsman can be trained upon reaching the international level to wait near the perimeter and not step onto the field of play to legally begin his or her innings until the on-field decision has been officially ratified upstairs.

My proposed system does not undermine the on-field umpires or make them obsolete at all. Think of the on-field umpire as the parliament, and the upstairs third umpire using video technology as the senate.

What happens if either the members of the parliament or the senate don’t do their jobs competently? They get voted out by the people.

Who are the metaphorical people electing the metaphorical parliament and senate in an international cricket match? The selection committee that appoints all umpires to such matches, of course.

Even our good friend Shane from Ipswich would say, “it’s elementary, my dear Watson.”

The Crowd Says:

2020-08-15T01:06:56+00:00

Jon Richardson

Roar Pro


Agree on the last point. But no need to bother about trying to calculate down to the last erg of force whether the ball might have hit the stumps. Leave it at - if less than 50% mightn’t have been hitting, there’s enough doubt.

2020-08-14T23:05:48+00:00

Paul

Roar Guru


A very good article Bernie. You've pointed out one ludicrous part of the current way the Laws are handled, ie batsmen being given out or not out, even though the ball hit the stumps at the same place in different innings, but the other ludicrous thing I can't get my head around is players effectively having to be umpires, but not being able to do that through an entire innings. Captains now have to become umpires and decide they know when an umpire has erred. That's almost an impossibility for things like lbws, but I'd suggest the bulk of reviews are because the ball hit the pads. So now they're not only captaining this sides, they're unofficial umpires as well. But they're only umpires as long as they have reviews left. Why? The real umpires are still going to make howlers once the reviews have been used up as we saw in the Ashes last year. Paine has been soundly bagged for his captaincy at Edgebaston, but I'll bet few can remember the name of the umpire who made such a poor lbw decision, which caused much of Paine's pain. If all lbws are going to be reviewed, then two things should happen. The first is there should be no captains reviews. As you rightly point out, the other types of dismissals are invariably referred anyway, so why would the captain need a review? The other thing that has to happen is the enforcement of Laws around frivolous appeals when the ball hits the pads. I agree the third umpire shouldn't take long to give the umpire a signal, but if the spinners are operating at both ends, it will still slow the game down. At the least, your idea or something similar should be trialled at Shield level. If it works and I suspect it would, Benaud's words ring true. Umpires can do their jobs and let the players play.

2020-08-14T22:07:33+00:00

Marcus

Guest


I agree the current system needs to be looked at. For run outs and stumpings we always use the third umpire and we pretty much always get it right. You can’t blame anyone for the ones the are millimetre tight. So for two modes of dismissal we always get them right. And we can stop the game for 100 of these reviews no questions asked I suggest of of two solutions. 1) give both teams a limited number of reviews for the whole match. This way they will be less likely to burn them on stupid reviews either batting or bowling, as it could cost you later. 2) Give every batsman the right to review their dismissal, While avoiding the top order burning the rest of the team, or choosing not to early when there is a lot of doubt. In the bowling innings you get 5 unsuccessful reviews. Yes more reviews will slow down the game, but this is test cricket, the longest game in the world. Add 30 mins a day more playing time.

AUTHOR

2020-08-14T12:37:46+00:00

Once Upon a Time on the Roar

Roar Guru


Yeah, as I said, I haven’t seen the soccer system in action though I know full well how soccer is played. It’s different in the way that the ball could be in play indefinitely whereas in cricket it’s a ball by ball or delivery by delivery basis, so breaks in play are more frequent. If we can just perfect ball tracking so that after any delivery you can just hit a button and get the result in a second or two then we can certainly get rid of player challenges. And umpires on the field as well as in front of the video replay must be totally accountable.

2020-08-14T12:19:56+00:00

Gonzo99

Roar Rookie


Problem is though that VAR hasn't totally eradicated the howler either. There's been a few occasions where the people running the technology have apologised for mistakes after matches have finished. Another consequence has been that referees seem afraid of making decisions and stopping play - they let it run then get the VAR to sort it out once the passage of play's over. My feeling is that the tech is currently pretty good and has got rid of most mistakes, so progress has been made, but it's not perfect. I'd agree that the goal should be to get rid of the review system once the tech is quick & accurate enough. The West Indies seemed to use their spare reviews in the 3rd test in England to just waste a bit of time. I'm not sure how you'd get rid of this kind of stuff without losing the review system all together.

AUTHOR

2020-08-14T09:42:34+00:00

Once Upon a Time on the Roar

Roar Guru


I just googled it actually, and yeah, if it can work in one sport, it can certainly work in another I feel.

AUTHOR

2020-08-14T09:20:57+00:00

Once Upon a Time on the Roar

Roar Guru


I'll have to take your word on that mate, I don't follow soccer. I would find it interesting though if you want to take the trouble to explain it to me. Cheers

AUTHOR

2020-08-14T09:00:41+00:00

Once Upon a Time on the Roar

Roar Guru


AUTHOR

2020-08-14T08:53:17+00:00

Once Upon a Time on the Roar

Roar Guru


Your point about appeals increasing in frequency in tight situations is valid, but in the Headingly test last year when Stokes hit the winning runs there was still plenty of time left on the 4th day, time was never going to be an issue. The moronic review on Leach, ball tracking, however long it takes, would have settled the issue with at least one non-line i.e. not pitching where it has to. While the umpire knew, and the players prolly knew, the umpire could be sure, just like they do with run outs and stumpings.

AUTHOR

2020-08-14T08:43:37+00:00

Once Upon a Time on the Roar

Roar Guru


Best solution with ball clipping is perfect the technology enough to factor in speed of delivery to ascertain whether the bails would have been knocked off. Yes, I agree 100% with what you say about line ball boundaries and this would certainly make it easier for umpires at levels where no replay technology is available. Back when they had fences, you could lean against, even stand on the fence to take a catch as long as you didn’t topple over and make contact with the ground on the other side, so why not be allowed to stand on the rope as long as you don’t touch the ground on the other side.

AUTHOR

2020-08-14T08:38:01+00:00

Once Upon a Time on the Roar

Roar Guru


Yeah but when they say “Go to ball tracking when ready/available”, it’s usually not too many seconds later that they play it. I am wondering if ball tracking is something that once loaded can’t be stopped and has to be played immediately and if this is the case it would explain why they have to load it with such a request because they don’t know how long the video umpire will spend looking at hot spot and snicko, repeatedly ‘rocking and rolling it’? The technicians doing the ball tracking would need to be ready for potential use after any delivery and basically as soon as the players appeal give the command “Ball tracking to 3rd umpire (NOW)!” Plus, as another roarer pointed out above, without the player challenge option gone, 10 seconds is gained in any case because that is the time that ticks down while they decide whether or not to review under the current system. Players will also know when an appeal is frivolous and to just get on with the game, invariably a fieldsman at square leg or point will point out “Nah way too high – it hit him on the thigh” or someone behind the wicket will admit out loud that he hit it. Plus it’s not as if there’s an lbw appeal even every over, there’s prolly only a dozen or so across a whole day’s play.

2020-08-14T07:39:02+00:00

Brendan

Guest


So similar to how the VAR check works in soccer?

2020-08-14T07:35:07+00:00

AWin

Guest


"If the on-field decision was not out, then ball-tracking can be completed before a spinner off a short run fully returns to their mark." My understanding is it can't - it takes longer than that for balll tracking to calculate. You'll usually hear the third umpire say something like "now go to ball tracking when available", usually after checking the no-ball and pitching in line first as they fill the time which tracker is working. Doing this every time there is an appeal (there are a lot of very hopeful appeals, esp in tight situations) will slow the game down way way too much.

2020-08-14T06:26:13+00:00

Jon Richardson

Roar Pro


I like your idea of reviewing the ball tracking first. Makes sense. Not so sure about reviewing every lbw. Your proposal makes sense if the batsman is given out, but if it’s not out we could end up with a lot of time wasting. I’d prefer just to extend the number of reviews to say three or four per innings. I dont hate umpire’s call that much, but I do like the proposal here on umpire’s call if it means anything that shows less than 50% ball hitting the stumps will be given not out. This mirrors real life umpiring where it’s pretty much impossible to tell with the naked eye in real time if a fraction of the ball is going to nick the stumps. And can the technology really tell that accurately a ball is going to just nick the stumps every time. This is also consistent with the traditional philosophy in cricket (as in the justice system) where you need to be certain beyond a degree of reasonable doubt that someone is out/guilty. There is too much muddled thinking of the “counting the number of angels on the head of a pin” variety in cricket about being absolutely certain about whether someone is out or not, when there are so many near misses (especially with edges and plays and misses) that there is a big element of luck and uncertainty. All you want is a robust framework for decision making. Actually the biggest nonsense with replays for me is slow motion replays of outfield catches that are taken close to the ground. It’s normally easier to tell whether it was a catch at normal speed - slow motion and closeups are often misleading. Also, spending 5 minutes looking at umpteen replays of whether the foot of a fieldsman on the boundary has touched the rope is idiotic. They should really change the rule to make the criterion whether the ball crosses the line or touches it, which is easier to determine and more within the spirit of the game, in the sense that that is the basic requirement - and for most of cricket’s history and at most levels of cricket ropes weren’t/haven’t been used. And it’s easier for a spectator on the boundary (or teammate/opponent on the field) to determine with a naked eye.

AUTHOR

2020-08-14T04:09:56+00:00

Once Upon a Time on the Roar

Roar Guru


For as long as Drs allows players to challenge the empire's decision we will never rid the game of the hail Mary review as someone in a Facebook cricket group coined it.

2020-08-14T03:20:30+00:00

Peter85

Roar Rookie


This has been my internal, un-shared opinion for a few years now. The only benefits the current system provides is manufactured TV drama, which becomes tedious very quickly as they sift through a minute of did he hit it only to find out that it pitched outside leg. I would go as far to say that the need for a referral can nearly always be determined in a single slow motion replay which the third umpire can then relay through to the the main umpire who can then hold up play as required when a not-out decision has been given (the out decision was covered well in your piece). On the not out decision, the 3rd umpire reviews a single replay with the stumps overlay and determines 1) fair delivery 2) pitches correctly 3) hasn't been obviously hit and 4) hits the pads correctly. By doing this you can either confirm the not out call or escalate to an official review. The challenging part is the time taken for ball tracking technology to be available will hold up the game where the initial replay confirms everything legal up to the point of impact, but probably less so than the current situation given you have an appeal, it gets struck down, then 10 seconds to deliberate before you consider walking back to your mark to bowl the next ball. The last thing they need to do is go to ball tracking as soon as it is available for the reason I initially stated.

AUTHOR

2020-08-14T01:23:29+00:00

Once Upon a Time on the Roar

Roar Guru


It's been fixed. Thanks Roar.

AUTHOR

2020-08-13T23:37:16+00:00

Once Upon a Time on the Roar

Roar Guru


Disclaimer: I did not write DBS in the title.

Read more at The Roar