How to email a weekly sermon recap to your church
Sunday's sermon doesn't have to end on Sunday. A short email early in the week — the main point, a verse, a thought to carry — keeps the message alive and reaches people who couldn't make it. It's one of the highest-engagement things a church can send. The only catch is producing one every single week. Here's how to make it sustainable.
Why a weekly recap works
People forget a sermon within days — not because it didn't matter, but because the week floods in. A short recap email pushes back on that:
- It extends the message. A midweek reminder helps Sunday's teaching actually stick.
- It reaches the absent. Whoever missed church gets the heart of it in two minutes.
- It builds rhythm. A reliable weekly touchpoint keeps your church connected between services.
And unlike social posts that scroll away, an email lands directly with your people.
What to put in it
Keep it short — a few hundred words, readable in a couple of minutes:
| Part | What it does |
|---|---|
| A warm intro | One or two lines connecting to Sunday |
| The main point | The core of the message, stated simply |
| A key passage | The scripture to revisit |
| A memorable quote | The line worth carrying |
| A reflection or application | One question or action for the week |
That's it. Longer isn't better — sustainable is better.
The reason it usually fails
Every church that's tried this knows the failure mode: it works for three weeks, then a busy season hits and the email that takes an hour to write from scratch quietly stops. The idea is never the problem; the time each week is.
A weekly email lives or dies on how long each one takes to produce. Twenty minutes is sustainable through a busy season; an hour isn't. The whole game is getting the writing time down low enough that it survives the weeks when you're stretched.
Draft it from the transcript
Here's how the time collapses. If Sunday's sermon was transcribed automatically, you already have the full text. Feed that to AI and let it produce structured notes — the main points, the key passages, the quotes, the applications. That's 80% of your recap, already written. Your job shrinks to shaping it into a warm, short email and adding the personal touch.
- Start from the transcriptThe sermon's already captured — no writing from memory.
- Generate the notesLet AI pull out the points, quotes, and applications.
- Shape it into an emailTrim to the essentials, add a warm intro and a reflection question.
- Make it sound like youRead it over, add your church's voice, and send.
Keep it human
One rule: never send an unread AI draft. It gets you most of the way, but the warmth, the pastoral tone, and the accuracy are yours to add. The tool removes the blank page; you make it personal. For more on that draft step, see how to write a sermon summary.
Start this week
Take Sunday's transcript, draft the notes, shape a short email, and send it Tuesday. Once you see it's a twenty-minute job rather than an hour, it becomes a habit your church will come to look forward to.
Draft your weekly recap from the transcript — with AI, free.
Download TajiCast — freeFrequently asked questions
- What should a weekly sermon recap email include?
- A short intro, the main point of Sunday's message, the key passages, one memorable quote, and a simple application or reflection question for the week. Keep it short — a few hundred words people can read in two minutes.
- How do I write a sermon recap quickly every week?
- Start from the transcript rather than a blank page. AI can draft the recap — points, quotes, and applications — from the transcript of Sunday's sermon, so you're editing a near-complete draft instead of writing from memory.
- How often should we send a sermon recap email?
- Weekly works well — it matches the rhythm of your services and keeps the message fresh in people's minds. Consistency matters more than length; a short, reliable email beats an occasional long one.
Keep reading
How to turn your sermons into blog posts
A practical workflow for turning each Sunday's sermon into a written blog post, starting from an automatic transcript instead of a blank page.
Read the guide →ContentHow to write a sermon summary (and let AI do the first draft)
What makes a sermon summary useful, a simple structure to follow, and how to let AI generate the first draft from the transcript so you're only editing.
Read the guide →ContentBuild a sermon archive your church can actually search
Why a folder of sermon videos isn't really an archive, and how to build one you can search by the words that were actually preached.
Read the guide →