Fielding Event Standards

Fielding events are the third and final part of each delivery you capture when coding a match. This article covers ground fielding, runs saved and cost, how to grade catches, run-outs and stumpings, and throwing.

In this article

1. Ground fielding
2. Runs saved and cost
3. Opportunities and outcomes
4. Throwing
Where to go next

1. Ground fielding

Event	When to code it	Examples
Dive stop / misfield	A fielder dives to try to stop the ball. Always record the runs saved or cost.	Watch
Misfield	A fielder misses or fumbles the ball and it costs the fielding side at least one run. Always record the runs cost.	Watch
Outstanding play	A special effort in the field, such as a great catch, a direct-hit run-out from side on, or a superb diving or sliding stop.	Watch
Slide stop / misfield	A fielder slides to gather the ball or stop a boundary.	Watch

2. Runs saved and cost

Runs saved

Code runs saved for good anticipation, a dive stop, a slide stop, or any extra effort that saves runs.
Every catch and run-out is recorded as runs saved (+1).

Runs cost

When a misfield, or a lack of awareness or movement off the ball, lets the batters score, code the extra runs as runs cost.
This also applies to outfielders who don't back up throws at the stumps, allowing overthrows.

3. Opportunities and outcomes

Catches, run-outs and stumpings are graded 1 to 3, whether they were taken or missed. Each has three criteria: a Grade 1 meets all three, a Grade 2 misses one, and a Grade 3 misses two or more.

Catches

Criterion	It's met when…
Positioning	The fielder is in a good position to take the catch: two hands, balanced.
Ball velocity	The ball was hit slowly enough for the fielder to get into position.
Ball trajectory	The path of the ball off the bat let the fielder get into position and attempt the catch. Weather and venue conditions can affect this.

Grade	Meaning	Taken	Dropped
1	Expected to be taken: meets all three criteria.	Watch	Watch
2	Expected to be taken, but harder: misses one criterion.	Watch	Watch
3	A difficult catch: misses two or more criteria.	Watch	Watch

Catch assists: code an assist when a second fielder is involved in a catch, through a deflection, tap, juggle or throw. Watch examples

Run-outs

Criterion	It's met when…
Positioning	The fielder or fielders are balanced and in a good position to complete the run-out.
Distance	The fielder is close enough to the stumps or the keeper to make the run-out possible.
Angle	The fielder's angle to the stumps makes the run-out possible.

Grade	Meaning	Made	Missed
1	Expected to be made: meets all three criteria.	Watch	Watch
2	Expected to be made, but harder: misses one criterion.	Watch	Watch
3	A difficult run-out: misses two or more criteria.	Watch	Watch

Run-out assists: when more than one player is involved in a run-out, code an assist. It's usually the keeper or bowler who removes the bails.

Stumpings

Criterion	It's met when…
Positioning	The keeper is in a good position to take the stumping.
Delivery	The line, length and spin off the pitch gave the keeper a fair chance at the stumping.
Batter's actions	The batter's movement didn't make the stumping harder.

Grade	Meaning	Made	Missed
1	Expected to be made: meets all three criteria.	Watch	Watch
2	Expected to be made, but harder: misses one criterion.	Watch	Watch

4. Throwing

Event	When to code it
Good throw	The throw arrives, on the full or on the bounce, within one metre of the top of the stumps. If the receiver isn't over the stumps, within one metre of the receiver's midriff.
Bad (error) throw	Any throw outside that zone.
Throw hit / miss	Any throw at the stumps, from the infield or outfield, at the keeper's or bowler's end. Select the fielder, the throw location and the outcome.
Throw backed up / not backed up	Only for throw hits and misses, unless backing up (or not) saved or cost runs.

Where to go next

Bowler Event Standards: the first part of each delivery.
Batting Event Standards: the second part of each delivery.
Coding Process: the standard coding requirements for every delivery.