Teams and players is the part of fantasy cricket where the squad-list trivia stops helping and the workload notes start mattering. This hub is built around three questions: who is in the squad, who is in form, and who is going to play this match.
Squad depth and the rotation problem
The most useful fantasy question is not "who is the best batter on this team" — it is "who will the team actually pick on this surface". Squad depth charts are how you answer it: the third seamer is rarely the best seamer, but the third seamer plays more matches.
Batting profiles
An opener is not the same pick as a middle-order anchor or a death-overs hitter. The role on the team sheet shapes the role in your XI: openers carry powerplay bonuses, middle-order anchors carry fifty-point ceilings, death-overs hitters carry six-hitting bonuses.
Bowler workload
Workload is the most under-discussed signal in fantasy. A seamer who bowled 30 overs across two formats in the last week is a different fantasy pick from a seamer who bowled four. Read the bowling workload guide before the deadline.
Role comparison
Comparing two players without comparing their roles is the most common analytical mistake. Two batters with the same season average can have radically different fantasy value if one opens and the other bats at number six.
Reading the squad list in detail
Read the squad list before every match. The squad list tells you who is available; the playing card at the toss tells you who will actually play. The difference between the two is the rotation; the rotation is the single most under-discussed signal in fantasy cricket. The third seamer is rarely the best seamer, but the third seamer plays more matches.
The squad list also tells you who is injured and who is being rested. A squad list that excludes a key player is a strong signal that the player will not play. Read the squad list in conjunction with the venue and the conditions; the squad list is the first input, not the only input.
Workload management across formats
Multi-format players carry the highest workload risk. A player who played a Test match, an ODI, and a T20 in the same week is a different pick from the same player with a week's rest. The workload note is the most under-discussed signal in fantasy; read it before the captain pick.
Workload management also affects the bowling line-up. A bowler who bowled 30 overs in the last week is a different pick from a bowler who bowled four. The workload column in the squad-depth chart is the most useful column for bowler picks.
Role comparison: how to do it
Comparing two players without comparing their roles is the most common analytical mistake. Two batters with the same season average can have radically different fantasy value if one opens and the other bats at number six. The role comparison is the first step; the stat comparison is the second.
The role comparison is built on three columns: the role on the team sheet, the conditions that suit the role, and the recent form in the role. The three columns together produce a research pick; any one column alone produces a name pick.
Fantoss questions on teams and players
Where do you source squad information? From the operator's official squad announcements, the franchise press notes, and dated news reporting. We never invent squad information.
How do you handle workload? Multi-format players carry the highest workload risk. We flag every multi-format pick in the tips guide.
What about young players? Young players are the highest-variance picks. They are also the cheapest differentials. We treat them as matchup-driven, not name-driven.
Use the squads in the IPL hub
The IPL hub tracks franchise squad depth and the rotation patterns that shape every contest night.
Squad depth charts: how to read them
A squad depth chart is a list of players ordered by role, with notes on recent form, workload, and the conditions that suit their style. Reading the chart is a five-minute exercise; making selection decisions from the chart is a 20-minute exercise. The chart is the input; the selection is the output.
The most useful column in the chart is the conditions column. A batter who scores on slow tracks is a different pick from a batter who scores on green tracks; the chart makes the distinction visible. The workload column is the second most useful; a bowler who bowled 30 overs in the last week is a different pick from a bowler who bowled four.
The rotation problem
The most useful fantasy question is not "who is the best batter on this team" — it is "who will the team actually pick on this surface". Squad depth charts are how you answer it: the third seamer is rarely the best seamer, but the third seamer plays more matches. Read the depth chart before the match, not after.
Workload notes across formats
Multi-format players carry the highest workload risk. A player who played a Test match, an ODI, and a T20 in the same week is a different pick from the same player with a week's rest. The workload note is the most under-discussed signal in fantasy; read it before the captain pick.
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.