Strategy guides: durable explainers for fantasy cricket

Evidence-led explainers, worked examples, decision tables, and glossary pages. The guides hub is built to outlast any single tournament — it is the durable knowledge layer underneath the live desk, the predictions desk, and the player desk.

What lives in the guides hub

The guides hub is a collection of durable explainers — pieces that do not change when the fixture list changes. Topics include captaincy frameworks, credit allocation logic, role-stability notes, powerplay and death-overs analysis, venue dossiers, and a working glossary of fantasy-cricket terms. Every guide is anchored to evidence and updated when the underlying principle changes.

How to read a guide

Guides follow a fixed format: answer-first introduction, a small working example, a decision table or framework, a checklist, and a glossary block where relevant. The aim is for the reader to walk away with a defensible working model — not a borrowed team.

Evidence-led explainers

Every guide in the hub is anchored to evidence — typically the desk's own role logs, venue dossiers, or matchup notes. The aim is for each piece to be useful even if the reader has never read any other page on the site. Where a guide depends on a number, the sample size, date range, and source are stated explicitly.

Worked examples

Each major framework in the hub has a worked example: a hypothetical team, a hypothetical conditions read, a hypothetical captain-case. The worked example is not a real team the desk picked — it is an illustration of the framework applied. The aim is for the reader to see how the framework handles a non-trivial input.

Glossary pages

The glossary covers terms the desk uses across its reporting — from 'powerplay overs' and 'death overs' to 'role stability' and 'ownership use'. Glossary pages are short, link out to the relevant guide, and are updated when the desk introduces a new term in its reporting.

How to read a guide

Guides follow a fixed format: answer-first introduction, a small working example, a decision table or framework, a checklist, and a glossary block where relevant. The aim is for the reader to walk away with a defensible working model — not a borrowed team. If a guide reads like a tip sheet, it has not been written correctly. Guides describe how to think; tip sheets describe what to pick.

Readers who are short on time should read the answer-first introduction and the decision table. The working example and the checklist are for readers who want to stress-test the framework against a non-trivial input. The glossary block is for readers who want to use the framework in their own writing.

Evidence-led explainers

Every guide in the hub is anchored to evidence — typically the desk's own role logs, venue dossiers, or matchup notes. The aim is for each piece to be useful even if the reader has never read any other page on the site. Where a guide depends on a number, the sample size, date range, and source are stated explicitly.

Guides are updated when the underlying principle changes — for example, when a tournament introduces a new rule that affects captain-case logic, the relevant guide is updated within days. Guides are not updated when the fixture list changes; the durable principle survives the fixture list.

What the glossary does not cover

The glossary covers terms the desk uses across its reporting. It does not cover generic cricket terminology that is widely available elsewhere — terms like 'cover drive' or 'yorker' are not in the glossary because they are not fantasy-specific. The glossary is for fantasy-relevant terminology — role stability, ownership use, ceiling framework, and the like.

If you want to suggest a glossary term, route it to the contact page. We add terms when they appear in our reporting with enough frequency to warrant a glossary entry.

Working with the worked examples

Worked examples in the guides hub use a hypothetical team and a hypothetical conditions read. They are not real teams the desk has picked, and they do not represent a recommendation. The aim is for the reader to see how the framework handles a non-trivial input — a fixture where the captain-case is genuinely contested, a credit allocation where the slot is genuinely close.

If you want to stress-test the framework against a real fixture, take the hypothetical team and replace it with your own working team. Then ask whether the framework's captain-case table produces the same pick your team uses. If it does, the framework is aligned with your read. If it does not, the framework is showing you a different angle — which is the value of a guide.

How guides relate to one another

The guides hub is interconnected — the captaincy framework guide links to the role-stability guide, which links to the credit-allocation guide, which links to the four-factor guide. Readers who want a full picture should read the hub in that order; readers who want a specific answer can land on the relevant guide and follow the inbound links from there.

The hub is updated when a guide's underlying principle changes. If a tournament rule change affects captain-case logic, the captaincy framework guide is updated and the relevant cross-links are refreshed. The hub's structure is durable; the content within each guide is the part that moves.

The glossary block

Each major guide ends with a glossary block that links to the relevant glossary page on the hub. The glossary is for terms the desk uses across its reporting — from 'powerplay' and 'death overs' to 'role stability' and 'ownership use'. The glossary pages are short, link back to the relevant guide, and are updated when the desk introduces a new term.

If you read a guide and a term is unclear, the glossary block is the first place to look. The desk's working rule is that any term used in a guide should also appear in the glossary, so the reader does not have to context-switch to a different page to understand the guide.

Frequently asked