▲
Read the conditions guide
Pitch, dew, wind, and overhead lights change everything. The conditions guide covers the inputs that decide fantasy points before skill does.
Pitch & weather →
Prediction Framework · Evergreen Reference
What Toss, Pitch and Weather Actually Do to a Fantasy XI and Captain Pick
A pre-toss fantasy team is a sketch, not a selection. The five questions that decide between a working XI and a losing one are the playing XI itself, the toss call, what the pitch does in the second innings, what the dew forecast says about grip, and which player on the card will still be touching the ball at the death. Each answer is short. Read them together and the captain choice writes itself.
The frame
Why the question is not who is in form
Most fantasy cricket advice begins with form. Form is a lagging indicator: it tells you what a player did on surfaces that no longer matter. A fantasy XI is a forecast about the next three hours, and the inputs that move a forecast most are not career averages. They are the five things that change between morning inspection and the toss: which eleven players are actually on the field, which captain calls bat or bowl, how the strip behaves under floodlights, whether the outfield will sweat, and who on the card is going to bat or bowl in overs 17 to 20.
The five inputs interact. A flat deck with 60 percent dew probability is not the same match as a flat deck with no dew. A green seamer under cloud cover is not the same match as a green seamer under a baking afternoon sun. A captain who wins the toss at a slow turner is not the same captain as one who wins the toss at a flat venue with heavy dew. The framework below is the order in which the desk works through those interactions. It is the same order used for every prediction we publish, and it is the same order we recommend when readers ask how to lock their own XI.
The mistake the framework is built to prevent is the most expensive one in fantasy cricket: locking the XI at the team-sheet release, before any of the five inputs are known. A team-sheet release is a probable XI, not a playing XI. The probable XI carries information about role allocation and likely batting order, but it carries no information about whether the captain will choose to chase, how much dew will settle by the tenth over of the second innings, or whether the strip will grip for the slower bowlers once the lights come on. Locking the XI at the team sheet means locking a forecast before the forecast's own inputs are known. That is the failure mode the rest of this article is built to defend against.
Step one
Confirm the playing XI before you read anything else
The probable XI published an hour before the toss is the only document you should be working from before the toss itself. Once the captains walk out, the probable XI either holds or it does not. If it holds, your role weightings still need to be adjusted for the toss call, but the players themselves stay where they were. If it does not hold, every role weighting above has to be redone from scratch.
The reason the playing XI matters more than any other input is that a fantasy XI is a closed system. You carry eleven names through the entire match. A change to the playing XI at the toss, whether it is an extra seamer coming in for a spinner, a left-handed batter replacing a right-hander, or a wicketkeeper promoted up the order, is a structural change that ripples through every role weighting you built around the probable XI. A late change to the playing XI without reweighting the roles is the second most expensive mistake in fantasy cricket, after locking the XI at the team sheet.
Two checks matter more than the others. First, the wicketkeeper position: most fantasy points systems pay for catches and stumpings separately from batting points, and a change at keeper changes both the fielding-points line and the batting-order line. Second, the all-rounder at number five or six: the role of an all-rounder at five or six is to convert a half-start into a fifty with the bat and to chip in with two or three overs. A change in that slot, whether a like-for-like swap or a specialist batter for an all-rounder, moves both the batting-points ceiling and the bowling-points ceiling at once.
Step two
The toss is the first decision, not the first coin flip
At dew-prone venues, the toss call changes role weightings between roughly ten and thirty percent on a slow deck. That is the headline number the desk uses when readers ask how much the toss is worth. The actual swing depends on three things: how much dew is forecast, how abrasive the surface is, and how the captain reads the chase target. On a black-soil turner with no dew forecast, the toss call barely moves role weightings at all because both captains will take spin into account either way. On a red-soil deck with 70 percent dew probability and a 180-plus first-innings target, the toss call can flip the captain choice from a death bowler to a powerplay batter.
The toss is a decision, not a coin flip, for two reasons. First, the captain who wins the toss knows more about the pitch than the captain who loses it. The home captain has read the surface since the morning inspection, and the visiting captain has had the curator walk them through the grass cover. Second, the captain who wins the toss is choosing between two scenarios with very different probabilities, not two equally likely outcomes. On most T20 surfaces in the subcontinent, the chase is the higher-variance option and the bat-first option is the lower-variance one. The captain who picks the lower-variance option is also picking the option that fantasy XIs are typically built around.
What changes the toss reading is venue knowledge. A captain who wins the toss at the Wankhede in April under floodlights knows the dew will be heavy by the tenth over of the second innings and will bowl first. A captain who wins the toss at Chepauk in mid-May knows the surface will grip from ball one and will bat first. The reading of the toss is the reading of the surface, not the reading of the coin. A fantasy XI that treats the toss as a coin flip has already missed the most actionable piece of information on the day.
Step three
Pitch behaviour: read the strip, not the reputation
Most fantasy cricket advice treats pitch reputation as a fixed property of a venue. It is not. A pitch at the Wankhede in mid-March is a different pitch from the Wankhede in mid-May. A pitch at the Oval in late July is a different pitch from the Oval in early May. Reputation is the average of every match played at the venue across years, and the average is a less useful number for a fantasy forecast than the specific strip being walked on the morning of the match.
Length matters more than colour. A dry, abrasive surface shortens the innings; a green, moist one extends it. A black-soil turner will grip from ball one; a red-soil turner will grip from the tenth over onwards. The colour of the strip tells you what it is made of; the length of the grass tells you how much it will move. The two together tell you whether the role weights tilt to spin or to pace, and whether the batting-points ceiling is closer to 150 or 200.
The practical implication for fantasy selection is that the same venue can carry two different XIs across two different matches in the same week. A Wankhede match on a damp Monday morning strip is a different XI from a Wankhede match on a dry Thursday evening strip. A captain who locks the XI based on the venue's reputation is locking the XI based on a multi-year average that may not apply to this specific match. A captain who reads the strip at toss is locking the XI based on the only piece of information that matters today.
Step four
Dew and wind: the conditions that move the most points
Dew is the single biggest conditions input in T20 cricket. A dew probability above 60 percent at the toss flips the chase call. Below 50 percent, treat dew as situational rather than deterministic. The reason dew matters so much is that it changes which bowlers can grip the ball. Spinners lose grip in the second innings under heavy dew; quicks lose swing but retain pace; death-over variations become harder to control. The captain call moves with dew because the bowling attack that worked in the first innings is unlikely to be the attack that works in the second.
Wind is the underweighted input. A cross-wind at 15 kilometres per hour or above helps seam movement off the pitch, particularly for bowlers who angle the ball into the right-hander. A wind straight down the ground flattens swing and reduces the effectiveness of wobble-seam deliveries. Most fantasy XIs do not adjust for wind direction at all. The desk treats wind as a secondary input, relevant only when the speed crosses 15 kilometres per hour or when the direction is straight down the ground, but it is the kind of secondary input that separates a captain who pays attention from one who doesn't.
Wet outfields and rain are the third conditions input. A wet outfield reduces boundary length for the first six overs of the innings, which compresses the run-rate ceiling and tilts the role weights toward batters who can rotate the strike rather than batters who rely on boundary clearance. Rain delays truncate innings and reduce the available overs, which moves the captaincy lever toward players who bat or bowl in the powerplay rather than the death. A forecast of a 30 percent chance of a mid-innings rain delay is enough to change the captain pick from a death-overs bowler to a powerplay bowler.
Step five
Captaincy: pick the player who touches the ball in the highest-multiplier phase
Once the playing XI, the toss, the pitch and the conditions are read, the captain pick is a calculation, not a vote. The 2x multiplier on the captain is points amplification, not form judgement. The framework for choosing a captain is to find the player on the card who will touch the ball in the highest-density scoring phase and pick that player, regardless of how good they look in the form guide.
The highest-density scoring phase is overs 17 to 20 for batters, and overs 17 to 20 plus the powerplay for bowlers. A death-overs batter on a flat deck with no dew has a higher captaincy ceiling than a powerplay batter on the same deck because the run-rate in the last four overs is higher than the run-rate in the first six. A powerplay batter on a green seamer has a higher captaincy ceiling than a death-overs batter on the same surface because early wickets swing the run-rate more than late wickets. The role with the highest scoring density at this match is the role that should carry the 2x multiplier.
For vice-captain, the framework is different. The 1.5x multiplier on the vice-captain is small. The vice-captain protects a captain miss; the vice-captain does not double a probable. Pick someone whose probability of a strong return is at least 60 to 70 percent even on a quiet night, typically a top-order batter on a flat deck, or a powerplay seamer on a green seamer. The vice-captain is a probability bet, not a ceiling bet. A captain pick with a 50 percent ceiling and a vice-captain pick with a 70 percent floor is a more defensible combination than two ceiling picks with 50 percent floors.
Putting it together
How the five inputs combine on a single match
A worked example shows how the five inputs combine. Take a 7:30 PM T20 start at a subcontinental venue in late summer, with the probable XI published an hour before the toss. The probable XI carries a wicketkeeper-batter at four, a specialist all-rounder at six, and three seamers plus a wrist-spinner. The pitch report reads as a red-soil deck with light grass cover and a forecast first-innings score in the 155 to 165 band. The dew probability is 65 percent at the toss. The captain wins the toss and chooses to chase.
Read together, the inputs tell the desk to do three things. First, lock the XI after the toss, not before. The chase call and the dew probability both move role weightings on a slow deck. Second, drop one of the three seamers and bring in an extra wrist-spinner for the second-innings grip, but only if the bench has a wrist-spinner of the same quality. Third, captain the wicketkeeper-batter at four on the assumption that the chase will reach a tight finish in the last three overs and that the keeper-batter will be at the crease through the death.
The same five inputs at a different venue tell a different story. A black-soil turner under floodlights with no dew is a different XI entirely. The same probable XI carries the same eleven names, but the role weightings tilt toward the wrist-spinner in the bowling attack, away from the seamers, and the captain pick moves from the wicketkeeper-batter to the wrist-spinner because spin carries the middle-overs wickets on a turning surface. The framework is the same in both cases. The output is different because the inputs are different. That is the entire point of reading the five inputs together rather than reading them in isolation.
Common failure modes
Five mistakes the framework is built to prevent
The first failure mode is locking the XI at the team-sheet release. The team sheet is a probable XI. It is not a forecast. A fantasy XI built on a probable XI without waiting for the toss is a forecast built on inputs that have not yet been observed.
The second failure mode is treating the toss as a coin flip. The toss is a decision under uncertainty. The captain who wins the toss at a dew-prone venue has more information about the surface than the captain who loses it. The captain who wins the toss will also choose the lower-variance option on most T20 surfaces, which means fantasy XIs that ignore the toss are typically picking the higher-variance XI on a given match.
The third failure mode is reading the venue's reputation rather than the strip. A green seamer at a venue known for batting is still a green seamer. A turner at a venue known for pace is still a turner. The specific strip is more informative than the multi-year average for the venue. Fantasy XIs that build role weightings on venue reputation are typically over-weighting pace on a turner or over-weighting spin on a seamer.
The fourth failure mode is captain-by-form. The captaincy multiplier pays off on density, not form. A player in career-best form but batting at seven in a chase is a weaker captain pick than a player in average form batting at four on a flat deck. The captain multiplier amplifies whatever role ceiling the player carries at this match, not whatever role ceiling they have carried over the last six months.
The fifth failure mode is the post-mortem skip. Most fantasy players review their own XIs by score, not by role. The score line on a single match is a noisy signal; the role weightings are the actual decision. Reviewing the XI by role, asking whether the wicketkeeper-batter touched enough balls, whether the death bowler bowled enough overs, and whether the captain pick matched the multiplier ceiling, is the only review process that improves the next XI.
Limitations of the framework
Where the inputs break down
The framework is built around T20 cricket, and most of the underlying logic is calibrated for the formats where the role weightings are most extreme. In an ODI played at a flat venue with no dew, the death-overs density argument carries less weight because the chase has more overs to absorb a slow start. In a Test match, the framework is almost entirely the wrong tool. The role weightings move differently across five sessions, and the captain multiplier carries no points differential.
The dew forecast above 60 percent is reliable; below 60 percent, the probability is a softer signal. The desk uses two independent forecast sources and only treats the highest as a factor when both agree. A forecast of 45 percent dew probability from one source and 70 percent from another is closer to 55 percent than to either source on its own. Treat sub-60 dew forecasts as situational, not deterministic.
The pitch strip is a morning read. A pitch that looks like a flat track at 9 AM can turn into a turner by 4 PM if the sun bakes the surface and the grass cover dies back. A pitch that looks like a turner at 9 AM can flatten out under cloud cover by 4 PM if the grass cover stays alive. The framework is calibrated for the toss-time read, not the morning read. Treat the morning read as preliminary and the toss-time read as authoritative.
Next-step checklist
What to do in the ninety minutes before the toss
- Confirm the probable XI is still probable. A late squad change at the warm-up is the most common late disruption.
- Read the morning pitch report from two independent sources, ideally one venue-local source and one national source.
- Pull the dew probability from two independent forecast providers and only treat the higher one as a factor when both agree above 60 percent.
- Note the wind speed and direction for the first hour of the match. The cross-wind argument applies above 15 kilometres per hour.
- Shortlist three captaincy candidates before the toss, ranked by expected role-weighted ceiling under the toss decision you expect.
- Wait for the toss. Adjust role weightings for chase versus bat-first. Lock the XI. Pick the captain.
- After the match, review the XI by role, not by score. Where did the role weightings hold, and where did they fail?
Related reading
Carry the framework into a specific match
The framework above is a tool, not a verdict. To use it on a real fixture, pair it with the conditions guide, the fantasy tips desk, and the prediction desk's working view of the upcoming calendar. Each guide accepts the same frame: roles, points, context, captaincy.
◇
Fantasy team selection
Role-based shortlists, all-rounder strategy, and the deadline checklist before every match, built around the same five-input framework.
Fantasy tips →FAQ
Framework questions
Is form ever relevant to a fantasy XI?
Form is a lagging indicator. It tells you what a player did on surfaces that no longer matter. The five inputs in this framework are the leading indicators, what the player will face in the next three hours. Form should weight the shortlist inside a role, not replace the role weightings themselves.
How reliable is the dew forecast above 60 percent?
Dew forecasts above 60 percent probability at the toss are reliable. Below 60 percent, treat them as situational rather than deterministic. The desk uses two independent forecast sources and only treats the higher one as a factor when both agree.
Should the captain pick change if the toss is delayed?
Yes. A delayed toss typically means a curtailed innings, which moves the captaincy lever toward players who bat or bowl in the powerplay rather than the death. A 12-over chase is a different match from a 20-over chase, and the captain multiplier should be reweighted to match.
What if the playing XI is announced only at the toss?
A late XI announcement is not unusual for franchise cricket, but it compresses the time you have to reweight role allocations. Keep the role shortlist built before the toss and apply it to whichever XI lands. The framework still works. Only the time to apply it shrinks.
A prediction you can argue with
The desk publishes predictions the reader can disagree with
Every prediction card on this desk carries the same five inputs as the framework above. The reader can disagree cleanly, swap a player, and verify the delta against the next match audit. That is how the desk improves, and that is how the framework above was built in the first place.