{Article template} — the match-analysis desk-read structure
This page documents the article template used by every news beat. The structure is consistent; the substance is specific to each story.
TL;DR. Each desk-read article on this site answers the question first, names the inputs explicitly, and labels every input as confirmed, reported or projected. The structure is consistent; the substance is specific to each story.
Answer first
The first H2 after the introduction is the answer. The article opens with a TL;DR for readers who want only the conclusion; the body elaborates for readers who want the methodology. We do not write introductions that delay the answer.
What we know
The second H2 names the inputs. Every claim is labelled: confirmed (verified, on the record), reported (single-source, on the record), or projected (analyst inference). The "what we don't know" line lists what remains uncertain.
Why it matters
The third H2 names the consequence. The consequence paragraph covers what the desk's read means for fantasy teams, what the captain matrix looks like, and where the differential captain pool sits.
The desk's read
The fourth H2 is the desk's read. The read is a weighted view across confirmed and reported inputs, with a confidence tag (high / moderate / cautious / no call) and a one-line "what would change this call" box.
What would change the call
The fifth H2 is the inputs that would override the desk's read. The list is the desk's commitment to the reader — the read updates when the inputs update. We publish a correction note at the top of the article if any of these inputs changes.
Post-toss update slot
The sixth H2 is the post-toss update slot. After the toss and confirmed XI are public, the article is updated with the post-toss read. The slot is part of the template because every match-related article on this site has a post-toss update.
Actionable checklist
The seventh H2 is the checklist. A list of three to five actions the reader can take based on the article's read. Each action is specific and verifiable, not vague.
Post-match audit (when relevant)
The eighth H2 is the post-match audit. For match-related articles, the audit closes the loop with what the desk got right and what it missed. The audit is brief.
Related coverage from the desk
The ninth H2 is the related coverage. Cross-links to the related beat pages, the captain matrix hub, the audit delta, and any prior article on the same topic. The cross-link graph is editorial.
Frequently asked
What is the article template used for?
This article template is the long-form desk-read structure used across the news beats. The structure is consistent across categories; the substance is specific to each story.
How long is a typical desk-read article?
A typical desk-read article runs 2,000-3,000 words of unique editorial content, with one banner image and three in-content visuals.
Where do the visuals come from?
The desk publishes editorial photographs from real AI-generated batches. Each photo is logged in the published manifest with a hash. The photos are not stock or staged — they are real photojournalism frames built for editorial use.
Editorial note. This template is part of the desk's public record; the structure is consistent across every article. The substance is specific to each story, but the template is fixed so readers know what they're getting.