Tournaments: the competition desk
The tournaments desk tracks fixtures, table implications, squad changes, and the qualification scenarios that actually matter for fantasy selection windows. Coverage is anchored to the senior men's franchise calendar first, with selective coverage of parallel competitions.
What the tournaments desk does
The tournaments desk covers the senior men's franchise league in depth — every fixture, every table implication, every squad change, every qualification scenario. We also cover parallel T20 leagues selectively, with depth depending on reader demand and the fantasy overlap with the senior men's calendar.
Reading the fixture desk
Each tournament page has a fixture desk with the upcoming matches, the venue, the format, and a short note on the fantasy relevance. The fixture desk is updated when the schedule is confirmed and refreshed when rain or scheduling changes land.
| Round | Fixture | Venue | Format | Note |
|---|---|---|---|---|
| Group | MI vs RCB | Wankhede | T20 | High-scoring venue |
| Group | CSK vs KKR | Chepauk | T20 | Spinners in play |
| Group | RR vs DC | SMS Jaipur | T20 | Toss-driven |
| Group | GT vs SRH | Narendra Modi | T20 | Death-overs watch |
| Group | LSG vs PBKS | Ekana | T20 | Dew window |
Table implications and qualification
Table implications are tracked as a rolling scenario, not a one-off calculation. As fixtures resolve, the desk updates the qualification picture and names the matches where a result would change the playoff math. For fantasy selectors, the table picture matters because it changes captain-case logic: a team that must win often bats first and chases hard, while a team that is already through may rotate.
How to use the qualification picture
If you are selecting for a multi-fixture lock-in window, check whether teams in your side are playing for points or playing for rest. A team that is already qualified may rest a frontline bowler at the death; a team that must win may bowl its best death-over option early.
Squad changes that matter
Squad changes that matter for fantasy selectors: a returning player, a player ruled out, a substitution announced, a trade-window move. The desk tracks these in a rolling log and updates the relevant team and player pages when a change is confirmed by the tournament's official channel.
Tournament-specific reporting
Tournament-specific reporting covers the unique pattern of each competition: powerplay approach across the league, average scores by venue, the chasing-versus-defending record over the relevant sample, and the most successful captaincy patterns. The reporting is updated as the tournament progresses and is archived when the tournament ends.
Reading the qualification picture
The qualification picture on each tournament page is a rolling scenario, not a one-off calculation. As fixtures resolve, the desk updates the playoff math and names the matches where a result would change the picture. For fantasy selectors, the table picture matters because it changes captain-case logic: a team that must win often bats first and chases hard; a team that is already through may rotate. The desk tracks the qualification picture in parallel with the live desk so the read is current at the lock-in window.
The qualification picture is updated when fixtures resolve and when net-run-rate calculations change materially. We do not publish a qualification calculator — the desk's working rule is to name the matches that would change the picture and let the reader model the rest.
Squad changes that matter
Squad changes that matter for fantasy selectors: a returning player (especially after an injury layoff), a player ruled out, a substitution announced within the tournament window, a trade-window move, or a confirmed-XI change at the toss. Each change is logged in the rolling squad-changes block on the tournament page and is reflected in the relevant team and player pages when confirmed.
We do not log speculation — only confirmed changes. A leaked lineup is treated as a leak until the official team sheet lands. Readers who lock-in teams based on leaks should be aware that the desk's predictions are anchored to the official sheet, not the leaks.
Reading fixture density
Fixture density is the schedule pattern that affects fantasy selection most. A team playing three fixtures in seven days has different selection pressures than a team playing one fixture in the same window. The desk tracks fixture density in the tournament page's upcoming-fixtures block and names the matches where rotation is most likely.
For multi-fixture lock-in windows, fixture density is more material than form. A team that is rotating to manage workload will give less overs to frontline bowlers and less batting time to anchor bats. The captain-case logic for those fixtures is different from a one-off lock-in.
Reading the chasing-versus-defending record
The chasing-versus-defending record on the tournament page is anchored to the same conditions sample the live desk uses — a defined set of fixtures with a date range. The record is most useful when read against the toss-to-bat and toss-to-bowl split for the same sample. A tournament where teams are electing to bat first at unusual rates is signalling that the conditions read has shifted; the chasing-versus-defending record then lags the shift by one or two matches.
For fantasy selectors, the chasing-versus-defending record is most material for captain-case logic. If the chasing rate is unusually high, the captain-case for a chasing team's top-order anchor improves. If the chasing rate is unusually low, the captain-case for a defending team's death-overs bowler improves.
What the tournament desk doesn't do
The tournament desk does not run a fantasy platform, does not host contests, does not take deposits, does not pay out winnings, and does not sell picks. The desk is an editorial publication. Where the desk names a player as a relevant fantasy pick, that is reporting on the player's role and conditions fit, not a recommendation to enter a contest.
The tournament desk also does not publish leak-driven lineups. Leaks are noted but not used as the confirmed XI; the desk waits for the official team sheet. Readers who want to lock in before the official sheet should be aware that the desk's predictions are anchored to the official sheet, not the leaks.
Reading the schedule changes
Schedule changes — rain, venue moves, double-headers, fixture reschedules — are tracked in the tournament page's rolling update block. Each change is logged with a timestamp and a one-line note on the fantasy implication. A rain-affected fixture may have a revised over target, a venue move may change the conditions read, a double-header may compress the rotation cycle.
For multi-fixture lock-in windows, the rolling update block is the section to check first. A reader who locks in teams based on a schedule that has changed since the lock-in window opened is working with stale inputs.
Reading support on this page
Every section in this article is sourced. Where a figure is from a small sample we say so explicitly. The article is updated when fixtures confirm, when the toss lands, and when post-match review changes the read.
Frequently asked
Do you cover women's franchise leagues?
We cover the women's franchise league when fixtures align with the fantasy calendar and when reader demand supports depth. Coverage is selective.
Do you cover domestic red-ball cricket?
Red-ball cricket is covered in the news desk only when it has a direct fantasy impact (a player switching format, an injury that affects a T20 squad).
How are tournament-specific numbers sourced?
Tournament-specific numbers use the same conditions-table format as the live desk — a defined sample, a date range, and an explicit caveat for small samples.