The live match desk: how we cover fixtures on the day
A working desk for fantasy cricket readers who want grounded match coverage, not hot takes. This page explains the format our match reports use, the order in which we publish updates, and the boundaries we keep between reporting and prediction.
How the live desk works
Every fixture covered on Fantasy Cricket Live follows the same four-stage pattern: a pre-match briefing published 4-12 hours before the toss, a toss update that revises the briefing once conditions and XI are confirmed, a confirmed-XI post that names the actual team sheet, and a post-match review that names whether our pre-match read was right and why. Each stage is timestamped and the original wording is preserved when later updates land.
The desk treats fixtures as a sequence of evidence, not a single moment. A captaincy call made before the toss and a captaincy call revised after the toss are two different decisions — both are documented and the link between them is visible to the reader.
Reading order
If you only have two minutes before lock-in, read the toss update and the confirmed-XI post. The pre-match briefing is useful for the model behind the call, but the actionable read is always post-toss.
Match-status language we use
Cards on the live desk use one of three status labels. Live means play is in progress and the desk is publishing over-by-over notes. Toss 30 min prior means the fixture has not started but the toss window is imminent and the desk is preparing the confirmed-XI post. Post-match review means the result is in and the desk is writing the review piece.
We do not use the word 'upcoming' for fixtures more than 24 hours away — those live on the tournaments desk or the fixtures index, not the live desk. The live desk is a working surface for the day of play.
What changes after the toss
Three things change the selection model after the toss: the playing XI, the choice to bat or bowl first, and the conditions read (dew window, pitch behaviour, square boundaries). The toss update is short — usually 200-400 words — and names each change explicitly. If nothing material changes, the desk says so plainly.
Why we wait for the toss
Pre-toss modelling is built on probabilistic assumptions about the XI. Once the toss lands and the team sheet is confirmed, the model's inputs change and the call has to be revised. Readers who lock-in teams at 18:00 IST for a 19:30 fixture are usually working from a model that has not been updated.
Conditions table: what to read
Match briefings include a conditions table with four rows: surface behaviour over the last five fixtures at the venue, average powerplay and death-over scoring bands, dew likelihood given the time of year and ground, and chasing-versus-defending record over a defined sample. We never publish a single number without a sample size and a date range.
| Venue | Sample | Powerplay RR | Death RR | Chase % |
|---|---|---|---|---|
| Wankhede | Last 5 IPL | 8.4 | 10.1 | 62% |
| Chepauk | Last 5 IPL | 6.9 | 8.7 | 44% |
| Narendra Modi | Last 5 IPL | 8.1 | 9.6 | 58% |
| Ekana | Last 5 IPL | 7.6 | 9.2 | 55% |
| Chinnaswamy | Last 5 IPL | 8.7 | 10.4 | 60% |
Bands are aggregated from the venue's last five completed fixtures in the same format. Venues with fewer than three relevant fixtures are labelled 'small sample'.
Confirmed-XI reads we publish
Confirmed-XI posts are the most time-sensitive pieces on the desk. They run 250-500 words and cover four questions: who is in, who is out, which role shift is the most material, and which captaincy case has changed. The post goes up within ten minutes of the team sheet landing on the official tournament channel.
Captain-case format
Each match briefing includes a captain-case table. We do not name a single captain. We name two — the conservative case and the aggressive case — with the conditions under which each is the better pick. The conservative case is the one we would lock-in with limited information; the aggressive case is the one we would lock-in if our specific scenario reads (pitch behaviour, dew window, opposition matchup) prove correct.
| Case | Captain | Logic | Risk |
|---|---|---|---|
| Conservative | Top-order anchor | High floor, role security, low variance | Ceiling capped by cautious batting order |
| Aggressive | Powerplay specialist | High boundary ceiling if pitch is flat | Low floor if early wickets fall |
Late-news log policy
If a significant update lands between the confirmed-XI post and the toss — a player pulls out with a niggle, a substitution is announced, the venue's pitch report is revised — the desk appends a 'late-news log' block at the bottom of the existing post rather than replacing the original. Readers can see what changed and when.
We do not silently rewrite
Once an update is published, the original wording remains in the article. Later updates are appended, not substituted. This is why the post-match review always cites the original pre-match call.
Post-match review pattern
Post-match reviews open with the result, name the decisive performer, then walk through the desk's pre-match call: was the captain case right, was the conditions read right, was the role-shift note right. We name what we got wrong as explicitly as we name what we got right. Reviews include the original prediction link so the reader can audit the chain.
What we will not publish
The desk will not publish guaranteed teams, captain picks without a conditions rationale, or 'best XI' lists that are not backed by the desk's four-factor check (role, conditions, workload, selection logic). We will not run sponsored picks, take affiliate commissions, or accept payment for coverage. The boundaries are the reason the publication can be read as an editorial product and not as a marketing funnel.
The pre-lock checklist
Our pre-lock checklist is short by design. Five minutes before the toss window closes, run four checks on the team you are about to submit. First, did the confirmed XI match the team sheet you modelled? If not, every credit allocation that assumed the leaked XI is now stale. Second, did the venue's pitch behaviour over the last session match your conditions read? If the surface is playing slower or quicker than expected, the death-overs bowler calculus changes. Third, is the dew window realistic for the time of year and the ground? Dew flips the chase-bat-first split, which in turn changes how aggressive the chasing captain can be. Fourth, is there a late-news item that has not yet been folded into the prediction page? If so, the captain-case table is not yet revised. We do not name a single lock-in team — the checklist exists so the reader can defend the team they pick, not so they can borrow ours.
If a piece of the checklist fails, the desk's working rule is to revise the captain-case before the credit allocation, not after. The captain pick compounds through the multiplier; the credit allocation compounds through the team shape. A captain mistake is recoverable inside the same fixture; a credit-allocation mistake cascades through the rest of the contest.
Reading the captain-case table
The captain-case table on each match briefing includes two cases — a conservative case and an aggressive case — with the conditions under which each is the better pick. The conservative case is the one we would lock-in with limited information; the aggressive case is the one we would lock-in if our specific conditions reads (pitch behaviour, dew window, opposition matchup) prove correct. Each case is anchored to a specific player, a specific role, and a specific risk label.
The table does not name a winner because no probabilistic model produces one number that survives contact with a live match. The table names two defensible picks with stated conditions, which is what a selector actually needs to make a decision. The floor framework produces the conservative case; the ceiling framework produces the aggressive case. The matchup framework can produce either, depending on whether the matchup favours role stability or upside.
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
When does the live desk publish?
Pre-match briefings go up 4-12 hours before the toss. Toss updates land within five minutes of the toss result. Confirmed-XI posts land within ten minutes of the team sheet. Post-match reviews land within two hours of the result.
Do you publish during rain delays?
Yes — a delay post names the revised over target if DLS has been applied, the reset batting order, and any fantasy-relevant implications for bowler overs and death-bowl shares.
What if the official team sheet conflicts with leaks?
We use the official team sheet, not the leaks. The desk will publish a correction if a leak was widely circulated and the team sheet differs.
Can I request a fixture be covered?
Yes — readers can route requests via the contact page. We add fixtures when our coverage calendar allows and when there is reader demand for that fixture.