Every prediction on this desk comes with the four signals we used to make it — pitch read, dew factor, head-to-head, and opposition match-up. We tell you the conditions that would change the call. Read the desk's framing before you lock your XI.
The desk calls every match with a confidence level — High, Medium, or Low — and explains what would move the call up or down. We do not publish "lock of the day" superlatives. We publish reasoning.
The four signals are tuned for the IPL specifically: pitch read (curator comment, square turning, pace carry), dew factor (after 8 PM at Wankhede, Chinnaswamy, Eden, the chase is statistically the right side), head-to-head (last three match-ups, weighted by recent player presence), and opposition match-up (best batter against this bowling unit, best bowler against this batting order).
When all four signals agree on the same team, the call is High. When three agree, the call is Medium. When the signals split, the call is Low — and the desk publishes the disagreement rather than papering over it.
The DPL 2026 11th T20 preview weighs North Delhi's 209-run batting start against East Delhi's two opening losses, the Arun Jaitley surface and the two recent head-to-head wins for the Riders.
An IPL curator's pre-match comment is the single most predictive signal for a contest call. Watch the square outside the playing area. If the surface looks dry, with fine cracks, the spinners will come into the match. If the surface looks green with grass retained, the seamers dominate the powerplay.
Three quick visual cues to read a pitch before the toss:
A pitch read takes 90 seconds once you know what to look for. Most casual contestants never read it — they pick by franchise brand.
Across the eight-year sample of night IPL matches, the team batting second wins roughly 55% of matches where dew is forecast after 8 PM. The grass gets wet. The ball stops gripping. The spinners lose a turn that the dry first innings had. The outfield speeds up because the surface is slick. The chase becomes the easier side.
Counter-cases exist — Wankhede in early April can be dry with no dew even at 10 PM — but for the median IPL evening fixture the dew rule applies. Watch the local weather feed, watch the outfield under the first ten minutes of play, watch the ball behaviour in the second innings.
Rain reduces overs and changes the points calculus. A 5-over rain-shortened match flips the captain logic: differential power-hitters outperform anchor top-order; pace loses impact; all-rounders regain ground because every role earns points per ball bowled.
Across the IPL, the franchise-versus-franchise head-to-head stories are often tiny samples with massive roster churn. The desk weights head-to-head by player continuity: a player who's played in three of the last five match-ups has a meaningful data point. A franchise "history" without players present is essentially noise.
The way to use head-to-head is to look at recent individual match-ups: which batter in tonight's XI scored against which bowler in the previous fixture, and on what kind of pitch? That's the signal. Anything older than two seasons or with fewer than two roster overlaps is not signal.
The desk's heuristic: a player's last-five innings should have a 70% weighting, last-season a 20% weighting, career-aggregate a 10% weighting. Form decays fast in T20 cricket; career averages move slowly. The right mix weights form more than reputation, but still anchors reputation from below — so a top-order batter who has misfired in the last five innings is a downgrade candidate, not a drop candidate.
The flip-side risk is over-fitting to form. A bowler with three of his last five matches at flat Wankhede and one at Chepauk is not in form at Chepauk because the surface is different — he's in form against a specific batting order. Read the surface before you read the form.
Median fantasy points last five: 56. Recent strike rate at this venue: 174. Match-up favoured against left-arm spin. Vice-captain candidate in large contests.
Confidence: HIGH
Three wickets in two of last four match-ups against left-handers. Pitch reads square turn. Expected overs: 4. Bonus if the side loses early wickets.
Confidence: MEDIUM
Three sixes off the last ten balls faced. Owned by 8% of mega-contest entries. A captain-only pick if the contest rewards ceiling, not median.
Confidence: LOW
Across the last three IPL seasons' published picks, the desk's captain pick finished inside the top-3 fantasy scorers in 62% of matches when confidence was High.
The desk's match winner call (which side wins the match) was correct in 71% of matches over the last three seasons when all four signals agreed.
The desk's differential captain picks cleared top-0.1% in 14% of mega-contest entries last season — well above the random baseline of ~1%.
The desk publishes predictions in advance of every match-day. To back-check: open your notes from the same match-day, mark which signal you weighted highest, and compare against the published pick. If your reasoning tracked the desk's, you can take the calls into contests; if it diverged, you should explain the divergence to yourself first.
We do not publish a "results" leaderboard because the contest-level result depends on your full line-up, not just the captain pick. The metric we publish is signal-level accuracy: did the four signals, applied correctly, point to the right outcome? That is a prediction-level metric, contest-agnostic.
Fantasy cricket rewards readers who apply the framework, not readers who copy the pick. Open the points reference, the captain logic, and the venue notes — and make your own call.
