A patron walks up with a phone, a screenshot, and one question: "Is this true?" That's where source evaluation actually gets taught in a library. Not in a slide deck, but in the two minutes we spend at the desk showing someone how to check.
The goal isn't to turn every patron into a fact-checker. It's to send them home with three or four moves they'll actually use the next time something lands in their group chat.
Most of us learned source evaluation as a checklist: authority, accuracy, currency, purpose, bias. Those concepts matter, but a long checklist loses people before they ever apply it on a phone. What sticks is a short pause with three questions:
The most effective teaching I've seen happens out loud, in the middle of an ordinary reference question. Staff just narrate what they're doing:
The same skill shows up across your services with different stakes:
When everyone uses the same language, patrons hear consistent guidance whether they're at the main branch or a storytime outreach table. But don't turn it into another four-hour training. I'd give staff four questions and a little permission:
1. Who is responsible for this, and what expertise or accountability do they have?
2. What evidence, documents, or named sources back it up?
3. When was it published or updated, and does timing matter here?
4. What do other credible sources say?
Then be honest about the gray areas. A local Facebook group post may be the only source for a road closure and still be useful. A personal story can be meaningful without proving a broad claim. A government page can be authoritative and three years out of date. Teaching source evaluation well means holding those distinctions, not pretending one label settles everything.
And give staff permission to say, "I'm not sure. Let's check together." That one sentence models healthy skepticism better than any handout.
"Evaluating Information Sources" gets you a handful of attendees. "How to Check a Health Claim Before You Share It" or "Is This Job Post Real?" gets people in the door. Same content, clearer reason to come.
What works in practice:
The gap I hear about most is practice. A workshop teaches the method once, but evaluating sources is a habit, and habits need a daily dose of real news to work on. That's why I point libraries to Newsreel.
Newsreel turns real news, written and fact-checked by journalists, into a daily habit. It was started by journalist Jack Brewster, who broke the story on the source of the viral false claim that Haitian migrants were eating pets in Springfield, Ohio, so source-checking is in its DNA. What makes it practical for this work:
Logins and attendance count, but they don't tell you whether anyone checks a claim differently. Add two or three quick questions to your feedback form: Do you feel more confident checking a claim? What's one step you'll use? Did you find a trusted source for something you needed? For systems, one shared workshop outline and common outcome questions save every small branch from building its own.
The risk with this work is leaving people convinced that nothing can be trusted. That's not the lesson. Trust can be earned, checked, and adjusted when new information shows up.
We do this best when we make it ordinary. Ask where it came from. Look for the evidence. Compare credible accounts. Then help the patron use what they found for the decision in front of them. One careful question at a time, that's a public service only a library can offer this well.