Before you share an urgent online claim, use this five-minute check

Urgency is a reason to slow down

A message says a bank account is at risk, a new rule takes effect tonight, a product is dangerous, or a friend needs immediate help. It may arrive as a screenshot, a short video, a forwarded voice note, or a post with thousands of reactions. The natural response is to warn someone else quickly. That instinct can be generous. It can also turn one unverified fragment into a much larger problem: people may click a malicious link, send money to an impersonator, panic about a false claim, or miss the details that would let them respond sensibly.

The useful habit is not to become suspicious of everything. It is to match your confidence to the evidence before you amplify a claim or act on it. The Federal Trade Commission advises people to pause when an unexpected message asks for money or personal information, and to contact an organization using details they independently look up. CISA’s public guidance similarly recommends letting an emotional reaction cool, understanding the content beyond its headline, and checking trusted reporting or primary sources. Those are small steps, but they create space for better decisions.

This matters even when a post is not a deliberate scam. A true photograph can be old. A genuine quotation can be missing the sentence that changes its meaning. A local notice can be presented as if it applies everywhere. A popular account can repeat an error made by another popular account. Sharing is not the same as endorsing, but it does give a claim another route to an audience. A short check respects the people who may rely on it.

First, separate the claim from the feeling

Start by putting the message into one plain sentence without its dramatic language. Instead of ‘Everyone needs to see this now,’ write down what it actually asserts: ‘This company is asking customers to move funds,’ or ‘This school will close tomorrow,’ or ‘This video shows an event that happened today.’ Then ask what the post wants a reader to do: share it, click, pay, download, vote, avoid a place, or simply become angry or afraid. The action request often reveals why the claim needs a closer look.

Strong feeling is not proof that a claim is false. It is a signal that you may be more likely to react before checking. CISA warns that provocative headlines and memes can prompt passionate responses; the FTC notes that scammers use surprise and time pressure to keep people from checking a story. A message that says ‘do this before it is deleted’ or ‘do not tell anyone’ deserves an especially deliberate response. Urgency can be real, but a legitimate instruction can still be confirmed through a channel that is not controlled by the message itself.

• What exactly is being claimed, in one sentence?
• What action does the sender want me to take right now?
• What detail would have to be true for that action to be sensible?

Find the source, not just the account that posted it

A familiar name, a blue badge, a polished logo, or a long list of reposts does not establish where information began. Look for the original document, full recording, official notice, data release, court filing, product recall, or first-hand organization responsible for the matter. If a claim is about a school, check the school or local authority’s own channels. If it is about a company account, type the company’s known web address yourself or use contact details from a statement you already trust. Do not rely on a phone number or link inside the alarming post.

There is an important difference between checking a source and finding a source that agrees with you. A genuine source should be able to answer basic questions: who published it, when, what evidence it is based on, and what its limits are. A screen capture often hides all four. Open the surrounding page when possible. Read beyond the headline or clip. If the only trace of a major claim is a chain of accounts quoting one another, you have found a distribution network, not independent confirmation.

For claims that could affect health, safety, money, rights, or a public service, seek the authority responsible for the decision as well as reliable independent reporting that names its evidence. This is not an instruction to believe authorities uncritically. It is a way to locate the record that can be examined, corrected, dated, and compared with other evidence. If the relevant authority has not confirmed a supposedly urgent development, say that clearly rather than filling the gap with assumptions.

Check time, place, and missing context

Many misleading posts are built from material that was real somewhere else or at another time. Check the publication date, the location, and whether the event is still current. Search a distinctive phrase from the caption, a name on a sign, or a reverse-image match to find earlier appearances. For a video, look for the full version: a short excerpt may omit a correction, an answer to a question, or the event that prompted the reaction. Treat date labels added by a reposting account as claims to verify, not as proof.

Then look for what the message leaves out. Is a number presented without its denominator or timeframe? Is a policy proposal being described as a final rule? Does a photo show an outcome but not the cause? Has a headline made a tentative finding sound certain? Context is not an excuse to dismiss an uncomfortable fact. It is what lets a reader understand the fact accurately enough to decide what it means.

A useful test is to ask what evidence would change your mind. If there is none, you are no longer verifying a claim; you are defending a conclusion. If a simple dated notice, a full document, or a direct confirmation would settle the point, find it before sharing. And if the evidence remains mixed, the honest result may be ‘I cannot confirm this yet.’ That is a valuable message in its own right.

Use a different rule when money or access is involved

When a message asks for money, a password, a verification code, an identity document, remote access to a device, or a download, move from ordinary fact-checking to a safety check. The FTC says not to respond to unexpected messages that request money or personal information, and to reach the purported organization through contact information you know is real. A sender who claims to be a bank, government agency, delivery service, employer, charity, or friend does not become trustworthy merely by naming one.

Do not try to prove the message is fraudulent by replying, clicking its link, or calling the listed number. Start a new browser search, use a saved official app, or call a number printed on a card or an established statement. If the request is from someone you know, confirm it through a separate channel; an account can be compromised. The same principle applies to a tempting giveaway, investment pitch, or bargain: pressure to act fast, secrecy, and unusual payment methods are reasons to stop, not reasons to negotiate.

If you already clicked or paid, shift from embarrassment to containment. Contact the payment provider or financial institution using verified details, change a password if it may have been exposed, and report the account or post through the relevant platform and official reporting route. The exact recovery options depend on the service and country, but delay can reduce them. A calm, factual report can also help prevent the next person from being drawn in.

Share corrections in a way people can use

Finding a problem in a post does not require turning the correction into a public trial. If a friend or colleague shared it, begin with the claim and the evidence rather than a judgment about their motives: ‘This appears to be from last year; here is the dated notice,’ or ‘The company says this number is not theirs; use this official contact page instead.’ Give people a safer next action. A correction that only says ‘fake’ may leave a real concern unresolved and can encourage someone to look for another unreliable answer.

Avoid repeating a false claim more vividly than the correction. Lead with what is known, link the original source, and acknowledge uncertainty where it remains. If a post contains a risky link or request, do not quote it in a way that makes it easier to click. Report it through the platform instead. For a rumor involving a local emergency or public service, point people to the specific official update page and its publication date so they can check for changes themselves.

The goal is not to win an argument. It is to improve the information environment shared by a family, workplace, school, or community. That becomes easier when the correction makes a clear distinction between a confirmed fact, an unverified report, and a false or impersonating request. People are more likely to pause next time when they can see the method, not just the conclusion.

A five-minute routine worth keeping

Before you forward an urgent-looking claim, take five minutes: name the precise claim; notice the action it requests; find the underlying source; check date, place, and context; and use an independently verified route for anything involving money, credentials, or a consequential decision. If you cannot complete those checks, reduce your confidence and do not add a certainty you do not have. You can still share a careful note saying that the claim is unconfirmed and where people should look for reliable updates.

This routine will not make every confusing situation simple. Some facts take time to establish, and reputable sources can correct their own early reporting. But it prevents a common error: treating speed, emotion, and repetition as substitutes for evidence. In an online world built for rapid reaction, choosing a brief, evidence-led pause is one of the most useful things a reader can do for other people.