Confirmed: the playing XI
The only fact on the page. If the prediction does not show the XI it relied on, the rest is speculation. Discount the read.
Evergreen explainer · Reading order, not a tip sheet
What a fantasy cricket prediction should actually answer before the toss
A standalone explainer for the window between team sheets and the toss. The reading order this desk follows, the questions a prediction has to answer to be useful, and the limits of any pre-toss call when a venue is unknown.
What the pre-toss window is for
A prediction has to answer four questions, in order
It is 6:30 pm at a floodlit venue. The team sheets have landed. The toss is an hour away. A prediction that reads "Team A looks strong and Team B has injuries" earns nothing in that hour. Every franchise team sheet looks roughly the same until the surface is read. The window between the team sheet release and the toss is when a prediction earns or loses its keep. What a fantasy prediction should actually answer before the toss is a smaller, more boring question than most previews attempt. It is a sequence. Who is playing. Where are they playing. What does the air and surface look like. And which role changes weight when the toss lands.
The first two questions are factual. The third is a read. The fourth is a conditional. Most published previews skip the conditional step because they want a captain pick on the page, and conditionality reads as indecision. The desk treats it the opposite way: a captain pick written without a "if the toss goes to X, switch to Y" line is a guess, not a prediction. This explainer walks through the four questions in the order they should be answered, with a worked example drawn from a generic pairing so the numbers stay hypothetical.
The playing XI is the only verified fact on the page
The team sheet, once printed, is the only piece of information on a fantasy cricket prediction that is not a read. Everything else downstream is interpretation layered on interpretation. Step one of the reading order is therefore mechanical: confirm the XI, then map each name to a role, and only then ask what each role is supposed to earn on this surface.
In a typical T20 fixture, a published XI rarely tells the desk anything surprising. The opening slots are obvious. The bowling combination carries clues: three seamers plus one spinner implies the surface has lateral movement, two seamers plus two spinners implies turn, and four seamers is almost always a death-overs side picking grip over variety. Reading the XI is mostly refusing to be distracted by it. The trap is treating probable-XI whispers from the day before as facts and building a captain pick around a name that did not start.
What the XI also encodes
Three signals hide in the XI that affect captain picks more than player reputation does. The position of an all-rounder (number four or five signals batting depth; number seven signals a bowler-first role). Whether a second wicketkeeper is travelling (a like-for-like swap if the first choice pulls out at the toss). Whether the four-overseamer combination is right-arm heavy or mixed (mixed combinations attack both sides of a left-right batting order, and that affects which batter is the captain target rather than which bowler).
What to keep on a separate sheet
Once the XI is verified, split the names into four small groups: powerplay batters, middle-overs batters, wicket-taking bowlers, and death bowlers. Each group carries a different captaincy question. Powerplay batters earn their points on dot-ball rate and boundary frequency against the new ball. Death bowlers earn theirs on wickets and dots in overs 17 to 20. Mixing the two groups when reasoning about a captain call is the most common pre-toss mistake.
Pitch reads translate only if the venue is honest
Pitch reads translate only if the venue is honest. Step two is the pitch read, and it is where most previews fail quietly. The pitch is not a generic surface type. A flat track with even bounce rewards high-tempo batting. A two-paced track rewards bowlers who can change pace. A turning track rewards spinners who already have wickets on this ground. A green-seam track rewards quicks with the new ball. Reading the pitch accurately depends on a second layer of data, the average first-innings score at this exact venue across the recent season, that previews usually borrow from a different surface entirely.
A worked example (hypothetical, drawn from a generic pairing). Suppose the venue is a batting track where the average first-innings score is in the 170s and the chasing side has won three of the last five. The role tilt is unambiguous. Pick powerplay batters, pick death-over hitters, avoid spinner-heavy bowler combinations, and weight pace-bowling all-rounders above spin-bowling all-rounders. Each of those calls has a different captaincy consequence than the same pitch read at a turning venue. A pre-toss prediction that does not name the surface type and the venue's recent first-innings average is signalling to the reader that the captaincy pick is mostly reputation.
The pace-spin split on this surface
A useful starting proportion is two pace quicks to one spinner when the surface has carry, and the reverse on a turner. The split is not deterministic. Bowler role, matchup against the batting order, and dew expectations all push it around. A prediction that does not name a starting proportion is asking the reader to invent the bowler read. A captain pick built on an invented bowler read is a captain pick the desk does not put on the page.
The first-innings target matters more than the chase record
Chasing is favoured in roughly half of T20 venues in a typical competition. The chase advantage is not evenly distributed. Some venues are flat enough that 180 is routine; at those venues, the second-innings batting order is the captaincy bet. Other venues are slow enough that 140 is competitive; at those venues, wickets in the powerplay decide the match and the bowling captain pick is the bet. Reading "the venue favours chase" without the average first-innings score is a soundbite, not a signal.
Dew, wind, overhead
Weather translates to captaincy, not to description
Step three is the weather, and it is the step where most previews treat a forecast as a forecast and stop. The forecast is not the signal. The signal is how the forecast changes the captain pick. Three weather variables matter for fantasy cricket: dew probability, wind direction, and overhead lights.
Dew probability above 60% flips the toss bet
Dew above 60% makes the second innings a chase. The ball stops gripping in overs 12 to 20, spinners lose their edge, and the captain pick migrates from a bowling all-rounder to a powerplay batter who will face the easier half of the chase. Below 50%, the dew is too speculative to override form. The 50-to-60% band is where the desk makes a separate call from the published forecast and trusts the closer source.
Wind changes boundary length more than swing
A cross-wind is more important than swing. A wind blowing straight down the ground from the bowler's end shortens effective boundaries for straight-bat shots. Boundary-hitting captaincy candidates earn 6 to 12 more fantasy points when the wind helps them. A wind blowing across the ground changes which side of the field is short, and which batter is hitting into it. This is a small read, but on a 170-run track, it separates two viable captain calls.
Overhead lights rarely move a captain call on their own
Lights matter when the white ball swings earlier. On a green surface under lights in the evening session, the new ball can move through the first three overs when otherwise it would not. A seam-bowling captaincy candidate becomes a slightly better captain pick under these lights. The effect is small, perhaps equivalent to the difference between a 30 and a 35 fantasy-point ceiling on the night. It does not, on its own, justify moving the captain off an obvious batting choice.
The captain pick is the last answer, not the first
Step four is the captain pick, and the desk writes it last because every earlier step narrows the field. A published captain pick written before the XI was confirmed is a guess. A captain pick written after the surface read but before the dew check is a conditional guess. A captain pick written after the XI, the surface, and the dew has been verified, with a contingency line for the toss. That is the start of a prediction worth reading.
The two-tier captain call this desk uses
Tier one: the captain pick that holds regardless of the toss. Built around a powerplay batter on a flat track or a death bowler on a green-seam track. Tends to be a high-floor rather than a high-ceiling call. Tier two: the captain pick that depends on the toss outcome. Built around a spinner on a turning track who bowls in the second innings (only useful if bowling first), or a powerplay batter who faces a dew-faded second innings (only useful if chasing). Both tiers are written on the page; the user picks whichever matches the toss.
Reading a captaincy note on someone else's page
A pre-toss captaincy note that names a captain, gives one sentence of role context, and does not name a contingency should be discounted by roughly 25%. A captaincy note with a specific contingency line is the only kind this desk treats as a working prediction. The contingency line is also the step most readers skip. Skipping it is the difference between a captain pick that justifies its slot in a fantasy XI and a captain pick that quietly loses points.
Signal-versus-noise checklist
Reading any prediction the desk has not written
Verified: the pitch read
A specific surface type and a recent first-innings average. Generic "batting-friendly" without either is not a pitch read.
Sourced: the weather inputs
Dew probability with a number, wind direction with a side, lights named or omitted with reason. A forecast bullet alone is not a weather section.
Conditional: the captain pick
A primary captain call and a contingent captain call for the toss outcome. A single-line captain pick is a guess, not a prediction.
FAQ
Questions the desk hears about pre-toss predictions
Why does the desk publish a captain pick conditional on the toss rather than a single call?
A single captain pick written before the toss assumes information that does not exist yet. The contingency line is a way of being honest about which information is missing. It also lets the reader lock the right captaincy once the toss and the chase-or-bowl decision land, instead of having to re-do the pick under time pressure.
How early before the toss should a prediction stop being updated?
The prediction should stop being edited once the team sheets are in. Any later update is a reaction to a warm-up rumour or a player pull-out, and the desk prefers to fold those into the post-toss call rather than chase moving news inside the prediction window.
What is the strongest pre-toss signal the desk tracks?
The matchup between the top of the batting order and the new-ball bowler combination. A new-ball combination that troubles the opponent's top three is the single largest predictable shift in captaincy points on a typical T20 surface. The signal is small in absolute terms (two or three fantasy points per game for the affected player) but consistent across matchdays.
Does this reading order apply to ODI and Test predictions?
It applies in principle but the weights shift. Test predictions lean more on the surface read and the bowling order; ODI predictions lean more on the dew probability and the chase. T20 is the format where the pre-toss reading window is shortest and the contingency line matters most.
Limitations
What this reading order cannot catch
Three classes of pre-toss information cannot be folded into the reading order above. Late injury news after the team sheet is printed (a fast bowler who warmed up at 80% capacity and is now visibly restricted). A net session where a player is batting or bowling in a style they have not shown publicly (rare but observable in 10% of pre-toss windows across a season). A confirmed playing XI that does not match the social media card the broadcaster displays (a deck-class reporting error, more common than the desk would like).
This explainer is bounded by the verified-source ladder used elsewhere on this desk: it uses generic, hypothetical examples for the worked read and avoids any claim about a current event, partnership, offer or verification timestamp. A reader who needs a venue-specific captaincy note for a particular fixture should follow the live desk at the predictions coverage area for the post-toss call.
What to watch next
The post-toss call is the one this explainer holds open
The reading order above fixes the value of a pre-toss prediction to four questions. Confirmed XI. Verified pitch. Sourced weather. And a conditional captain pick. The most useful thing to track next is the post-toss call, where the captaincy narrows to one name, the bowling order is fixed, and the prediction has to defend itself with points rather than with conditions. Anyone who can compare a pre-toss call against a post-toss call across a season has the raw material for a much sharper fantasy read than the one this explainer can give. The desk treats that audit as the working currency of the predictions coverage, and it is the standard readers should ask of any pre-toss prediction they take forward into their own XI.