The IPL changes shape every fixture. This hub tracks the version-of-the-tournament our desk sees, with weekly captain matrices, venue reads and ten franchise desks you can switch between.
Six windows into the 2026 schedule so you can switch between team and role in one read.
Tournament structure, schedule context, venue trends, ten franchise desks, latest match reports and weekly captain matrices — all written as independent editorial reads, not as a league-mandated feed.
We anchor every claim to a phase, a window and a sample size. The charts on this desk read phase-by-phase rather than season-aggregate so the captain signal actually moves across conditions.
Yes. After every match we publish a post-match audit, a captain matrix update for the next fixture and any corrections to projections made earlier in the week.
| Venue | Matches | Avg 1st-innings | Chase record | Dew rate | Spin influence |
|---|---|---|---|---|---|
| MA Chidambaram, Chennai | 4 | 168 | 4W-0L chasing | Moderate | High (turn from day 2) |
| Wankhede, Mumbai | 3 | 192 | 1W-2L chasing | Low | Medium (slow wrist-spinners thrive) |
| Eden Gardens, Kolkata | 3 | 175 | 1W-2L chasing | High | Medium (variable bounce) |
| Narendra Modi, Ahmedabad | 4 | 186 | 2W-2L chasing | Low-moderate | Low early, rising late |
| M. Chinnaswamy, Bengaluru | 3 | 201 | 2W-1L chasing | Low | Low-medium |
| Arun Jaitley, Delhi | 3 | 170 | 2W-1L chasing | High | Medium-high (Kotla turn) |
| Sawai Mansingh, Jaipur | 2 | 178 | 1W-1L chasing | Moderate | Medium (assistance for spinners) |
| BRSABV Ekana, Lucknow | 2 | 164 | 0W-2L chasing | High | Medium-high |
| PCA Stadium, Mohali | 2 | 181 | 2W-0L chasing | Low-moderate | Medium |
| Rajiv Gandhi, Hyderabad | 2 | 195 | 1W-1L chasing | Low | Low |
Numbers are through the back half of the 2026 schedule as logged by the desk. Chase record equals wins by side batting second. Spin influence is a desk-judgement column built from turn, grip and wicket-kind distribution over the window; the chase record is a straight count.
Pre-toss frame: Pre-toss frame called dew from 19:00 and a chase-friendly second innings.
Actual outcome: CSK chased down a 188 target with 8 balls spare; dew confirmed the read.
Captain matrix delta: +38% leverage on the spin-AR captain pick; -8% on the powerplay anchor.
Edit for next match: Lock the dew call earlier in the day, not at the toss, on slow Chepauk decks.
Pre-toss frame: Pre-toss frame flagged Bumrah's workload reduction to three overs.
Actual outcome: Bumrah bowled 3.0-0-22-1; the captain matrix missed 12 fantasy points.
Captain matrix delta: -12 fantasy points on the workload under-projection.
Edit for next match: Tighten the workload model on back-to-back fixtures; check franchise management notes 48h out.
Pre-toss frame: Pre-toss frame called powerplay aggression on a flat Uppal deck.
Actual outcome: SRH racked up 78-1 in the powerplay; SRH won by 15 runs.
Captain matrix delta: +55% leverage on the powerplay specialist; matrix delivered above 90th percentile.
Edit for next match: Keep the powerplay aggression cap on Uppal only — not transferable to all flat decks.
Tuesday's match sits on a venue that has averaged 178 in the first innings across the last four matches but is yet to see a chase over 14-over dew points. The desk's pre-toss frame will lead with the dew reading at 18:30 IST and confirm both XI choices before publishing. The captain matrix will sit on a wrist-spinner if the chase record holds and on a powerplay aggressor if dew is moderate.
Watch for workload notes on the away quick bowler — the back-to-back fixture suggests he might be held to 3 overs. The differential captain play sits on the away team's middle-overs anchor, who is rotating strike better this season than his composite average suggests.
Wednesday moves to a high-scoring venue where four of the last six matches have crossed 190. The deck reads flatter, the outfield reads faster, and the captain matrix shifts to powerplay batters and death-overs specialists. Boundary length on the leg side is shorter than straight, which means wrist-spinners who bowl into the pads will leak; finger-spinners who bowl at the stumps will hold.
The two differentials this week both sit on the away side — a top-order batter coming off three low scores whose role is unchanged, and a death-overs finisher whose points-per-over ceiling is being mispriced by the field. Watch the toss carefully: on flatter wickets the chase bias flips back toward the side batting first.
The weekend double-header opens with an afternoon fixture where three teams are within 1.5 games of the playoff cut-off. The captain logic compresses as the table tightens — role-stable picks start to outrank differential reads. We expect the safe captain pool to narrow, the differential pool to widen, and the desk's matrices to reflect that by Saturday morning.
The evening fixture sits on a venue with a 2W-6L chase record this season. The captain matrix will lean heavily on the side batting first unless the toss reads unusual. Read the toss report before locking teams.
Across the four fixtures, the captain-shortlist intersection — the players who appear on every desk matrix this week — is small. That intersection matters more for grand-league entries than the per-fixture captain pick. The post-toss list narrows further to players whose role is unchanged and whose workload is not flagged.
The desk publishes the intersection list on Saturday morning and updates it after every confirmed XI on the weekend. Subscribers and casual readers see the same desk read; we do not gate the captain work behind a paywall or an email list.
On every match day, the desk publishes a pre-toss frame, a post-toss update, the captain matrix, and live mid-innings notes. After the match, the post-match audit closes the loop and feeds the next fixture's matrix. Daily match desk coverage is the desk's most consistent commitment to the reader.
Every Monday, the desk publishes a weekly recap covering the previous seven days. The recap aggregates the captain-matrix deltas, the post-match audits, the corrections and the editor's take on the previous week's reads. The recap is the cheapest way to catch up if you missed the week.
At the mid-season mark, the desk publishes a mid-season audit aggregating every captain-matrix call. The audit covers the role-confidence ladder, the venue reads, the workload notes, and the desk confidence score. The audit is a snapshot of where the desk's reads sit at the season's halfway point.
At the end of the season, the desk publishes a framework review covering what worked, what missed, and the explicit edits for the next season. The review is part of the editorial graph; the next season's coverage starts where the previous one ended.
