Strand · Fantasy Decisions

How to make a fantasy decision without panic.

Fantasy reading is downstream of cricket reading. The fantasy decisions strand teaches you how to translate a clean read of the game into a clean side — without picking on instinct, panic, or the most-mentioned player on social feeds.

Desk news

Recent fantasy decision reading from the desk.

Match-eve frames, captaincy notes and historical fantasy case studies filed under Fantasy Decisions — newest first.

Inside the strand

Five rooms inside the fantasy decisions reading.

Each room is a self-contained piece of reading. Together they form a method — and the method is what the desk thinks matters, not any individual pick.

Captaincy

The captaincy lens

The captaincy multiplier rewards the read, not the player. The lens separates best player from best differential under captaincy, and treats them as different questions.

Open the captaincy math →

Salary

The salary-cap lens

The salary cap is a constraint. Reading it well means editing the side you want into the side you can afford — not adding the most-mentioned player and accepting the imbalance.

Read the points glossary →

Impact

The impact-player lens

The impact player is the most counter-intuitive piece of modern fantasy reading. The lens walks through when to use the slot, when to save it, and how to read the bowling order it implies.

Open team balance →

Differentials

The differential lens

A differential is a player whose ownership is low. Reading differentials well means asking what the ownership ratio is actually telling you — and when the consensus is right.

Read match reading →

Translation

The points-system translation

Every fantasy format scores the game differently. The translation piece walks through the most common format variations — captain multipliers, strike-rate bands, milestone bonuses — and how they change the read.

Open the glossary →

Limits

The session-length rule

One written session-length rule, set before the first contest of the night, is the rule that protects every other rule. The fantasy strand ends where the responsible-play strand begins.

Read the rule →

A piece of slow reading

The cognitive traps the desk tries to avoid.

Fantasy reading is prone to a small, predictable set of cognitive traps. The desk tries to name them up front — naming a trap makes it easier to spot in the moment.

The most common trap the desk has watched readers fall into is the recency trap — weighting the last match much more heavily than the innings before it.

A single innings of 80 off 52 does not make a player a captaincy pick. A single spell of 0/45 does not make a bowler a punt. The recency trap is what makes a side feel obvious in the moment and look ridiculous three matches later. The desk's response is the same as a careful reader's — re-read the last six innings, not the last one, before any captaincy decision.

The same logic applies in reverse. A player who had a quiet last match is not necessarily out of form; he or she may simply have been on the wrong end of a wicket cluster. The recency trap cuts both ways, and the desk tries to give equal weight to both cuts.

The second trap is the social-feed trap — weighting the most-mentioned player on social media as if mention-count were a proxy for expected performance.

Mention-count tells you what other readers are thinking. It does not tell you whether those readers are right. The desk's standing rule is to log the side before reading social media on match day, and only revisit the social feed once the side is locked. The rule is not sophisticated; it is just hard to keep.

Where the social feed does help — and the desk tries to be honest about this — is in the direction of the consensus. If the entire social feed has shifted from one bowler to another in the last hour, the shift is information, even if the conclusion is wrong. The desk treats mention-count as evidence about the conversation, not about the bowler.

The differential question, properly framed

A differential is a player whose ownership is low and whose expected points are at least league-average. The naive framing — pick the lowest-owned player who will perform — is usually wrong, because performance is what the consensus is already pricing in.

The better framing is the inverse — ask why the consensus has priced this player low, and whether that reason is justified. If the reason is justified, leave the player alone. If the reason is unjustified — and the desk tries to do the work of telling which is which — then you have your differential.

The salary-cap edit, not the salary-cap add

The most common salary-cap mistake the desk has watched is the cap-add — taking the most-mentioned player, paying the salary, and then trying to fit the rest of the side around them. The cap is rarely the binding constraint in that framing; the imbalance is.

The cap-edit framing is the inverse — start with the side the read says you want, then ask which two or three players you can drop down to a cheaper equivalent without losing the read. Most sides get better in the edit, not the add.

Editor's invitation

The fantasy read ends where the responsible read begins.

The fantasy decisions strand is editorial reading — slow, deliberate, and built around your own read of the game. The next room is the match reading strand; the responsible-play strand is the guard-rail.

Open match reading Read the responsible-play rule
Play now