Predictions desk

Predictions — scenarios, not certainties

A prediction here is a scenario with conditions. If the conditions hold, this is what we expect; if they don't, we revise. We don't promise winners — we publish the reasoning and let the record show.

This week's scenarios

Each prediction is paired with the conditions under which it holds. Read both.

CSK vs MI · Tonight

Scenario: If CSK bat first and the surface holds turn as forecast, expect a measured total in the 165–180 range with significant middle-overs spin pressure.

Conditions: Toss winner bats first; dew below moderate; one spinner gets the full 4 overs in the middle.

Confidence: Strong indication

RCB vs SRH · Afternoon

Scenario: If RCB bat first on the flat Chinnaswamy square, expect a powerplay-driven total crossing 200, with the top-order ceiling boosted by short straight boundaries.

Conditions: Toss winner bats first; powerplay scoring rate above 9 RPO; no early cluster of wickets in overs 1–3.

Confidence: Confirmed

KKR vs RR · Tomorrow

Scenario: If KKR pick the extra spinner and Eden Gardens holds grip, expect middle-overs economy under 7 RPO and the match decided in overs 11–16.

Conditions: KKR combination includes two tweakers; toss winner bowls first; dew moderate to heavy.

Confidence: Strong indication

DC vs PBKS · Tomorrow

Scenario: If PBKS bat first and the Delhi surface holds grip, expect off-side power hitters to dominate middle overs and a total in the 175–190 range.

Conditions: PBKS open with their off-side pair; toss winner bats first; powerplay economy under 8 RPO.

Confidence: Strong indication

Matchup analysis with batter-bowler notes on a clipboard
Matchup analysis with batter-bowler notes on a clipboard. Source: editorial photograph, iplplaynow.

Player-specific scenarios

Where a single player's role or form drives a prediction, we publish it separately.

Jadeja's ceiling

If Jadeja bowls his full 4 overs in the middle on a turning Chennai surface, his fantasy ceiling jumps meaningfully. If he's used as a powerplay option instead, his ceiling drops. Watch the bowling order in the first innings for the answer.

Confidence: Strong indication

Head's powerplay

Travis Head's powerplay scoring rate is materially higher than his middle-overs rate. If SRH win the toss and bat first on a flat ground, expect Head to bat through the powerplay and accelerate after.

Confidence: Confirmed

Russell's role shift

Andre Russell's batting slot has shifted earlier this season — he's coming in at No. 5 instead of the death-overs slot. The implication: more responsibility, different match-up window, lower ceiling but higher floor.

Confidence: Strong indication

Cummins' powerplay

Pat Cummins' powerplay economy is the single biggest factor for SRH's bowling. If he keeps the new ball in good hands for two spells, SRH's ceiling rises. If he goes early, the middle overs become the swing factor.

Confidence: Confirmed

Accuracy log

How our predictions have held up

The accuracy log is published every Monday. It is the public record of what we got right and what we missed — not a marketing claim.

WeekPredictions madeHeldPartly heldMissed
Week 12 (last week)14932
Week 11161042
Week 1015852
Week 914932

"Held" means the prediction's primary scenario played out. "Partly held" means conditions were partly met and the prediction required adjustment. "Missed" means the scenario did not play out.

An analyst reviewing probability ranges on a screen
An analyst reviewing probability ranges on a screen. Source: editorial photograph, iplplaynow.

Reading the accuracy log

A prediction that holds is one whose primary scenario played out as forecast. A partly-held prediction required an adjustment because conditions changed mid-match. A missed prediction is one whose primary scenario did not play out.

The log is the single most honest page on the site. It's also where our predictions desk reads its own work back.

Reading predictions

How to use a scenario-based prediction

A scenario-based prediction is a conditional claim. If the conditions hold, this is what we expect. If the conditions don't hold, we revise. The conditions are published alongside the prediction; they're not hidden in the methodology section.

For fantasy readers, the practical use of a scenario-based prediction is to weight your captaincy order. A prediction whose conditions hold in 70% of fixtures is a safer captaincy frame than a prediction whose conditions hold in 30% of fixtures.

The accuracy log is the public record of how the predictions held up. We don't hide the misses. Where a prediction was missed, we publish the reason alongside the correction note.

Common prediction types

Five prediction patterns we use

Toss branch

The prediction depends on which captain wins the toss. We publish both branches and label which we think is more likely.

Matchup

A specific batter-bowler or bowler-batter matchup. The prediction is that the named player outperforms their average against the named opponent.

Conditions

The prediction depends on surface, dew, or boundary conditions. We publish the conditions and the prediction under each.

Role

The prediction depends on the role a player is given. We publish the role assumption and the prediction if the role holds.

Score range

A prediction of the match total, with a stated range. We publish the range, not a point estimate.

Player milestone

A prediction that a player reaches a milestone (50, 100, 3 wickets). The prediction is conditional on the player being in their expected role.

SponsoredView offer on partner site
Join the Game