Sometime in the last year, AI stopped being a topic your church would decide whether to touch. It slipped in quietly through Canva, through email drafts, through the sermon prep tool a small group leader was already using at work. The question is no longer whether AI is in your ministry. It is whether anyone has said out loud what it should and should not be doing there.
The most recent research is stark. Around 64 percent of churches believe an AI policy is important. Only 5 percent have one in place. That gap is not a scandal. It is a very human lag between a technology moving faster than most staff meetings can keep up with. But we think fall 2026 is the reasonable outside edge. Before the program year picks up, before another volunteer starts drafting newsletters with a tool nobody vetted, it is worth putting one page on paper.
Why a one-page policy is enough for most churches
We are not fans of long, lawyerly documents that live in a shared drive and get read once. For most churches, a one-page AI policy will do more real work than a twenty-page one, because staff and volunteers will actually remember what it says.
The point is not to cover every future scenario. The point is to give the people already using these tools a clear enough frame that they can make good calls in the moment. If a policy answers roughly six questions in plain language, you are ahead of almost every other congregation in your city.
The six questions your policy should answer
What are we comfortable using AI for? Naming this in the positive first matters. Sermon research help, first-draft newsletters, meeting summaries, image generation for social posts, cleaning up transcripts, answering routine questions on the website. When staff know what is clearly fine, they stop hiding what they are already doing and start doing it better.
What will we never hand to AI? This is the shorter, more important list. Pastoral counseling notes. Anything a member shared in confidence. Prayer requests submitted through your site. The final words of a sermon delivered on Sunday. The eulogy at a funeral. A response to a family in crisis. The line is not about capability. It is about presence and trust.
When do we disclose that AI helped? Congregations are asking. Our recommendation for most churches is simple. If AI substantially shaped the content, say so briefly. A short note in the footer of a blog post, a line in a devotional email, a quick acknowledgement when a leader used a tool to prepare a study. Silence is not neutral here. Once people find out later, it feels like something was hidden.
Where does member data go? This is the question most policies skip and most lawyers wish they would not. Free AI tools often train on what you paste into them. That means birthday lists, giving records, prayer chains, and youth rosters should never be dropped into a general-purpose chatbot. Your policy should name which tools are approved for member data, and default everyone to assume the answer is none unless it is on the list.
Who owns the decision when we are not sure? Every policy needs a human name attached. A staff member, an elder, a small committee. Not because they will be right every time, but because a question with a clear person to bring it to gets asked. A question with no one to bring it to gets guessed at.
How often do we revisit this? Twice a year is plenty. The tools will keep moving. Your policy should move with them, without becoming a project that consumes a whole quarter.
What we see actually work
The churches we help draft these are almost always surprised by how quickly the conversation moves once it starts. The hard part is not the writing. The hard part is admitting, in a room with your team, what tools you are already using and where you are unsure.
We recommend a single ninety-minute meeting. Bring the staff who touch communications, the person who manages your church database, and one elder or board member. Walk the six questions in order. Have someone type the answers as you talk. What you have at the end is a draft. Sit with it for a week. Then post it where staff and key volunteers can see it, and send a short note to the congregation explaining that it exists and where they can read it.
Most of the ministries we walk with land somewhere around three hundred words. That is the entire policy. It is enough.
A quiet way to lead
There is a temptation to treat AI as either a threat to guard against or a shortcut to celebrate. Neither posture ages well. What ages well is a church that noticed the shift, thought about it out loud with its team, and put a short, humble document on the wall that says here is how we want to use this thing and here is where we will not.
That kind of quiet leadership is exactly what many members are hoping to see from their pastors right now. Not a pronouncement on artificial intelligence in the abstract. A clear, human answer to the small question they will not always ask out loud, which is whether the note in their inbox this week came from a person who knows them.
We help churches and faith-based nonprofits write these kinds of policies, and build the websites and systems that make them easy to live out. If you would like a hand drafting your one page before fall picks up, reach out through our contact page and tell us where you are starting from.