Helpful uses
- Historical and cultural background on a passage (always verify with commentaries).
- First-pass sermon outlines you reorganize around your main point.
- Brainstorming illustration categories—not fabricated stories.
- Slide bullet tightening for clarity (you approve every line).
Boundaries worth keeping
- Do not paste member situations into public AI tools.
- Do not publish AI devotionals without theological review.
- Do not skip scripture reading because a summary “sounds good.”
A simple weekly workflow
- Study the text manually first—observation, interpretation, application.
- Ask AI for background questions you still have; check answers against trusted sources.
- Draft your outline yourself; use AI only to stress-test transitions or clarity.
- Pray through the final message before Sunday.
Why the boundary matters more here than in other work
A sermon is not a deliverable; it is one half of a pastoral relationship. A congregation that discovers its pastor has been preaching machine-drafted sermons loses something no efficiency gain buys back, and the pastors most tempted to outsource are the busiest ones — which is precisely when a congregation most needs to hear its own shepherd's voice wrestling with the text. The honest test: if you would be uncomfortable telling your elders exactly how the message was produced, the process needs to change, not the disclosure.
Where AI genuinely earns its keep in sermon work
The week's low-stakes language work: tightening a bulletin blurb about the series, drafting three title options you rewrite, turning your finished manuscript into small-group discussion questions, or producing a plain-language summary for the youth handout. All of it is downstream of the sermon you already wrote, none of it stands in the pulpit, and each piece saves twenty minutes you can spend on people. A hallucinated Greek etymology, by contrast, ends up quoted from the platform — verify every factual claim against a commentary you trust before it reaches paper.