A pastor's guide to using AI without losing your voice
AI is already in your staff team, whether you have talked about it or not. The question is what you will let it do, and what stays yours.
By Mark Odendaal
It is already here
Whenever I raise the topic of AI with church teams, I usually discover the same thing pretty quickly:
Someone is already using it.
Maybe to draft a newsletter. Maybe to turn notes into small group questions. Maybe to write a social caption. Sometimes to help structure a sermon.
The interesting part is that, in many churches, nobody has really talked about it.
And I think that is where the risk is.
The issue is not simply whether AI is good or bad. The issue is whether your team has actually decided how it should and should not be used.
Not all ministry work is the same
I think one of the most helpful distinctions is between work that is **administrative** and work that is **formative**.
There is plenty of ministry work that is repetitive, time-consuming and functional. Reformatting documents. Summarising notes. Transcribing meetings. Cleaning up a roster. Drafting the first version of an email. Turning a long piece of content into something shorter.
I have no problem using AI for that.
But there is another kind of work in ministry that should not be outsourced.
Sitting with a biblical text until it confronts you. Praying for the people you are about to preach to. Knowing what your church is carrying. Wrestling with how truth lands in the lives of real people.
That is not the admin around the ministry.
That **is** the ministry.
If AI does that work for you, you may save time, but you also risk skipping the very process that gives the ministry depth.
Churches need some guardrails
I don’t think most churches need a fifty-page AI policy.
But I do think every church team should be able to answer a few basic questions.
What are we happy for AI to help us with?
What information should never be entered into an AI tool?
Who is responsible for checking what gets published?
And where do we draw the line between assistance and replacement?
Some boundaries should be obvious.
Pastoral care information, counselling notes, safeguarding matters and people’s private circumstances should not be pasted into general AI tools.
Anything that goes public should still have a human being responsible for it.
And staff should know what the rules are before everyone develops their own version of them.
The uncomfortable upside
There is also a side of this conversation that churches should not be afraid of.
Used properly, AI can remove a surprising amount of low-value work from ministry.
And if that means a pastor spends less time formatting documents and more time with people, that is a win.
If it means a communications person spends less time resizing the same piece of content five different ways and more time thinking creatively, that is a win too.
The goal should never be to use AI because it is new.
The goal should be to use it where it helps us do the real work of ministry better.
Because AI is already in the church.
The question is whether we are going to use it thoughtfully, or just discover later that everyone was making up their own rules.