Breaking update types compared

What to take away

• A confirmed fact, attributed statement, and newsroom analysis need different wording.
• Event time, source time, publish time, and correction time should not be merged.
• Scheduled events describe plans, not outcomes.
• Context belongs when it changes understanding of the live event.
• A correction is a disclosure, not simply a replacement post.

Live coverage becomes unreliable when every post looks the same. Readers need to know whether an update reports an observed event, repeats a source's claim, announces a schedule, adds background, offers analysis, or corrects an error. These types operate inside the live coverage machinery described in the breaking updates and timelines guide.

Comparison table

Update type	What it establishes	Required fields	Unsafe shortcut
Confirmed fact	A checked event or record	Evidence, place, event time, verifier	"Confirmed" without naming how
Attributed claim	What a source says	Speaker, role, exact scope, source time	Turning the claim into newsroom voice
Scheduled event	A stated plan	Issuer, date, time zone, change warning	Writing as if the event occurred
Context	A prior fact that explains now	Source, date, link to present meaning	Adding unrelated history
Analysis	A reasoned interpretation	Evidence, method, assumptions, author	Predicting beyond the record
Correction	What was wrong and what is right	Original claim, fix, time, affected posts	Silent deletion

Confirmed fact

Use this type when the newsroom has direct observation, a primary record, or a source with authority for the exact fact. State the method when it matters. "The county order closes the road from 6 p.m." is different from "drivers report a closure."

Confirmation is claim-specific. A verified agency account confirms who issued a post, not necessarily the accuracy of every early statement inside it.

Attributed claim

Name the person or body, role, and limit of knowledge. A hospital may confirm patients received, while an investigator may later determine cause. A political office can state its proposal, but it cannot establish how every affected party will respond.

Keep attribution close to allegations, estimates, motives, and disputed facts.

Scheduled event

Give the date, local time and time zone, issuing body, purpose, and whether attendance or streaming details are confirmed. Use future or conditional wording. If the schedule changes, update the notice rather than leaving two conflicting posts.

The federal web standard for a content timeliness indicator recommends showing a publication, last-updated, or last-reviewed date as appropriate and including the period covered by data. The standard applies to federal sites, not every newsroom, but its distinction helps a live page communicate which date means what.

Context

Add background only when it explains authority, scale, sequence, or consequence. Label its date so an old rule or figure does not look current. A prior disaster toll should not be used as a casual comparison before the present count is stable and comparable.

Context also needs a source-status check. A rule can expire, an official can leave office, and a statistical series can be revised. Record the version and state the connection to the present event. If that connection cannot be explained in one sentence, the material probably belongs in a later background article rather than the live stream. Choosing that later container is what the comparison of daily explainer formats is for.

Analysis

Analysis connects verified facts through a stated method. It should identify assumptions and alternatives. Do not place speculation in a live stream under an analytical label. If the evidence cannot support a conclusion, describe the questions investigators are examining.

CDC guidance on communicating during an outbreak or public health investigation recommends stating what is known and unknown, giving specific timelines, explaining steps being taken, and avoiding overpromises. Although written for public-health communicators, those distinctions help a newsroom describe uncertainty without filling it with prediction.

Correction

A correction names the prior error, provides the accurate information, gives the correction time, and identifies dependent summaries or visuals that changed. A source update is not automatically a newsroom correction if the earlier article accurately described the source's preliminary statement. In that case, label the new information as an update and preserve the earlier status. Data releases are the classic case: revisions are routine, and the economic release reporting checklist builds them into the fields from the start.

Use status consistently

Maintain the update type in the source ledger even if readers see plain language rather than a badge. Consistency lets the desk search all preliminary claims, scheduled items, or corrections during handoff. The ledger itself is described in how to run a live update desk, where every claim carries a status and owner.

Common questions

Is an official statement a confirmed fact?

It confirms what the named body said. Whether it confirms the underlying event depends on the body's authority and evidence.

Can context be posted during a lull?

Yes, when it helps readers understand the live event. Do not use it merely to maintain posting frequency.

Does analysis belong in breaking coverage?

It can, if clearly labeled, evidence-based, and separated from still-developing factual claims.

Is every revised number a correction?

No. Some data are designed to be revised. Correct the newsroom when its statement was wrong; update the figure when the source publishes a new vintage.