Live desk Updated 25 Jul 2026 · India · 18+

Match preview desk — conditions first, form second.

Every preview on this desk names its evidence: venue scoring ranges, recent player workload, role allocation, weather where it materially affects play, and toss impact. Where a piece of evidence is unverified or contested, we say so in the article and update it when confirmed.

Cricket captain at toss with team sheet, editorial sports photograph
Preview desk · Live
COVER · Preview desk · sample match read
Preview desk · Live

The full read.

The five-point preview template

Every preview published on this desk follows the same five-section structure, in order. The order is deliberate: conditions outrank form, and form outranks reputation. Reading the sections in any other order produces a less reliable captaincy read.

  • Venue history. Last 6 matches at the ground, range of first-innings totals, how the surface behaved on day two. Where the venue is hosting its first game of the season, the read falls back on the surface-type read (flat, two-paced, green) and the curator's history.
  • Boundary dimensions and square. Square boundaries of 60 metres punish mishits differently to 72-metre straights. A power hitter's value changes by roughly 8–12 expected fantasy points per match between a short square and a long one. The pre-match venue read includes this calculation.
  • Weather and dew outlook. Hourly forecast, not day's average. Dew at the toss is worth 15–25 runs in the second innings; that single number changes the captaincy decision more than any form input.
  • Toss impact and matchup. Recent head-to-head clustering around bat-first wins is treated as a soft signal — your XI selection should mirror that lean, but only if the dew read supports it.
  • Role allocation and ownership. Who is locked in the playing XI, who is rotating, and what the public-contest ownership band looks like. Captaincy reads below 20% ownership are flagged as differentiation plays, with the downside named.

How captaincy reads are framed

Captaincy reads on this desk are written as probability framings, not verdicts. When we say "lean captain", we mean the read is leaning in that direction with the stated evidence — we do not promise a multiplier outcome. When the read is split (no clear lean), we say so and present the trade-off. Where a piece of evidence is unverified or contested, we say so in the article and update it when confirmed.

What a preview does not do

It does not name a guaranteed XI. It does not promise a winning team. It does not publish a win rate. Captaincy reads are a probability framing, not a verdict — your job is to do the same read for your own contest type and salary pool.

Read the how-to-play primer if you need the selection framework before applying it to a match read.

Affiliated — read disclosure
PLAY NOW