How to track fantasy cricket news through the day: a beat reporter's reading schedule

The day a fantasy match is played is not when most of the important cricket news actually lands. The day before the toss, the eleven named by the captains has to be confirmed. The morning of the match, a dew update or a pitch report changes the captaincy math. The post-match evening, a press conference line sets the next morning's headline. Between those three moments sit three more — squad announcement, fantasy-team lock, and the post-play review. A beat reporter tracks all six. A reader who logs on twice a day, in the morning and the evening, usually catches the headlines and misses the context.

The schedule below is the desk's working rhythm. It is the order in which the editor reads the feed, the order in which the editor decides what to verify, and the order in which the editor decides what to publish. The schedule is not a secret — most beat desks run something close to it. What is rarer is the discipline of treating the schedule as a schedule: knowing which window a story belongs to, and refusing to publish a story that lands in the wrong window at the wrong time.

Window 1 — The 24-hour-out squad note (evening before)

Three things make a squad note worth reading carefully. First, the captain — if the named captain differs from the expected one, the rest of the squad reads differently. Second, the impact player — the player who can be substituted in at the toss is a different fantasy asset from the player who starts. Third, the bench — a strong bench is a sign the franchise is reading the conditions the way the fantasy desk is, and the bench is the player pool that will move up the next-day rankings if the XI shuffles.

The discipline of this window is to read the squad note against the surface note. If the side has named an extra spinner on a dry pitch, the captain is telling you the pitch is dry. If the side has named an extra seamer in overcast conditions, the captain is telling you the seamers will share the powerplay. The squad note is the first line of the day's reading; the press conference is the second.

Window 2 — The 12-hour-out press conference (morning of)

The press conference window is the one most readers skip. The press conference is held 10–14 hours before the toss; the transcript lands on the league's media portal and on the named beat reporters' Twitter feeds. The press conference is the most important read of the day, because the captain will say things the squad note will not. The captain will describe the pitch, the dew, the opposition, the batting order and the bowler rotation. A captain who says "we will look to bat first" is telling the desk the captain has won the toss call. A captain who says "we have options" is telling the desk the captain has lost the toss call.

The discipline of this window is to read the press conference against the squad note. The press conference is the verb; the squad note is the noun. The two together tell the reader the captain's plan, the conditions the captain is reading, and the choices the captain has already made. Without the press conference, the squad note is a list of names. With the press conference, the squad note is a plan.

Most readers see the press conference as a quote-collection exercise — find the best line, paste it into a tweet, move on. The beat reporter's discipline is the opposite. The press conference is a long-form document. The captain is asked the same question three different ways by three different reporters; the answer that survives the third version is the one the captain meant. The answer that changes between the first and the third version is the one the captain is hedging. Reading the press conference in full is the difference between a same-day note and a recycled rumour.

Window 3 — The toss and the playing XI (90 minutes before)

Three things make the toss window worth treating as a separate read. First, the toss decision — bat or bowl — is a captaincy call that the squad note and the press conference have only hinted at. Second, the playing XI is rarely identical to the squad list; the franchise usually holds back one or two names that the captain can promote only at the toss. Third, the impact player is named; this is the substitution the captain has chosen to expose to the conditions.

The discipline of this window is speed and accuracy together. A beat reporter who publishes the wrong XI at the toss is wrong within 20 minutes; a beat reporter who publishes the right XI 30 minutes late is irrelevant. The window is small, the read is short, and the consequence of getting it wrong is large. The desk's rule is to confirm the XI against two sources before publishing — the official scorer and the broadcast graphic — and to publish only when both agree.

Window 4 — The match (live)

The match window is the only window the casual reader watches. The beat reporter watches the match in a different way. The match is not a single read; it is 20 overs per innings, each with its own micro-window. The powerplay is a window; the middle overs are a window; the death is a window. The match window is also a window in which the desk does not publish — the desk reads the match, the desk does not narrate the match.

The discipline of this window is to separate the read from the publish. The match produces a flow of events; the desk's job is to read the flow and identify the one or two moments that will change the next-day note. A captaincy call in the 12th over. A bowling change that breaks a partnership. A dew point that crosses the threshold. The beat reporter's note during the match is internal — the beat reporter's note after the match is the published one.

Most readers skip the match window because the match is on broadcast. The desk reads the match because the broadcast is one view; the desk's read is the other view. The two together are the full story. Reading only the broadcast is reading the match without the beat.

Window 5 — The post-match press conference (within two hours of the close)

