Define “recent” before opening the scorecards
Form is a description of recent performance, not a permanent player rating. Choose a comparison window before inspecting the results: for example, the last ten innings in the same format, with dates shown. Selecting only matches that support a preferred argument creates a flattering or damaging story without a consistent method.
A short window reacts quickly to improvement but is noisy. A longer window is more stable but can include an old role or a different technical approach. Present both when useful, and distinguish international cricket from domestic competitions. This guide does not publish a live India form ranking; it explains how to build one without disguising uncertainty.
Read batting average alongside scoring rate
Batting average is total runs divided by dismissals, not innings. Strike rate is runs divided by balls faced, multiplied by 100. In an illustrative ten-innings sample, 300 runs with two not-outs produces an average of 37.50 because there were eight dismissals. If those runs came from 200 balls, the strike rate is 150. Both measures are useful, but neither describes the match situations by itself.
Not-outs are real contributions, yet they can make comparisons between openers and finishers difficult. An opener regularly faces a new ball; a finisher may face fewer deliveries with a greater demand for immediate boundaries. Compare players doing similar jobs and include balls faced, not merely headline averages.
Split a T20 innings into phases
For a standard full-length T20 innings, a common analytical split is overs 1–6, 7–15 and 16–20. The first phase usually has the tightest fielding restrictions; the middle often features spin and strike rotation; the final phase rewards boundary access and rapid decision-making. These are analytical conventions, and shortened matches require attention to revised playing conditions.
A batter with an overall strike rate of 140 might be excellent against middle-overs spin but slow against high pace at the death. Boundary percentage and dot-ball percentage can explain that pattern. Always state whether a percentage uses balls faced or runs scored as its denominator; the two tell different stories.
Bowling figures need a difficulty adjustment
Economy rate is runs conceded per over. In cricket notation, 3.2 overs means three overs and two legal balls: twenty deliveries, not 3.2 decimal overs. Conceding 24 runs from those deliveries gives an economy of 7.20. Misreading the notation creates a calculation error before any interpretation begins.
Bowling average measures runs conceded per wicket; bowling strike rate measures legal balls per wicket. If no wicket was taken, do not display a fabricated zero average. Compare powerplay bowlers with other powerplay bowlers and death specialists with death specialists. Eight runs an over can be expensive on one surface and a valuable defensive spell on another.
Look for repeatable skills, not just outcomes
A dropped catch can turn a well-executed delivery into a wicketless spell. A mistimed shot can clear a short boundary. Outcomes matter, but video or detailed ball-by-ball observation can help distinguish control from fortune. For batters, watch balance, shot selection and options against a specific length. For bowlers, consider line discipline, change-up execution and whether the intended field supports the plan.
Fielding deserves its own caution. Raw catch totals mostly reflect opportunities; they are not a complete ranking of catching quality. Without consistent chance-quality data, avoid precise “runs saved” claims. An honest qualitative note is better than a confident number whose method cannot be explained.
Finish with a useful player note
A concise form assessment should state the period, format, role, sample size, two relevant measures and one limitation. For example: “Across the last ten T20 innings, the player has accelerated well against spin, but the death-overs sample is only eighteen balls.” This says more than “in red-hot form” while making the evidence easy to challenge.
Do not let a ranking become a selection algorithm. Team balance, conditions and availability still matter. Use the squad guide to connect individual strengths to team roles, then test the combined argument in a match preview. The objective is not to remove judgement from cricket; it is to make the basis of that judgement visible.