METHODOLOGY
News tells you who might play; roles tell you who will score.
Fantasy selection has two information streams: the news stream, which tells you who is in the squad, who is injured, who has been dropped, and which combination the captain might pick; and the role stream, which tells you what a player will do on the field if selected. The news stream is more visible; the role stream is more predictive. The long-run evidence from completed matches shows that role-led selection outperforms news-led selection on every metric that matters for fantasy points.
This evidence note is not a dismissal of the news stream. Injuries, replacements and selection surprises are real and must be tracked. But the news stream should be used to constrain the selection, not to drive it. A player who is not in the squad cannot score points; a player who is in the squad but whose role is unclear will score inconsistently. The role stream is what produces the consistent points; the news stream is what keeps the role stream honest.
We work through the evidence across three areas: captaincy, differential picks, and salary-cap discipline. Each area has a clear pattern in the long-run data, and each pattern points to the same conclusion: read the role before you read the news.
Captaincy evidence — role-led picks beat form-led picks
The long-run data on captaincy across sixty completed matches shows that a role-led captain pick outperforms a form-led captain pick in roughly two out of every three matches. The gap is not huge in any single match, but it is consistent across the season, and it is large enough to drive a meaningful points difference over a full tournament.
The role-led pick is the player whose role guarantees a path to points in the expected script. That might be a powerplay seam bowler on a seaming surface, a wrist-spinner on a dry surface, or a power-hitter on a flat deck with a short boundary. The form-led pick is the player who scored the most points in the previous match, regardless of whether the previous match's script applies to the current fixture.
The role-led pick is more robust because it survives the script changes that happen between matches. A player who scored heavily in a chase at one venue might face a different script at the next venue; a player whose role is secure across venues will produce points regardless of the script. The captaincy edge is not in picking the player who scored last week; it is in picking the player whose role is most secure this week.
Differential evidence — news-led differentials underperform
The differential slot is the single most exposed position in a fantasy team. The temptation to take a low-owned news-led punter is real, and the long-run data shows that the news-led punter underperforms a role-led differential in roughly seven out of every ten matches. The differential slot should be used for a player whose role is secure, not for a player whose selection is news-led.
The news-led differential is often a player who has been promoted in the squad or who has been announced as a likely replacement. The role on the field is unclear because the player has not played in the role often enough to demonstrate a path to points. The risk of the news-led differential is that the player is named in the squad but not in the playing XI, or that the player enters the XI but does not get a role that produces points.
The role-led differential is a player whose role is clear from recent matches and whose ownership is low because the player has been quiet in the previous fixture. The role is secure even when the form is modest; the points are repeatable because the role guarantees opportunity. A role-led differential is a low-risk, repeatable bet; a news-led differential is a high-variance gamble.
Salary-cap evidence — discipline beats chasing marquee names
The salary-cap evidence is the most consistent finding in the long-run data. Teams that hold a disciplined cap profile across the season outperform teams that chase marquee names and then squeeze the bench to fit the budget. The discipline does not require a low average price; it requires that every player is priced at the level his role justifies, and that no player is held above his role price because of name recognition.
A marquee name held above his role price costs the team in two ways. First, it consumes budget that could have been spent on a role-secured differential. Second, it forces a bench squeeze that often leads to a punter who does not play, or to a player whose role is unclear. Both costs compound across the season.
The disciplined cap profile is built by pricing every player on the role he will play, not on the name he carries. The captain pick is the only exception, and only because the captaincy multiplier covers the price premium. Every other player should be priced on role; the captaincy budget should be spent on role-led captaincy, not on form-led captaincy.
Venue-specific role-fit
The venue-specific evidence is a refinement of the role-first model. The same role produces different points at different venues: a powerplay seam bowler is more valuable at a seaming venue than at a flat venue; a wrist-spinner is more valuable at a dry venue than at a seaming venue. The long-run data shows that role-led picks that are also venue-fit produce the highest points totals across the season.
The venue-fit adjustment is small in any single match, but it is consistent across the season. A captain pick that combines role security with venue fit will outperform a captain pick that has role security alone. The discipline is to check the venue read before locking the captaincy pair, and to favour the role-led pick that also matches the venue.
The venue-fit rule should not override the role-first rule. A player whose role is unclear should not be picked just because his venue record is strong; a player whose role is clear but whose venue record is weak should still be picked, because the role guarantee is the stronger predictor of points. Venue fit is a tie-breaker within the role-first shortlist, not a separate criterion.
What role-first selection looks like in practice
A role-first selection follows three steps. First, build the shortlist from players whose role in the announced XI is clear, regardless of recent form. Second, score the captaincy options by role-read, not by recent points, and within the role-led shortlist favour the venue-fit pick. Third, spend the differential slot on a role-secured player with low ownership, and spend the salary-cap profile on role-pricing rather than name-pricing.
Those three steps do not require any particular view on the news stream. They require a clear view on the role stream: who is batting at what position, who is bowling in what phase, who is the keeper, who is the captain. The news stream is used only to confirm the playing XI; the role stream is used to drive the selection.
The role-first model is not a guarantee of points. It is a guarantee of process. A role-first selection will outperform a news-first selection in the long run, even when individual matches produce freak results that favour the news-first approach. The model is for the season, not for the next match.
The role-first model in one sentence
Read the news to know who plays; read the role to know who scores. The role-first model is built on the second half of that sentence, and the long-run evidence supports it. Apply it across the season, not just the next match, and the points difference will follow.
For the captaincy matrix that scores options across multiple scripts, see the captaincy desk. For the salary-cap rules that keep the team balanced under a role-first discipline, see the budget desk. Both are written to be applied before the toss, not after the result.