A fire engine blocks the end of your road. You take a photo, write two lines and post it. When you check back, your post has been shared by people you have never met — and so has a blurry image of a completely different fire, in a different city, from six years ago.
Breaking news is the hardest thing to share well. The information is thin, the pressure to be first is real, and the audience is paying attention for exactly as long as the story stays live. Most of the mistakes below are not the result of carelessness. They come from wanting to help. That is precisely why they need a routine.
A screenshot is a photograph of a moment, stripped of everything that would date it. The timestamp is cropped out. The original post is gone or unlinked. The image has been through four accounts before it reached yours, and each share has made it look more like evidence and less like what it is.
Before you pass one on, try these:
If you cannot find the origin, say so rather than deleting the doubt. “I cannot verify where this was taken” is a perfectly good caption. Better still: ask whether the claim even needs a picture. A road closure can be confirmed from a council notice without a photo of somebody else's flood.
Context is not decoration. A protest photograph without the location is meaningless. A set of crime figures without the period they cover can be made to say almost anything. A council decision summarised without mentioning that it was deferred reads as a decision that has already been made.
The fix is usually one extra sentence. Name the place. Give the date and time. Say who is making the claim — a police force, a witness, an anonymous account, a friend of a friend. If a number comes from a survey, say who ran it and when. If a video has been edited, say so.
And separate what you know from what you assume. “The road is closed both ways, according to the fire service” is useful. “The whole area is being evacuated” when you have seen two people walk away with bags is not.
The strongest urge to post arrives at the moment you know the least. That is not a coincidence; the gap between a thing happening and a thing being confirmed is exactly when speculation is most comfortable to produce and most dangerous to spread.
Watch for the tell-tale signs of a claim that has not been checked. It cites “sources” with no source. Every account quoting it is quoting the same single post. The details keep changing while the certainty stays fixed. Nobody has named a place, a time or an official body.
Run this before you share a claim:
If any answer makes you hesitate, wait. Ten minutes rarely costs you anything. Being wrong in a public post can cost you a great deal.
For most people, your caption is the story. They will not click through, and they will not read the thread. So the words you choose carry the weight of the whole post.
Be stingy with absolutes. “Confirmed”, “banned”, “all”, “never”, “dead” and “arrested” are strong claims, and early reports are often wrong about them. Casualty numbers shift. Causes are investigated for weeks. Names should come from official sources, or not at all — publishing a name before a family has been informed is a cruelty that no amount of accuracy later undoes.
If an incident involves a death, an ongoing emergency or a missing person, remember that the people closest to it may be reading. Write as though they are. Because they are.
Not everything that is true needs to be posted immediately. Live locations of police operations, evacuation points, or crowds gathering at the scene can put people at risk and get in the way of the response. When an incident is active, the most useful thing you can share is often the official guidance and any helpline — not your own running commentary.
Timing matters for quieter stories too. An appeal for a missing person may have been resolved weeks ago. Check the date on the poster before you reshare it, or you will send anxious people looking for someone who is already home.
You will get something wrong eventually. What matters is what you do next.
Do not quietly delete. Deletion looks like concealment, and the wrong version carries on circulating in other people's screenshots without your correction attached. Instead, edit the original post with a clear note, or reply to your own post with the correction and leave it visible. Then share that correction as widely as you shared the error — to the same groups, the same thread, the same audience.
Say plainly what was wrong, what is correct, and when you learned it. One short paragraph is enough. No excuses and no blaming your source; people forgive an honest error far more readily than a defensive one.
Before sharing anything from a breaking story, answer three questions: where did this come from, when is it from, and what would a stranger need to know to read it correctly? If you cannot answer all three, you are not ready to share it.
Do one more useful thing: follow your local council, police force, fire service, NHS trust and transport operator, and keep them where you can find them quickly. When something happens, you will have somewhere solid to point people towards instead of a screenshot of a screenshot.
And get comfortable with the sentence “I do not know yet.” It is not a failure of news sharing. It is the most honest thing anyone can post during a story that is still moving.
Photo: DayronV / Pixabay
Most news summaries lose readers through a handful of fixable habits — buried leads, missing context, jargon and...
A plain-English guide to how UK television ratings are measured in 2025, why streaming data now counts, and how to...
National digests skim over devolution, council budgets and regional economies. Here is how to follow the local...
Your daily spot for concise news digests..
Read More© 2026 Digest Spot · Theme by QuomodoTheme