By Brent Lacy

Culture is what happens when no one is watching. It is the sum of a thousand small decisions made by staff, volunteers, and leaders when there is no policy to consult and no one looking over their shoulder. It is the volunteer who decides whether to disclose that she used AI to write the children’s lesson. It is the pastor who decides whether to type a member’s personal situation into a chatbot. It is the worship leader who decides whether to pray an AI-generated prayer as if it were his own.

Right now, your church has an AI culture. You may not have named it or shaped it intentionally, but it exists. Your volunteers are making decisions about AI every week. The question is whether those decisions reflect your church’s values or just the path of least resistance.

Building a healthy AI culture is a leadership task. It belongs to the pastor. Not because the pastor needs to become a technology expert, but because culture follows leadership, and the AI moment requires someone to lead.

What a Healthy AI Culture Looks Like

A healthy AI culture in a small church is not one where everyone uses AI for everything. It is not one where AI is banned and everyone pretends it does not exist. Both of those are failure modes, and both are more common than they should be.

The Barna/Gloo 2026 research captures the tension well: 87 percent of pastors are using AI in ministry, but 71 percent describe themselves as cautious and 40 percent feel conflicted. That combination, widespread use paired with significant personal ambivalence, is the condition that produces unhealthy AI cultures. Pastors who feel conflicted but have not worked through the conflict tend to use AI quietly, without guidelines, without transparency, and without the kind of intentional leadership that would help their teams use it well.

A healthy AI culture is one where people know what AI tools are approved for use and what is off-limits, not just the rules but the reasons. Where the theological reasoning behind the guidelines is understood. Where AI is used to serve people better, not to avoid the work of ministry. Where human relationships remain the center of church life. Where mistakes are handled honestly and not covered up. Where the pastor models the behavior they expect from their team. Where the policy is reviewed and updated as the technology changes.

This is not complicated. But it requires intentional leadership, and intentional leadership requires that the pastor has actually worked through the issues, not just forwarded an article about AI to the board and called it done.

Five Steps to Building That Culture

Step 1: Work Through Your Own Ambivalence First

You cannot lead your church through the AI moment if you have not worked through your own ambivalence about it. The Barna/Gloo research found that 79 percent of pastors worry about AI acting as a replacement for God, and 63 percent worry about AI replacing the role of pastors or spiritual leaders entirely. Those are not irrational fears. They are the right questions, asked by people who take their calling seriously.

Work through those questions before you try to lead your congregation through them. Spend a few hours with an AI tool. Ask it to help you draft a bulletin. Ask it a theological question and evaluate the answer carefully. Ask it to write a pastoral letter and notice what is missing. Ask it to summarize a passage of Scripture and check the result against your Bible. Firsthand experience is worth more than secondhand descriptions, and it will make you a more credible leader when you talk to your congregation about AI.

Then ask yourself: where do I draw the line? What will I use AI for, and what will I not? Write it down. The pastor who has a clear, written personal policy for their own AI use is in a much better position to lead their church to one.

Step 2: Write a Simple Policy

A church AI policy does not need to be long. A one-page document that answers five questions is sufficient for most small churches: What AI tools are approved for church use? What uses of AI are not appropriate in our ministry context? What information should never be entered into an AI tool? How should AI-generated content be reviewed before use? When and how will this policy be reviewed and updated?

Our Church AI Policy Guide includes a free template that covers all five questions in plain language. Your board can read it, discuss it, and adopt it in a single meeting. The policy does not need to be perfect. It needs to exist. A policy that is imperfect but exists is better than a perfect policy that is never written.

One addition worth making: a specific section on data privacy. Specify which categories of information may never be entered into AI tools, and require that all staff and volunteers complete a brief training before using AI tools for church purposes. See our post on AI and Data Privacy in the Small Church for specific guidance on what to include.

Step 3: Have the Conversation with Your Team

A policy that lives in a file cabinet does not shape culture. The conversation does. Bring your staff and key volunteers together, even if that is just four people around a table, and talk through the policy. Explain the theological reasoning. Answer questions. Acknowledge that this is new territory for everyone, including you.

The goal of this conversation is not compliance. It is understanding. A volunteer who understands why member information should not go into an AI tool will make better decisions in the moment than a volunteer who just knows the rule. Rules without reasons produce rule-following when someone is watching and rule-breaking when no one is. Understanding produces consistent behavior because the person has internalized the value, not just the policy.

