Your volunteers are already using AI. The question is whether anyone told them what’s off-limits.

Barna’s 2026 research on church leaders and AI found that only 5 percent of churches have AI guidelines. Meanwhile, most pastors use AI in some way. That gap is where the trouble starts.

This post gives you a church AI policy that fits on one page. You can copy it, fill in the blanks, and adopt it this month. It’s written for a solo or bivocational pastor with no IT team and no time to waste.

Why a small church needs a church AI policy now

A policy draws a bright line. Inside it, people can move fast.

Barna’s numbers show where pastors are:

So nearly everyone uses it. Most feel uneasy about it. Almost nobody has written down the rules.

That’s a SALY problem in a new outfit. The tools changed. The church’s habits stayed the same as last year.

The risk is quieter than you think

Imagine a 90-person Methodist church. A kind volunteer runs the weekly prayer email. She pastes the whole prayer list into a free AI app to “clean up the wording.”

Now names, diagnoses, and a marriage crisis sit in a consumer account. Nobody meant harm. Nobody told her not to.

One page would have stopped that.

What goes in a church AI policy (the 8 sections)

A church AI policy doesn’t need to be long or written for lawyers. Yours can be short and plain.

Each of the eight sections runs two to four lines on the page.

  1. Purpose. Why the church uses AI at all.
  2. Allowed uses. The green-light jobs.
  3. Never-uses. The red-light jobs.
  4. Privacy. What data can go into which tools.
  5. Disclosure. When you tell people AI helped.
  6. Human review. Who checks AI work before it goes out.
  7. Quarterly review. When you revisit the policy.
  8. Signature. Everyone who uses AI for the church signs it.

That’s it. Below is the full template with suggested wording.

The 1-page template (copy this)

Fill in the brackets. Delete anything that doesn’t fit your church.

1. Purpose

[Church name] uses AI tools to save time on admin, communication, and outreach. AI helps our people do ministry. It never replaces pastoral care, prayer, or personal presence.

2. Allowed uses

Staff and approved volunteers may use AI to draft:

  • Event announcements, bulletin copy, and slide text
  • Social media captions and short video scripts
  • Website copy and blog outlines
  • Volunteer schedules and reminder messages
  • First-time guest follow-up emails (see Human review)

These are the boring jobs that eat a bivocational pastor’s week. I cover a bunch of them in how bivocational pastors can save 10 hours a week with AI.

3. Never-uses

We never use AI to:

  • Write replies to pastoral care, grief, or crisis situations
  • Process counseling notes, prayer requests with names, or confession
  • Handle anything involving minors’ personal information
  • Make decisions about people (membership, discipline, hiring)
  • Impersonate the pastor in a personal message without review

Your church decides where sermon prep lands. Some leaders are fine with AI for research. Others want a hard stop. Pick your line and write it here.

4. Privacy

No member names, contact details, prayer requests, giving records, or care notes go into a free or personal AI account. Church data only goes into the church’s approved business account: [tool name].

This is the rule that matters most. More on it in the next section.

5. Disclosure

When AI does most of the writing on something public, we say so where it makes sense. We don’t use AI images of real people from our church without their permission.

6. Human review

A person reads every AI draft before it’s sent, posted, or printed. Anything sent to a first-time guest is reviewed by [name/role].

7. Quarterly review

[Pastor name] reviews this policy every [January, April, July, October] and updates the approved tool list.

8. Signature

I’ve read this policy and agree to follow it.

  • Name: ________
  • Role: ________
  • Date: ________

The privacy rule, with real prices

Which account you use changes where your data goes. Most church AI policy guides skip this part.

On many free and personal AI plans, your chats can be used to train the model unless you opt out. Claude’s own pricing page lists Free and Pro training as “Opt-out.” Most volunteers never touch that setting. They don’t know it exists.

Business plans work differently. Claude’s Team plan costs $20 per seat per month billed yearly, or $25 month to month. Its pricing page promises “No model training on your content by default.”

Other AI companies sell business plans too. Read the privacy terms on the pricing page before you buy, since prices and terms shift.

What this looks like on a small budget

  • Solo pastor: one Team seat at about $20 to $25 per month.
  • Pastor plus two key volunteers: three seats at about $60 to $75 per month.
  • Everyone else: allowed uses only, in their own accounts, with zero church data.

That’s a cheap way to make your biggest risk go away. It also gives your privacy section a clear line people can remember.

Write your church AI policy for volunteers, not just staff

Policies written for bigger churches assume a staff team and a board. Your church probably runs on volunteers.

Think about who touches AI in a typical week:

  • The person building Sunday slides
  • The social media helper writing captions
  • The greeter team lead sending reminder texts
  • The admin who drafts the newsletter

Each one needs the short, one-page version. If you run social with a helper, pair this policy with how to run church social media with one volunteer and AI.

Keep it printable

Print it. Put it in the volunteer binder. Pin a copy near the office computer. A policy nobody can find is the same as no policy.

Where AI belongs in your first-visit funnel

This is where the policy protects your growth as well as your data.

AI is great at drafting first-time guest follow-up. In my experience, weak follow-up is where most church marketing money gets lost. I call it the 80% follow-up gap.

But the policy sets two hard lines inside your follow-up system:

  1. AI drafts guest emails. A human approves them. Your welcome sequence can start as an AI draft. Someone reads it before it goes live.
  2. Care replies are never automated. If a guest replies “my mom just died,” a person answers. Every time.

If you’re building this out in HighLevel, start with the 5 church automations every small church should turn on first. Then add your policy’s review step to each one.

Thinking about a website bot too? Read should your church website have an AI chatbot? before you install one.

How to adopt your church AI policy in one meeting

You don’t need an IT committee. You need 30 minutes and a printed draft.

  1. Fill in the template before the meeting. Pick your approved tool and your reviewer.
  2. Send it out two days early. Ask people to mark anything unclear.
  3. Spend 10 minutes on the never-uses. That’s the section people care about most.
  4. Spend 10 minutes on the privacy rule. Name the approved account out loud.
  5. Vote or approve it. Use whatever process your church already uses.
  6. Collect signatures that day. Anyone who uses AI for the church signs.
  7. Put the quarterly review on the calendar. Right now, before people leave.

What if people push back?

Some members will want a total ban. That’s fair to hear out. But a ban doesn’t stop AI use. It just stops people from telling you about it.

A clear policy brings it into the light. That’s safer for your people and more honest for your church.

Start with one page this week

Plenty of churches will keep skipping this. You don’t have to.

Copy the template. Fill in the brackets. Adopt it at your next leadership meeting. Then get back to building a church that reaches new people, with AI doing the admin and people doing the ministry.

Want the fill-in-the-blank Google Doc version of this AI policy, plus a volunteer sign-off sheet? Join The Fellowship, my free community for church leaders, and grab the template inside.

Leave a comment

0/5