How to Use AI for Sermon Preparation Without Outsourcing the Sermon

The line that matters: assistance or authorship

A concordance assists. A commentary assists. A proof-reader assists. None of them stand up on Sunday. The useful question is never “did I use a tool?” but “who did the work that only the preacher can do?”

Four things belong to the preacher and cannot be delegated:

• Prayer — the sustained asking that precedes and accompanies preparation.
• Interpretation — deciding what the text means, with the weight of responsibility that carries.
• Conviction — being addressed by the passage before addressing anyone else with it.
• Proclamation — speaking as one who believes what is being said.

Everything else — locating background material, checking whether an argument holds, tidying a clumsy paragraph, producing discussion questions — is ordinary preparation work that a tool may legitimately share.

A week-shaped preparation process

This is the process taught in the Accelerator’s preaching modules, reduced to its skeleton.

1. Day one — cold reading and prayer. Read the passage several times in at least two translations. Write your own observations, questions and first structure. No tools at all. This protects the sermon from being shaped by whatever the model happened to say first.
2. Day two — research support. Now ask for help: historical setting, literary structure, how the passage sits in the wider book, standard interpretive disagreements. Treat every answer as a lead to check, never as a finding.
3. Day three — write it yourself. Full manuscript or full notes, in your own words, from your own outline.
4. Day four — critique, not composition. Paste your draft and ask for the weakest transition, the unsupported claim, the paragraph a visitor would not follow, the jargon a new believer would not know. Accept the diagnosis; write the cure yourself.
5. Day five — congregational extras. Discussion questions, a short summary for the notices, an accessible version for members with limited English.
6. Day six — verification and prayer. Every reference checked. Then close the laptop.

Prompts that assist rather than replace

The difference between a helpful and a harmful prompt is usually whether it asks for analysis of your work or production of new work. Useful forms include:

• “Here is my outline of Romans 8:18–25. Which move in the argument is least supported by the text itself?”
• “List the main interpretive positions on this passage and the strongest objection to each. Do not tell me which is correct.”
• “Rewrite this paragraph at the reading level of a fourteen-year-old without losing any of the meaning.”
• “What questions would a first-time visitor have after hearing this section?”
• “Give me five comprehension and application questions for a small group, based only on the text below.”

Harmful forms are the mirror image: “write me a twenty-five minute sermon on forgiveness”, “give me a moving illustration about a widow”, “write a pastoral prayer for a bereaved family”. The first outsources authorship, the second invites fabrication, the third replaces intercession with imitation.

Four traps to avoid

1. Invented illustrations. A model asked for a moving story will produce one. Told from the pulpit as though true, it is a lie. Use only what happened, with permission where people are identifiable.
2. Fabricated citations. Plausible references to commentators, councils and studies that do not exist are common. If you have not seen the source, do not quote it.
3. Flattened voice. Heavy editing towards “polish” strips out the particularity that makes a preacher trusted. Keep your own cadence.
4. Devotional drift. If the tool becomes the first place you go when the text is hard, your own study muscles will weaken. Keep day one sacred.

Before you preach: a verification checklist

• Every Scripture reference opened and read in a Bible, in context.
• Every quotation traced to a primary source, or deleted.
• Every statistic traced to the body that published it, with a date.
• Every illustration true, and cleared with anyone identifiable in it.
• Every claim about church history or original languages checked in a reference work.
• No personal or pastoral information about a member entered into any tool.
• The manuscript reads in your voice when spoken aloud.

Should you tell the congregation?

You do not owe a footnote for a spell-checker, and you do not owe one for a clarity edit. You do owe honesty if asked, and you owe leadership a clear account of your practice. Most congregations react far better to “I use these tools for research and editing, never for prayer or for the sermon itself” than to silence followed by discovery. Say it once, publicly, and the question stops being a rumour.

Where to go next

Modules three to five of the programme cover the SHEPHERD prompting method, Bible study without doctrinal drift, and sermon development in full, with practice tasks against your own passages. If your wider concern is congregational data and policy, read the church AI policy checklist.