Whether you're setting up a match or downloading it from the cloud, the match details need to be complete and correct. This article goes through each tab of the match setup and what to check.
In this article
Match details
This is the first screen you see when you create or select a match. For domestic matches, most of it should already be filled in by the Cricket Australia representative. The fields are straightforward, and they make sure the match turns up under the right filters later.
Before the start of play: fill in Toss won by and Match Innings, and check that the required overlays are marked and the coder and reviewers are correct. Change the Coding Status once you start coding.
Lineups
Coders and reviewers usually need to select the players in each team and check these fields.
| Field | What to do |
|---|---|
| Selected players | Double-click a player to add them to or remove them from the team. To find players faster, use the drop-down list, choose All teams, or type in the search field. |
| Batting hand | Right-click to change. |
| Bowling hand / style | Right-click to change. |
| Wicketkeeper / captain | Players move between teams more often now, so check that only one keeper and one captain are selected. |
| Status | The player's role in the match (see the next table). |
| Coach | Choose the coach from the drop-down. Use the yellow box to add a new coach if needed. |
| Status | Meaning |
|---|---|
| Playing | Named in the starting XI |
| 12th | Named as the 12th player and involved in the match in that role |
| Substitute | Took part in the match as a substitute |
| Concussion | Came into the match as a concussion replacement for another player |
| X-Factor | A substitute used under the X-Factor rule in T20 leagues that have it |
Options and toggles
The Options tab lets the coder customise their setup.
| Option | What it does |
|---|---|
| Beehive style | Perspective adjusts the beehive for the player's height; flat uses a fixed height. |
| Viewing from | Matches the coding window to the camera setup: always from behind the bowler's arm, or alternating ends. |
| Sort players | Sorts players by name or jumper number. If you don't know the players well, sort by jumper number. |
| Broadcast | Make sure Broadcast to Stats Server is ticked, so the vision connects to the wider system. |
| AthleteAI | Read and write responses for automated ball tracking by AthleteAI. |
| Pitch layout | Pitch and venue dimensions, so insights can be compared over time. |
Powerplays
In limited-overs matches, powerplays restrict how many fielders can be outside the 30-yard circle. When you set up a match, check the powerplay details against the competition's playing conditions:
| Competition | Playing conditions |
|---|---|
| Sheffield Shield | 2024-25 playing conditions |
| One Day Cup | 2024-25 summary |
| WNCL | 2024-25 summary |
| BBL | Not yet linked |
| WBBL | Not yet linked |
| Spring Challenge | 2024-25 summary |
Each powerplay is set up for each innings: its number, the overs it starts and ends, and the maximum number of outfielders. The powerplay number and maximum outfielders are then recorded on every delivery automatically as you code.
You can also change powerplays during the match, in the coding screen or the audit trail, or after the match in the match details.
Session details
Fill in the session details at the start of every session. Several of these fields feed directly into insights.
| Field | What to record |
|---|---|
| Day and session | The day and session of the match. Especially useful for multi-day matches. |
| Recording conditions | The environmental conditions at the venue. Optional since the 2024/25 domestic season. |
| Bowling and umpire ends | Now that Hawk-Eye data arrives live at BBL and international matches, the right bowling end matters for insights. The reviewer should confirm the ends with the coder before the first ball. |
| Capture details | Optional toggles for what you capture. Ball speed and revolutions depend on having the right technology. Stroke/intent, ball movement and X/Y data depend on the coder's experience. Third-party data from AthleteAI, Hawk-Eye or Opta can overlay these where it's available. |
Results
The Results tab records how each innings ended and the result of the match.
Innings closures
| Closure | When to use it |
|---|---|
| Declared | The batting captain ended the innings before all wickets were lost. |
| All out | All ten wickets fell. |
| Unfinished | The innings wasn't completed because the match ended (time, weather or other reasons). |
| Compulsory closure | The innings was ended by the playing conditions rather than by wickets, usually because the scheduled close of play or the over limit was reached. |
| Not started | The innings didn't begin. |
Result
- 1st innings result: the match position after the first innings, from the home team's perspective.
- Match result: the final result. Depending on the format, only a few win/loss options apply.
Where to go next
- Coding Process: the standard coding requirements for every delivery.
- Incoming and Outgoing Feeds: connecting Analyzer and Receiver to live data.
- Coding Standards: what each event means and when to use it.
0 comments
Please sign in to leave a comment.