How to play IPL daily fantasy · the read, not the slogan
A short, plain guide to the workflow. If you can read a cricket match preview, you can build a team. The rest of the work is just patience and a small set of rules you apply the same way every match.
Eight steps, in the same order, every match
1. Open the brief
Start with the match preview. Note the surface, the dew forecast and the probable XI.
2. Build the role list
From the probable XI, separate players by role: openers, middle order, all-rounders, spinners, quicks, wicketkeeper.
3. Filter by matchup
Drop any role that does not match the opponent or the surface. Be ruthless — small lists work better.
4. Check recent form
Look at the last 3–5 matches in the same role and phase. Career averages do not help.
5. Pick the captain
Use the captaincy test. Role stability, matchup, ownership profile. Pick the conviction, not the headline.
6. Pick the vice-captain
Second-highest conviction. The 1.5× multiplier matters in a small pool; the leverage matters in a large one.
7. Choose the contest
Small pools reward conviction, large pools reward differentials. Match the team to the contest.
8. Wait for the toss
The toss lands 30 minutes before the first ball. Be ready to adjust the XI, the captain and the contest.
What each role actually does on the field
Powerplay batters
Face the new ball, set the tone. High strike-rate variance, dot-ball exposure, and a ceiling that depends on the powerplay read.
Top-order accumulators
Batter through the powerplay and the middle overs. Lower strike rate, higher runs total, more captaincy candidates on batting surfaces.
Run accelerators
Bat from overs 7–15, accelerate into the death. Matchup dependent — spin or pace, depending on the side.
Multi-phase contributors
Bat in the middle, bowl two or three overs. The highest variance role — either pays off or doesn’t.
Powerplay and death quicks
New ball with the new ball, yorker at the death. The two extremes of the bowling role. Most points in the wickets and economy brackets.
Middle-overs control
Hold the run rate through the middle overs, take wickets in clusters. Matchup-driven, surface-driven, handedness-driven.
WK-batter
Fielding points plus a batting slot. The role is usually stable; the batting order is the variable.
The credit cap is a constraint, not a strategy
What the cap does
The cap forces a trade-off between star players and unproven picks. The trade-off is the contest, not the answer.
What the cap does not do
The cap does not pick your captain, your differential or your contest type. Those decisions are still yours.
How we use the cap
We start with the matchup read, not the cap. The cap is the final filter. The matchup is the first.
The honest version of the read
Fantasy cricket is a way to engage with the match, not a financial plan. The work is the read — the venue, the role, the matchup, the risk. The rest is small, careful decisions applied the same way every match.
What readers ask about how to play
Is there a single best team for every match?
No. The right team depends on the contest, the surface and the role read. The match preview shows the work that goes into the recommendation; the contest is the final filter.
What about the Impact Player rule?
The impact player is one substitution from a four-player bench, used at any point in the match. The choice usually reflects the role read — fourth seamer, batting substitute, spin option.
How important is the toss?
The toss is important but not decisive. The dew forecast and the pitch note matter more in the read; the toss decides which side of that decision you are on.
What if I lose?
Losing is part of the format. The post-match review explains what the read got right and what it got wrong, so the next shortlist starts from a clearer place.