Is Using AI for Sermons Cheating?

"Cheating" is the word pastors actually use. Not "is it ethical," not "what about AI alignment"—cheating. As in: I pasted my passage into a chatbot on Thursday night, preached what came back on Sunday, and I haven't told anyone, because it feels like I copied someone's homework.

That instinct deserves a straight answer, not a hand-wave. So here's ours.

Cheating implies a rulebook. Whose?

Call something cheating and you're claiming a rule was broken. But preaching has never had a rule that says work alone. Pastors have always prepared with help—commentaries written by other people, sermons heard in seminary, a mentor who tears apart your outline on Tuesday, a spouse who reads the draft and says the second point is missing. Nobody calls a commentary cheating. Charles Spurgeon read himself full of other preachers and told his students to do the same.

So the rule was never no help. Look at what the congregation actually assumes when you stand up: that the message passed through you—that you wrestled with the text, that God dealt with you in the preparation, that the words in your mouth are yours even where the insights aren't original. That's the real rulebook, unwritten but universally assumed.

Which gives us a cleaner question than "is AI cheating?" Ask instead: did the sermon pass through me, or around me?

The line runs through the middle of "using AI"

By that test, "using AI" splits cleanly in two.

Help that makes you wrestle better passes through you. Background on the text. A question that exposes the hole in your second point. Honest feedback that your introduction promises a sermon you never deliver. A push to say your big idea in one sentence when you've been hiding behind three. None of that is cheating for the same reason a commentary isn't: you're still the one doing the work—arguably more of it, because good questions make the wrestling harder, not easier.

Help that removes the wrestling goes around you. A generated outline you lightly edit. A full draft you rephrase into your own cadence. The moment of arrival—where the text finally breaks open and the message becomes yours—gets outsourced, and what's left is delivery. Preach it and something true has been skipped, whether or not anyone can tell. Most pastors who've tried it describe the same tell: the sermon was competent, and it was hollow in their mouth.

Notice the line doesn't run between "AI" and "no AI." It runs between assistance and substitution—straight through the middle of the AI aisle. That's why the cheating question feels so muddy: both kinds of tools get called "AI for sermons," and they're opposites.

And the lazy question?

Sometimes the real accusation is softer: not cheating, just lazy. Here the honest answer cuts the other way. A bivocational pastor with nine hours of prep time using a tool to reach clarity faster isn't lazy—they're a steward. Guarding hours for prayer and people by working efficiently is the opposite of laziness.

Laziness is skipping the part that costs you something. And the part that costs you something isn't the typing—it's the thinking. Compress the typing all you want. The week the text spends working on you before you preach it: that was never yours to compress.

Where we stand

We should say plainly where we sit: we build an AI sermon coach, and we drew it on this exact line. It will question you, push you, and critique your draft; it will not write your sermon, by design, ever. We built it that way because we think the assistance side of the line is genuinely good for preachers—and the substitution side quietly costs them what makes preaching worth doing. We've mapped where that line sits in detail if you're working out your own convictions.

One step: take whatever tool you're using—or considering—and ask it one question this week: will you write the sermon if I ask? Then decide, on purpose, which side of the line you want to prepare on. The pastors who feel like they're cheating are almost always the ones who drifted across it without deciding.