The captain armband is the largest single decision in any contest
The captain armband carries the multiplier shown on the scoring table. A high-scoring XI without the captain armband underperforms. A captain pick with a poor XI underperforms too. Balance wins.
The criteria below apply to Test, ODI and T20 formats. Each role carries a different captain weight depending on the format. The boundary column lists the conditions where the captain logic fails. Verify recent form on the BCCI / IPL feed before locking.
What each role brings to the captain armband
| Role | What it brings | T20 weight | ODI weight | Test weight | Boundary |
|---|---|---|---|---|---|
| Top-order batter | Most balls faced | Very high | High | Very high | Bowled early on green; verify pitch |
| Pace bowler | Wickets, dot balls, death overs | High | Very high | High | Batted out on flat track; verify matchup |
| Spin bowler | Wickets, middle-overs control | Moderate | High | High | Subcontinent-only dominance; verify conditions |
| Middle-order batter | Death overs, acceleration | High | Moderate | Moderate | Slow start on slow pitch; verify conditions |
| All-rounder | Bowl + bat points combined | Very high | High | Very high | Two-format dependency; verify role fit |
| Wicketkeeper | Catches, stumpings, batting bonus | Variable | Variable | Variable | Lower-order bat on slow track; verify |
Weights reflect format-specific scoring rules. Verify the exact weights on app before each contest.
The boundary column
Every captain logic has a break condition. The boundary column lists the conditions where the captain logic fails. Pitch, toss, format and recent form are the four that matter most. The boundary column applies to every role, not just the captain pick.
The captain armband amplifies whatever the player produces. A 0 with the captain armband is 0, multiplied. A bowled-out batter with the captain armband is -2, multiplied. Captain logic must respect recent form and pitch read before applying the multiplier.
What the boundary column is not
The boundary column is not a prediction. It is a checklist of conditions where the captain logic breaks. The captain pick must be verified against each condition before locking. Pitch report, toss call, recent form and format fit are the four checks.
Where to verify before locking
Batter form read
Recent innings on the BCCI / IPL feed. Average, strike rate, dot-ball percentage against pace and spin. Verify before each captain pick. Recent series gives the cleanest signal; older series give context only.
Bowler form read
Recent wickets, dot-ball share and death-over load. Economy against right and left-handed batters. Matchup data against the opposing XI. Verify on the BCCI / IPL feed.
All-rounder fit
All-rounders carry two-format dependency. The bowling role and the batting role must both fit the format and the XI. Verify the all-rounder's role fit before locking the captain armband.
Pitch report and toss
Pitch report decides batting order and pace / spin balance. Toss decides whether the captain pick is first or second in. Verify pitch and toss on app before locking the captain armband.
Lock the captain armband in five checks
-
Pick the role
Top-order batter, pace bowler, all-rounder or wicketkeeper. Match the role to the format. Verify on the BCCI / IPL feed.
-
Read recent form
Recent innings or overs. Average, strike rate, dot-ball share. Verify on the public data feed.
-
Read the matchup
Matchup against the opposing XI. Bowler vs batter. Pace vs spin. Verify on the BCCI / IPL feed.
-
Check the boundary
Pitch report, toss, format. Each condition can break the captain logic. Verify each one before locking.
-
Lock the armband
Lock the captain armband on app. Squad lock follows the toss. Verify before each contest.
Verify on app, not here
The captain pick reference sets the framework. The captain pick decision runs on app. Recent form, pitch report and toss update on the live feed. The armband locks on app. Verify before each contest.
The captain picks reference in detail
The captain armband is the largest single decision in any contest. The captain armband carries the multiplier shown on the scoring table. A high-scoring XI without the captain armband underperforms. A captain pick with a poor XI underperforms too. Balance wins.
Role weights
Top-order batter: most balls faced. Pace bowler: wickets, dot balls, death overs. Spin bowler: middle-overs control. Middle-order batter: death overs, acceleration. All-rounder: bowl + bat points combined. Wicketkeeper: catches, stumpings, batting bonus.
The boundary column
Every captain logic has a break condition. The boundary column lists the conditions where the captain logic fails. Pitch, toss, format and recent form are the four that matter most. Verify each before locking.
Recent form reads
Batter form read, bowler form read, all-rounder fit, pitch report and toss. Each maps to the captain pick ledger. Verify on the BCCI / IPL feed.
Decision tree
Pick the role. Read recent form. Read the matchup. Check the boundary. Lock the armband. Five checks before locking on app.
When the multiplier breaks
The multiplier amplifies whatever the captain produces. A 0 with the captain armband is 0, multiplied. A bowled-out batter with the captain armband is -2, multiplied.
What to do with this reference
Use this reference to walk the captain pick ledger before locking. Verify on app and on the BCCI / IPL feed.
Captain picks in detail
The captain armband is the largest single decision in any contest. The captain armband carries the multiplier shown on the scoring table. A high-scoring XI without the captain armband underperforms. A captain pick with a poor XI underperforms too. Balance wins.
Role weights
Top-order batter: most balls faced. Pace bowler: wickets, dot balls, death overs. Spin bowler: middle-overs control. Middle-order batter: death overs, acceleration. All-rounder: bowl + bat points combined. Wicketkeeper: catches, stumpings, batting bonus.
The boundary column
Every captain logic has a break condition. The boundary column lists the conditions where the captain logic fails. Pitch, toss, format and recent form are the four that matter most. Verify each before locking.
Recent form reads
Batter form read, bowler form read, all-rounder fit, pitch report and toss. Each maps to the captain pick ledger. Verify on the BCCI / IPL feed.
Decision tree
Pick the role. Read recent form. Read the matchup. Check the boundary. Lock the armband. Five checks before locking on app.
When the multiplier breaks
The multiplier amplifies whatever the captain produces. A 0 with the captain armband is 0, multiplied. A bowled-out batter with the captain armband is -2, multiplied.
Verified captain pick scenarios
Three recent match states show how the captain pick ledger applies. The ledger stays the same; the inputs shift with the match state. Each scenario opens with the state, walks the role weight, names the boundary check, and points to the live verification feed.
Green pitch, T20 night game, powerplay pressure
Recent state: square boundaries under 65 metres, outfield quick, dew expected in the second innings. Role weight: powerplay top-order batter. The armband goes to the batter who faces the most powerplay balls. Boundary check: dew likely, so the chasing side's openers get extra value. Verify on the IPL match feed before the first ball.
Dry ODI, used surface, spin in the middle overs
Recent state: dry pitch, used for day-three of a Test before the ODI, spinners have already extracted turn in the warm-up nets. Role weight: middle-overs spinner. The armband goes to the spinner with the best dot-ball share in the last completed series. Boundary check: pace bounce is inconsistent, so the pacers' economy is a coin flip. Verify on the BCCI match feed.
Day-five Test, slow turn, batting fourth
Recent state: pitch has slowed, spinners dominate the second new ball, the team batting fourth chases under 200. Role weight: lower-order all-rounder who bowls spin. The armband goes to the all-rounder with both batting and spin points. Boundary check: a collapse early in the chase forces the lower order in, so the all-rounder's bat gets more balls. Verify on the BCCI match feed.
When the multiplier does not save a wrong pick
The captain armband amplifies whatever the captain produces. A duck with the armband is a multiplied duck. A wicketless spell is a multiplied wicketless spell. The armband cannot rescue a wrong pick. Verify the role fit, recent form, matchup and boundary before locking the armband, not after.
Captain pick ledger: role, recent form, matchup and the boundary column
The captain pick ledger is a sub-decision inside the contest. The ledger walks the visitor through role, recent form, matchup, boundary column and the captain multiplier. Each input is verifiable against the BCCI / IPL feed and the published scoring table.
Role is the starting input. Top-order batter in Test, pace bowler in ODI, powerplay batter in T20, all-rounder in mixed formats. The role sets the captain weight, which is the multiplier on the score. A wrong role picks the wrong captain, regardless of the form read.
Recent form is read against the most recent completed series. The read covers batting average, strike rate, dot-ball share and death-over share. Recent form gives the cleanest signal; season stats include cold patches. Verify on the BCCI / IPL feed before applying.
The boundary column is the most important input. A read without a boundary is a guess. The boundary column lists the conditions where the captain logic fails: pitch report, toss call, format and recent form. Verify each one before locking the captain armband.
What is the captain multiplier?
The captain multiplier is a published value on the scoring table. The value is 2x for the standard contest, 1.5x for the vice-captain. The exact value 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. The column is the same for every role; the application differs.
Where do I get the matchup data?
Matchup data is published per series on the public data feed. The data is behind a delay during the live match and is public after the match.