Your church needs an AI policy. Here's the one-page version.

Most churches do not decide to adopt AI. It arrives quietly. A staff member starts drafting the midweek email with ChatGPT. A volunteer builds a small-group guide with it on a Tuesday night. A worship leader asks it to reword a slide. By the time leadership notices, the practice is already a habit — and nobody ever agreed on the edges.

That gap is the real risk. It is not that churches are reckless with AI; it is that most have never had the conversation. In recent church-technology surveys, more than nine in ten church leaders said they support some role for AI in ministry. In the same studies, roughly three-quarters of the churches already using it had nothing written down — no shared understanding of what it should touch, who checks its output, or what happens to the personal information it sees.

So here is the encouragement: you do not need a legal document. You need one page, four questions, and one meeting. This article walks through all three.

Why a policy — and why only one page

The word "policy" makes people picture a binder. Set that image aside. A church AI policy is not a restriction document; it is a permission document. Its job is to tell your staff and volunteers, in plain terms, what they are free to do — and to draw the few edges that actually matter, so nobody has to guess.

When there is nothing written, two failure modes show up. The cautious people freeze: they avoid a tool that could genuinely give them back an afternoon, because no one told them it was allowed. The enthusiastic people overreach: they paste a counseling conversation or a giving record into a public chatbot, because no one told them not to. A short policy fixes both at once.

It has to be one page for a simple reason. A twelve-page document does not get read, does not get remembered, and does not get followed. A one-page document can be read in a staff meeting, posted next to the office printer, and handed to every new volunteer. If your policy cannot fit on a page, it is not yet a policy — it is a draft.

The four questions a church AI policy has to answer

Strip away the formatting and every workable church AI policy answers the same four questions. Get these right and the document almost writes itself.

1. What is AI allowed to touch — and what it isn't?

Name the green zone and the red zone in concrete terms. The green zone is usually broad: bulletins, announcement copy, social posts, event descriptions, first drafts of newsletters, research and brainstorming, summarizing a long document. The red zone is short but firm: pastoral counseling notes, anything a member shared in confidence, giving and financial records, and any final word on doctrine or church discipline.

The principle underneath both lists: AI is welcome on the administrative work and never substitutes for the pastoral work. It can draft the email that invites someone to a grief group. It does not sit in the room.

2. Who reviews it before it goes out?

Every piece of AI-assisted content that reaches a member or the public gets read by a named human first. Not "someone." A role. The bulletin is reviewed by the communications lead. A sermon illustration is the preaching pastor's call. A small-group guide is checked by whoever owns groups. AI produces the draft; a person owns the decision to send.

3. What happens to people's information?

This is the question most churches skip, and it is the one with real consequences. The rule is plain: do not put information that identifies a specific person into a public AI tool. Names, addresses, health situations, financial details, prayer-request specifics — these stay out. If a task genuinely needs that data, it belongs in a tool built for ministry that keeps your church's data isolated, not in a consumer chatbot whose terms you have not read.

4. When do we tell people AI was involved?

Decide your disclosure habit on purpose, before it is tested. A common and healthy standard: routine administrative copy — an event reminder, a calendar note — needs no label. But anything that carries pastoral weight, or that a reader would assume came straight from a person's own study, gets a simple line of honesty. Many churches settle on a single sentence: "Drafted with AI assistance and reviewed by church staff." It costs nothing and it protects trust.

A policy is not the church being suspicious of its staff. It is the church being clear with them — so the careful feel free and the eager stay safe.

A one-page policy you can adapt

Here is a starting draft. Read it as a skeleton, not scripture — change the wording to fit your tradition and your team, then bring it to your leadership for a real decision.

How to get it adopted — without a six-month committee

A policy that never gets approved protects no one. Keep the path short.

• One person drafts it. Adapt the page above. This is an afternoon of work, not a quarter.
• Bring it to the next leadership meeting you already have. Do not schedule a special summit. Fifteen minutes on an existing agenda is enough.
• Decide, date it, and name an owner. A policy with no owner drifts. One person keeps it current as tools change.
• Read it to the team and post it. Walk your staff and key volunteers through it once, out loud, then put it where they will see it.
• Revisit it twice a year. The tools change quickly. Two short reviews a year keep the page honest.

That is the whole project. Not a binder, not a working group, not a consultant — one page, one meeting, one owner. The churches that handle AI well in the next few years will not be the ones with the most sophisticated tools. They will be the ones who had the conversation early, wrote the answer down, and kept it short enough to follow.

Want the editable version? The one-page policy template is in our resource library — free, no strings.