Breaking news updates and timelines: a reporting guide

What to take away

• Open a live page only when continuing updates serve a clear reader need.
• Timestamp the reporting state, not merely the moment a post was typed.
• Separate observation, official statement, witness account, and newsroom finding.
• Keep a current summary above the stream so late arrivals can orient themselves.
• Correct errors in place and preserve a clear record of the change.

A live page is a reporting product, not a container for every incoming message. Its value comes from verified change, clear chronology, and editorial selection. Before opening one, define the event, geographic boundary, intended audience, update threshold, staffing plan, and condition for closing the page. Some stories are better served by a single considered piece; the daily news explainer guide covers that route.

Photo and credit

The image illustrates live production equipment. It does not show this newsroom or an event covered by this guide.

Set the live-page contract

Write five fields before publication:

Field	Decision
Scope	Event, place, time window, and exclusions
Audience	Who needs updates and for what decision?
Threshold	What new information merits a post?
Authority	Who can publish, amend, pin, and close?
End state	When does the page become a summary or archive?

Do not open a live page when developments are too sparse, the desk cannot verify them, or an ordinary article can explain the situation more clearly. Staffing that contract is its own craft; how to run a live update desk assigns the roles and checks.

Use a reporting-state timestamp

Each update should state when the event occurred, when the source issued the information, and when the newsroom verified or published it when those times differ. Include the time zone. On the page itself, the HTML time element with a datetime attribute can attach a machine-readable date, time, and time zone to the displayed clock, so feeds and search results carry the same moment a reader sees. A label such as "10:42 a.m. ET, verified from the transit agency alert issued at 10:35" communicates more than a bare clock time.

Never change an old timestamp to make revised text appear original. Add a correction or update time and explain the material change.

Classify every update

Use an internal status field:

• Observed: directly witnessed or documented by the newsroom.
• Official: attributed to a named body within its authority.
• Reported: supplied by another newsroom or named source and checked to the stated degree.
• Preliminary: credible but expressly subject to change.
• Disputed: material accounts conflict.
• Corrected: an earlier statement was wrong or misleading.
• Context: verified background that explains a live development.

The label guides editing. It does not need to appear as newsroom jargon, but readers must understand the source and confidence.

Keep orientation above chronology

Pin a short current summary containing the confirmed event, public effect, source status, main unknown, and next expected milestone. Update it when the answer changes. Do not make a reader reconstruct the situation from 40 reverse-chronological posts.

Verify before compressing

Short updates still need full source notes. Save the original record, exact claim, source role, location, event time, verification steps, and editor. Check media separately from the account sharing it. The Journalist's Resource keeps an overview of tools for verifying user-generated content that can help establish where a photo or video first appeared; it dates to 2015, so treat specific tools as a starting point rather than a current inventory. Ask whether multiple posts trace back to one unverified assertion.

When speed prevents adequate confirmation, say what is known and what is being checked. Do not imply that frequent posting is evidence of progress. The breaking news verification checklist keeps those checks explicit under deadline.

Correct visibly

For a typo that changes no meaning, fix it under the newsroom's routine policy. For a material factual error, mark the affected update, state the wrong information, provide the correction, record the correction time, and revise the pinned summary if needed.

Do not delete a material error and leave later posts referring to it. Search the whole live page for dependent claims.

Close the page

End live coverage when the public effect stabilizes, the event moves to a slower process, or staffing can no longer meet the verification promise. Publish a closing note with the final reporting cutoff, unresolved questions, and next scheduled check. Keep the archive date visible. A closed page often hands its material to the next morning news brief, which reframes the event for readers starting their day.

Common questions

Should every update be one paragraph?

No. Use the form the information requires, including a short table, list, quote, or correction box. Keep each post focused on one development.

Can social posts be used as sources?

Yes, for what a verified account posted or for media that the newsroom authenticates. A post does not confirm every claim it contains.

How often should a live page update?

When meaningful, verified information arrives. A fixed posting rhythm can encourage filler and weak checks.

What belongs in the pinned summary?

The current verified situation, immediate effect, main uncertainty, reporting cutoff, and next expected milestone.