A complete workflow for picking a fantasy cricket squad every match: roles, salary caps, points math, captain multiplier logic, and the picks desk’s evidence-led methodology. Read it once, use it for the whole season.
Fantasy cricket rewards discipline, not tips. The desk’s workflow is split into five steps that anyone can follow from the first match of the season.
The fantasy cricket workflow is not a single secret. It is five steps executed in order, every match, by every picker who wins more than they lose. Pickers who skip steps blame variance; pickers who follow steps build a sample large enough to win.
Each step is explained in the sections below, with the role math, the salary cap math, the captain multiplier logic, and the late-swap checklist. Read it once, run it for every fixture, and adjust once or twice per season as the format changes.
Most squads are built by reputation. Winners are built by role. The 11 splits into wicketkeeper, top-order batter, middle-order batter, all-rounder, and bowler — and each role has a different points-per-credit expectation.
The highest points-per-credit role in T20 because of stumpings and catches behind the stumps. Pick on glovework first, batting second.
Anchors who bat in the powerplay. Highest individual ceiling but also highest volatility. Choose two anchors + one aggressive opener.
Accumulator role that gets you through a collapse. Look for batters with 25+ ball innings history in the role.
The second-highest points-per-credit role. Pick all-rounders with confirmed 4-over bowling quotas, not part-timers.
Death-overs specialists and powerplay wicket-takers score heavily. Spend credits on the bowlers, not on the role label.
On some platforms, a 12th slot substitutes into your XI based on toss. Treat the impact slot as a hedge, not a captain alternative.
A 100-credit budget over 11 players. Allocate by role scarcity, not by reputation. The exact split varies by format and operator.
Your captain (2x) carries the squad. Your vice-captain (1.5x) is your hedge. The desk publishes a captain and VC call for every preview.
Always verify the published points table on your operator’s site before lock. The numbers below are typical for the dominant T20 platforms.
| Action | Points | Notes |
|---|---|---|
| Run scored | 1 pt | Strike-rate bonuses apply at 130+ / 150+ |
| Boundary bonus | 4 pts | Plus the 1 pt per run |
| Six bonus | 6 pts | Plus the 1 pt per run |
| Wicket (bowler) | 25 pts | LBW and bowled count |
| Dot ball (bowler) | 1 pt | Death-overs bowlers collect heavily |
| Catch | 8 pts | Slip and outfield both count |
| Stumping | 12 pts | WK-specific scoring |
Every match preview from the desk is paired with a five-point late swap checklist. Run it 90 minutes before the contest locks.
The late swap window opens when both teams publish their playing XIs. Most operators allow a single swap (or unlimited on some contests). Use it surgically.
Start with fantasy cricket selection by writing down the items that can change: role security, scoring routes, credits, and captain multipliers. A board built before toss keeps the first attractive name from becoming an automatic selection. It also makes uncertainty visible instead of hiding it inside a confident sentence.
Use recent scorecards, confirmed XIs, venue use, batting position, and bowling phase. Add the source time beside every note, because a correct update from yesterday can become wrong after a squad change. The aim is a record another picker can follow, not a verdict that depends on memory.
A player scores through opportunities, not reputation. For fantasy cricket selection, estimate balls faced, overs bowled, fielding access, and the probability of completing the expected role. A lower-credit player with stable volume can outrank a star whose position moves from match to match.
Separate floor from ceiling. Floor comes from secure participation; ceiling comes from wickets, boundary volume, catches, or multipliers. Use both rather than asking only who has the highest recent score.
Conditions alter how role security, scoring routes, credits, and captain multipliers should be weighted. A dry surface can extend a spinner’s wicket window, while dew can reduce grip and improve chasing batters. Rain can shorten the match enough to increase the value of top-order access and new-ball overs.
Record the forecast as a range and update it close to toss. A venue label is not enough: fresh surface, used strip, boundary side, wind, and match time can produce different selection priorities at the same ground.
A proposed squad stays provisional until official lineups arrive. Check recent scorecards, confirmed XIs, venue use, batting position, and bowling phase. If a player is absent, moved down the order, or listed only as a possible substitute, rebuild the opportunity map rather than making a direct name-for-name swap.
The most useful late update says what changed and why it matters. “Player out” is incomplete; note who inherits the batting position, overs, or fielding role. That second-order effect often creates the better pick.
Captaincy should reflect the match scenarios in which the player remains involved. For fantasy cricket selection, a role spanning two disciplines can cover more outcomes, while an opener may own a larger single-phase ceiling. Match the multiplier to contest size and confidence.
Use a stable 2x option when the objective is a strong median score. A differential needs a genuine opportunity edge for the 2x tag; low expected selection by itself is not enough. The vice-captain can hedge a different match script.
Write each uncertain item beside the squad: famous names without current roles, unconfirmed XIs, and one-match form. Give it a practical response such as hold, swap after toss, reduce multiplier exposure, or avoid. That turns caution into an action rather than a generic warning.
Prediction quality improves when a desk records what it did not know. Review the log after the match and ask whether the error came from bad reasoning, missing information, or normal cricket variance. Only the first two require a process change.
Plain-English answers to the questions that show up most in our inbox.
Free-to-play contests run on every major operator. They are real contests with real points math — the only difference is that the prize pool is small or non-existent. Use them for the first two weeks to build confidence before depositing.
Your captain’s points are doubled (2x); your vice-captain’s points are multiplied by 1.5x. Pick the captain from the role with the highest expected points-per-credit; pick the VC from a role-stable accumulator.
Most squads run 5-7 from one side and 4-6 from the other. Going 8-3 is high-risk unless you have a strong captain differential.
No. You need to read the role math, the salary cap, the points system, and the captain logic. Watching helps, but the picks desk’s workflow is designed for pickers who watch selectively.
Head-to-heads reward consistency. Mega contests reward differentials. Small contests (10-50 entries) reward balanced squads. Match the contest to your confidence and your squad shape.
Expected points divided by salary. A 9-credit batter expected to score 45 has a 5.0 ratio; an 11-credit batter expected to score 50 has a 4.5. Spend where the ratio is highest.
Yes, on platforms that offer it. The impact slot substitutes in based on toss. Treat it as a hedge — pick a player who gains from toss impact (e.g. a death-overs bowler in a dew game).
On the operator’s official site under Help or FAQ. Always verify before lock — points tables change between seasons.
Captain (2x), vice-captain (1.5x), and the differential that wins mega contests. Updated after toss.