The fastest-moving conversation in church leadership right now isn't the worship-style debate or the building-vs-mission tension. It's AI.
61% of church leaders now use AI weekly or daily — up from 43% just a year ago. That's a big jump in twelve months. But here's the part that keeps wise pastors awake: 73% of churches have no AI policy in place. Barna's research shows 64% of church leaders say a policy is important. Only 5% have one written.
That gap is where things get expensive. Not necessarily in dollars — in trust.
This post will walk you through a usable, three-page AI policy framework your church can adopt this month. No legalese. No copy-pasted corporate language. Just the questions every church needs to answer, in pastoral plain English.
Three quiet shifts have happened in the last year, and any one of them is enough to force the policy conversation.
First, AI is now in the staff workflow whether leadership knows about it or not. Your worship pastor is using it to brainstorm transitions. Your communications director is using it to draft newsletter copy. Your youth pastor might be running sermon outlines through a model on her phone. The question isn't whether AI is in your church. It's whether you have any agreement about how it's used.
Second, AI is becoming a spiritual authority for the people you shepherd. Recent research found that nearly one in three U.S. adults consider AI spiritual advice as trustworthy as a pastor's. Among Gen Z and Millennials, that figure rises to two in five. That's not an abstract trend. That's the high schooler in your youth group asking ChatGPT for prayer guidance because it never seems too busy.
Third, the public and your members are watching. End-of-year giving statements drafted by AI, prayer requests funneled through a chatbot, sermon transcripts auto-summarized — all of it can be wonderful, and all of it raises a question you should have an answer to: "Did a person look at this before it reached me?"
A written AI policy answers that question before someone has to ask.
Forget the temptation to write something exhaustive. The most useful policy is the one your staff actually reads. Three pages, six sections, plain language.
Start with the why. Something like: "At [Church Name], we believe AI is a tool to free our team to do the work only humans can do — to pray with people, to listen, to disciple, to bear witness. AI never replaces pastoral relationship. It never speaks for the elders, the staff, or the church. It supports our work; it does not become our voice."
This single paragraph saves you a hundred future conversations. Print it on the policy. Print it again at the top of every staff handbook.
Be specific and generous here. Examples that work for most churches:
When the green list is concrete, your team stops asking and starts working.
This is shorter, but more important.
You can add or refine, but those five hold up well for almost any church.
"When AI helps create content sent under the church's name, a human staff member reviews and approves it before it goes out. When AI is the substantive author of something — a transcript, a translation, a summary — we say so."
That's it. Disclosure done.
Three rules cover most situations.
Name a person. The policy lives with someone — usually an executive pastor, operations director, or a designated staff lead — who reviews it twice a year and updates it as tools and laws change. AI moves quickly. A policy that's never reviewed becomes a fiction in eighteen months.
Once the document exists, hold one short meeting. Four questions are all you need.
Most staff teams leave that conversation more aligned than they've been in a year. The policy isn't a constraint. It's permission to use a powerful tool well.
For most churches, the boring use cases are the ones that pay off.
A communications director uses an AI assistant to draft a first version of the weekly all-church email. She edits, adds the pastor's voice, hits send. Time saved per week: about an hour.
An admin uses AI to convert a long staff meeting recording into structured action items. Time saved per week: about ninety minutes.
A children's ministry director uses AI to generate first-draft kids' lesson activities for the next quarter, then a human curriculum reviewer adapts them theologically. Time saved per quarter: a workday.
None of those examples replace ministry. All of them give ministry time back. That's the right question to keep asking: did this give us more time for the things only humans can do?
EvangelOS takes the disclosure-and-data-stays-inside posture seriously. The Google Gemini integration in EvangelOS is admin-side — it helps your staff draft communications, summarize reports, and generate first-draft content inside a member-data-aware boundary, so you don't have to copy member info into an outside tool. AI assists the staff. It does not become the pastor. That's a line we hold on purpose.
If you'd like the editable version of the three-page policy framework above, grab the Google Doc here — it's free to copy and adapt for your church.
Your church doesn't need a 40-page AI manifesto. It needs three pages your volunteers will actually read, and a ten-minute conversation with your staff. AI's a tool. Tools serve ministry. Ministry serves people. People are still the point.
Sources: 61% of leaders use AI weekly/daily and 73% have no policy — churchtechtoday.com; 64% say policy important / 5% have one — barna.com; AI as spiritual authority data — businesswire.com.