A pastor texted me last Tuesday night at 11:47 PM. The message said, “Am I cheating if I used AI to help me outline Sunday’s sermon?” He’d been pacing his office for three hours, staring at a blank page, watching the cursor blink. Then he opened ChatGPT, typed in his passage, and twenty minutes later had a working outline. The sermon he preached that Sunday landed. People cried in the third row. A teenager stayed after to ask him questions about prayer. And still, he felt guilty.
If you’ve ever been that pastor, this post is for you.
AI sermon writing is here, and it’s not going back in the box. You can use it to draft, outline, illustrate, translate, exegete, and edit. You can also use it to skip the hard, holy, necessary work of actually sitting with a passage long enough for it to sit with you. Both are possible. Both are happening. The question isn’t whether AI belongs in sermon prep. The question is where, how, and when to stop.
This is a pastor’s honest guide to AI sermon writing. What to use it for, what to never hand over, prompts that actually work, and the guardrails you need before you open a chat window on a Tuesday night and blur the line between “help” and “handoff.”
Why AI Sermon Writing Feels Weird (And Why That’s a Good Instinct)
You’re not crazy for feeling conflicted about this. Preaching isn’t the same as writing a quarterly report. You’re handling Scripture. You’re shepherding people. There’s a reason James 3:1 lands with a thud every time you read it.
The discomfort you feel when you open an AI chat window for sermon prep is telling you something real. It’s the same discomfort a surgeon would feel if someone offered them a robot to do a bypass while they played golf. The tool isn’t the problem. The handoff is the problem. And your instinct to feel the weight of that is actually healthy pastoral wiring.
Here’s what most of the church-tech conversation gets wrong. It treats AI like an on/off switch. Use it or don’t. Embrace the future or be left behind. That framing is lazy and it isn’t how pastors actually make decisions about tools. Nobody asks if commentaries are “cheating.” Nobody asks if Logos software is replacing the Holy Spirit. Those tools are assumed helpers, not substitutes.
AI can be in that same category, but only if you’re clear on the line. And the line isn’t about the tool. It’s about where your attention, your prayer, your wrestling, and your voice show up in the final product.
A sermon isn’t just information transfer. It’s a pastor, standing in front of a congregation they know, handling a text they’ve wrestled with, speaking into specific lives they’ve sat with in hospitals and hallways. No AI model has done any of that. It can help you shape. It can’t help you shepherd.
Hold that line and you’re fine. Lose it and you’ve traded something irreplaceable for efficiency.
What AI Is Actually Good At in Sermon Prep
Let’s get practical. Here’s where AI earns its keep in your week.
Research shortcuts. You can ask a model to summarize the historical context of a passage, pull the main interpretive options from major commentators, or list out the Greek and Hebrew word nuances for a key term. It won’t replace reading Carson or Keller or your own study Bible, but it’ll get you oriented in five minutes instead of fifty. Verify anything load-bearing against actual commentaries.
Outline drafting. Give it your passage, your main idea, and your audience, and it’ll spit out three or four possible outlines. Most will be mediocre. One will usually have a structural move you hadn’t considered. Steal that move. Throw out the rest.
Illustration generation. This is where AI is surprisingly useful. Ask for five illustrations for a specific point and you’ll get five mediocre ones. Ask for twenty-five and a handful will be interesting. Modify them to fit your actual congregation. Never use an AI illustration raw. Your people can smell a generic story from the second row.
Title and subhead writing. Stuck on what to call the sermon? AI is a title generator on steroids. Upload your sermon notes or manuscript. Ask it to look at your sermon library to find title patterns. Ask for fifteen options. Pick one, edit it, move on. This is a task with low spiritual stakes and high time-cost. Perfect for AI.
Transition smoothing. When you’ve got your points but the bridges between them feel clunky, paste in two adjacent sections and ask for three transition options. You’ll usually find your own voice in one of the rewrites.
Editing and tightening. Paste in a rough draft and ask it to identify sentences that are bloated, repetitive, or unclear. Don’t accept its rewrites. Just let it flag the weak spots so you can modify them yourself.
Translating a sermon for a different audience. If you’re preaching the same message at a Spanish-language service, a youth service, or a senior living community visit, AI can rough-translate or re-level your draft. You still need to read it, feel it, and adjust it, but the lift from blank page is gone.
Research organization. You’ve got six tabs of commentary notes, a podcast transcript, and a sticky note of quotes. Paste it all into a chat and ask it to cluster the insights by theme. You just saved an hour of sorting.
Notice what all of these have in common. They’re preparation tasks, not proclamation tasks. They speed up the loading dock but they don’t drive the truck. The pastor’s name isn’t Claude, it’s …..whatever your name is.
What AI Will Never Do For You
This list matters more than the last one. These are the parts of sermon prep that cannot be outsourced, no matter how sophisticated the model gets.
Time with the passage. There is no shortcut for sitting in Philippians 2 until it starts sitting in you. An AI can summarize the passage in four seconds. That summary is not what your congregation needs. They need a pastor who’s been walking around with the text for six days, watching it rearrange their own heart first. The Spirit does that work in you, not in a chat window.
Pastoral knowledge of your people. AI doesn’t know that Sharon’s husband just got diagnosed. It doesn’t know that your youth group is one bad week from losing three kids to doubt. It doesn’t know that your deacons have been tense since February. It doesn’t know the spiritual health of your church, much less individuals or groups inside the church. Every real sermon gets preached to a real room. Only you can write for that room.
Conviction. The clearest preaching comes from pastors who’ve been personally wrecked by what they’re about to say. An AI can generate a sentence that sounds convicting. Your congregation will know the difference. They’ve been watching you for years. If you copied a manuscript to pawn off as your own it will lack conviction. On top of that, if you’re doing crap like this you’re not shepherding well.
Theological judgment. AI models do not have a doctrine of Scripture. It’s just a computer man. They’re predicting what a confident-sounding answer looks like based on patterns in their training data. On surface-level exegesis they’re usually fine. On hard interpretive calls, contested doctrines, denominational nuance, or anything where your tradition’s theological commitments matter, they will confidently make mistakes. You need to be the one reading the text and the commentaries and making the call.
Your voice. I know ‘my sheep know my voice’ isn’t exactly what’s going on here, but your people know what you sound like. They know your stories, your recurring phrases, your tells. AI writing has a texture to it — even when it’s good, it reads a little too clean, a little too structured, a little too both-sides. Never preach something you didn’t mold and guide in your own words. If a sentence sounds more like a TED talk than like you, cut it.
Prayer. You cannot pray by proxy. You cannot outsource intercession for your congregation. If AI is saving you time in sermon prep, that time goes back into prayer and pastoral care and real ministry work, not into Netflix and pushing off other things. If it does, congrats, you’ve just become more efficient at being absent.
Put these two lists next to each other and you get the 80/20 split that works.
The 80/20 Split
Here’s the rule that I’ve seen healthy pastors land on, almost without exception.
80% of the sermon is you. Your time in the passage, your wrestling, your prayer, your voice, your illustrations pulled from your actual life and your actual people, your theological convictions, your pastoral knowledge of the room. That’s the sermon.
20% is support tasks. Research shortcuts, outline drafts, illustration brainstorming, title writing, editing passes, organization. That’s where AI can legitimately save you four to six hours a week without touching the part that matters.
It’s easy in theory and harder in practice. The temptation is always to drift. You start using AI for outline drafts, which is fine. Then you use its outline wholesale. Then you ask it to fill in the points. Then you edit its draft instead of writing your own. By Saturday you’ve preached a sermon you didn’t really write, to people you barely prayed for, about a passage you didn’t really sit with. And it sounded pretty good. That’s the danger.
It’s like backsliding but with sermon prep. You’ve never met someone that walked away from God overnight, and in 3 years as AI continues to grow, I doubt you’ll meet a pastor that let AI write his who sermon as soon as he started utilizing it.
The 80/20 split isn’t a time budget. It’s a where-does-your-attention-live check. If you’d be embarrassed for your congregation to see exactly how the sermon got built, something has slipped. Pull it back and address those patterns now.
Pastors who keep this line will say the same thing over and over. AI gave them back part of their week. AI cut admin time and gave it to prayer. AI made the research phase faster so the wrestling phase could be longer. That’s the version that works.
A Real Week: How One Pastor Uses AI Monday to Saturday
Here’s what a healthy rhythm looks like. This is crafted from several pastors who’ve built workflows with AI in the loop. Quick caveat. I’m an advocate of being done with your sermon by Thursday to hand off to your production team…but let’s be honest. Most pastors are handing their notes over on Saturday.
Monday morning. He prints the passage. He reads it three times in three translations. No screen. He writes down initial observations, questions, and what the Spirit is surfacing in his own life that week. No AI yet. Just him, the text, and a yellow notepad.
Monday afternoon. He opens a chat and pastes the passage. He asks for a summary of historical context, major commentator interpretations, and key word studies. He cross-checks two or three claims against Logos to make sure nothing is hallucinated. This takes 40 minutes instead of the 3 hours it used to take.
Tuesday. Staff meeting, hospital visits, lunch with an elder. He’s carrying the passage around in his head all day. The AI doesn’t factor in. But the loading from Monday means his brain has more room to actually think.
Wednesday morning. He writes the main idea of the sermon by hand, in one sentence. and gives it a rough outline. Then he opens AI and asks for three possible outlines given his main idea, his rough outline, his audience, and his series context. He ignores two of them. One gives him a structural move he likes. He re-writes his own outline that borrows the move but fills in points from his own prayer and study.
Wednesday afternoon. He asks AI for 15 possible illustrations for his hardest point. He throws out 13. The remaining two get heavily rewritten with details from his own life and his actual congregation.
Thursday. Writing day. Just him, his outline, his Bible, and a cup of coffee. He writes the full manuscript in his own words. This is the sacred part. No AI. He passes on this manuscript to production to get slides from.
Friday morning. Editing pass. He pastes the draft into AI and asks it to flag bloated sentences, unclear transitions, and places where the logic is weak. He doesn’t accept the AI’s rewrites. He uses the flags to rewrite weak spots himself. Ninety minutes instead of three hours.
Friday afternoon. Prayer walk. Final read-through. He marks the places that feel preachy or AI-flavored and rewrites them one more time in his own voice.
Saturday. He’s with his family. The sermon is done. This is the part that feels like a small miracle if you’ve ever done ministry without it.
Sunday. He preaches. It’s his sermon. Every word, prayed-over and wrestled-with, with AI-accelerated research underneath but nothing AI-generated in the final text.
That’s the shape. Your week will look different. But the principle holds. AI loads the truck. You drive it.
Prompts That Actually Work
Bad prompts give you generic output. Generic output makes mediocre sermons. Here are prompt patterns worth saving.
For historical context:
“I’m preaching on [passage]. Give me a 300-word summary of the historical, cultural, and literary context a pastor would need to know. Flag any debated interpretive issues and which major commentaries come down on which side.”
For outline drafts:
“I’m preaching on [passage] to a [audience description] church. My main idea is: [one sentence]. Give me three very different possible sermon outlines. One traditional three-point, one narrative arc, one problem-solution-application. For each, give a one-sentence summary of each main move.”
For illustration generation:
“I need illustrations for this point: [one sentence]. Give me 15 possible illustrations. Vary the categories: personal story, historical example, cultural reference, sports, parenting, nature, workplace, current events. Keep each under 75 words.”
For editing passes:
“Here’s my sermon draft. Don’t rewrite it. Just flag: (1) any sentences that are bloated or unclear, (2) any transitions that don’t land, (3) any spots where the logic or exegesis is weak. Give me a bullet list of specific spots to revisit, with line references.”
For translating to a different audience:
“Here’s a sermon I wrote for [original audience]. Re-level the language and examples for [new audience] without changing the main points or theological content. Keep my voice. Don’t soften anything.”
For title brainstorming:
“Sermon topic: [1 sentence]. Give me 20 possible sermon titles. Vary the styles: provocative question, declarative statement, surprising phrase, biblical quote, one-word title.”
Notice what these prompts have in common. They’re specific. They assume you already know what the sermon is about. They ask for options, not answers. They use the AI as a brainstorming partner, not as a sermon-writing service.
Bad prompts look like this. “Write me a sermon on [passage].” You’ll get back a generic, structurally boring, theologically mushy sermon. Don’t do that to yourself or your people.
Good prompts assume you’re doing the real work and AI is the assistant. Bad prompts assume AI is doing the real work and you’ll polish it. The first one leads to better sermons. The second one leads to pulpit decline.
The Guardrails: Your Personal AI Sermon Rules
Before you use AI for sermon prep again, write down your rules. Post them on your wall. Tell your spouse or your accountability group what they are. This is how you keep the line from drifting.
Here are rules most healthy pastors I know use in some form. Pick what fits.
Rule 1: The passage before the chat. I don’t open AI until I’ve read the passage in at least three translations and written initial observations by hand. The Spirit gets first access, always.
Rule 2: Prayer bookends. If I’m using AI for sermon work, I pray before I open it and after I close it. This is a small discipline that keeps the tool from becoming the author.
Rule 3: No AI-generated full paragraphs in the final text. I can use AI output as inspiration, but every paragraph that hits the pulpit gets rewritten in my own words. If my congregation heard it, it should sound like me.
Rule 4: Time saved goes back into ministry. If AI saves me four hours on sermon prep this week, those hours go into hospital visits, counseling, or prayer. Not into more sermon polish and not into screen time.
Rule 5: Full disclosure to my accountability partner. Somebody in my life knows exactly how I use AI for sermon work. No secrets. No creeping.
Rule 6: Annual audit. Once a year I review my sermon prep rhythms and ask honestly: has AI shifted the sermon from being mine to being something else? If yes, I reset.
Rule 7: Never for pastoral care correspondence or funeral homilies. Some things stay fully human. My personal rule is that anything involving a specific person’s grief, crisis, or life event gets zero AI involvement. Your list might be different. Have one.
These rules aren’t legalism. They’re the banks of the river that keep the current going in the right direction. Without them, drift is inevitable. Not because you’re a bad pastor. Because AI is that useful and humans are that tired.
A Note on Tools
You’re going to need more tools than just a chat window. You’ll want your sermon notes connected to your church communication rhythm. You’ll want a website where your messages live and people can find them. You’ll want your sermon follow-up actually reaching the people who showed up that morning.
This is where most church tech stacks fall apart. You end up juggling twelve tools that don’t talk to each other. The sermon gets preached and then disappears. New visitors don’t get a next step. Your communications team is copy-pasting from one platform to another.
If you’re rebuilding that stack and want something that actually works for ministry rather than against it, we built Leo to help pastors who are tired of duct-taping tools together. Sermon pages, visitor follow-up, staff collaboration, all in one place. AI for the admin and communication side so you have more margin for the pulpit side.
Wrapping Up
AI sermon writing is a tool. Like every tool a pastor has ever used, it amplifies who you already are. If you’re disciplined, prayerful, and clear on what can and can’t be outsourced, AI will give you back hours and make you a better steward of your prep time. If you’re tired, drifting, and looking for a shortcut, AI will help you drift faster and further than you thought possible.
The pastor who texted me at 11:47 PM last Tuesday isn’t cheating. He found a tool that helped him get through a hard night so he could preach a faithful sermon. That’s fine. That’s maybe even good. The only question is whether the next Tuesday looks the same, or whether the AI starts doing a little more and he starts wrestling a little less, and by the end of the year his sermons don’t sound like him anymore.
Don’t let that happen. Use AI like a research assistant, not a ghostwriter. Hold the 80/20 line. Write your own paragraphs. Pray twice as much as you prompt. And remember that the thing your people showed up for on Sunday isn’t a well-structured outline. It’s a pastor who’s been sitting with Scripture all week and has something real to say.
Start there. The AI is just a shovel. You’re still the one building.