Make the conversation concrete. Give examples of appropriate and inappropriate uses. Ask if anyone has questions. Ask if anyone is already using AI tools in ways the policy would address. Create space for honest conversation rather than just announcing the policy and moving on.

Step 4: Model It Yourself

Culture follows the leader. If you use AI carelessly, your team will use AI carelessly. If you use it thoughtfully, with clear lines, honest disclosure, and genuine human oversight, your team will follow that pattern. This is not a new principle. It is the same principle that applies to every other aspect of church culture.

Be willing to say, in ordinary conversation: “I used an AI tool to help with the first draft of this, and then I rewrote it to fit our context.” That kind of casual transparency normalizes honest AI use and sets the tone for your whole team without requiring a formal announcement or a lengthy explanation. It also signals that you are not hiding anything, which is itself a form of leadership.

Be equally willing to say: “I thought about using AI for this, but decided not to, because this is the kind of thing that needs to come from me.” That kind of statement models the discernment you want your team to practice.

Step 5: Review and Adapt

AI tools are changing faster than any policy can keep up with. Build a review cycle into your policy from the beginning. Once a year, bring the policy back to your board, ask what has changed, and update accordingly. The church that wrote its AI policy in 2024 and has not touched it since is operating on outdated assumptions about tools that have changed significantly.

The annual review does not need to be a major undertaking. A thirty-minute board conversation about what has changed and what needs updating is sufficient in most years. The questions to ask: Are there new AI tools our team is using that the policy does not address? Have any of our approved tools changed their privacy practices? Have we had any situations where the policy was unclear or insufficient? What would we do differently if we were writing the policy today?

Handling Violations Gracefully

When a volunteer uses AI in a way that violates your policy, and this will happen, handle it the same way you would handle any other policy violation: with grace, clarity, and a focus on understanding rather than punishment.

Most violations will be accidental. A volunteer who did not know the rule, or who knew the rule but did not realize their specific action violated it. Clarify the policy, explain the reasoning, and move on. The goal is a culture of honest AI use, not a culture of fear. A volunteer who is afraid to admit they used AI in a way that might have been wrong is a volunteer who will hide future mistakes rather than learning from them.

Reserve stronger responses for repeated violations or violations that caused actual harm, a member’s confidential information shared with an AI tool, a theologically problematic lesson taught to children without review. Even then, the goal is correction and learning, not punishment.

A Note for Bi-Vocational Pastors

If you are bi-vocational, you may feel like you do not have time to lead your church through an AI conversation on top of everything else. That feeling is understandable. But consider: a thirty-minute conversation now prevents hours of damage control later. And AI, used well, can give you back time you desperately need.

The Barna/Gloo research found that administrative tasks often dominate a pastor’s schedule, keeping them from their most meaningful work. AI is helping pastors reclaim those hours so they can focus on ministering to people. For a bi-vocational pastor who has 15-20 hours a week for ministry, reclaiming even two or three of those hours from administrative tasks is significant. See our AI Tools for Bi-Vocational Pastors guide for practical starting points.

The Theological Foundation of It All

Everything in this series, the imago Dei, congregational trust, data privacy, discipleship, the digital divide, worship, comes back to the same foundation: the church exists to love God and love people. Every tool the church uses should serve that mission. When a tool begins to undermine that mission, even subtly, even with good intentions, it needs to be evaluated and corrected.

AI is a powerful tool. Used wisely, it can free up time for deeper ministry, make your communications more effective, and help a stretched small church do more with less. Used carelessly, it can erode trust, compromise privacy, produce theologically thin content, and replace the human relationships that are the heart of small church ministry.

The difference between those two outcomes is leadership. Your leadership. The pastor who thinks carefully about AI, who sets clear guidelines, who models honest use, and who keeps the theological questions at the center of the conversation is doing something that matters, not just for their church, but for the broader conversation about what faithful ministry looks like in an age of artificial intelligence.

The Barna/Gloo research found that pastors are predominantly using AI for “behind-the-scenes work, as a thought partner, a visual aid.” That is the right instinct. The challenge is to make that instinct explicit, to name it as a theological commitment rather than just a personal preference, and to build a church culture that reflects it consistently. That is the work of leadership. It is also the work of faithfulness.

---

Frequently Asked Questions

How do I get my church board to approve an AI policy?

Frame it as stewardship and risk management, not technology adoption. Bring a specific scenario to make the risk concrete. A one-page document that addresses approved uses, prohibited uses, data privacy, and review requirements is sufficient for most small church boards and can be adopted in a single meeting. Use our free Church AI Policy Template as your starting point.

