News: the fantasy cricket reporting desk
The news desk is where the desk publishes reporting on confirmed-XI changes, injuries, tactical shifts, role changes, and other material updates that affect fantasy selection. Every piece is sourced and timestamped.
What the news desk covers
The news desk covers material updates that affect fantasy selection: confirmed playing XIs, late lineup changes, injury news, tactical shifts, role changes, squad announcements, and substitutions. We do not cover rumour, transfer speculation, or unverified leaks — those go in the team's late-news log only after confirmation.
How a news piece is built
A news piece opens with the fact (what happened), then names the source (where we got it), then walks through the fantasy implication (what it means for selection). The piece is timestamped at the top and bottom so the reader knows when it was written and when it was last updated.
Sourcing rules
We cite the tournament's official channel, the team or player's verified social profile, or a primary news outlet with a byline. We do not cite aggregator sites or anonymous leaks as primary sources.
Reporting vs prediction
The news desk reports facts. The predictions desk frames scenarios. The boundary matters: a news piece says 'player X is in the starting XI'; a prediction piece says 'in this conditions read, captain X has a stronger case than Y'. Mixing the two is how fantasy coverage loses its accountability.
Updates and corrections
If a news piece is updated after publication — for example, a player later pulls out of the XI — the update is appended as a new paragraph at the bottom of the piece with a timestamp. The original wording is preserved. Material corrections are also listed in the public corrections log.
What counts as a confirmed lineup
A lineup is treated as confirmed when the team's official channel publishes the team sheet — typically within 30 minutes of the toss. Leaks and aggregator reports are not treated as confirmed. The desk will publish a correction if a leak was widely circulated and the team sheet differs.
If a team sheet is published and then a player pulls out within the toss window, the desk treats the revised sheet as the confirmed lineup. The original sheet remains visible in the article, with a late-news log entry naming the change. Readers who lock-in teams based on the original sheet should check the late-news log before submitting.
Why we cite primary sources
We cite primary sources because aggregation is a known failure mode for fantasy coverage. A reader who trusts an aggregator is trusting the aggregator's source chain, which the reader cannot audit. A reader who trusts a primary source can verify the claim directly. The desk's working rule is to cite the tournament's official channel, the team's verified social profile, or a primary news outlet with a byline.
Where multiple primary sources conflict, the desk notes the conflict and uses the source closest to the event — typically the team's official channel, then the tournament's official channel, then a primary news outlet with a byline. Aggregator sites are never used as primary sources.
How we handle conflicting reports
When two primary sources conflict — for example, a team's official channel says a player is in the XI, but a primary news outlet reports the player pulled out — the desk notes the conflict and waits for the more authoritative source. The team's official channel is usually authoritative for the team's own XI; the tournament's official channel is usually authoritative for tournament-level updates (schedule changes, venue moves).
If the conflict cannot be resolved within the news window, the desk publishes the conflict and names both sides. Readers who need to lock in immediately should default to the most authoritative source for the type of update.
When we publish corrections
We publish corrections when a published piece contains a material error — a wrong squad player listed as in the XI, a wrong role attributed to a player, a wrong fixture date. Corrections are published in the public corrections log and are appended to the original article with a timestamp. The original wording remains visible so the reader can audit the chain.
We do not publish corrections for typos or non-material wording changes. Those are fixed silently in the article with an editorial note at the bottom. The corrections log is reserved for material errors.
Why we name sources inline
The desk names sources inline at the point of the claim, not in a footer. Inline sourcing makes the audit chain visible — a reader who wants to check a claim can find the source without leaving the paragraph. Inline sourcing also forces the desk to be specific about which source supports which claim, which reduces the aggregation-failure mode where one weak source is used to support several distinct claims.
Where multiple sources support the same claim, the desk names the primary source and notes that the secondary sources corroborate. The reader can verify the primary source first and treat the secondary sources as confirmation.
What we don't cover
The news desk does not cover transfer rumours, fan-driven campaigns, marketing-led announcements that have no material fantasy impact, or off-the-field stories that do not affect selection. The desk's editorial scope is the intersection of confirmed cricket news and fantasy selection relevance. Stories that are interesting but not material are noted in the social feed but not promoted to a published piece.
The desk also does not publish sponsor-driven coverage. We do not accept payment for coverage, do not run sponsored pieces, and do not link to operators in exchange for compensation. Where the desk names a player or a tournament, the relevance is editorial, not commercial.
Reading the archive
The news desk archive is searchable by team, by tournament, and by topic. To use it well, pick a narrow slice — for example, all confirmed-XI changes at one venue across the last ten fixtures — and read those entries before drawing conclusions. The desk's pattern of coverage is usually visible at that slice level; it is rarely visible at the aggregate level.
If you find a pattern the desk has not flagged, route it to the contact page. We treat reader-submitted findings as inputs to the relevant team's tactical-shifts block. Material corrections are added to the public corrections log.
Archived news pieces are timestamped and preserved verbatim. Where a piece has been updated, the original wording remains visible and the update is appended with a timestamp. The archive is for auditing the desk's pattern of coverage, not for generating a leaderboard metric.
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 pay for tips?
No. The desk does not pay for tips and does not accept paid tips from intermediaries. We cite primary sources only.
What happens if a piece needs to be updated mid-day?
The update is appended with a timestamp. The original wording remains. Material corrections are also listed in the public corrections log.
Can I send you a tip anonymously?
Anonymous tips are not used as primary sources. If you have information that should be on the record, contact the desk and we will work with you on attribution.
