The captain and vice-captain multipliers are the most powerful tools in fantasy cricket, and also the most common source of self-inflicted damage. A captain earns double points and a vice-captain earns one and a half times, which means these two picks can contribute more than the other nine players combined. Yet most players choose them on gut feel, habit, or whoever is most famous, and then wonder why a team full of good picks finishes mid-table. The mistakes below are small, repeatable, and entirely avoidable.

The first mistake is picking both the captain and vice-captain from the same team. If that team collapses, both multipliers fail together, and your team has no way back. Spreading the captain and vice-captain across both teams is basic insurance: one team's bad day does not sink both picks. The exception is when one team is so dominant on a particular pitch that both multipliers genuinely belong there, but that should be a deliberate decision based on the matchup, not a default habit.

The second mistake is captaining a player whose role limits his ceiling. A finisher who bats at number six might score a brilliant twenty off eight balls, but even doubled that is a modest return compared with an opener who faces fifty balls. The same applies to a bowler who bowls only two overs in a match. Captaincy should go to players with maximum involvement: openers, number three batters, all-rounders who bat and bowl, and bowlers who bowl their full quota including powerplay or death overs. Involvement is the raw material of fantasy points, and the captain needs the most of it.

The third mistake is ignoring the matchup. A star batter who struggles against quality spin is a poor captain on a turning track against two good spinners, no matter how famous he is. A fast bowler who feasts on batters weak against short balls is a strong captain on a bouncy pitch. Spend two minutes checking head-to-head records and recent performances against this specific opposition before locking in the armband. Matchup-blind captaincy is how good teams lose to average teams.

The final mistake is never changing a failing captaincy pattern. If you have captained the same star for five matches and he has delivered once, the pattern is telling you something. Rotate based on form, venue, and matchup each match, and keep a short note of your captaincy picks and their scores. Over a season, players who actively manage captaincy outperform players who set it on autopilot by a wide margin, because the multiplier magnifies every good and bad decision equally.

A useful discipline for captaincy is to decide your captain last, after the rest of the team is built. Many players pick their captain first and then build around him, which anchors the whole team to one decision made before the toss, the pitch report, and the confirmed elevens are known. Building the team first and choosing the captain last forces you to use the freshest information available, including late team news and conditions. It also prevents the common trap of captaining a player you picked early for sentimental reasons rather than current merit. Make captaincy the final decision of every team build, and give it the same careful attention you give to the other ten picks combined.

A final captaincy trap is overreacting to a single bad result. Every captain pick, even a well-reasoned one, will fail regularly, because cricket is volatile and one good delivery can end an innings. The mistake is to abandon a sound captaincy process after one failure and chase the player who happened to score big last match. Instead, judge your captaincy choices over ten or more matches: if your process picks are beating the average captain score over that sample, the process works and the failures are noise. Patience with a good process is itself a skill, and it is one that separates steady rank climbers from players who lurch from one hot pick to the next.