How to write the weekly church email after Sunday's sermon

The everything email

Most churches send one email a week, and it carries everything: the sermon recap, three upcoming events, the prayer list, a volunteer ask, a note about parking during construction, and a giving link at the bottom.

It's the reasonable thing to build. Sending one email feels considerate, like you're protecting people's inboxes. And every ministry leader who asked to be in it got in, so nobody on staff is unhappy.

But an email about six things is an email about nothing. A reader opens it, scans for whatever concerns them, doesn't find it in the first screen, and closes. Do that for a few months and the whole list learns that your email is a bulletin, and bulletins are for skimming, not opening.

The sermon is what suffers most. It's the thing your pastor spent 10 to 15 hours on, and in the everything email it's a paragraph competing with the potluck.

Send one email per topic instead

The fix isn't writing the everything email better. It's not sending it.

Split it into separate sends, one topic each:

• The sermon recap. One idea from Sunday, one action.
• Upcoming events. Whatever is actually time-sensitive this week.
• The prayer list. Its own thing, for the people who want it.

Each email now has a subject line that can tell the truth, because there's only one thing inside it to be truthful about. "This Week at Grace" becomes a subject line about the actual sermon, and someone deciding in half a second whether to open it now has something real to decide on.

Staff will push back that this is more email. Two things solve that, and you need both.

Segment. Not everyone gets every send. The prayer list goes to people who asked for the prayer list. Events go to the people who opted into events. The sermon recap goes to everyone, because everyone has some relationship to Sunday. Done right, most individuals get the same volume they got before, or less, and all of it is something they said yes to.

Stagger. Never two in a day. Sermon recap early in the week, events later, prayer on its own day. The list feels a steady rhythm instead of a pile.

The rest of this post is about the sermon recap specifically, because it's the one that goes to everyone and the one that's easiest to get wrong.

Subject lines: say what's inside

The subject line's only job is to tell the truth about what's in the email, specifically enough that someone decides in half a second whether to open it.

"This week's message" tells them nothing. "Sunday recap" tells them nothing. Build it off the sermon's actual content instead: the phrase the pastor used, the question the sermon raised, the tension it named. If Sunday was about staying patient in a season with no visible progress, a subject line built around that idea, not around the word "sermon," is what gets opened.

A few patterns that work without being a gimmick:

• The sermon's central phrase, stated plainly
• A question the sermon asked but didn't fully answer
• A specific promise of what's inside ("one question for your week")

Don't oversell. If the subject line promises a big reveal and the email is a paragraph of general encouragement, people learn not to trust your subject lines, and that costs you every week after.

The one-big-idea rule

A sermon runs 30 to 45 minutes and covers several points that build on each other. An email is read in under a minute, on a phone, between two other things. Treating the email like a condensed transcript is the most common mistake in the whole exercise.

Before writing anything, answer one question: what's the single sentence you'd say if someone asked what church was about this week? Not three points. One sentence. That's the spine of the email.

Everything else should serve that sentence. If a paragraph doesn't connect back to it, cut the paragraph, even if it was a good moment on Sunday. The email isn't preserving the sermon. It's extending one piece of it into the reader's week.

It should come from the pastor, in first person

The sermon recap works best as a short note from the person who preached it, written as "I," not as a summary written about them in the third person.

The difference is not stylistic. A recap written about the sermon reads like minutes from a meeting. A note from the pastor reads like the conversation you'd have with them in the lobby if there were time, and people answer it. Replies to a pastor-voice email are one of the few places where a church email produces an actual conversation instead of a click.

Skip the greeting. No "Hope you had a great week." Start on the idea, in one sentence, the way you'd start talking to someone who already knows you.

How to actually sustain that

Asking a pastor to write a personal email every week is asking for the thing that reliably doesn't happen. They're already spending 10 to 15 hours on the sermon itself, and by Tuesday they're working on next Sunday.

The workflow that survives: someone on staff drafts it from the sermon, the pastor edits two lines, and it ships.

That's it. The draft does the structural work, pulling the one big idea and shaping it into a page. The pastor's job shrinks to five minutes of making it sound like them, which is the only part that genuinely requires the pastor. A phrase they'd actually use, a reference to something that happened in the room, a sentence cut because it isn't how they'd say it.

Those five minutes are what makes it a first-person email rather than a ghostwritten one. Protect them and skip everything else.

A structure that holds up every week

Once you have the one big idea, the email mostly writes itself:

Subject line. Built off the big idea.

Opening line. Straight into the idea, one sentence, no greeting.

Body, two or three short paragraphs. First, expand the idea and state it more fully than the subject line could. Second, apply it to an ordinary Tuesday-through-Saturday moment rather than a hypothetical. Third, point forward: what's coming, a series continuation, a way to respond this week.

One clear action. One. If the sermon recap has a link to the full sermon and a link to the retreat and a link to give, it has quietly turned back into the everything email at a smaller scale.

It reads in under a minute and it never summarizes the sermon point by point.

What to cut

• A full sermon summary. If someone wanted the whole sermon they'd watch it. A recap that covers everything covers nothing well.
• Announcements. They have their own email now. That was the whole point.
• A greeting paragraph. "Hi church family, hope this finds you well" delays the actual content.
• Stacked scripture references. One verse, if it's central. A list of five reads as homework.
• A closing paragraph that restates the opening. If the email made its point, it doesn't need to make it again on the way out.

Pick a day and hold it

Tuesday or Wednesday works for most churches. Monday inboxes are still clearing from the weekend, and by midweek a good subject line has a real shot while Sunday is recent enough that nobody needs a recap to remember it.

The day matters less than the consistency. A list that gets an email on a different day every week never forms the habit of expecting it. Pick one, hold it, and let people learn when you show up.

Where Extend the Sermon fits

Drafting this well every week takes 30 to 45 minutes, most of it spent staring at a blank subject line trying to remember the sermon's exact wording days later. That's on top of the clips, graphics, and discussion guide the same sermon could produce, which comes to about 6 hours a week if you're building all of it by hand. If you'd rather read the draft than write it, run one sermon through free and see what comes back.

Extend the Sermon takes one sermon upload and writes the weekly email, along with 14 to 18 finished pieces total, in 20 to 50 minutes. It comes back built from the sermon's actual transcript, not a template, so the one-big-idea rule is already applied before you open it. Then the workflow above takes over: the pastor edits two lines and it ships in their voice.

You can read how Extend the Sermon works for the full breakdown. Your first sermon runs free, no card required to start, and everything we make is yours to send and keep.

Get your free sermon

Related

• Free sermon clip maker: run your first sermon free and see the email alongside the rest of the week's content.
• Sermon to social media content: the whole week from one upload, including this email.
• What to post after Sunday: where the email fits in a full six-day content plan.