Home › Predictions

Pre-match predictions built on five desk passes, not a single tip.

Our prediction desk produces scenario-led pre-match reads for fixtures across T20 leagues, ODI events, bilateral series, and Test cricket. Each read names the conditions, the squad, the role math, the matchup, and the captain scenarios we would consider.

How we read a fixture

Five desk passes per match.

Every pre-match read on this desk follows the same five-pass workflow so you can compare fixtures on the same axes. Replace any pass with your own research and the rest of the read still holds.

1
Conditions checkPitch type, weather, dew, floodlight timing, and any outfield constraint. We pull from venue reports, broadcast commentary notes, and primary weather services.
2
Squad verificationConfirmed XI once the toss is held. Before toss, we list the likely XI with the source we used.
3
Role mathExpected balls faced, overs bowled, fielding positions, captain multiplier fit. We publish the role inputs alongside the captain decision.
4
Matchup layerBowler-batter head-to-heads, left-right hand combinations, pace-spin balance. We link to scorecard data where available.
5
Decision summaryTwo or three captain scenarios, with risk notes. We never publish a single tipped outcome because research does not work that way.

Latest match predictions

Fresh fixture reads with likely playing XIs, pitch conditions and captain choices.

Scenario types

Three scenarios we publish before every fixture.

A scenario-led read names the conditions that would tilt a fixture in one direction, the role players most exposed, and the captain decisions each scenario implies.

A

Bat-first scenario

Read the pitch report. If the surface holds, captains go in with the chase. Powerplay aggression then matters more than death bowling.

B

Dew-adjusted scenario

Second-innings chases shorten under heavy dew. Bowl-first captains pick finger-spin; bowl-second captains bank on yorker length.

C

DLS scenario

Interruption math changes role demand. All-rounders who bat and bowl climb the points ladder under reduced-overs games.

Composed player near the boundary adjusting a batting glove
Scenario modelling

Three scenarios, not one tipped outcome.

A fantasy read is a model of how a fixture could play out. We publish three scenarios with explicit confidence bands so you can size your entry against the uncertainty, instead of paying for a guess dressed up as research.

Confidence band

Every scenario carries a low / base / high confidence band. The base is the read we would bet on; the low and high are the failure modes the captain choice has to survive.

Sensitivity test

Each scenario names the single input — dew, toss, wicket, role demand — that, if it moves, would invalidate the read. Sensitivity testing is what separates desk research from a hot take.

Decision revision

If the toss, pitch, or XI breaks our base scenario, we publish a one-paragraph revision before the deadline. Revisions are normal research behaviour, not a sign of error.

Uncertainty ranges

How wide the band is on any given fixture.

A captain pick on a flat Mohali deck has a tighter confidence band than one on a green seamer in Wellington. We publish the band width alongside every captain so you can read the size of your edge before you pay an entry fee.

Fixture typeTypical bandWhat widens itReader action
Flat deck, two balanced XIsNarrowToss, dew window, power-hitter formTake the primary scenario; size smaller entries
Spin-friendly subcontinent nightMediumDew intensity, wrist-spin matchup, outfield speedHold two scenarios; mix primary + differential
Seaming overseas Test day oneWideSession-one movement, overhead conditions, batting orderBank three scenarios; lower stake until day two read
DLS-threatened rain fixtureVery wideCut-off timing, par score, all-rounder role demandPause or reduce; do not pay into high-variance games
Debutant-heavy associate fixtureVery wideForm data gaps, role uncertainty, captaincy volatilitySkip; wait for at least two completed appearances
Pre-match checklist

Run this before every fantasy entry.

Before paying an entry fee, walk through this six-point check. Skip any item and you are gambling on instinct rather than research.

1
Pitch report readWhat surface behaviour did the curator describe? Does it match the venue history?
2
Toss impactDid the toss happen? If yes, what role demand does it imply?
3
Confirmed XI checkHas the playing XI been announced? Are your picks in it?
4
Captain scenario matchDoes your captain align with the primary or differential scenario?
5
Budget auditAre you within your weekly cap? Are you under your stop-loss?
6
Pause checkHave you taken this week's pause? If not, are you sure this is the right entry?
Reader FAQ

Questions on predictions.

Do you publish a single tipped outcome?
No. We publish two or three scenarios per fixture and never frame any of them as guaranteed. Research does not work that way.
How fresh is your pitch report data?
We re-pull pitch and weather data within 24 hours of the toss and update the read if conditions shift.
Do you adjust for dew late in the evening?
Yes. Dew is part of our conditions pass and is usually the largest single adjustment to the captain decision.

Move to the fantasy tips hub.

Pre-match reads work best when paired with the role-evaluation and captain-logic primers in our fantasy tips hub.

Editorial notice. Come Sports Picks is a research publication, not a contest operator, broker, or betting exchange. Nothing on this site is investment, legal, or financial advice. Fantasy cricket involves paid entry fees and the risk of loss; readers should be 18+ and play within their means. Read the responsible-play guide and your local regulations before participating.
Play now