Oracle of Delphi
Arnold
Paladin
Shan Jayaweera
KC Hill
Cibbuano
Craig HillCricket Tips #8: Calling
August 3rd 2006 08:09
Being run out is probably one of the worst ways you can be dismissed - why? It's because the fielding team has just scored a free wicket by just doing what they're supposed to be doing... stopping the ball. Run outs can be easily avoided - that is why they're annoying, especially when you're on the receiving end of a shocking call, or a non-existent one.
With cricket being a team game, it's no surprise that teamwork is an essential facet in winning matches. Not only is team work fundamental in the field, it is also definitely a massive factor when you're out there with one other team member with the bat. If you've got a batsman at the other end who either: a) Doesn't call whether to run or not properly or b) Doesn't call at all (so you just see him/her ran at you in silence) you're definitely asking for it. And if you're one of those batsmen yourself, I'm not surprised if every one else hates batting with you.
So for all you mutes or confused callers out there, here are the essentials:
1) Call loudly - there's no point calling a run when you're saying it as if the guy/girl at the other end has a sound amplification device stuck to his/her head. Make sure they can hear it. The best way is to almost yell.
2) The three calls - There's also no point in going into a deep conversation when calling a run. It's either 'Yes', 'No' or 'Wait'. Nothing else. And when you say 'yes' you go, and when you say 'no' there's no use running down to the other end. That's why there's 'wait'. This is used to let the other batsman know that there might be a run possible and to be ready to go if for instance, the ball pierces a small hole in the field. Then either a 'yes' or 'no' decision can be made. The batsman who strikes the ball normally calls this one as he/she knows how well they have struck it as soon as the ball leaves the bat.
3) Who calls when? - Two basic rules. If the ball ends up behind the batsman facing, the non-striker calls the run. If the ball ends up in front of the striking batsman, then most likely they will make the better call. Simple.
4) Running between wickets - Always make sure that you're facing the ball, whilst you are turning, and that you're taking a sneak peek at the ball when you're running. Also, there's no use keeping this information on the whereabouts of the ball to yourself, let your partner know how many runs that could be possible from the shot, and go from there. Try not to leave at full pace after turning, always have a quick look and assess the risk of the next run. If you've smacked the ball close to the boundary, there's no point in pondering over the second run when you know there's an easy three runs in it... just use your common sense.
With cricket being a team game, it's no surprise that teamwork is an essential facet in winning matches. Not only is team work fundamental in the field, it is also definitely a massive factor when you're out there with one other team member with the bat. If you've got a batsman at the other end who either: a) Doesn't call whether to run or not properly or b) Doesn't call at all (so you just see him/her ran at you in silence) you're definitely asking for it. And if you're one of those batsmen yourself, I'm not surprised if every one else hates batting with you.
So for all you mutes or confused callers out there, here are the essentials:
1) Call loudly - there's no point calling a run when you're saying it as if the guy/girl at the other end has a sound amplification device stuck to his/her head. Make sure they can hear it. The best way is to almost yell.
2) The three calls - There's also no point in going into a deep conversation when calling a run. It's either 'Yes', 'No' or 'Wait'. Nothing else. And when you say 'yes' you go, and when you say 'no' there's no use running down to the other end. That's why there's 'wait'. This is used to let the other batsman know that there might be a run possible and to be ready to go if for instance, the ball pierces a small hole in the field. Then either a 'yes' or 'no' decision can be made. The batsman who strikes the ball normally calls this one as he/she knows how well they have struck it as soon as the ball leaves the bat.
3) Who calls when? - Two basic rules. If the ball ends up behind the batsman facing, the non-striker calls the run. If the ball ends up in front of the striking batsman, then most likely they will make the better call. Simple.
4) Running between wickets - Always make sure that you're facing the ball, whilst you are turning, and that you're taking a sneak peek at the ball when you're running. Also, there's no use keeping this information on the whereabouts of the ball to yourself, let your partner know how many runs that could be possible from the shot, and go from there. Try not to leave at full pace after turning, always have a quick look and assess the risk of the next run. If you've smacked the ball close to the boundary, there's no point in pondering over the second run when you know there's an easy three runs in it... just use your common sense.
| 72 |
| Vote |
subscribe to this blog
Go to Craig Hill's home page by clicking here
