A practical breaking-news update workflow for online newspapers

Breaking news demands faster decisions than routine coverage, but urgency does not remove the need for verification. In a small newsroom, one person may report, edit, publish, and manage the homepage. It then becomes easy to lose track of what has been checked, what changed after publication, and what the next shift still needs to confirm. Readers may also struggle to understand how the story they first saw differs from the current version.

The goal is not to publish the greatest number of words first. It is to release the confirmed facts readers need, then make the reporting process and meaningful changes understandable. This guide sets out a practical workflow for roles, article structure, update notes, handoffs, and closure without requiring a large breaking-news system.

Decide what qualifies as breaking news

Not every new development needs breaking-news treatment. Ask whether there is a public-interest reason for immediate publication, such as a threat to safety, a consequential public decision, or a major disruption affecting the community. Do not rush an unverified claim onto the site merely because another outlet has reported it.

Document who can authorize breaking coverage and when others must be called. Specify who makes the decision overnight or on holidays, which events require the responsible editor, and who approves homepage promotion or alerts. Include a backup order for times when the first contact is unavailable.

Define the purpose of the first version. It should contain confirmed facts that readers need now, including immediate safety, transport, or service information where relevant. Background and reaction can be added as they are verified. Do not fill an early story with speculation or repetitive paragraphs simply to make it look complete.

Keep tips and verification status in one place

Information may arrive by phone, messaging services, email, and social platforms. If it remains scattered across personal conversations, reporters can repeat the same calls or miss an important lead. Create one event record containing the time received, provider, contact route, claim, and location of original files. Separate publishable information from internal verification material.

Give every material claim a status such as unverified, checking, independently supported, or officially confirmed. Distinguishing “a source said this” from “the newsroom has confirmed this” helps prevent assumptions from hardening into facts as information passes between colleagues. Preserve the original URL and time checked where possible rather than relying only on a screenshot.

When several reporters are available, divide assignments by location or verification target. One person might monitor official statements, another report from the scene, and another confirm effects on transport or public services. Mark ownership so multiple reporters do not repeatedly contact the same office.

Publish only the minimum confirmed account first

Lead with the confirmed parts of what happened, where, and when. Do not state a cause, casualty total, or responsibility as fact when it remains unclear. Saying that information has not yet been confirmed is not a weakness; it tells readers the present boundary of the reporting.

The headline must stay within the same boundary. A video from the scene or a single unnamed source rarely supports a definitive account of cause and outcome. When a number comes from an authority, attribute it clearly. Be especially cautious about putting rapidly changing figures in a headline.

For information that affects reader action, give the source, scope, and effective time. Road closures, evacuation instructions, and service suspensions can change quickly. Make clear which organization issued the guidance so that it does not appear to be an instruction invented by the newsroom.

Show the reference time and story status prominently

Publication time alone may not adequately describe a developing story. Make the latest update time easy to find near the top, and indicate whether coverage is ongoing or closed. Even when the site automatically displays a modified time, identify meaningful changes so readers can understand what the timestamp represents.

Use one time convention throughout the newsroom. For events crossing midnight, include the date as well as the time. Consider whether the audience could confuse time zones, and verify that scheduled publishing or server settings do not display a time different from actual release.

Maintain a short summary of the two or three most important current facts near the top. Continually appending paragraphs can bury the central development. Rewrite the summary as the situation changes, while preserving significant changes in an update log.

Record what changed in each meaningful update

Distinguish typographical cleanup from substantive revision. There is no need to list every punctuation change, but a revised impact figure, a new agency position, or the lifting of a closure can alter a reader's understanding or actions and should be marked with a time.

A note can be concise: “4:20 p.m. Updated the closure area following a new statement from the responsible agency.” Explain what changed rather than merely announcing that new information was added. If a central claim in the first version was wrong, do not silently overwrite it; use the newsroom's correction process to explain the error.

Internally record who made the update and what evidence supported it. The public article need not list every production action, but the next shift must be able to recover the reasoning. Link to the stored statement, recording, or interview note where access controls permit.

