How to send a sermon summary email every week (without writing it yourself)
A sermon summary email is a short note after the service: the title, the scripture that was read, a few things to carry into the week, one verse, one question, and a link to the full audio. It is a two-minute read, sent to people who asked for that service. The format is the easy part. Sending it every week, to the right people, is the part that usually slips.
What a sermon summary email is (and isn’t)
A sermon summary email is a short message sent after a service that gives members and visitors the heart of the sermon in about two minutes. It reinforces what people just heard, and it lets someone who was ill, away, or new catch up without sitting through an hour of video first.
It is not the church newsletter, and it is not the transcript. Those do different jobs.
| Format | What it’s for | Length | Who reads it |
|---|---|---|---|
| Sermon summary email | The heart of one sermon, plus the audio | About two minutes | People signed up for that service |
| Church newsletter | News, events, giving, the week ahead | As long as the week was | The whole church list |
| Transcript | A record of every word | The length of the sermon | Almost no one, unless they are searching for a line |
| Fill-in sermon notes | Listening along on Sunday, in the room | A page in the bulletin | People in the seats that morning |
The sermon email has one job: this message, for the people who wanted this service.
What to include: the anatomy of a good one
The same shape works for a handwritten email and for a draft prepared from the service. Write it as a letter to one person, not as a bulletin.
Title and scripture
Use the sermon title and the preacher’s name. List only the passages that were actually read. A verse that would have fitted, or one the preacher mentioned in passing and did not open, does not belong in the list. People trust the email more when the scripture matches what they heard.
Three things to carry into the week
Three is enough to remember on a Wednesday. Write each one as a short statement, in the order it was preached, then a few sentences of the explanation the preacher actually gave. Three is a shape, not a quota: if the sermon had four real movements, keep four. Don’t invent a third point to fill a blank, and don’t drop the point the preacher spent twenty minutes on so the email looks tidy.
The key verse and one question to reflect on
One verse to remember, quoted only if it was read aloud, in the words that were read. Then one question for the week — for the person reading alone, or for a small group. The question should follow from the sermon. It is not a new idea added at the end.
The full audio, one tap away
The summary is the doorway, not the room. Link the full message for the drive to work, and for anyone who missed Sunday. A person who was there can re-hear the line they needed. A person who wasn’t there shouldn’t have to hunt for the livestream archive.
Addressed to the person, from the church
“Hi Sarah,” from the church’s name, with replies going to the church office. A personal greeting is easier to forward to a friend than a message that starts “Dear church family.” Say which service it was, so a person on two lists knows what they’re opening.
Riverbend Grace Church · to Sarah · replies go to the church office
Sunday’s message: The Father Who Runs
Hi Sarah — Pastor Daniel Okafor preached from Luke 15. The parable isn’t mainly about a runaway son. It’s about a father with two lost sons, and he goes out to both of them.
- Asking for the inheritance was asking for the father to be gone
- Coming to your senses is where coming home begins
- The father runs before the apology is finished
“For this, my son, was dead, and is alive again. He was lost, and is found.” — Luke 15:24
That sample follows the sermon’s own movements, including a fourth point about the older brother, because that sermon had one. Open it to see the greeting, the audio link and the way a reply address sits on the church’s name.
How long it should be
Aim for a two-minute read. That is long enough to carry the idea, and short enough that people finish it.
The email’s job is to reinforce the message, not to replace it. A person who was in the room should recognise the sermon. A person who missed it should know the big idea and want the audio if they want the rest. A transcript feels thorough and doesn’t get read. A single sentence feels like a teaser and doesn’t help anyone live with the passage. Two minutes sits between them.
When to send it
Same day, or Monday. Both are honest options. Pick the one your church will still be doing in March.
Same day helps the person who missed the service, if someone can still read the draft before it goes. Monday morning is quieter, and a missed Sunday is still recent — as long as it sits on a real person’s morning, not on “someone.”
You choose: review and send, schedule a time, or send automatically with a window to cancel. On Sermonary those are the three options. Automatic still waits — you’ll have 15 minutes or more to read it, change it, or stop it. Edits made before a scheduled time are what goes out. A ministry can also require the pastor’s approval before any of those sends happen. Review and send is the step that keeps the promise that nothing leaves unread.
Who writes it, and who approves it
Four ways churches actually do this:
- The pastor writes it. Faithful, and it dies the first Monday they are in hospital visits all afternoon.
- A staff member or communications volunteer writes it from their notes or a recording. It lasts if that person has the time blocked, and if the pastor still sees it.
- A ministry leader writes their own — the youth leader for Friday, not the pastor for every gathering.
- A draft is prepared from the service, and a person who was there reads it, fixes it, and sends it.
The last one is how a weekly email survives a busy season. The draft does the blank page. The person does the judgment.
Pastor approval is worth turning on, especially when someone else prepared the words. The email goes out with the church’s name on it. The preacher should recognise their sermon in it. A youth leader can submit Friday’s summary and wait; the pastor approves, or sends it back with a note. That is a setting on the ministry, not a favour you have to remember to ask for. Approval is also how a church keeps prayer meetings and youth nights from being treated like a Sunday sermon that happened to be shorter.
The part most guides skip: building the list
A beautiful recap that goes to twelve staff inboxes is a staff memo. The visitor who never filled in a card, the member who was ill, and the young person who missed Friday are not on that list, and they are the reason to send the email at all.
One QR code on the pews
Print one code and put it where people already look: on the pew, in the bulletin, and on the announcement slide. They scan it with the camera they already have, enter an email address, tick the services they want, and confirm with one tap. No app. No church login. No card to hand to a host who then has to type it in on Monday. Signing up should take about a minute, in the seat, while the idea is still fresh.
One list per service
Sunday morning subscribers get Sunday morning. Midweek gets midweek. Youth gets youth. A person can be on more than one. They should not receive Friday’s youth talk because they once came on Sunday, and they should not receive Sunday because their teenager signed up for youth. One code can offer every service; each email still goes only to the people who asked for that one.
Online viewers too
The same sign-up link belongs in the livestream overlay, the YouTube description, and a button on the church website. People watching from a kitchen are just as able to miss next week. The outreach kit is those links, already worded, so nobody is writing a caption from scratch on Saturday night.
Anyone without a smartphone
Scanning needs a phone. Joining the list does not. Staff can add an email address for someone who asks at the door, or who calls the office. Say so out loud. Otherwise the people least likely to scan are the ones a sermon email would have served first.
Midweek, prayer and youth gatherings
Not every gathering is a sermon, and the email should admit that.
- Sermon. Title, preacher, scripture that was read, the movements of the message, a verse, a question, the audio.
- Prayer. Themes and scripture only. Never names, never a personal request, never a health detail, never a family situation. If you are unsure whether a line identifies someone, leave it out. Prayer requests stay in the room.
- Youth. Plain words a teenager will actually read, and a challenge for the week. Sign-up is for ages 13 and over, or a parent or guardian signing up on a young person’s behalf. Leave out anything personal a young person said in the room. There is a fuller note on youth night, and the age rule is in the privacy policy.
- Everything else — a members’ meeting, a testimony night — gets a short recap and the points that mattered, not a sermon shape forced onto it.
Each of those can be its own list. The youth leader is not waiting on the Sunday writer, and the prayer email is not a softer version of the sermon with the names taken out at the last minute.
Doing it without writing it: the Sunday timeline
Most advice on sermon recap emails is about writing a better email. The email still has to exist on the weeks when nobody has an hour. This is the order of a Sunday when the draft is prepared from the service itself. How it works is the same path in five steps.
- Record. From the sound desk while the service runs, or from the livestream the church already publishes. Afterwards, a YouTube link or an uploaded file can take the same path.
- A live transcript. Words appear as people speak. A helper on a second screen — the Live Desk — can fix a name or a book of the Bible while the service is still going. “Philippians” gets corrected then, not discovered in the email on Monday.
- The summary is ready after the service. It is written from the edited transcript: title, scripture that was read, the points in the order they were preached, a verse, a question. It does not add theology, stories, or applications the preacher did not make.
- A person reviews it. The pastor, or a ministry leader and then the pastor if that ministry requires approval. Change a sentence. Cut a line that felt different in the room from how it reads. Send a test to yourself if you want to see it as the reader will.
- Then it is sent — now, at a time you pick, or automatically once the cancel window has passed — and only to people who asked for that service.
The homepage shows a sample Sunday with clock times beside those steps. The times illustrate the order. They are not a measure of your service, or of how long review will take.
What a person still checks, even when the draft is faithful: the preacher’s name, every verse reference, anything said about a person, and whether the big idea is the one they meant. Speech-to-text will mishear a name. A tired reading will miss a tone. That read-through is the job. Writing the first draft from a blank page is the job you can stop doing.
A copy-and-use template
If you are sending this by hand, use the same shape. Fill the brackets from your notes or a recording. Delete a line rather than invent one. Only scripture that was read. Only applications the preacher asked for.
FAQ
What is a sermon summary email?
A sermon summary email is a short message sent after a service that gives members and visitors the heart of the sermon in about two minutes: the title, the scripture that was read, three key points, a verse to remember and a question to reflect on, with a link to the full audio. It isn’t a transcript or a newsletter. It reinforces the message for people who were there and lets people who missed it catch up.
What should a sermon recap email include?
A good sermon recap email includes the sermon title and preacher, the scripture passages actually read, three short takeaways written as plain statements, one key verse, a single reflection question for the week, and a one-tap link to the full sermon audio. It should come from the church’s name, greet the reader personally, and make it easy to forward to a friend.
How long should a sermon summary email be?
About a two-minute read. Long enough to carry the sermon’s idea into the week, short enough that it doesn’t try to replace being there or listening to the whole message.
When should you send a sermon summary email?
Same day works when someone can read it before it goes. Monday morning works when Sunday afternoon is already full. Either is fine. What fails is a send time nobody can keep. Choose one and protect it.
Who should write it, and does the pastor need to approve it?
A pastor, a staff member, a volunteer, or a draft prepared for them can write it. Someone who was in the room should still read it. Many churches ask the pastor to approve before it is sent, especially when a ministry leader prepared the draft. The person who preached is responsible for what goes out under the church’s name.
How do you get people to sign up for a weekly sermon email?
The simplest way is a QR code on the pews, in the bulletin and on the announcement slide. People scan it with their phone camera, enter their email, pick which services they want (Sunday morning, midweek, youth) and confirm with one tap, with no app or church login needed. For online viewers, put the same sign-up link in the livestream overlay, the YouTube description and a button on the church website.
How do you handle midweek, prayer and youth gatherings?
Give each gathering its own list and its own shape. A sermon carries points and a question. A prayer meeting carries themes and the scripture that was read, and never names or personal requests. A youth night is written in plain words, with a challenge for the week, and sign-up is for ages 13 and over or a parent or guardian.
Can a draft be prepared faithfully, and what should a person still check?
A draft can follow the transcript and stay inside what was actually said: only scripture that was read, no added illustrations, no invented applications. A person still checks names, verse references, anything tender, and whether the big idea is the one that was preached. Nothing should go out unread.
Do members need an app?
No. They scan a code or open a link, enter an email address and confirm. The summary arrives as an ordinary email.
Can people unsubscribe?
Yes. Every email should have a clear way to stop, and stopping should take one tap. People who leave the list should stay off it.
What does it cost?
On Sermonary, every church starts on the Starter plan, free for up to 50 subscribers. The Church plan is for a larger list. Both plans include the same features.