Advanced Match Analysis Project

In this lesson you will scope your analysis project. Choose a match or short series that you can access fully, ideally one with ball-by-ball live scoring and, if possible, a WinnTV replay. Agree a main question with a captain or coach, such as why did we lose control in the death overs, or what made our chase successful. Add two or three supporting questions. Decide what is in and out of scope, set a realistic deadline, and note any data limits from the start. A well-scoped project is narrow enough to finish properly and important enough that someone will act on the results.

• Pick a match with full data access
• Agree one main and two or three supporting questions
• Set scope, deadline and data limits
• Narrow enough to finish, useful enough to act on

In this lesson you will gather and check your data. Export or copy the scorecard and ball-by-ball record, read the match report, and note conditions such as pitch, weather and boundary size. If a WinnTV replay is available, list the time stamps of key moments. Check for errors before you analyse, for example totals that do not add up, missing extras or a dismissal credited to the wrong bowler. Raise any errors politely with the scorer rather than correcting the official record yourself. Store all data securely and follow WFA data protection and safeguarding policies throughout the project.

• Collect scorecard, ball-by-ball, report and conditions
• List replay time stamps for key moments
• Check totals, extras and dismissals
• Report errors to the scorer; store data securely

In this lesson you will analyse both batting innings. Calculate each side's run rate and wickets by phase, strike rates and dot-ball percentages for key batters, and boundary versus running runs. Build wagon wheels for the main innings where you have direction data. Analyse partnerships, including runs, balls and run rate, and mark any collapses or recoveries in the fall of wickets. Compare the two sides phase by phase to see where the match was won and lost. Remember the context of conditions and sample size, and focus on the findings that answer your main question rather than every possible figure.

• Run rate and wickets by phase for both sides
• Strike rate, dots and boundaries for key batters
• Wagon wheels and partnerships
• Compare phase by phase

In this lesson you will analyse bowling and fielding. Calculate economy, dot-ball percentage, boundaries and extras for each bowler by phase, and note how wickets fell. Build pitch maps for key spells if you have length data from observation or replay. Review the bowling rotation and match-ups: who bowled to whom, and did the plan work? Record fielding chances, misfields and estimated runs saved. Remember that byes and leg byes are not charged to the bowler, and run outs are not credited to them. Look for links between pressure, dot balls and wickets, and between fielding errors and big overs.

• Economy, dots, boundaries and extras by phase
• Pitch maps for key spells
• Review rotation and match-ups
• Fielding chances, misfields and runs saved

In this lesson you will identify the moments that decided the match. Use a worm chart and a manhattan to spot overs where one side pulled ahead. Track the required run rate through the chase, and think about how win probability would have shifted at key wickets, expensive overs or dropped catches. Watch those moments on replay where possible to understand why they happened. Usually two or three turning points explain most of the result. Describe each one clearly, for example three wickets in overs eight to ten against spin shifted the chase from comfortable to difficult, and link it to evidence.

• Use worm and manhattan charts
• Track required rate through the chase
• Consider win-probability shifts at key moments
• Two or three evidenced turning points

In this lesson you will turn findings into recommendations. Each recommendation should follow from evidence, answer part of your main question, and describe a clear action, such as plan two specialist death bowlers and keep their final overs in reserve. Separate process from outcome, so you do not recommend changing a good plan simply because it was unlucky. Limit yourself to three to five recommendations, and note which are for the team and which are for individual development plans. Be honest about uncertainty, especially where the sample is a single match, and suggest what further data would confirm each idea.

• Every recommendation follows from evidence
• Clear actions, three to five at most
• Separate process from outcome
• State uncertainty and what would confirm it

In this lesson you will present your project. Write a short report of one to three pages, or a handful of slides, starting with a headline summary and your recommendations, followed by the supporting charts and evidence. Use clear, labelled charts such as worms, manhattans, wagon wheels and pitch maps, and a few short video clips if appropriate. Present to the captain or coach first, invite questions, and agree what will happen next. Share individual findings privately and keep the tone positive and respectful. Finally, reflect on what you would do differently in your next analysis, because every project makes you a better analyst.

• Headline summary and recommendations first
• Clear charts and a few short clips
• Present to the captain or coach; invite questions
• Reflect on how to improve next time