Know when to update and when to publish a follow-up

An article becomes difficult to read when every development related to an event is appended indefinitely. Continue updating the main story for changes in the current situation. Create a separate follow-up for a distinct reporting question, such as analysis of the cause, accountability reporting, or interviews with affected people.

Connect related articles so readers understand the sequence. Add links from the initial alert to a detailed analysis or later comprehensive account. Give follow-ups a concise account of the basic event. Avoid publishing several near-duplicate articles that differ only slightly in headline and wording.

Decide in advance whether the breaking-news URL will remain the primary record or point to a comprehensive follow-up. Changing an address can break shared links and alerts, so prepare a redirect when a change is unavoidable. Do not transform the same URL into an entirely different article in a way that destroys the context in which it was shared.

Verify images and video under deadline pressure

Confirm the capture time, location, and provider of scene material. Compare the original post and visible clues such as weather, signs, landmarks, and terrain to avoid presenting an old or unrelated image as current. Do not publish unverified visuals first on the assumption that they can be checked later.

Consider both public value and possible harm when footage identifies injured people or exposes private spaces. Crop, obscure, or choose a different frame when names, faces, license plates, or addresses are not necessary to the report. Record whether the provider is the creator and what use has been authorized.

Autoplay and graphic scenes can create unnecessary harm. Select only the portion required to understand the story and provide a clear content notice where appropriate. Remember that confirmed text can be published before imagery is available.

Update alerts and social posts with the article

Push alerts and social posts may be difficult to edit and may continue circulating as screenshots. Do not make them more definitive than the article. Include the essential confirmed development and a link, reserving urgent language for information readers genuinely need at once.

When an important fact changes, do not stop after editing the article. Decide, based on likely reach and consequence, whether the existing post needs a reply or correction and whether a new alert is justified. Keep a channel and send-time record to prevent repeated notifications within a short period.

Also check the homepage headline, search description, and social sharing text. The body may be current while a cached card continues to display an old figure. Test one representative shared view after a major change.

Hand off unresolved work, not only the published story

For prolonged coverage, a handoff should emphasize what remains to be confirmed. Record the last verification time, offices already contacted, unanswered questions, the next expected statement, and unpublished tips with the reason they were withheld. Keep contact details and other sensitive information in an access-controlled workspace.

The incoming producer should read the article and event record, then restate the current summary in their own words. Resolve unclear items with the outgoing person before changing assignment ownership. A note that says only “handoff complete” forces the next shift to reconstruct the reporting from the beginning.

Make the responsible editor aware of each transition. High-risk allegations, wording awaiting specialist review, and material deliberately held back should be prominent rather than mixed into a routine task list. Confirm that the incoming person has both document access and publishing permissions.

Close the live phase deliberately

Do not leave a stable event labeled “developing” indefinitely. Confirm the latest official statement and observed conditions, then update the article's status. A final update time and a note that live updates have ended tell readers that later changes may not appear on that page.

At closure, read the headline, lead, summary, and principal figures from the beginning. Incremental editing can leave conflicting tenses, duplicate paragraphs, or an old figure in one section. Check linked alerts and social posts for any serious contradiction as well.

Move continuing reporting questions out of the live log and into the editorial calendar. Assign an owner and deadline for questions about cause, responsibility, recovery, and the experiences of affected people that could not be fully reported during the initial response.

Use a short review to improve the next response

After coverage ends, review the path from the first tip to the final update. Identify verification delays, duplicated calls, gaps between the alert and article, or confusion during a shift change. Focus on repeatable process weaknesses rather than finding an individual to blame.

Revise templates and checklists from actual experience. Add one or two missing items to the contact tree, update log, visual verification list, or handoff form. A form that is too long will be ignored under pressure, so retain only fields that support a decision or protect accuracy.

To prepare today, name the breaking-news decision maker and backup. Add fields for verification status, owner, and next check time to an event record. Put the latest update time and current summary at the top of each developing article, and log every meaningful change. This small structure turns urgent coverage from improvised reaction into a repeatable editorial process.