The post-match press conference is the second most important read of the day, after the pre-match press conference. The post-match press conference is where the captain explains the result — win, loss, no result — and where the captain is asked about the moments that decided the result. The post-match press conference is also where the captain is asked about the next match, and the next-match answer is the first line of the next-day note.

The discipline of this window is to read the post-match press conference for what is not said. A captain who is asked about a dropped catch and answers about the pitch is not addressing the dropped catch. A captain who is asked about a bowler's injury and answers about the batting order is not addressing the bowler's injury. Reading for what is not said is harder than reading for what is said, but it is the difference between a same-day note and a recycled rumour.

Window 6 — The next-morning review (the day after)

The next-morning review is the window in which the day's news becomes the next-day's news. The morning of the day after the match, the beat reporters publish their long-form reviews; the league's statisticians publish the day-end numbers; the fantasy desks publish the captaincy matrix for the next fixture. The next-morning review is the window in which the desk's earlier reads are tested against what actually happened.

The discipline of this window is the hardest: it is the window in which the desk admits which of its earlier reads were wrong. A press conference read that did not match the toss. A squad note that did not match the playing XI. A match read that did not match the result. The next-morning review is the window in which the desk publishes its own corrections, dated and attributed. A desk that does not publish its own corrections is a desk that has stopped reading itself.

The source ladder for each window

Each window has a different source ladder. The squad note ladder is the league's media portal, the franchise's official page, and the franchise's verified social accounts. The press conference ladder is the transcript on the portal, the named beat reporter's tweet, and the broadcast's caption. The toss ladder is the official scorer, the broadcast graphic, and the league's playing-card feed. The match ladder is the broadcast, the official scorer's running update, and the named beat reporter's over-by-over thread.

The discipline of the source ladder is to climb the ladder in order. A named beat reporter's tweet is not a substitute for the official transcript. The broadcast graphic is not a substitute for the official scorer's feed. Climbing the ladder takes a few minutes; skipping the ladder takes a few seconds. The few seconds is where the recycled rumour lives.

What the schedule looks like in practice

A working day for the desk on a match day looks roughly like this. The evening before, the squad note lands; the desk reads the squad note, the surface note, and the conditions note together; the desk publishes a 150-word same-day note. The morning of the match, the press conference lands; the desk reads the transcript in full; the desk publishes a 400-word pre-match note that links the squad to the conditions to the captain's plan. The toss lands 90 minutes before the play; the desk publishes the XI within 10 minutes of the captain reading it out. The match is read live but not published. The post-match press conference is read in full; the desk publishes a 400-word post-match note. The next morning, the desk publishes a long-form review and corrects the previous reads where the day has shown them to be wrong.

That is six windows, six reads, and four or five published notes across 36 hours. A reader who logs on twice a day sees two of those notes. A reader who reads each window as it lands sees all of them. The difference between the two readers is not intelligence; it is schedule.

What this means for the fantasy captain

For the fantasy captain, the schedule is a tool, not a rule. The captain does not have to read the press conference in full to win the contest; the captain has to read the press conference in full to make a captaincy call that survives the next morning's review. The captain who picks a captain from the squad note alone will be wrong about 30% of the time. The captain who picks a captain from the squad note plus the press conference will be wrong about 15% of the time. The captain who adds the toss and the playing XI will be wrong about 8% of the time. The captain who adds the match read and the post-match press conference will be wrong about 5% of the time. The numbers are illustrative; the pattern is real.

For the desk, the schedule is a discipline. The schedule decides which read gets a published note and which read gets an internal note. The schedule decides when to publish a same-day note and when to wait for the next-morning review. The schedule decides which corrections to publish and which corrections to keep. The schedule is not glamorous. The schedule is the part of the work that the reader never sees, and it is the part of the work that decides whether the reader's feed is the same-day feed or the recycled feed.

The next window to watch

The next window for the desk is the next squad note — the one that will land in the evening before the next fixture. The desk will read it against the surface note, the press conference, and the conditions. The desk will publish the same-day note within an hour of the squad landing. The desk will then read the press conference when it lands the next morning, and the desk will publish the pre-match note. The cycle continues. The schedule is the schedule; the schedule is the work.

Method: The windows in this schedule are derived from the desk's standing beat practice. The order of the windows, the source ladder for each, and the discipline of the next-morning review are the working rhythm the desk uses for every fixture. The percentages in the fantasy-captain section are illustrative ranges based on the desk's reading of the captaincy matrix; they are not league-issued statistics.

For the wider cricket news cycle from the desk, the same schedule applies to squad notes, transfer rumours, press conference cycles, and tournament reviews. The next window to watch is the next squad note for the next fixture on the desk's calendar.