A message lands in your neighbourhood group at 7:40 on a Tuesday morning. There is a photo of a flooded junction, a warning that the primary school is closing early, and a line saying a shop on the high street has shut for good. It has been forwarded four times. Someone asks, "Is this true?" and the thread moves on to something else.
Most people who pass along a shaky local story are not trying to mislead anyone. They are in a hurry, they trust the person who sent it, and the details look plausible. But local news is small enough that a wrong detail does real damage. A shop loses bookings over a closure it never announced. Parents rearrange a working day for a school that never closed. A named person gets blamed for something that did not happen.
The answer is not cynicism, and it is not refusing to share anything. It is a short, repeatable routine you can run in the time it takes to drink a coffee. Here is the one worth keeping.
Start With the Source, Not the Story
Before you judge whether a claim is true, find out who is making it. In most forwarded messages the chain is invisible: a screenshot of a post, a photo with no caption, a quote attributed to "a friend who works there."
Ask three questions in order. Who said this first? What is their name and role? Can I see the original, in full, on a page I can open myself?
If the only version you have is a screenshot, treat the claim as a rumour until the original turns up. Cropping takes seconds, captions are easy to rewrite, and the part that was cut away is often the part that changes the meaning. Look for a byline, an organisation name, a contact address, a date. A business announcing its own closure is a source. A stranger announcing it on the business's behalf is not.
Official sources are not always the fastest, but for certain things they are the only ones that count: road closures, school decisions, water notices, police incidents, planning applications. If a claim would normally come from a council, a school, a health service or a police force, check whether that body has said anything at all. Silence is information too.
Dates and Photos Are Where Most Errors Hide
The publish date
Old stories come back with a new haircut. A road closure notice from three years ago gets reposted as this morning's news. A storm photo from a different county appears under a local caption. A fundraising page for a family who have long since moved away resurfaces without context.
Check the date on the page itself, not in the share text. Search results and social posts routinely strip it out, and the word "today" in a caption is doing a lot of work when the article was published in 2019. If you cannot find a date anywhere, that is a reason to slow down, not a reason to assume it is fresh.
One quick trick for photos: look at the season. Leaves, light, what people are wearing, whether the shopfront in the background still exists. A picture of a packed high street posted as "look at the queues today" is easy to disprove if the shop behind it closed two years ago.
The picture
A dramatic image is the easiest thing in the world to move out of context. Run a reverse image search on any photo you have not seen before — right-click the image and search for it, or upload it to one of the standard reverse image tools. If the same photo appears attached to five unrelated stories in five different towns, you have your answer.
Then read the edges of the frame. Shop signs, number plates, road markings, bin colours, the spelling of street names, the language on a poster. These small details are hard to fake and easy to check. If the image has been cropped tightly, ask what is just outside it: a crowd waiting for a bus is not a crowd queuing for a closing-down sale.
For video, watch once with the sound off and count the cuts. A clip assembled from several different recordings is not necessarily false, but it is not evidence of a single event either.
Check the Specifics Before You Repeat Them
General claims are hard to disprove and easy to spread. Specifics are where a story either holds up or falls apart, so focus there.
- Names and titles. Is this person real, spelled correctly, and in the role the post claims? Misspelled names are one of the clearest signs a story has been retold rather than reported.
- Numbers. "Hundreds of homes" and "a dozen streets" are very different claims. Ask what figure the original source actually gave, and whether the share text rounded it upward.
- Places. Does the address exist? Is it the right branch of the right business? Towns with similar street names cause more confusion than you would expect.
- Times and scope. "Closed all week" is not the same as "closed on Monday." "Banned" is not the same as "under review."
- Quotes. Read the whole sentence. A fragment often drops the word "may," "might" or "not," and that one missing word can reverse the meaning.
Then look for one independent confirmation. Two sources that both copied the same original post are one source, not two.
The Ten-Point Accuracy Checklist
Run this before you hit share. It takes about ninety seconds.
- Can I open the original source in full, rather than a screenshot or a forwarded caption?
- Is the publication date visible, and is it recent enough for the claim to still be true?
- Does the story name a specific place I can confirm exists?
- Does the photo show what the caption says, and has it survived a reverse image search?
- Are the names and job titles correct and spelled properly?
- Are the numbers the ones the source actually used?
- Has at least one independent source — ideally an official one — confirmed the main claim?
- Have I read past the headline to check the body says the same thing?
- If there is a quote, have I seen the full sentence in context?
- Would I be comfortable if the person named in this story read what I am about to post?
If you get a "no" on any of the first four, stop. Share nothing, or share the question instead: "Has anyone seen confirmation of this?" That is a useful contribution rather than a risky one.
When It Is Health, Money or the Law
Some local stories carry more weight than others. A rumour about water quality, a benefits change, a scam doing the rounds, a dispute between neighbours, a planning decision that affects your street — these can push people into decisions they cannot easily undo.
For anything touching health, money or legal trouble, go to the body that actually holds the information: the council, the health service, the regulator, the court, the advice service. And if the answer will shape what you personally do next, speak to a qualified professional rather than relying on a group chat. Local knowledge is valuable; it is not a substitute for proper advice.
A Habit, Not a Hurdle
The point of all this is not to make sharing feel like paperwork. It is to keep the local information stream useful, so that when something genuinely urgent appears — a real road closure, a missing person, a genuine safety warning — people believe it and act on it.
Three things worth doing from now on. When you are unsure, say so out loud: "I have not been able to confirm this" is a perfectly good message. When you get something wrong, correct it in the same place you shared it, with the same energy. And when a friend forwards you a shaky story, send them this checklist instead of an argument — it is easier to accept and it works better.
The next message that lands at 7:40 on a Tuesday will still look convincing. You will just have a faster way to tell whether it is true.
Photo: Jakub Zerdzicki / Pexels
