Fantasy tips: how to think about selection

Strategy explainers for fantasy cricket readers who want to improve their own decision-making. Not tip sheets — frameworks. The aim is for the reader to walk away with a defensible model, not a borrowed team.

What this hub is for

The fantasy tips hub is a collection of strategy explainers — captaincy frameworks, credit allocation logic, role-stability notes, common mistakes, and the four-factor checklist our desk uses before publishing a call. The hub is durable across tournaments. Pieces here are updated when the underlying principle changes, not when the fixture list changes.

Captaincy frameworks

There are three captaincy frameworks a fantasy selector can use. The floor framework prioritises the player with the highest expected score at low variance — usually a top-order anchor with a settled role. The ceiling framework prioritises the player with the highest upside — usually a powerplay or death-overs specialist. The matchup framework prioritises the player whose role is best suited to the specific opposition's bowling or batting pattern.

Each framework produces a different captain pick. The desk's default in close contests is the floor framework — it underperforms the ceiling framework only when the conditions read is unusually clear. Our published captain-case tables always include a conservative case (floor) and an aggressive case (ceiling).

Credit allocation

Credit allocation is the most-used decision in fantasy selection. Getting the captain pick wrong by 10% loses less than getting credit allocation wrong by 5%, because the credit budget compounds across the side. The desk's working heuristic is to spend 60-65% of the credit budget on seven positions (top-order bat, wicketkeeper, three bowlers, an all-rounder, and a sixth-bowler credit), with the remaining 35-40% spread across the riskier upside slots.

Role stability and ownership

Role stability is a better predictor of fantasy output than recent form. A player with a settled role will return floor value even on a bad day; a player whose role is contested can return zero on a bad day even if their recent scores are high. Ownership use — the gap between your pick and the field — is a separate axis: high ownership on a settled-role pick gives you nothing; low ownership on a contested-role pick is a coin flip.

The desk's working rule: do not pick players whose role is contested in this fixture, regardless of recent form. Pick players whose role is settled, even if the upside feels lower.

Common selection mistakes

The five mistakes we see most often in reader-submitted teams: (1) chasing last match's top scorer, (2) over-stacking one side of a fixture, (3) ignoring credit allocation to chase two premiums, (4) picking on reputation rather than role, and (5) failing to check whether the venue's conditions actually support the role they are relying on.

The four-factor checklist

Every selection the desk makes passes through four checks: role confirmation (did the player actually play their role last match?), conditions fit (does the venue and opposition support the role?), workload and risk (is the player fresh?), and selection logic (within credit constraints, is this player the right fit?). If any of the four fails, the player is dropped from the desk's working team — even if their season average is high.

Reading our guides vs reading picks

The guides hub is for frameworks. The predictions desk is for scenario reads. The match desk is for fixture-specific coverage. Reading all three gives you a defensible model; reading only the predictions gives you borrowed picks. We encourage readers to spend more time in the guides hub and use the predictions desk to stress-test their own working team.

Why we focus on role, not form

The desk's strongest finding over two seasons of tracking role logs is that role stability is a better predictor of fantasy output than recent form. A player with a settled role will return floor value even on a bad day; a player whose role is contested can return zero on a bad day even if their recent scores are high. The implication for selectors is to filter on role first, then on form, then on matchup. Filtering in the opposite order produces teams that look strong on paper and underperform at the deadline.

This is counter-intuitive because form is the easiest signal to find. Every scorecard lists last match's runs and wickets. Role logs require more digging — how many overs, at what stage, with what finishing pattern. The desk publishes role logs on the players hub so readers do not have to reconstruct them from broadcast data.

The mistake we see most often

The most common mistake we see in reader-submitted teams is over-stacking one side of a fixture. If the captain is on the team you have stacked, you double-expose yourself to that side's outcome. The desk almost never recommends more than three players from one fixture, and almost never recommends captain and vice-captain from the same team. The exception is a fixture where the conditions read clearly favours one side — and even then, three players is the cap.

The second-most-common mistake is chasing last match's top scorer. Last-match top scorers are a noisy signal: the sample is one match, the conditions may have been unusual, and the player's role may have shifted the next fixture. The desk's working rule is to wait for two consecutive matches before upgrading a player from 'watchlist' to 'pick'.

Frequently asked