AI literacy for the congregation
Most of this site's policy work has been aimed at staff and leadership: the pastor who drafts with AI, the administrator who handles giving data. But the people in the pews are using AI too — for work, for homework, for health questions, for prayer. And nobody has sat down with them to talk about how.
This past weekend in Washington, the Forward Religions Conference did something about that gap. The conference, presented by the National Museum of African American History and Culture's Center for the Study of African American Religious Life for the center's 10th anniversary, brought Black faith, culture and technology into the same conversation. On Saturday afternoon, Dr. Fallon Wilson introduced “We Have Come This Far By Tech: Black Religion, Home, and Techno-Possibility,” and with it a multifaith public interest technology curriculum: a 70- to 80-page introduction to machine learning, data and the questions they raise for people of faith, drawing on Christian, Islamic and African-centered traditions.
The curriculum itself is not the point for a local church. The point is that someone has shown a faith-shaped AI curriculum is possible — and that a congregation can talk about AI the way it talks about anything else that shapes daily life: honestly, practically, with its values in the room.
What AI literacy means for ordinary members
AI literacy for a congregation is not a technical course. Nobody needs to understand how a language model is trained. What people need is a working sense of three things: what AI does well, what it does badly, and what it should never be handed.
What it does well is the easy part — drafting, summarising, translating, searching, organising — and most members already know it from their own use. What it does badly is the part worth naming out loud: AI can be confidently wrong. It invents quotations, garbles facts, and presents guesses in the tone of certainty. An unchecked AI summary in a Bible study handout can pass on an error that sounds authoritative.
The practical version: teach one habit — treat AI output as a first draft, never a finished answer. Check anything that matters against a real source, the way you would check a quote before putting it in the bulletin. That one habit covers most of the risk, for teenager and grandparent alike.
Spotting what AI made
The second skill is recognition. AI-made images, videos and voices are now good enough to fool a casual glance, and they are already circulating in church life — a dramatic photo in a group chat, a voice note that sounds like someone you know, a “news story” that never happened. Members need the pause before sharing, not forensic tools. Does the image look slightly wrong? Does the story appear in any source you trust?
The practical version: make “check before you share” a congregational norm, not a scolding. One person forwarding a fake image to the church group chat does more damage than one person believing it quietly: if you cannot verify it in a minute, do not pass it on.
What never to paste in
The privacy lesson is the most important part of the session, and the one most members have never heard. A general chatbot is not a private conversation: anything typed into it may be stored, reviewed, or used to train future models — and the free version of a tool is the most likely to do all three.
That matters in a church because the things people most want help with are the most sensitive: a prayer request with someone's medical details, a pastoral situation described in full, a child's schoolwork, a safeguarding concern. None of that belongs in a chatbot. The “never-enter” list from this site's policy template was written for staff, but it applies word for word to members: private, pastoral, medical and children's information stays out of AI tools.
The practical version: give the congregation the same two short lists the staff has — what never goes into a chatbot, and what never leaves human hands — printed on one page. People remember a list they can stick on the fridge.
A familiar voice asking for money
The scam lesson is the one that pays for the whole session. A message that sounds like your pastor, in their voice, asking for money urgently — a gift card, a transfer, a password reset — is exactly the kind of request a church member is built to honour quickly. And it is exactly the kind AI can now fake — the same goes for a “fellow member in trouble” or a “church office” asking for bank details.
The practical version: agree one rule and say it from the front, so everyone hears it together: any unusual request involving money, a password or access — however familiar it sounds — gets checked on a second, separate channel before anything moves. Call the person back on a number you already have. That single habit is worth more than any clause in a policy, and it is the same rule the newest version of the Church Law & Tax template now recommends.
AI and children
Children deserve their own five minutes: they use AI in ways adults often do not see — homework help that becomes homework done for them, chatbots treated as confidants, AI companions that listen without judging and never tell a parent. The watch-out is not that children use AI — it is that they use it alone. A chatbot will not flag a safeguarding concern, will not notice a child in distress, and will happily keep a secret that should not be kept.
The practical version: the rule for children is the same as the rule for adults, said plainly: AI is a tool, not a friend and not a secret-keeper. Anything personal, anything that worries you, anything you would not want your parents to read — that goes to a person, not to a chatbot. And parents should know which AI tools their children can reach.
A session outline a church could run this month
None of this needs a course. One evening, one hour, four short parts:
- What AI is, in plain words (10 minutes): what it does well, what it does badly, and the one habit — treat output as a first draft.
- Spot the fake (10 minutes): two or three real examples — an AI image, a fake voice message, a made-up news story — and practise the pause before sharing.
- What never to paste in (10 minutes): the two short lists, printed on one page to take home.
- The scam rule (10 minutes): the familiar voice asking for money, and the second-channel check. Then questions — and the questions are the point.
Then do what Dr. Wilson asked of pastors: be honest about how the church itself uses AI. If the pastor uses it for research, say so — and say how. “If you're going to use it to synthesize literature about a text, outline how you did it,” she said. A congregation that hears its leaders describe their own AI use, limits named, will trust the guidance far more than one handed a list of rules.
An honest limit
This piece is built from Word In Black's report of the Forward Religions Conference (12 November 2026), published before the conference took place — so the curriculum is described here only as Dr. Wilson described it beforehand: a 70- to 80-page introduction to machine learning, data and the questions they raise for people of faith. We have not read the curriculum itself, and claim nothing about its contents beyond that description, or whether it is publicly available. The session outline above is our own suggestion, not the conference's programme. And as with everything on this site, this is general guidance, not legal or safeguarding advice — your church's own policies always take precedence.
Sources: Word In Black, “Black Churches Are Asking Bigger Questions About AI,” 12 November 2026 — the Forward Religions Conference, 13–15 November 2026, Washington, presented by the National Museum of African American History and Culture's Center for the Study of African American Religious Life, marking the center's 10th anniversary under the theme “Welcome Home”; Dr. Fallon Wilson (vice president of policy, Multicultural Media, Telecom and Internet Council; co-founder, Black Tech Futures Research Institute) introduced “We Have Come This Far By Tech: Black Religion, Home, and Techno-Possibility” at 1:15 p.m. on 14 November; the multifaith public interest technology curriculum debuted there, described by Wilson as a 70- to 80-page introduction to machine learning, data and the questions they raise for people of faith, drawing on Christian, Islamic and African-centered traditions; Wilson's guidance that pastors using AI for research should have a policy and document the process, quoted verbatim: “If you're going to use it to synthesize literature about a text, outline how you did it.” One limit, stated in the article: the report was published before the conference took place, so the curriculum debut is described in future tense there — post-event confirmation was not checked, and nothing is claimed about the curriculum's contents beyond Wilson's description or whether it is publicly available.
Related reading: A church AI policy in a weekend — the copy-ready template whose never-enter list this piece extends to members; Three things your church AI policy probably doesn't cover yet — the v2.0 template's deepfake-verification rule, the same second-channel check this piece recommends from the front; What to tell your congregation about AI and 94% of pastors say churches need AI guidance. Only 4% have a policy. — the congregation-facing companion pieces; Responsible AI — the site's guide to privacy, accuracy and trust. This guidance is general and educational, not legal or safeguarding advice; your church's own safeguarding, data-protection, and denominational policies always take precedence.