This review of Fantoss is independent. We do not run contests, sell picks, or accept payment for coverage. The rubric below lists every factor we assess, the evidence we use, and the limits of our assessment. Read the methodology page for the filters we apply before publishing any review.
What we assess
Fantoss is an editorial publication. We assess it on six factors: editorial independence, fact-checking process, source documentation, navigation clarity, accessibility for new readers, and the responsible-play reminders we surface. We do not assess the underlying operator; we assess our own publication.
Feature audit
The features we audit on every guide: dated references on every fact, primary-source links where possible, second-editor challenge, navigation back to the parent hub, accessible typography, mobile-readable tables, and the responsible-play reminder that ends every guide.
Support process
Readers can reach the editorial desk through the contact page. We aim to respond within five working days. For reader-reported factual errors, we publish a correction within seven working days and update the guide's last-updated stamp.
Verdict and limitations
Fantoss publishes methodology, not picks. The verdict is that the publication is useful for new fantasy-cricket readers and for experienced readers who want a second opinion on the scoring math or the captain logic. The limits are the limits of independent editorial work: we cannot guarantee the operator you choose will publish the same rules we reference, and we cannot guarantee a winning team.
What a good review looks like in detail
A good review is specific, dated, and source-anchored. It does not publish a single numeric score; it walks through every factor it assesses, the evidence it uses, and the limits of the assessment. A good review is useful for readers who want a second opinion; it is not a substitute for the reader's own research.
A good review also revisits the rubric. The rubric should be revisited every quarter; the factors should be revisited when the publication changes. The rubric is the most useful source of information about what the review assesses.
What this review assesses in detail
This review assesses Fantoss as an editorial publication: the editorial process, the fact-checking rubric, the support process, the navigation, and the responsible-play reminders. It does not assess the underlying operator; it assesses our own publication. The assessment is dated and revisits the rubric every quarter.
The assessment also includes the publication's limitations. Limitations are part of the rubric; they are not separate from the rubric. The limitations section is the most useful source of information about what the review does not assess.
What this review does not assess
This review does not assess winning rates, ownership percentages, or any rate of return. We do not publish those numbers; no legitimate source can promise them. The review is built around methodology, not metrics.
This review also does not assess the underlying operator. The review assesses our own publication; the operator is assessed separately by readers using our verification guides. The separation is the most useful source of clarity about what the review covers.
Fantoss questions on the review
Who funds Fantoss? Affiliate commissions from outbound links to operators fund editorial work. Commissions never influence our reporting.
Does Fantoss publish winning teams? No. We publish methodology and dated verification.
How do I report an error? Use the contact page. Include the URL, the date you noticed the issue, and the source you believe is more accurate.
Read the methodology behind the review
The review is built on the methodology page: the filters we apply before publishing any guide.
What a good review looks like
A good review is specific, dated, and source-anchored. It does not publish a single numeric score; it walks through every factor it assesses, the evidence it uses, and the limits of the assessment. A good review is useful for readers who want a second opinion; it is not a substitute for the reader's own research.
What this review assesses
This review assesses Fantoss as an editorial publication: the editorial process, the fact-checking rubric, the support process, the navigation, and the responsible-play reminders. It does not assess the underlying operator; it assesses our own publication. The assessment is dated and revisits the rubric every quarter.
What this review does not assess
This review does not assess winning rates, ownership percentages, or any rate of return. We do not publish those numbers; no legitimate source can promise them. The review is built around methodology, not metrics.
How to read this page across a season
The most useful way to read this guide is to revisit it after every contest night. The first read is a foundation pass: the headline, the worked example, the verification checklist. The second read is a context pass: the matched-pair signals, the captain logic walk-through, the related links. The third read is a critique pass: find the strongest objection, write it down, and decide whether to revise your selection rule for next time.
The three-pass habit is what turns a guide into a season-long tool. Most guides are read once and forgotten; the guides that survive a season are read three times. The three-pass habit is the most useful single addition you can make to your research workflow.
What other readers found useful
The most-read sections of this guide are the worked example, the captain logic walk-through, and the verification checklist. The least-read sections are the methodology notes and the cross-references. If you are short on time, start with the most-read sections; if you have a full hour, read the methodology and the cross-references too. The reading order is part of the value of the guide.
The other readers who found the guide useful typically combined it with the sibling hubs. The captain logic walk-through on this page pairs with the captain multiplier math on the fantasy tips hub. The verification checklist on this page pairs with the app download guide. The reading order across hubs is the most useful source of additional value.
How to send corrections
If you find an error in this guide, use the contact page to report it. Include the URL, the date you noticed the issue, and the source you believe is more accurate. We aim to publish a correction within seven working days and update the guide's last-updated stamp.
Corrections are part of the publication's value. A guide without corrections is a static document; a guide with corrections is a living document. The corrections process is the most useful source of trust in the publication.
The discipline of writing your own notes
The most underrated habit in fantasy research is writing your own notes. After every contest night, write a one-line note that captures the most important thing you learned. The note should be specific, dated, and actionable. "Pick captain for floor" is too vague; "Bumrah on a green track at 7pm with dew expected was the right captain pick on 18 May" is specific enough to remember.
The note-taking habit is what separates a research-led XI from a name-led XI across a season. The notes accumulate; the captain logic refines; the contest-night decisions improve. The discipline of writing your own notes is the most useful single habit for fantasy research.
Common objections to this guide
Every guide on Fantoss is read by a second editor who writes the strongest possible objection. The most common objections are: the captain logic is too conservative; the role balance is too rigid; the verification checklist is overkill for an experienced player; the responsible-play reminders are patronising. Each objection is addressed in the guide; if you disagree with the response, write a one-line note and revisit next week.
The objection-and-response habit is what makes the guide useful for readers who already know the basics. The guide does not pretend to be the only source; it pretends to be the most useful source of structure. The structure is the most useful single contribution.
How this guide compares to operator-published material
Operator-published material is the authoritative source for the operator's own rules, terms, and eligibility lists. It is not the authoritative source for captain logic, role balance, or contest-night decisions. Fantoss publishes the second category; the operator publishes the first category. The two sources are complementary, not competitive.
Where this guide references an operator, we link to the operator's own published information for the authoritative record. We do not paraphrase ownership, company, or legal information. The operator's own page is the source of truth; Fantoss is the source of structure.
What to read after this guide
The reading order across the site is built around three passes. The first pass is the homepage; the second pass is the relevant hub; the third pass is the relevant money or trust page. The reading order is the most useful source of context for every guide on the site.
For the most useful next guide, follow the inline links at the bottom of this page. The links are part of the reading order; they are not filler. The reading order is what makes the site useful as a publication, not as a collection of pages.