Your worship director is already using AI to draft song intros. Your office administrator is quietly running meeting notes through a summarizer. Someone on your team asked a chatbot a pastoral question last week and didn't tell anyone.
This is happening in nearly every church right now — often without a plan, and almost always without training. Recent surveys found that 61% of church leaders now use AI weekly or daily, up from 43% a year earlier. Yet only about 12% of pastors feel comfortable teaching on it, and roughly three-quarters of churches have no guidance in place at all.
The good news? 87% of church leaders say they're willing to invest in training. The gap isn't willingness. It's that no one has shown them a simple way to start. So let's fix that.
Start With Honesty, Not a Policy
The instinct is to write a rulebook first. Resist it. A page of restrictions handed to people who are already using these tools tends to do one of two things: it gets ignored, or it pushes usage underground where no one can learn from it.
Begin instead with a single honest conversation. Gather your staff and volunteers and simply ask: who's already using AI, and for what? You'll be surprised. Naming what's already happening turns a vague anxiety into a shared, workable reality — and it earns you the trust to guide it.
Teach the Three Questions
Most AI training gets lost in tool tutorials that are outdated within months. What lasts is a way of thinking. We encourage churches to teach their teams three simple questions to ask before leaning on AI for anything:
Is this a task or a relationship? Drafting an email, summarizing a document, or brainstorming event names are tasks — AI is genuinely useful here. Comforting a grieving family, discipling a new believer, or making a pastoral judgment is a relationship. AI has no business standing in for that, and your team should be able to feel the difference instantly.
Would I be comfortable if someone knew I used it here? This one quietly handles most gray areas. Using AI to tidy up newsletter grammar? No problem. Using it to write a "personal" note of sympathy that a member believes came from your heart? That's a different thing. Transparency is the test.
Can I verify what it told me? AI sounds confident even when it's wrong. Teach your team to treat every factual claim, Scripture reference, and statistic as a draft to check, not a truth to trust. This single habit prevents the most damaging mistakes.
Do One Real Task Together
Abstract training doesn't stick. Hands-on training does. Block one hour and walk through an actual church task as a group — turning a sermon into three social media captions, drafting a first pass of a volunteer thank-you email, or building an outline for next quarter's newsletter.
Let people watch a good prompt take shape. Show them the messy first result, then how you refine it. Show them where it got something wrong and how you caught it. That single hour of doing the real thing teaches more than any slide deck, and it gives your team a concrete win they can repeat on Monday.
Match the Tool to the Person
You don't need a dozen subscriptions. Most churches are well served by a small, practical stack: a general assistant for writing and brainstorming, a transcription tool for meetings and sermons, and whatever AI features already live inside the design and email tools you use.
Point each person to the one or two tools that fit their actual work. Your communications volunteer needs different things than your bookkeeper. Overwhelming everyone with every option is the fastest way to make sure nobody adopts anything.
Write the Short Guidelines Last
Now — after the conversation, the three questions, and the hands-on hour — is when a written guide actually helps. Keep it to a single page. Name the tools you've approved, the kinds of tasks they're good for, the lines you won't cross (pastoral care, confidential member data, anything presented as personal that isn't), and who to ask when someone's unsure.
Because your team helped shape it, they'll actually follow it. A guideline that grows out of shared practice is a living document. One handed down cold is just another file nobody opens.
Formation, Not Just Efficiency
It's worth remembering why this matters. The point of training your staff to use AI well isn't only to save time, though it will. It's stewardship — of your team's attention, of your members' trust, and of the human, relational work that no tool can do for you.
A church that trains its people thoughtfully ends up with staff who use these tools with wisdom instead of anxiety, who know where the line is, and who spend the hours they save on the things that actually require a person. That's a good outcome. And it's within reach of any church, regardless of budget.
You don't need a technology department to get there. You need one honest conversation, three good questions, and an hour of practice.
If you'd like help building a simple AI training plan or a one-page guide your team will actually use, reach out. We'd be glad to think it through with you.