Batting event standards are the second part of the event delivery process to be captured when coding a match. This can be broken down into seven sub - sections
1. Contact
2. Batting Event
3. DRS
4. Extras
5. Overthrows
6. Score
7. Shot Type
1. Contact
1a. Contact Error
Descriptor - When the batter's attempted shot, results in an unexpected contact - this includes inside/leading/top edges & contact errors.
Use Cases - Intention of the shot made by batter and result of the contact or location of same delivery does not match. This would incumbencies batter's trying to manipulate shots into gaps in the field and resulting in leading edges, but also defensive shots resulting in balls off the glove or inside edges occurring.
1b. Hit on body
Descriptor - When a delivery hits parts of the body outside legs, hand or head.
Use Cases - Hit on body can have a force or unforced intent. Most likely is to occur as a consequence of misreading the bowlers delivery.
1c. Hit on Head
Descriptor - When a delivery hits player on the head.
Use Cases- Hit on head can have a force or unforced intent. Most likely is to occur as a consequence of misreading or being beaten the bowlers delivery. However can also occur from sporadic events such as mis executed throws or contact errors.
1d. Hit on pad
Descriptor - When a delivery hits the batter on either leg (pad, thigh, foot)
- generally, this would include Play and Miss and potentially Appeal
Use Cases - Can occur with either a force or unforced intent. In the case of an LBW decision - a Batter's may be deceived by a delivery which misses the bat and connects with the pad in front of the stumps. But also in a forced intent were tactical against spin, a batter made choose to use a pad as a barrier.
1e. Inside Edge
Descriptor - When a delivery hits the inside edge of a vertical bat.
Use Cases - Intention of the shot made by the batter and result of the contact does not match, as batter has been deceived or misjudged delivery. Inside edges typically result in the ball going to the leg side or even hitting batter.
1f. Outside Edge
Descriptor - Deflection of a ball on the outside edge of the bat
Use Cases - Outside edges will most likely end up behind square on the offside (slips/gully/wicketkeeper) region. The intention of the shot could vary from a defensive stroke in a multi-day format match, to an aggressive shot attempting to make runs through the offside.
1g. Play and Miss
Descriptor - Where the batter plays a shot at a delivery and no contact is made with the bat.
Use Cases - Consequence of misreading or being deceived by the delivery with the intention of playing a shot.
2. Batting Events
2a. Appeal
Descriptor - Anytime the fielding team ask the umpire to make a decision on whether the batter is out or not out according to laws of cricket. This could vary from the entire team asking as collective to individuals.
Use Cases - Appeal are most common for LBWs, caught behind, run outs or stumpings, however in rare cases they occur for inclusive caught attempts.
Click here to view some examples
2b. Batter Movement
Descriptor - Whenever a batter moves up or down the wicket or across the crease laterally in either direction, to deceive or exploit bowler's delivery.
Use Cases - Batter movement is more commonly seen in shorter formats of the game, where batters need to access 360 degrees of the ground. It would also be strongly utilized for spinners as a tactic to adjust length or counter the amount of spin experienced.
Click here to view some examples
2c. Bowler Variation
Descriptor - A delivery which differs from the bowler stock ball in an attempt to deceive the batter. This could involve change of speed in delivery, use of fingers to provide revolutions or bowling the delivery in different crease positions
For more information on Bowler variations - click through to Bowler event standards
2d. Free Hit
Descriptor - A free hit is awarded to the batting team after a no-ball is bowled by the bowler limited and T20 formats. The subsequent delivery is designated as a free hit. During a free hit:
- The batsman cannot be dismissed in any of the normal ways like being bowled, caught, leg before wicket (LBW), stumped, or hit wicket.
- The batsman can still be run out, and can be given out for obstructing the field or handling the ball.
- Field changes are restricted if the same batsman is on strike.
The concept of a free hit is intended to penalize the bowler for overstepping and to provide the batting team with a scoring opportunity.
2e. Opportunity
Descriptor - When a batter presents an opportunity to be dismissed - usually through means of hitting the ball in the air.
- All dropped catches, missed runouts/stumpings are an assumed opportunity and do not need to be coded
Use Cases - Catchable height through the slips/gully region, or a top edge flying high are example of what should be coded as an opportunity
2f. Out
Descriptor - Refers to a batsman being dismissed from their turn at batting. There are several ways a batsman can be dismissed:
- Bowled: The ball is bowled by the bowler and hits the stumps, dislodging the bails.
- Caught: The batsman hits the ball with the bat or glove, and a fielder catches it before it touches the ground.
- Leg Before Wicket (LBW): The batsman is struck on the leg by the ball, and the umpire believes the ball would have hit the stumps if the leg had not been in the way.
- Run Out: A fielder hits the stumps with the ball while the batsman is outside the crease, attempting to complete a run.
- Stumped: The wicketkeeper puts down the stumps while the batsman is outside their crease and not attempting a run.
- Hit Wicket: The batsman dislodges the bails with their body or equipment while playing a shot or setting off for a run.
- Handled the Ball: The batsman deliberately uses their hand to return the ball to a fielder without the fielding side’s consent.
- Obstructing the Field: The batsman deliberately interferes with a fielder’s attempt to field the ball.
- Hit the Ball Twice: The batsman hits the ball twice, other than to protect their stumps.
- Timed Out: The next batsman takes longer than the allotted time to take the field.
2g. Retired Hurt
Descriptor - Situation where a batsman leaves the field of play due to injury or illness. The batsman can return to continue their innings later, provided they are fit enough to do so.
2h. Umpire Referral
Descriptor - When the on field umpires signal for assistance from the third umpire to assess a decision (e.g. a runout or catch).
3. DRS Events
Descriptor - the Decision Review System (DRS) is a technology-based system used to assist the on-field umpires in making decisions. It allows players to challenge and review certain decisions made by the on-field umpires.
4. Extras
Descriptor - Extras (or Sundries) are runs scored by means other than the bat or glove of the batsman. Extras are added to the team's total but not to any individual batsman's score. There are several types of extras:
-
No-Ball: A run awarded when the bowler oversteps the crease or bowls an illegal delivery (e.g., a high full toss). The batting team gets an extra run, and the next delivery is a free hit, meaning the batsman cannot be dismissed in most ways except for being run out.
-
Wide: A run awarded when the bowler delivers a ball too wide or high for the batsman to reach. The batting team gets an extra run, and the ball must be bowled again.
-
Byes: Runs scored when the ball passes the batsman and the wicketkeeper without touching the bat or the batsman's body, allowing the batsmen to run.
-
Leg Byes: Runs scored when the ball hits any part of the batsman’s body (excluding the hand holding the bat) and the batsmen are able to run. The runs are counted even though they did not come off the bat.
5. Overthrows
Descriptor - Overthrows occur when a fielder's throw at the stumps goes astray, allowing the batsmen to run additional runs. These runs are added to the total of the team and can be awarded in the following situations:
-
Fielding Errors: If a fielder throws the ball inaccurately, missing the stumps or the intended target, and the ball travels away from the fielders, the batsmen can run additional runs.
-
Boundary Overthrows: If the ball thrown by a fielder hits the stumps or another fielder and then goes over the boundary line, four additional runs are awarded to the batting side. These runs are added to the number of runs the batsmen had already completed before the ball reached the boundary.
Within the code window to correctly score the match, a coder will need to attribute the runs completely as well as resulted overthrows to correctly score the delivery.
6. Score
Descriptor - Outcome of delivery
WK (Off) - Delivery has gone through to the keeper on the offside
WK (Leg) - Delivery has gone through to the keeper on the legside
0 - Delivery has resulted in no runs being scored
1 - Delivery has resulted in 1 run being scored
2 - Delivery has resulted in 2 runs being scored
3 - Delivery has resulted in 3 runs being scored
B4 - Delivery has gone for boundary and resulted in 4 runs being attributed to batter
5 - Delivery has resulted in 5 runs being scored
B6 - Delivery has gone for boundary and resulted in 4 runs being attributed to batter
4 All Runs - Delivery has resulted in 4 runs being scored, however this has been completed by batters running between the wickets.
7. Shot Type
7a. Paddle
Descriptor - The batsman moves across the stumps and uses the wrists to flick or sweep the ball, often with a closed face, to guide it towards the fine leg or short fine leg area against spin bowling
Use Case - To manipulate the field and access not fielded areas, batter will use a scoop to utilise space behind the wicket. Can be executed to spin bowlers.
7b. Ramp/Scoop
Descriptor - Attacking bottom handed shot where the batter attempts to lift the ball behind the wicket against fast bowling.
Use Case - To manipulate the field and access not fielded areas, batter will use a scoop to utilise space behind the wicket. Can be executed by pace bowlers.
7c. Reverse Sweep
Descriptor - Sweep shot played through the off side. The batter may change their hands but their stance remains the same (unlike a Switch Hit), i.e. the left leg remains the front leg for a right hander.
Use Cases - To protect stumps and generate more power behind square, batter will use a reverse sweep to break field or manipulate field on the offside.
7d. Sweep Shot
Descriptor - Down on one knee, played into the legside. Can also be lapped or ramped. Traditionally played against slow bowling.
Use Cases - To protect stumps and nullify spin, sweep shot will be used to break field and generate scoring shots on the legside.
7e. Switch Hit
Descriptor - The batter changes their hands and their stance around so a right hander effectively becomes a left hander and vice versa.
Use Cases - Similar to reverse sweep intention is to break field and score boundaries, by changing hands.
0 comments
Please sign in to leave a comment.