AI sermon summaries that stay faithful to what was preached

What an AI sermon summary is

It is not a new sermon, and it is not a transcript. It is the heart of the one that was preached, short enough to read in about two minutes, sent to people who asked for that service.

A sermon-style summary carries the title and the preacher’s name, the passages that were actually read, the movements of the message, a verse to remember, a question for the week, and a link to the full audio. You can read the shape of one in the sample email from Riverbend Grace, a made-up church. A wider guide to the format itself is how to send a sermon summary email.

The worry is fair

Pastors who hesitate are usually not asking whether a machine can write. They are asking whether it will put words in their mouth.

That worry shows up in pieces written for ministers, not for software. Ed Stetzer’s “Navigating the Ethics of AI in Ministry and Sermon Writing” (also on ChurchLeaders) treats AI as a sous chef: useful for finding an illustration or tidying a task, and the wrong person to cook the sermon. He warns that using it to skip time in Scripture, dependence on the Spirit, and knowledge of the congregation makes an existing bad habit worse. He names the practical risks too: material drawn from the open internet can be inaccurate, biased, or quietly plagiarised, and the pastor remains responsible for what is said in their name.

Those are sermon-writing problems. A summary has a narrower job, and a narrower way to fail. The failure that matters is a verse the preacher never opened, a point they never made, or a prayer request that leaves the room. Guardrails have to be mechanics, not a promise that the tool is “faithful.”

How Sermontary keeps the summary faithful

It starts from the words actually spoken

While the service runs, a transcript builds from the sound desk or the livestream. Each line can be corrected as it is said. A helper on a second screen, the Live Desk, can fix a name or a book of the Bible without stopping the recording. Fix a word once and it stays right on later weeks. The summary is written from that edited transcript, not from a rough first pass and not from notes someone typed on Monday.

Only scripture that was read

The summary is told to list only passages the speaker actually cited, and not to guess a reference it isn’t sure of. A verse is quoted only if it was read aloud, in the words that were read. It is not told to “find verses that back up the point.” A person still checks the list. We don’t publish an accuracy rate.

It knows who preached, with consent

A speaker is named from their voice only after they agree. Enrolment is a short reading — a psalm, about forty seconds — on their own phone or at the church’s computer. The recording of that reading is deleted once the voice profile exists. We keep the profile, not the audio, and a record that they agreed. Someone who has not enrolled is not named from their voice: the line stays unassigned until a person on the team puts a name on it. Guest profiles are removed 90 days after the last visit unless the guest chooses to keep theirs. Speakers under 18 need a parent or guardian’s agreement. The detail is in voice data on the privacy policy.

A style for each gathering

The church sets the style on the service. A sermon is written as a sermon. A youth night is written in plain words, with a challenge for the week, and personal things said by young people are left out. A prayer meeting is a different instruction entirely, below. The style is not guessed from the audio. More on youth night.

Nothing leaves without a person deciding

When the summary is ready, someone reads it, changes anything that doesn’t sound like the sermon, and can send themselves a test. Then they send it now, schedule a time, or leave automatic sending on. Automatic still waits: you’ll have 15 minutes or more to read it, edit it, or cancel it. A ministry can require the pastor’s approval first — a youth leader submits Friday, and it waits until the pastor approves or sends it back. How it works is the same path without the mechanics.

Prayer meetings: themes, never people

A prayer-meeting summary shares themes and scripture only. It does not include names, health details, family situations, or a personal request. If a line might identify someone, it is left out. The church still reviews the summary before it is sent.

That is the whole claim. Sermontary does not say that prayer audio is never recorded. If the church records the prayer meeting, the audio is handled like any other recording the church keeps. What changes is what the summary is allowed to say.

Where the audio goes, and how long it’s kept

This is the same account as the privacy policy, in shorter form. The policy is the one to rely on if the two ever differ.

• Service audio is turned into text by a speech-to-text service. The summary is written by an AI model working from that transcript. Both are run by specialist providers acting for Sermontary, who receive only what they need to do that job.
• Sermontary does not sell personal information, show advertising, or use member data to market itself. Members are emailed only on behalf of the church they signed up with.
• Audio, transcripts and summaries are kept while the church keeps them. A recording the church deletes is removed completely after 30 days.
• Within the church, what each person can see follows their role. Ministry leaders see their own ministries, and subscriber counts rather than the list.

Why not just paste it into ChatGPT?

A general chatbot can summarise a transcript you paste in. So can a sermon content tool that turns one upload into clips, guides and a newsletter draft. The difference is what is built in, and what you would have to remember every week. Where another product’s own site doesn’t say, the cell says “not stated” rather than “no.” A fuller, dated table is on sermon AI tools compared.

Is it right for a church to use AI for this?

Used this way, the tool is not preaching and it is not writing the sermon. Sermontary does not write sermons. It carries the pastor’s own words to people who asked for them: the member who was ill, the visitor who never filled in a card, the young person who missed Friday.

A church that wants to be plain about it can say so in the announcements. One sentence is enough: the summary is prepared from Sunday’s sermon, a person here reads it, and it goes only to people who signed up. That matches the guardrails above, and it matches the caution in the ethics writing: the pastor stays responsible for what goes out in their name.

If the church is deciding a wider policy — what staff may paste into a public chatbot, what must never leave the building — that is a separate conversation. This page is only about the summary.

FAQ