Fielding events are the third and final piece of the event delivery process to be captured when coding a match. This can be broken down into four main categories
1. Ground Fielding
2. Fielding Measures
3. Opportunities & Outcomes
4. Throwing
Ground Fielding
Dive Stops/Misfield
Whenever a player dives in the field to attempt stopping the ball.
- Dive Stops/Misfields should have runs cost/saved attributed to them
Misfields
Whenever a fielder misses or fumbles a ball that costs at least one run to the bowling team.
- Misfields always have Runs cost attributed to them
Outstanding Plays
For any special or spectacular efforts in the field, including great catches, direct hit run outs from side on or superb diving/ slide stops.
Slide Stops/Misfields
- Whenever a player slides to gather a ball or stop a boundary.
Fielding Measures
Runs Cost/Saved
Runs Saved
- Good anticipation, a dive stop, slide stop or extra effort that saves runs is also coded as Runs Saved.
- All catches and runouts recorded as runs saved (+1)
Runs Cost
- Whenever there is a misfield or lack of awareness / movement off the ball and runs are scored, the additional runs that result should be coded as Runs Cost.
- This is also used for outfielders who do not “shut down” when throws at the stumps occur and overthrows are allowed.
Opportunities
Catch Gradings
The grade of catches (dropped or taken) should be based on the following criteria
Positioning - Fielder is in a sufficient position to take the catch (2 Hands/Balanced when attempting)
Ball Velocity - Speed at which ball is hit at, gives fielder time to position correctly
Ball Trajectory - The ball trajectory off the bat has allowed the fielder to correctly position and attempt the catch. This can be affected by environmental (&venue) conditions
Grade 1 - Catch that expected to be taken, having satisfied all of the above criteria
Click here for example - G1 Catches
Click here for example - G1 Catches Dropped
Grade 2 - Catch is expected to be taken, however has acquired difficulty having not satisfied one of the Criteria above
Click here for examples - G2 Catches
Click here for examples - G2 Catches Dropped
Grade 3 - Difficult catch to be taken and has not satisfied two or more of the above.
Click here for examples - G3 Catches
Click here for examples - G3 Dropped
Assists - Instance where a second fielder is involved in the outcome of a catch. This could involve a deflect, tap, juggle or throw.
Runouts Gradings
The grade of run outs (dropped or taken) should be based on the following criteria
Positioning - Fielder(s) are in a sufficient position to execute the runout (Balanced)
Distance Proximity - Distance of the fielder in relation to the stumps/keeper has provided opportunity for runout
Angle Proximity - Position of the field in relation to the stumps that has provided opportunity for runout.
Grade 1 - Runout is expected to be made, having satisfied all of the above criteria
Click here for examples - G1 Runouts
Click here for examples - G1 Runouts Missed
Grade 2 - Runout is expected to be made, however has acquired difficulty having not satisfied one of the criteria above
Click here for examples - G2 Runouts
Click here for examples - G2 Runouts Missed
Grade 3 - Difficult Runout to be executed and has not satisfied two or more of the above.
Click here for examples - G3 Runouts
Click here for examples - G3 Runouts Missed
Assists - Whenever there are multiple people involved in the runout - there should be assists attributed to it. This will typically be the keeper or bowler who take the bails off, resulting in the runout.
Stumpings
Positioning - Keeper is in a sufficient position to take the stumping opportunity
Pitch Complexities - Line/Length and Spin off pitch have been sufficient to take stumping opportunity
Batter Actions - Actions/Movement of the batter have placed difficulty within stumping opportunity
Grade 1 - Stumping is expected to be made, having satisfied all of the above criteria
Click here for examples - G1 Stumpings
Click here for examples - G1 Stumpings Missed
Grade 2 - Stumping is expected to be made, however has acquired difficulty having not satisfied one of the criteria above
Click here for examples - G2 Stumpings
Click here for examples - G2 Stumpings Missed
Throwing
Good/Bad Throw
- A Good throw can be taken on the full or bounce within one metre of the top of the stumps, or a metre from the bellybutton of the receiver if they are not over the stumps.
- All other Throws outside of this zone should be coded as Error throws.
Throw Hit/Miss
All infield/outfield throws to the keeper or the bowler end. that an attempt at the stumps have been thrown
- Select Fielder, Throw location and Outcome
Throw Backed up / Not Backed Up
- To be used for Throw hit and Throw misses only, unless runs are saved or lost when the throw is backed up or not.
0 comments
Please sign in to leave a comment.