Breaking news updates and timelines: a reader's guide

This breaking news updates guide is for the reader who opens a live page in the middle of a story. It explains what a well-run page of updates and timelines should show you, how to read its timestamps and labels, how to tell a confirmed fact from a claim still being checked, and how a correction or a closed page should look. Every part of it answers the same three questions: what happened, what it changes for you, and how sure anyone is.

What to take away

What a reader arriving cold should find

A live page exists for the reader who opens it in the middle of a story. Within a few seconds you should be able to answer five questions from the page itself, without scrolling the whole stream:

If a page cannot answer those five, treat it with care. Everything below explains where each answer should sit and how to check it.

What a well-run live page settles first

Before a newsroom opens a live page, it should be able to name six things. You will rarely see them listed, but you can tell from the page whether they were settled.

A page that drifts from its event, posts every rumour or never says when it will close has skipped these steps. Some stories read better as one considered piece, and Daily news explainers: a reporting guide shows what that form gives a reader instead.

A live page is the wrong form when developments are too sparse, when the newsroom cannot check them, or when one article explains the situation more clearly.

How to read the timestamps

Each update should state when the event happened, when the source issued the information, and when the newsroom verified or published it, wherever those times differ. The time zone should be named every time. If an update gives only one time, you cannot tell whether it describes the last five minutes or the last hour.

[figure 2]

Behind the clock on screen, the HTML time element with a datetime attribute binds a machine-readable date, time and zone, so feeds and search results carry the same moment you see.

House style governs the words that carry those times. The AP Stylebook sets how dates, times and datelines are written in most U.S. newsrooms, and the SPJ Code of Ethics treats correcting mistakes promptly and prominently as a duty rather than a courtesy. Both are reasons to expect clear times and visible corrections from any page you rely on.

Example: one update, read closely

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 you what is known, who said it, and how fresh the check is: the agency spoke at 10:35, the newsroom confirmed it at 10:41, and the post went up a minute later.

An old timestamp should never be backdated so revised text looks original. A revised update should carry a correction time and say what changed.

What the status labels mean

The status label tells you what the newsroom may claim and what you should weigh.

[figure 3]

No rule forces a newsroom to print these exact words, but every update should tell you the source and the confidence. A witness account and an official statement are not interchangeable, and a page that blends them gives you no way to weigh either.

Start with the pinned summary

The pinned summary above the stream should hold the confirmed event, the public effect, the source status, the main unknown and the next expected milestone.

It should change the moment an answer changes. A reader who lands at post 40 should not need to rebuild the story from the stream. If the summary says one thing and the newest update says another, trust neither until the page reconciles them.

On a well-run page someone owns that summary for the whole shift, and a second person reads it against the latest entries before each change goes out, so the summary never lags the stream it sits above.

How to follow the chronology

A timeline is the page's record, ordered by when the event happened rather than when the post went up. One line per development, carrying the time, the place and the source, keeps the sequence readable when the stream runs long.

A good page keeps three layers visible: the pinned summary for what is true now, the chronology for how the story got there, and the newest update at the top of the stream. When a later fact changes an earlier entry, the entry should be marked as revised, with what changed, rather than rewritten quietly.

Example: a five-line chronology

Continuing the transit example above, a chronology for the same morning reads like this. The times, stations and sources are illustrative.

Each line is ordered by when the event happened, not when it was posted, and the revised entry keeps its first time visible beside the correction time. Skimming only this table, you can say what happened, in what order, and which lines rest on the agency rather than on a single witness.

The chronology should stay with the closing note and the reporting cutoff, so a reader returning weeks later can still see the order of events.

Wire services and broadcasters such as The Associated Press, Reuters and the BBC run public live pages. When you follow one, look at how it pins its summary, how it times each entry and how it marks a corrected post.

How claims are checked before they reach you

Short updates still rest on full source notes in the newsroom: original record, exact claim, source role, location, event time, checking steps, editor.

Images and videos are checked apart from the account that shared them. You can run the same basic checks yourself: put a still image through Google reverse image search or TinEye to see where it appeared first, read a video with a verification plug-in such as InVID-WeVerify, and compare the location with satellite and street imagery in Google Earth. The Journalist's Resource overview of tools for verifying user-generated content is still a useful method list, but it dates to 2015, so confirm that each tool still runs before you lean on it.

Several posts that trace back to one unchecked assertion are still one claim. When speed blocks confirmation, a good page says what is known and what is still being checked; posting volume is not evidence. The breaking news verification checklist sets out those checks step by step.

For product recalls, go to the official CPSC recall database rather than relying on a live page's summary of hazard details that can shift. The same rule covers other registers: the National Weather Service for warnings, the FDA for food and drug notices, NHTSA for vehicle recalls.

How corrections and closing should look

A typo that changes no meaning is simply fixed.

A material error should be marked in place: the wrong information stated, the correction given, the correction time shown, and the pinned summary revised. Claims that depended on the error should be revised too.

A page should close when the public effect stabilises, the event slows, or the newsroom can no longer check updates at the pace it promised. The closing note should give the final reporting cutoff, the open questions and the next scheduled check.

The archive date should stay 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. Each update should take the form the information needs: a short table, a list, a quote, a correction box. What matters is that each post carries 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, so look at the label, not the screenshot.

How often should a live page update?

When verified information arrives. A page that posts on a fixed rhythm with nothing new is filling space, and a long gap is not a sign that nothing is happening.

What belongs in the pinned summary?

The verified situation now, the immediate effect, the main uncertainty, the reporting cutoff and the next milestone. If any of those is missing, read the newest updates before acting on the summary.