Role security over reputation
Pick the batter whose role is locked, not the batter whose average looks best.
2026-07-25 — desk edition
Editorial Desk • Fantasy Cricket Knowledge
Conditions: Mostly cloudy, light breeze
Edition: Selection Tips
Editorial disclosure: independent • no paid placements
IND vs ENG · 3rd ODI — 14:30 ISTAUS vs SA · 2nd T20I — 18:00 ISTT20 World Cup · Asia Qualifier — 28 JulIPL 2026 · Mega Auction — 30 Aug
Selection Tips
Selection tips — the principles that survive a losing streak
Five principles we apply to every squad we build. None of them guarantee a win, but they do mean your squad makes sense on paper — which is the only edge a fan can build over time.
Section 1 · Principles
The five principles we use every match
None of these are tactics. Tactics change with format, contest type and the fixture. Principles do not.
Batting position matters more than batting average
A 35-run opener is more useful than a 35-run number five in most contests.
Overs allocation beats wickets-taken
The bowler who bowls the 19th over is more useful than the bowler with the better average.
Ownership use is a contest-type call
A player 80% owned is fine in small leagues. In large fields, a 12% owned differential is the edge.
Differential picks need an upside story
Never pick a differential just because the field is underweight on them. There must be an upside case.
Section 2 · Contest type
How the five principles change with contest size
The same squad makes very different sense in a 3-person league and a 1,000-person mega contest.
| Principle | Small league (3–10 entries) | Large field (500+ entries) |
|---|---|---|
| Role security | Pick the safest role, always | Pick safe roles for 9 of 11 slots, leave 2 for differentials |
| Batting position | Top order is fine | Top order for safety, middle order for one differential |
| Overs allocation | Powerplay bowlers are fine | Death bowlers matter more in large fields |
| Ownership use | Ignore — pick consensus | Look for one 12-20% owned pick with an upside case |
| Differential picks | Avoid | One or two maximum, with an upside story each |
Section 3 · Worked example
Applying the five principles to a single fixture
A worked example using the IND vs ENG 3rd ODI as the case study.
Worked example — IND vs ENG 3rd ODI
We apply the five principles to the confirmed XI and the contest type.
Role security: 9 of 11 picks go to players with a locked role. 9 locked
Batting position: 6 of 11 picks come from the top six. 6 top-order
Overs allocation: 3 of 11 picks are bowlers who bowl the death overs. 3 death bowlers
Ownership use: 1 pick is below 15% owned with an upside story. 1 differential
Differential pick: the chosen differential has an upside case written down. 1 case
Batting position: 6 of 11 picks come from the top six. 6 top-order
Overs allocation: 3 of 11 picks are bowlers who bowl the death overs. 3 death bowlers
Ownership use: 1 pick is below 15% owned with an upside story. 1 differential
Differential pick: the chosen differential has an upside case written down. 1 case
The squad is now explainable on paper. Whether it wins depends on the toss, the conditions and a lot of luck — but the explanation is what makes it improvable over time.
Section 4 · Common mistakes
Six selection mistakes that cost fantasy squads points
Mistakes are easier to recognise than principles. Here are the six we see most often.
- Picking by reputation, not by role. A big name with a vaguer role is worse than a less-famous name with a locked role.
- Ignoring the toss. If the captain bowls first, the chase-batter captain pick is wrong half the time.
- Over-loading all-rounders. Three all-rounders who do the same job is worse than one all-rounder and two specialists.
- Chasing last match’s haul. A 95-run performance is a data point, not a prediction. Treat it as such.
- Confusing bowling average with bowling value. Wickets in the death overs are more valuable than wickets in the powerplay. Check the role, not the average.
- Locking the lineup too late. Most platforms lock 2 minutes before the toss. The last-minute swap is rarely worth it.
Section 5 · Questions
Frequently asked questions
Are these principles guaranteed to win?
No principle guarantees a win. They reduce variance, explain the squad, and let you improve over time.
Which principle matters most?
Role security. The other four are ways to apply it.
Where do I see ownership numbers?
Most fantasy platforms publish a public ownership percentage per player per contest. We do not have a private feed — we read the public one.
Section 6 · Read next
Six neighbours from the desk
Topic ribbon
Read order
Captain and vice-captain matrix
The floor/ceiling comparison.
Points system explainer
What your platform rewards.
Match guides hub
Daily match preparation.
Predictions desk
Methodology-led previews.
App review methodology
Seven dimensions before you write about an app.
Responsible play controls
Deposit limits, time-out, self-exclusion.
Editor’s pick
Fantasy Cricket Selection Tips & Principles
The desk is open. Pair this page with the match checklist in your hand and the conditions report on a second screen.
Take the next step
Two ways to read more from the desk
Either way, the editorial reading stays the same — what we publish on this page is the same reading we publish everywhere else on CricketChallenge.
Extended reading · desk notes
Notes the desk keeps while writing this kind of page
A working record of the editorial decisions behind the page. Not a feature. Not a paid placement. Just the way the desk thinks about a page like this one.
Every page on CricketChallenge is written by an editor and reviewed by a second editor. The first editor writes the draft; the second editor checks the sources, the dates and the tone. The review is logged. When the second editor approves the page, it moves to publication. If the second editor asks for revisions, the revisions are logged with the date and the rationale.
The first decision the desk makes for any page is what the page is for. A captaincy page is for a reader who needs to decide between two captain picks before the toss. A points-system page is for a reader who wants to understand what their platform rewards. A responsible-play page is for a reader who has decided to set a deposit limit. Each page has a single job. Pages that try to do two jobs at once tend to do both badly, so we keep each page focused on a single reader need.
The second decision is the evidence key. Every preview on the desk carries a confirmed / probable / unknown tag. Confirmed facts come from the captains' press conference, the playing-card announcement or the league office. Probable facts come from two independent sources or one named beat reporter. Unknown facts are those we cannot verify from any reliable source. We never publish the same confidence for an unverified rumour as for an official squad announcement. The evidence key is on the page; the rule is that the reader can see what kind of evidence we are relying on.
The third decision is the date. Every page carries a last-updated stamp. The stamp is the date the most recent editor reviewed the page. It is not the date the page was first published, and it is not the date the page was created. It is the date a human editor last reviewed the page for accuracy, sourcing and tone. If a reader sees a page with an old date stamp, they should treat the page as one that needs review.
The fourth decision is what we will not publish. We do not publish rumours as news. We do not publish a story that names a player without verifying the source. We do not publish an offer that we cannot verify against the platform's own page. We do not publish a piece of editorial coverage that has been paid for. Each rule is enforced by the desk, not by a separate compliance team. The editor who writes the piece is also the editor who decides whether it stays.
The fifth decision is what we publish when we are uncertain. When the editorial team does not have enough verified information to publish a story, we do not publish the story. When the editorial team has some information but not enough to confirm a fact, we publish the fact with the probable evidence key and we mark the date. When the editorial team has a confirmed fact that contradicts a previously published fact, we update the previously published fact and add a correction note.
The sixth decision is how we work with readers. If a reader writes in with a correction, we review the correction against the primary source and update the page if the correction holds. If a reader writes in with a story tip, we review the tip and decide whether the story is worth writing. If a reader writes in with an editorial enquiry, we reply within five working days. The contact page on this site is the working channel.
The seventh decision is how we maintain editorial independence. Where affiliate links are present on the site, the link is labelled 'Visit partner — affiliate link' and the affiliate disclosure is on the page. Where the partner programme would benefit from a piece of editorial coverage, the editor who writes the piece decides what the piece says. The partner programme does not see the draft before publication. The partner programme does not have a veto over the published piece.
These decisions are the editorial standard we hold ourselves to. They are not negotiable and they are not relaxable. The reader can hold us to them by reading the page, checking the date stamp, checking the evidence key, and writing to us when something is wrong. If you have read this far, you are probably the kind of reader we publish for.