Pitch reading is the most undervalued step in fantasy research. Most fantasy tips articles start with the player list; this one starts with the pitch. Read this guide before you open the player list, and the captain pick will be easier to defend at the deadline.
Step 1: colour and grass cover
A dry brown strip with little grass cover usually turns for spin from the second innings onwards. A green strip holds the ball up for seamers. The colour reading takes ten seconds; the impact on captain logic is the largest single shift you can make.
Step 2: cracks and footmarks
Cracks on a dry track indicate variable bounce. Footmarks at the batting-end crease indicate spin dominance. Both reward bowlers who can vary pace and angle.
Step 3: weather and dew
Hour-by-hour weather and dew forecast. Monsoon windows in the second innings erode spin grip and reward second-innings aggression. Treat the dew window as a captain pick, not a coin flip.
Step 4: the confirmed XI
The pre-match chatter rarely survives first contact with reality. The playing card at the toss is the only document that matters. Confirm it before locking your XI.
Step 5: the team sheet
Combine the pitch reading with the team sheet: a batting-paradise strip with two premier batters is a high-ceiling XI; a turning track with two premier spinners is a high-floor XI. The pitch reading frames the captain pick; the team sheet confirms it.
Putting it together
The five steps take ten minutes in total. They are the only signals that survive contact with reality on every match. Skip any of them and the captain pick is guesswork; complete all five and the captain pick is a research decision.
For the methodology behind these signals, read the match predictions hub. For the captain logic that turns the signals into a pick, read the fantasy tips hub.
Putting it together for next week
The most useful next step is to apply this guide to a specific contest night. Pick a match on the upcoming fixture list; run the three-pass habit on this guide; combine the captain logic with the points-system worked example; and write a one-line note for the next session. The note is the most useful single output of the research workflow.
The other useful next step is to revisit the related hubs. The match predictions hub, the fantasy tips hub, and the points-system hub are the three most-relevant sibling pages. Read them in the order suggested by the inline links; the order is part of the value of the guide.
What the editorial desk will publish next
The editorial desk revisits this guide every quarter and after every material event. A material event is a rule change, a season shift, a verified operator update, or a reader-reported error. The next revisit is dated at the top of the guide; the last-updated stamp is the most useful source of information about how recent the guide is.
The editorial desk also publishes field notes on the blog. The field notes cover specific matches, specific player situations, and specific captain picks. The blog is the most useful source of context for the long-form guides.
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.
The editorial desk's commitment
The editorial desk revisits this guide every quarter and after every material event. The commitment is to keep the guide accurate, useful, and free of fabricated facts. Where evidence is incomplete, we say so on the page and date the gap. The commitment is the most useful source of trust in the publication.
The editorial desk also commits to a fast corrections process. Reader-reported errors are reviewed within seven working days; confirmed errors are corrected within seven working days. The corrections process is the most useful source of trust in the publication.
What this guide does not promise
This guide does not promise winning teams, ownership percentages, or any rate of return. No legitimate source can promise any of those, and a guide that does is a tip sheet pretending to be editorial work. The promise this guide makes is methodology: a structured way to read the match, a captain logic that survives a season, and a verification checklist that protects your account.
The methodology promise is what makes this guide useful across many matches. A tip-sheet promise is useful for one match; a methodology promise is useful for a season. The methodology promise is the most useful single contribution this guide can make.
How to give feedback
Use the contact page to send feedback, corrections, or suggestions. Include the URL, the date, and the specific change you would like to see. The feedback inbox is the most useful source of improvements to the guide; the editorial desk reads every message.
Feedback is also the most useful source of new guides. The most-read guides on the site are the ones that address the questions readers actually ask. The feedback inbox is the most useful source of new editorial directions.
What the editorial desk will publish next
The editorial desk revisits this field note every quarter and after every material event. A material event is a rule change, a season shift, a verified operator update, or a reader-reported error. The next revisit is dated at the top of the field note; the last-updated stamp is the most useful source of information about how recent the field note is.
The editorial desk also publishes related field notes on the blog. The blog covers specific matches, specific player situations, and specific captain picks. The blog is the most useful source of context for the long-form guides; the long-form guides are the most useful source of context for the blog.
How to send corrections
If you find an error in this field note, 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 field note's last-updated stamp.
Corrections are part of the publication's value. A field note without corrections is a static document; a field note with corrections is a living document. The corrections process is the most useful source of trust in the publication.