How a player profile reads
Player profiles are short by design. The structure is fixed so you can scan a profile in 20 seconds before locking a captain pick.
- Team and role cell. Where the player sits in the role map (top-order anchor, finishing all-rounder, powerplay wrist-spin, etc.) and what their registered franchise is.
- Expected batting slot. The position the player typically bats in. Pre-toss deck-rotation notes are noted but not used in the profile.
- Bowling phase. Powerplay, middle, death, or a multi-phase role. The phase is the strongest predictor of fantasy points ceiling.
- Recent opportunity trend. Whether the role has expanded, narrowed, or stayed flat across the past six fixtures.
- Venue/opponent splits. Provided only when the sample size supports a meaningful split (≥ 3 innings for batting, ≥ 4 overs for bowling).
- Availability log. A dated log of injuries, rests, role shifts, and any franchise handle-confirmed statements.
Top-order batters — published profiles
| Player | Franchise | Role | Profile cell | Home advantage |
|---|---|---|---|---|
| Ruturaj Gaikwad | CSK | Batter · batting 2 | Top-order anchor | Chepauk + spin |
| Yashasvi Jaiswal | RR | Batter · batting 1 | Powerplay top-order | Sawai Mansingh |
| Shubman Gill | GT | Batter · batting 3 | Steady anchor | Narendra Modi |
| Virat Kohli | RCB | Batter · batting 3 | Cover-drive top-order | Chinnaswamy |
| Suryakumar Yadav | MI | Batter · batting 4 | Sweeper, 360° | Wankhede |
| Travis Head | SRH | Batter · batting 2 | Powerplay six-hitter | Rajiv Gandhi |
| KL Rahul | DC | Wicketkeeper-batter · batting 4 | Anchor + middle | Arun Jaitley |
| Sanju Samson | RR | Wicketkeeper-batter · batting 3 | Middle-order accelerator | Sawai Mansingh |
All-rounders — published profiles
| Player | Franchise | Role | Profile cell | Home advantage |
|---|---|---|---|---|
| Hardik Pandya | MI | All-rounder · batting 4 / death bowling | Finishing + death | Wankhede + dew |
| Ravindra Jadeja | CSK | All-rounder · batting 7 / powerplay spin | Spin + finishing | Chepauk spin |
| Andre Russell | KKR | All-rounder · batting 5 / death power | Finishing big-hitter | Eden Gardens |
| Glenn Maxwell | RCB | All-rounder · batting 5 / spin | Middle-order spin | Chinnaswamy |
| Sunil Narine | KKR | All-rounder · opening powerplay spin | Powerplay wicket-taker | Eden Gardens |
| Axar Patel | DC | All-rounder · batting 4 / powerplay spin | Steady all-rounder | Arun Jaitley |
| Marcus Stoinis | LSG | All-rounder · batting 5 / death | Finishing + power | IS Bindra |
Bowlers — published profiles
| Player | Franchise | Role | Profile cell | Home advantage |
|---|---|---|---|---|
| Jasprit Bumrah | MI | Pace · death | Death yorker | Wankhede + dew |
| Rashid Khan | GT | Wrist-spin · middle + death | Differential wicket-taker | Narendra Modi |
| Yuzvendra Chahal | RR | Wrist-spin · middle | Powerplay wicket-taker | Sawai Mansingh |
| Pat Cummins | SRH | Pace · powerplay | Test-match new ball | Rajiv Gandhi |
| Ravichandran Ashwin | RR | Finger-spin · powerplay | Spin control | Sawai Mansingh |
| Kuldeep Yadav | DC | Wrist-spin · middle | Spin differential | Arun Jaitley |
| Trent Boult | RR | Pace · powerplay | New-ball swing | Sawai Mansingh |
How the desk builds a profile
A profile is built from the public scorecard record, the franchise handle, the partner operator squad page, and the desk’s own interview notes when available. Splits are reported as a number, not a vibe — that means a sample-size threshold and a confidence label on every split. We never publish a “recent form” split that relies on three innings of evidence and call it a trend.
How to read a player profile
A profile is structured for 20-second scanning. The role cell tells you where the player sits in the team’s role map. The expected batting slot tells you where they bat in the order. The bowling phase tells you where they bowl. The recent opportunity trend tells you whether the role is expanding or shrinking. Splits are reported with sample-size thresholds so you can weight them.
Profile strength and where to use it
Profiles are strongest when they tell you where a role cell is in the team cycle (early season, mid-season, late season). They are weakest on transient role shifts — those belong to the partner operator squad page and the captain-watch frame.
Profile tagging and the desk’s coverage
Profiles are tagged by role (top-order, middle-order, all-rounder, bowler, wicketkeeper) and by franchise. The desk maintains tag-level feeds inside the editorial archive.
The fan side of profiles
A profile is structured for fan reading first. The fan reads the role cell to understand where the player sits in the team cycle. The fan reads the expected batting slot to understand where the player bats. The fan reads the bowling phase to understand where the player bowls.
The analytics side of profiles
Profiles are also structured for analytics reading. Splits are reported with sample-size thresholds. Trends are reported as expansions or contractions of role, not as win-rate predictions. Availability logs are timestamped.
Profile limits
Profiles do not predict captain value. Profiles do not score against contest size. Profiles do not replace the captain-watch frame. Profiles are a working reference; the reader decides what to do with them.
The profile format in detail
The desk maintains one profile per active player on every franchise’s registered squad. Profiles cover batting position, bowling phase, recent opportunity trend, venue/opponent splits where the sample supports it, and the availability log. Profiles refresh weekly during the IPL season.
The profile strength in detail
Profiles are strongest when they tell you where a role cell is in the team cycle (early season, mid-season, late season). They are weakest on transient role shifts — those belong to the partner operator squad page and the captain-watch frame.
How to apply a profile to your XI
Read the role cell first. Read the expected batting slot second. Read the bowling phase third. Read the recent opportunity trend fourth. Splits are reported with sample-size thresholds. Lock your XI before the platform deadline.
What profiles do not cover
Profiles do not predict captain value. Profiles do not score against contest size. Profiles do not replace the captain-watch frame. Profiles are a working reference; the reader decides what to do with them.
The profile discipline
The desk maintains one profile per active player on every franchise’s registered squad. Profiles cover batting position, bowling phase, recent opportunity trend, venue/opponent splits where the sample supports it, and the availability log. The discipline protects the editorial independence of the desk.
How to read a profile
Read the role cell first. Read the expected batting slot second. Read the bowling phase third. Read the recent opportunity trend fourth. Splits are reported with sample-size thresholds. Lock your XI before the platform deadline.
Profile audit
The desk audits the published profiles quarterly. The audit verifies each profile against the partner operator’s published squad page. The audit notes material changes inside the corrections pathway. The audit cycle is part of the desk’s quality signal.
Closing thoughts on profiles
Profiles are working references, not captaincy picks. The desk publishes the profile with a verification reviewer name and a corrections pathway. The desk’s role is editorial.
The profile discipline final
The desk maintains one profile per active player. The discipline protects the editorial independence of the desk. Profiles are working references, not captaincy picks. The desk publishes the profile with a verification reviewer name and a corrections pathway.
Closing on profiles
Profiles are working references. The desk publishes the profile with a verification reviewer name and a corrections pathway. The desk’s role is editorial reference.
