Guides
Breaking news updates and timelines: a reporting guide
Breaking news updates guide covering live-page scope, verification, timestamps, source status, orientation, corrections, safety, accessibility, and closure.
What to take away
- Open a live page only when a running stream of verified updates serves a clear reader need, and write the contract first.
- Timestamp three clockswhen the event happened, when the source issued it, when the newsroom checked it.
- Label each update by evidence type so the label decides what the page can claim.
- Hold a pinned summary above the stream for readers arriving cold.
- Correct material errors in place and publish a closing note with the reporting cutoff.
Write the live-page contract first
Do not publish until six fields are settled. They justify the page and define when it ends.
- Eventthe one thing changing, named in a line.
- Boundarygeography, institutions and services covered, plus what is out of scope.
- Audiencewho is reading and what decision they are making.
- Update thresholdwhat counts as an update, and what can wait.
- Staffingwho writes, who verifies, who owns the pinned summary, who may publish unread.
- Closing conditionthe observable signal that ends the page.
A page that cannot name all six is usually an article. Some stories read better as one considered piece, and the daily news explainer guide shows how to choose that form and keep it tight.
Do not open a live page when developments are too sparse, when the desk cannot check them, or when one article explains the situation more clearly.
Timestamp the reporting state
Each update states when the event happened, when the source issued the information, and when the newsroom verified or published it, wherever those times differ. Name the time zone every time.
[figure 2]
Reporting-state timestamp
- 1035 Source issues transit agency alert
- 1042 Newsroom verifies and publishes update
- LaterCorrection or update time added if changed
The HTML time element with a datetime attribute binds a machine-readable date, time and zone to the clock on screen, so feeds and search results carry the moment a reader sees.
Example: one update, formatted
10:42 a.m. ET. Trains holding at two stations, per the transit agency alert issued 10:35 a.m. ET and verified against the agency feed at 10:41 a.m. ET.
It tells a reader what is known, who said it, and how fresh the check is.
Never backdate an old timestamp so revised text looks original. Add a correction time and say what changed.
Label the status of every update
The status field tells the desk what it may claim and tells a reader what to weigh.
| Status | What it means | How to write it |
|---|---|---|
| Observation | A reporter saw or heard it | First person, with place |
| Official statement | An agency or company issued it | Attribute and link the document |
| Witness account | A person describes what they saw | Name the person and the vantage point |
| Newsroom finding | Confirmed by our own reporting or records | State the record checked |
| Unverified claim | Circulating, not yet checked | Name the source and the missing piece |
| Correction | A published item was wrong | State the error and the fix |
| Follow-up pending | A live question with a named owner | Name the owner |
[figure 3]
Update status labels
Status
- Observed
- Directly witnessed or documented
- Official
- Named body within its authority
- Reported
- Another newsroom or named source, checked
- Preliminary
- Credible but subject to change
- Disputed
- Material accounts conflict
- Corrected
- Earlier statement was wrong or misleading
- Context
- Verified background explaining a development
Meaning
- Observed
- Official
- Reported
- Preliminary
- Disputed
- Corrected
- Context
No rule forces a newsroom to print these words. Readers need the source and the confidence. A witness account and an official statement are not interchangeable, and a page that blends them teaches readers to distrust both.
Keep a pinned summary above the stream
Pin a short summary holding the confirmed event, the public effect, the source status, the main unknown and the next expected milestone.
Update it the moment an answer changes. A reader who lands at post 40 should not need to rebuild the story from the stream.
Someone owns that summary for the whole shift. How to run a live update desk sets out the roles and the checks that keep a long day honest.
Verify before you compress
Short updates still need full source notes: original record, exact claim, source role, location, event time, checking steps, editor.
Check the media apart from the account that shared it. The Journalist's Resource overview of tools for verifying user-generated content is the usual starting list. It dates to 2015, so treat the named tools as a method rather than a current inventory.
Ask whether several posts trace back to one unchecked assertion. When speed blocks confirmation, say what is known and what is still being checked. Posting volume is not evidence. The breaking news verification checklist keeps those checks visible under deadline.
For a recall page, send readers to the official CPSC recall database instead of restating hazard details that shift.
Correct visibly and close the page
A typo that changes no meaning is fixed under routine policy.
A material error is marked in place: state the wrong information, give the correction, log the correction time, revise the pinned summary. Then search the page for dependent claims.
Close when public effect stabilises, the event slows, or staffing can no longer meet the verification promise. Publish a closing note with the final reporting cutoff, the open questions and the next scheduled check.
Keep the archive date visible. A closed page often feeds 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 needs: a short table, a list, a quote, a correction box. Keep each post to one development.
Can a social post be a source?
Yes, for what a verified account posted, or for media the newsroom authenticates. A post does not confirm every claim inside it.
How often should a live page update?
When verified information arrives. A fixed posting rhythm invites filler and weak checks.
What belongs in the pinned summary?
The verified situation now, the immediate effect, the main uncertainty, the reporting cutoff and the next milestone.
