EkklisiaAI for the ΑΩ

English · Διαβάστε στα ελληνικά →

A one-page AI disclosure your church can copy

17 November 2026 · 6 min read

Here is where AI is in our church, and here is where it is not.

A post yesterday by JR Houn, “Churches, It's Time…” (jrhoun.com, 16 November 2026), puts the church's AI work in three steps, in this order: disciple your people on where the lines are, give your staff guidelines, and — if your church uses AI — publish a disclosure of where it is used. The order matters: discipleship is the actual job, and the other two are how a church practices what it teaches.

This site has covered the first two steps: a one-hour session outline for teaching the congregation about AI, and a copy-ready policy template for staff. This piece is the third step — the disclosure itself, in a form your church can copy, adapt, and put on its website this week.

Why say it out loud

When your pastor prays over you, you assume those are his words. If they aren't and nobody told you, something has broken, even if the prayer was beautiful. That is Houn's example, and it is the right one: the issue is not whether AI helped — it is whether people had to guess.

And your congregation is probably not of one mind on this. Lifeway Research asked Protestant churchgoers about pastors using AI in sermon preparation: 44% saw nothing wrong with it, 43% were opposed, and 13% weren't sure. You cannot assume your people share your view, whichever way you lean. A disclosure does not settle the argument — it makes the argument possible, in the open, instead of as suspicion.

There is a wider reason, too. People now doubt everything they see online: the first thought on seeing a photo or a video is “is that AI?” Houn calls telling people “this is AI, this is not” an act of cognitive kindness. The church should be at least one place people don't have to wonder.

The practical version: a disclosure is not a policy and not an apology. It is a short, plain statement of fact: here is where AI is in our church, and here is where it is not. It takes one meeting to agree and one page to publish.

The three steps, in order

1. Disciple first. The people in the pews are already using AI. Barna found nearly half of practicing Christians (48%) would trust AI with their spiritual growth, and a third (34%) say AI's spiritual advice is as trustworthy as a pastor's. A chatbot is available at 2 a.m., never gets tired of you, and never disagrees too hard. It cannot sit with you, bear your burdens, or tell you a hard truth out of love earned over years. Talk about it from the pulpit and in small groups before people settle the question on their own — this site's session outline and its companion piece on what to tell the congregation are built for exactly that conversation.

2. Guidelines for staff. Without even an informal policy, you don't know what your staff are doing with AI or how they are doing it. Barna and Pushpay found only 5% of churches have guidelines — while in a separate Barna survey, 94% of pastors say churches should have them. One staff meeting and one page of “here is what we do and don't do” beats nothing, and the weekend policy template, with the three additions from its v2.0 update, is that page.

3. Then the disclosure. Only once the first two are in place does the public statement mean anything. It is the congregation-facing summary of decisions already made, not a substitute for making them.

The practical version: do them in order, but don't wait for perfection on step one before starting step two. A church that has taught one session and held one staff meeting is ready to publish.

The template: copy, adapt, publish

Pick the lines that are true of your church, delete the rest, and fill in the brackets. Keep it short — if it needs a second page, it is a policy, not a disclosure.

How [Church Name] uses AI

We want you to know where artificial intelligence is part of our church life, and where it is not.

What we use AI for

  • Administrative work: first drafts of announcements, the newsletter, and rotas — always reviewed by a staff member before anything goes out.
  • Study aids: our pastor and leaders may use AI to research background, brainstorm, and check their thinking.
  • [Add or delete lines to match your church — for example, captions on the livestream, translations, or image editing for the website.]

What we never use AI for

  • Sermons, lessons, and prayers are written by the person delivering them. AI does not write what is spoken, sung, or prayed in our services.
  • We do not enter prayer requests, counselling conversations, giving records, or member information into AI tools.
  • We do not record or transcribe pastoral, counselling, or children's conversations with AI.
  • [Add your own lines — for example, we do not use AI-generated images in worship materials.]

Who to ask

If you have a question about how we use AI, or you spot something you think we got wrong, speak to [name / role] or email [address].

Keeping this up to date

We review this statement [every six months / once a year] and whenever we start using a new tool. Last updated: [date].

Two variants are worth knowing. If your church doesn't use AI at all, say so in one line: “We do not use generative AI in our ministry or operations. What you read, hear, and see from us was made by hand by a human.” And for a single item — a graphic, a bulletin, a newsletter — a footer label does the same job: “This [graphic / newsletter / handout] was made with help from AI and reviewed by [name or team].”

The practical version: put the disclosure where people can find it — the church website, the noticeboard, the welcome pack. And give it a review date: a disclosure that goes stale is worse than none, because it describes a church that no longer exists.

An honest limit

This piece is built from JR Houn's post “Churches, It's Time…” (16 November 2026) and the surveys it cites. The survey figures are Barna's and Lifeway's, not ours, and each is labelled with its survey — figures from different surveys should not be combined into a single claim. The template above is our own adaptation of the examples in the post, written for a church to copy and change; it is a starting point, not a legal document, and it does not replace your church's safeguarding, data-protection, or denominational policies — the Responsible AI guide covers the privacy, accuracy, and trust questions behind those lines in more detail. And one limit no template can fix: a disclosure is only as good as the practice behind it. If the staff guidelines don't exist yet, write those first.

Sources: JR Houn, “Churches, It's Time…”, jrhoun.com, 16 November 2026 — the three-step framing (disciple, staff guidelines, disclosure), the author's “line in the sand” (AI as study and brainstorming aid, never a mask or a substitute for genuine connection; prayer is direct communication no model can say for you), the example disclosures, and the author's own AI disclosure (“JR wrote this post. I used Claude to check the Barna numbers against the source and to help me edit and finish the draft.”); Barna Group / Gloo, “AI Is Becoming a Spiritual Authority, Even Among Practicing Christians,” 19 May 2026 (1,514 US adults, November 2025; 442 Protestant pastors, December 2025) — 48% of practicing Christians would trust AI with their spiritual growth, 34% say AI's spiritual advice is as trustworthy as a pastor's; Barna Group / Gloo, Faith & AI (442 US Protestant pastors, December 2025; report 6 October 2026) — 94% of pastors say churches should have AI guidelines; Barna / Pushpay, State of Church Tech 2026 (1,306 US church leaders) — 5% of churches have AI guidelines; Lifeway Research, “Pastors, Churchgoers See AI as Concerning and Confusing,” 21 April 2026 (1,200 US Protestant churchgoers, 2–7 September 2025) — 44% saw nothing wrong with pastors using AI in sermon preparation, 43% opposed, 13% unsure. Figures from different surveys are not combined into a single claim; each figure above is labelled with its survey.

Related reading: A church AI policy in a weekend — the copy-ready template for staff guidelines, step two of the three; Three things your church AI policy probably doesn't cover yet — the v2.0 update's three additions; AI literacy for the congregation — the one-hour session outline for step one, discipling the congregation; What to tell your congregation about AI — the companion piece for that conversation; 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.