By Brent Lacy

Most AI training for pastors falls into one of two traps. Either it is so technical that you need a computer science degree to follow it, or it is so vague that you finish the session knowing nothing more than “AI is important.” Neither one helps you on a Tuesday morning when you have a sermon to write and a hospital visit at noon.

This is a four-week self-guided path. Each week has a clear focus, specific exercises, and a concrete outcome. By the end, you will have real working knowledge of AI tools, a personal framework for using them ethically, and a plan for helping your congregation work through the same questions.

You do not need a seminary degree. You do not need a technology background. You need about 30-45 minutes per week and a willingness to try things that feel unfamiliar.

Week 1: Understanding What AI Actually Is

You cannot use a tool wisely if you do not understand what it does. This week is about building an accurate mental model of AI, not a technical one.

What AI Is (In Plain Language)

Large language models, which is what ChatGPT and Claude are, work by predicting what words should come next based on patterns in enormous amounts of text. They have processed more written material than any human could read in a thousand lifetimes. When you ask a question, the model generates a response that fits the pattern of how that question has been answered in its training data.

This means AI is very good at tasks that involve language patterns: summarizing, drafting, explaining, translating, brainstorming, and organizing. It is not good at tasks that require current information, verified facts, or genuine understanding. It does not know what is true. It knows what sounds like a plausible answer based on patterns.

That distinction matters for ministry. AI can help you draft a newsletter. It cannot tell you whether a theological claim is accurate. You have to bring that judgment yourself.

What AI Is Not

AI is not intelligent in the way humans are intelligent. It does not understand what it says. It does not have beliefs, values, or intentions. It does not pray. It does not know your congregation. It does not have the Holy Spirit.

This is not a criticism of AI. It is just an accurate description. A hammer is not a screwdriver. Knowing the difference makes you a better builder.

Week 1 Exercise: Ask It Something Hard

Open ChatGPT or Claude. Ask it a theological question you know well, something like the meaning of a specific passage or the difference between two theological positions. Read the response carefully. Notice where it is accurate. Notice where it is vague, oversimplified, or subtly wrong. Notice what it cannot know.

This exercise builds the most important skill in AI literacy: critical evaluation. You are not looking for a tool that is always right. You are learning to use a tool that is often useful but always needs your oversight.

Week 2: Trying the Tools

Reading about AI is not the same as using it. This week you will use AI tools for actual ministry tasks and develop a feel for where they help and where they fall short.

Exercise 1: Sermon Research

Take your sermon passage for next Sunday. Open ChatGPT or Claude and ask for the historical and cultural background of the passage, the main theological themes, and three common misunderstandings of the text. Read the output. Cross-reference one claim against a commentary you trust. Note where the AI was helpful and where it needed correction.

Exercise 2: Draft a Communication

Think of a newsletter article, announcement, or email you need to write this week. Give the AI your church name, the topic, and two or three key points you want to make. Ask for a 200-word draft. Read it. Edit it to sound like you. Notice how much time you saved on the first draft versus how much editing it needed.

Exercise 3: Brainstorm a Problem

Bring a real ministry challenge to the AI. Something like: “I lead a small rural church with 40 members and no budget for outreach. Give me 10 low-cost outreach ideas that would work in a small town.” Evaluate the ideas. Some will be generic. Some will be genuinely useful. The point is to see AI as a brainstorming partner, not an answer machine.

Exercise 4: Test Its Limits

Ask the AI something it cannot know: a specific detail about your congregation, a recent local event, or a question that requires current information. Notice how it responds. A well-designed AI will acknowledge uncertainty. A poorly designed one will make something up. Knowing how your tool handles uncertainty is essential information.

Week 3: Developing Your Personal AI Ethics Framework

Before you can lead your congregation through AI questions, you need to know where you stand. This week is about developing your own framework, not adopting someone else’s.

Four Questions to Answer for Yourself

The Biblical Anchor

Your framework does not need to be built from scratch. Scripture gives you the foundation. Humans are made in the image of God (Genesis 1:27). That image includes creativity, relationship, moral reasoning, and the capacity for genuine love. AI has none of these. It can simulate language. It cannot bear the image of God.

That distinction is not a reason to fear AI. It is a reason to use it without confusion about what it is. A tool that helps you serve people more effectively is a good tool. A tool that replaces the human presence that ministry requires is a bad use of a tool.

Week 4: Preparing Your Congregation

Your congregation is already using AI. Some of them know it. Some of them do not. Some are enthusiastic. Some are frightened. All of them need pastoral leadership on this question, and most of them are not getting it from anywhere else.

Start with a Sermon

You do not need a full sermon series on AI. One well-prepared message that addresses the theological questions honestly is enough to open the conversation. Cover three things: what AI is and is not, what Scripture says about human dignity and technology, and what your church’s approach will be. Give people permission to ask questions.

Hold a Conversation

After the sermon, hold an informal Q&A. A Sunday school hour or a Wednesday evening works well. Let people ask what they are actually wondering. You will hear questions about job loss, about AI relationships, about whether AI-generated sermons are ethical, about deepfakes. These are real questions your people are carrying. The conversation itself is pastoral care.

Adopt a Simple Policy

Your congregation needs to know what your church’s approach to AI is. Not a 20-page document. A one-page policy that covers staff use, data privacy, and disclosure standards. Something your board can read, discuss, and adopt in a single meeting.

Keep the Conversation Going

AI is not a topic you address once and move on. It is a permanent feature of the landscape your congregation is navigating. Build it into your regular teaching. Reference it when it comes up in pastoral conversations. Let your people know you are paying attention and that the church has something to say.

What Comes After the Four Weeks

AI literacy is not a destination. It is a practice. The tools will change. The questions your congregation brings will evolve. New pastoral situations will emerge that nobody has faced before.

What stays constant is your role. You are the shepherd. You bring theological grounding, pastoral wisdom, and genuine relationship to questions that AI cannot touch. The more fluent you become with these tools, the better equipped you are to help your people use them wisely and avoid the ways they can cause harm.

The goal is not to become a technology expert. The goal is to be a pastor who is not afraid of the tools his congregation is already using, and who can speak with wisdom and clarity when those tools raise hard questions.

Related: The Church AI Toolkit for Small Churches | Free Church AI Policy Template | AI Tools for Bi-Vocational Pastors

Frequently Asked Questions