Reply To: How can a non-technical user set up AI to flag claims that need fact-checking?

Quick win: Pick one headline claim you saw today, copy the one-sentence claim, paste it into the prompt below and get a 60–90 second read on whether reputable sources back it. Do that now — you’ll see how fast this works.

The problem

People share claims without checks because it’s fast and feels harmless. AI can help, but it also makes confident-sounding mistakes unless you force it to name sources and dates.

Why this matters

False or outdated claims spread quickly. Your simple process reduces the risk of sharing misinformation and protects your credibility — especially online or in groups you influence.

Short lesson from experience

I’ve set this up for busy teams: the difference between “looks plausible” and “verified” is a two-line source check. Once people ask for sources and dates, garbage claims get filtered out immediately.

What you’ll need

• A smartphone or computer with a browser.
• An AI chat you can access (free is OK, but always ask for sources and dates and avoid sharing private info).
• Optional: a keyword-highlighting browser extension (pick one with good reviews and minimal permissions).
• A simple tracker: notes app or spreadsheet with columns: Claim | Date | AI verdict | Sources | Action.

Step-by-step (how to set this up and use it)

1. When you see a claim, reduce it to one sentence (who/what/when).
2. Paste this prompt into your AI (copy the prompt below and replace [CLAIM]).
3. Read the AI reply and check for: named reputable sources, dates, and a clear confidence level.
4. If the answer lacks sources or is “mixed,” mark as “Needs deeper check” and save to your tracker.
5. Weekly: review saved items, run the deeper prompt and update the tracker with final verdict.

Robust copy-paste AI prompt (quick check)

“Here is a one-sentence claim: [PASTE CLAIM]. In 3 short bullets: 1) Say whether reputable sources support or contradict this and name up to three specific sources with dates; 2) State your confidence (high/medium/low) and why; 3) List one next place to verify (specific journal, agency, or news outlet). Use plain language.”

Metrics to track (KPIs)

• Claims flagged per week (target: 5–10 first week).
• % of flagged claims confirmed unsupported (goal: identify at least 20% unsupported initially).
• Average time per check (goal: <5 minutes for quick checks).
• Shares prevented (estimate: how many times you didn’t re-share a flagged claim).

Common mistakes & fixes

• Mistake: Trusting an AI reply that names no sources. Fix: Ask it to list sources and dates; if it can’t, mark as Needs deeper check.
• Mistake: Using vague claims. Fix: Reduce to one clear sentence before you check.
• Mistake: Installing an extension without checking permissions. Fix: Choose extensions with few permissions and good reviews.

1-week action plan (day-by-day)

1. Day 1: Do 5 quick checks with the prompt above; log results.
2. Day 2: Install a keyword highlighter and add 5 keywords you care about.
3. Day 3–5: Let flags come in; run quick checks and mark “Needs deeper check” when needed.
4. Day 6: Run deep checks on two saved claims (use the deeper prompt from your AI if needed).
5. Day 7: Review metrics, refine keywords, and pick 3 trusted sources to prioritize next week.

Polite correction: free AI tools are fine for quick triage, but never rely on them alone — always require named sources and dates, and avoid pasting private or sensitive content into chats.

Your move.