Laws 18.3-5 & 23.2 Short Runs and Run Outs

[johnfgolding]

I would be interested in experience of others with the following scenario.
The batsman in question is normally at the non-strikers end, his colleague strike the ball and they run through for a single.
The batsman in question never actually make his ground, there is never an attempt to run him out. In fact he never grounds his bat or part of his person behind the popping crease at any time from taking his run to taking his guard and the bowler starting his run up.

• At what point in time before the bowler starts his run up do you consider the ball to be dead and confidently not call out if a fielder spots this and attempts a belated run out. Law 23.2 is clear in its definition, but as the ball is automatically dead I can see the potential for controversy?

• Would laws 18.3, 18.4 & 18.5 short runs be considered?

• Does anyone have any experiences they can relate?

[umpireindia]

I had a similar query in the thread. But there should be something concrete to deal with this, because I have seen this happening in a few ODIs as well. Though a short run cannot be called for a single run, shouldnt we take the clause "make good his ground from end to end" into consideration at all?

[swerveman]

This is sloppy practice by the batsman, but I think we have to be practical here, and use Law 23.1(b) "The ball shall be considered to be dead when it is clear to the umpire at the bowler's end that the fielding side and both batsmen have ceased to regard it as in play".

Perhaps you could have a word with the batsman?

[johnfgolding]

This what I do as a matter of course.
Basically it, like most of our role, is about good man management.
The law is quite specific but I always adopt the position of trying to prevent any problem before it happens.

swerveman said:

This is sloppy practice by the batsman, but I think we have to be practical here, and use Law 23.1(b) "The ball shall be considered to be dead when it is clear to the umpire at the bowler's end that the fielding side and both batsmen have ceased to regard it as in play".

Perhaps you could have a word with the batsman?

[umpire]

You will find better answer on
www.lords.org/laws-and-spirit/laws-of-cricket/
A question & Answer relate with same senario is:
Question: The batsmen run a single on the last ball of an over. The striker unintentionally just fails to make good his ground at the bowler’s end, and starts to walk unhurriedly towards his partner for a chat. It is clear that both sides regard the ball as dead. Before calling Over, should the umpire call and signal Short run?
Answer: No. A run is short only when the batsman, having failed to make good his ground, turns for a further run. It is clear that all regard the ball as dead. Clearly the striker is not trying to take a further run when he goes to ‘have a chat’. Therefore, there has not been any short run.
It is true that the run has not in fact been scored, under the definition in Law 18.1(a), but the umpire is empowered to call Short run only when there is short running. Law 42.2 states very firmly that umpires are not to interfere with the progress of play, unless
either a player’s action is considered unfair
or they are required to do so by the Laws.
The call is not required by Law. The umpire cannot consider the player to be trying to gain an unfair advantage in the situation described. Therefore he cannot intervene.
On the other hand, the batsmen have clearly crossed, so under Law 18.11 (Runs scored when ball becomes dead) the run in progress when the ball becomes dead will be credited to the batting side [Law reference: 18.4, 18.1, 18.11, 42.2]