What is the biggest mistake small churches make with AI?

Using AI without any guidelines and then reacting to a problem after it occurs. The second biggest mistake is banning AI entirely out of fear, which leaves your team using it anyway, just without any accountability or guidance. The healthy middle is clear guidelines, honest conversation, and regular review.

How often should a church review its AI policy?

At minimum, annually. AI tools and their capabilities are changing rapidly. Build a review cycle into the policy itself. The annual review does not need to be a major undertaking. A thirty-minute board conversation about what has changed and what needs updating is sufficient in most years.

How do I handle it when a volunteer uses AI in a way that violates our policy?

Handle it with grace, clarity, and a focus on understanding rather than punishment. Most violations will be accidental. Clarify the policy, explain the reasoning, and move on. The goal is a culture of honest AI use, not a culture of fear.

---

The Culture You Are Building Now Will Outlast Any Specific AI Tool

The AI tools that exist today will be replaced by better tools within a few years. The specific questions about ChatGPT’s privacy settings or Gemini’s data practices will be superseded by questions about tools that do not yet exist. The policy you write today will need to be rewritten.

But the culture you build today will persist. A church that learns to talk honestly about AI, to apply theological principles to technology decisions, to hold the line on human relationships as irreplaceable, and to review and adapt its practices as circumstances change, is a church that is building a capacity that will serve it well through every technological change that follows. That capacity is more valuable than any specific policy.

This is why the work of building a healthy AI culture is worth doing even though the specific tools will change. You are not just managing a technology question. You are building a community that knows how to think theologically about technology, how to hold its values under pressure, and how to lead through uncertainty with honesty and grace. Those are capacities that every church needs, and they are capacities that the AI moment is forcing churches to develop whether they want to or not.

The Pastor’s Own Formation

One dimension of this conversation that rarely gets addressed is the pastor’s own spiritual formation in relation to AI. The question is not just how AI affects the congregation. It is how AI affects the pastor.

A pastor who uses AI to avoid the hard work of sermon preparation is a pastor whose own formation is being affected. The wrestling with the text that produces a sermon is not just a means to an end. It is itself a formative practice. The pastor who stops wrestling with the text because AI can produce an adequate outline is a pastor who is losing something important, not just for their congregation but for themselves.

The same is true of pastoral care. A pastor who uses AI to draft pastoral letters is a pastor who is spending less time in the kind of careful, prayerful attention to another person’s situation that makes pastoral care formative for the pastor as well as the person being cared for. Pastoral care forms the pastor. When AI substitutes for that care, the pastor loses the formation that the care would have provided.

This is not an argument against using AI for administrative tasks. It is an argument for being honest about which tasks are administrative and which tasks are formative. The bulletin is administrative. The sermon is formative. The volunteer schedule is administrative. The pastoral letter is formative. The distinction matters, and it matters for the pastor’s own soul as much as for the congregation’s wellbeing.

The pastor who builds a healthy AI culture in their church is the pastor who has thought carefully about their own formation, who has identified which practices are essential to their own spiritual health, and who has drawn clear lines to protect those practices from the efficiency pressures that AI creates. That kind of self-awareness is itself a form of pastoral leadership, and it is the foundation on which everything else in this series rests.

Starting Today

The best time to build a healthy AI culture in your church was six months ago. The second best time is today. Not next month, when you have more time. Not after the next board meeting, when you have official approval. Today, with whatever you have available.

Here is what you can do today, in thirty minutes or less. Open an AI tool and spend fifteen minutes using it for something low-stakes, drafting a bulletin announcement or brainstorming small group discussion questions. Notice what it does well and what it does poorly. Then spend fifteen minutes writing down three things you will use AI for in your ministry and three things you will not. That is the beginning of your personal AI policy, and it is the foundation on which everything else in this series rests.

Share those six things with one other person in your church this week. That conversation is the beginning of your church’s AI culture. It does not need to be formal. It does not need to be comprehensive. It just needs to happen, honestly and openly, between two people who care about the same congregation.

From there, the path forward is clear. Write a simple policy. Have the conversation with your team. Model honest AI use yourself. Review and adapt annually. That is the whole framework. It is not complicated. It is not expensive. It does not require technical expertise or a large budget or a communications team. It requires a pastor who has thought carefully about what their church believes about people, and who is willing to lead their congregation through a new technological moment with the same honesty and theological grounding they bring to every other challenge of ministry.

That pastor is you. Start today.