Player notes by role
The myteam11 squad carries eleven players across six roles: top-order batter, middle-order batter, all-rounder, pace bowler, spin bowler and wicketkeeper. The captain pick ledger reads the role fit before the recent form. Verify on the BCCI / IPL feed.
Below: the four role checks the captain ledger asks for. Each role carries a different weight depending on the format. Verify on app.
Recent form read
Recent form is read against the most recent completed series. Average, strike rate, dot-ball share. Verify on the BCCI / IPL feed. Recent series gives the cleanest signal; older series gives context only.
Matchup read
Matchup against the opposing XI. Bowler vs batter. Pace vs spin. Right-hand vs left-hand. Verify on the BCCI / IPL feed. Matchup data is published per series.
Boundary column
Pitch, toss, format. Each condition can break the captain logic. Verify each one before locking. Boundary conditions are part of the captain pick ledger and verified on app.
What each role asks of the captain pick
Top-order batter
Most balls faced, longest at crease. Recent average and strike rate. Matchup against the new ball. Boundary: bowled early on green; verify pitch.
Middle-order batter
Death overs, acceleration. Recent strike rate. Matchup against the death bowlers. Boundary: slow start on slow pitch; verify conditions.
Pace bowler
Wickets, dot balls, death overs. Recent wickets and economy. Matchup against right and left-handed batters. Boundary: batted out on flat track; verify matchup.
Spin bowler
Wickets, middle-overs control. Recent wickets and economy. Matchup against right and left-handed batters. Boundary: subcontinent-only dominance; verify conditions.
All-rounder
Bowl + bat points combined. Recent all-round form. Matchup against the opposing XI. Boundary: two-format dependency; verify role fit.
Wicketkeeper
Catches, stumpings, batting bonus. Recent catches and batting form. Matchup against the pace bowlers. Boundary: lower-order bat on slow track; verify.
Player notes verify on the BCCI / IPL feed
Each player note references recent form on the BCCI / IPL feed. Verify before each captain pick. The role fit is set on app and updated for each match.
What this reference does not cover
This reference covers the player notes by role. It does not cover every player on the current roster. The full roster lives on app and on the BCCI / IPL feed. Verify on the live feed before locking the captain pick.
This reference also does not cover player transfers, franchise retentions or domestic selection. Those events are published on the BCCI / IPL feed and on app.
Recent form read
Recent form is read against the most recent completed series. The signal is the cleanest at the start of a series. The signal degrades as the series progresses. Verify on the BCCI / IPL feed before each match.
Matchup data
Matchup data is published per series on the public data feed. Matchup data includes batter vs bowler, pace vs spin, right-hand vs left-hand. Verify on the BCCI / IPL feed before each captain pick.
The players reference in detail
The myteam11 squad carries eleven players across six roles: top-order batter, middle-order batter, all-rounder, pace bowler, spin bowler and wicketkeeper. The captain pick ledger reads the role fit before the recent form.
Recent form read
Recent form is read against the most recent completed series. Average, strike rate, dot-ball share. Verify on the BCCI / IPL feed. Recent series gives the cleanest signal; older series gives context only.
Matchup read
Matchup against the opposing XI. Bowler vs batter. Pace vs spin. Right-hand vs left-hand. Matchup data is published per series on the public data feed.
Boundary column
Pitch, toss, format. Each condition can break the captain logic. Verify each one before locking. Boundary conditions are part of the captain pick ledger and verified on app.
Role checks
Each role asks a different question of the captain pick ledger. Top-order batter: most balls faced. Middle-order batter: death overs. Pace bowler: wickets, dot balls. Spin bowler: middle-overs control. All-rounder: bowl + bat points. Wicketkeeper: catches, stumpings, batting bonus.
What to do with this reference
Use this reference to verify the recent form and the matchup for each player. Verify on app and on the BCCI / IPL feed before each captain pick.
Players reference in detail
The myteam11 squad carries eleven players across six roles: top-order batter, middle-order batter, all-rounder, pace bowler, spin bowler and wicketkeeper. The captain pick ledger reads the role fit before the recent form.
Recent form read
Recent form is read against the most recent completed series. Average, strike rate, dot-ball share. Verify on the BCCI / IPL feed. Recent series gives the cleanest signal; older series gives context only.
Matchup read
Matchup against the opposing XI. Bowler vs batter. Pace vs spin. Right-hand vs left-hand. Matchup data is published per series on the public data feed.
Boundary column
Pitch, toss, format. Each condition can break the captain logic. Verify each one before locking. Boundary conditions are part of the captain pick ledger and verified on app.
Role checks
Each role asks a different question of the captain pick ledger. Top-order batter: most balls faced. Middle-order batter: death overs. Pace bowler: wickets, dot balls. Spin bowler: middle-overs control. All-rounder: bowl + bat points. Wicketkeeper: catches, stumpings, batting bonus.
What to do with this reference
Use this reference to verify the recent form and the matchup for each player. Verify on app and on the BCCI / IPL feed before each captain pick.
Players reference in detail
The myteam11 squad carries eleven players across six roles: top-order batter, middle-order batter, all-rounder, pace bowler, spin bowler and wicketkeeper.
Recent form read
Recent form is read against the most recent completed series. Average, strike rate, dot-ball share. Verify on the BCCI / IPL feed.
Matchup read
Matchup against the opposing XI. Bowler vs batter. Pace vs spin. Right-hand vs left-hand. Verify on the public data feed.
Boundary column
Pitch, toss, format. Each condition can break the captain logic. Verify each one before locking.
What to do with this reference
Use this reference to verify the recent form and the matchup for each player. Verify on app and on the BCCI / IPL feed before each captain pick.
Players: role-by-role reads, recent form and the captain fit
A player read is a single paragraph: who the player is, what role they play, what their recent form looks like, what their captain fit looks like. The read is short because the captain logic and the boundary column are what matter, not the biography.
Top-order batters face the bulk of the innings. The captain weight is high in Test and very high in T20. The boundary is the green pitch and the bowled-early risk. Verify the pitch report on the morning of the match.
Pace bowlers carry the dot-ball share and the death-over load. The captain weight is high in ODI and Test. The boundary is the flat track and the batted-out risk. Verify the pitch report and the matchup.
Middle-order batters carry the death overs and the acceleration. The captain weight is high in T20 and moderate in ODI. The boundary is the slow start on a slow pitch. Verify the conditions and the matchup.
Where do I get the recent form data?
The BCCI / IPL feed. The feed is public and updates on the morning of the match.
What is the captain fit?
The captain fit is the role-by-role read against the format. The fit is published inside the app and may differ across formats.
What is the boundary column?
The boundary column lists the conditions where the captain logic fails. Pitch report, toss call, format and recent form are the four that matter most.