Write your Sunday bulletin in 10 minutes — without losing your voice.

Ask a church communications volunteer where their week goes and the bulletin always comes up. It is not one big task — it is twenty small ones. Chase the ministry leaders for their announcements. Reconcile three versions of the calendar. Reword the same building-fund update for the fourth Sunday in a row. None of it is hard. All of it is slow. And by Saturday night it is still not done.

AI can take real time off that job. But most people try it once, paste their notes into a chatbot, read the result, and quietly give up — because the draft that comes back is technically correct and completely generic. It sounds like a press release. It does not sound like your church. So they go back to writing it all by hand.

Here is what changed once we stopped treating this as a writing problem and started treating it as a voice problem. The goal is not to ask AI to be a good church communicator. The goal is to teach it, one time, how your church already communicates — and then let it do the assembly work every week. This article gives you that workflow for the bulletin, the midweek email, and the announcement slide.

Why the generic draft happens

When you hand an AI tool a pile of raw announcements and say "write our bulletin," it has no idea who you are. So it reaches for the average of every church bulletin it has ever seen. The average is bland. It over-explains, it leans on tired phrases, it is warm in a way that feels like a greeting card rather than a greeting from people who know you.

That is not a flaw you fix with a cleverer prompt each week. You fix it once, by giving the tool a reference point. Think of it the way you would think about a new volunteer. A capable new volunteer still writes a strange-sounding bulletin in week one — not because they lack skill, but because they do not yet know your church. You would not fire them. You would show them three past bulletins and tell them the handful of things your church always does and never does. Within a month they sound like you. AI needs the exact same orientation, and you only have to give it once.

Step one: build your voice profile (one time, about 30 minutes)

The voice profile is a short document you write once and reuse forever. It is the single most valuable step in this whole workflow. Open a plain document and fill in four sections.

Tone words

Pick five or six words that describe how your church sounds when it is at its best. Be specific. "Warm, plainspoken, hopeful, unhurried, a little playful, never stiff" tells a tool far more than "friendly." Then add a one-line negative: how you do not want to sound. "Never corporate, never guilt-driven, never breathless" closes a lot of doors a tool would otherwise wander through.

Things we always say

Capture the small habits that make your communication recognizable. The name you call your congregation — "church family," "friends," "everyone." How you refer to the gathering — "the service," "worship," "Sunday." The phrase you close announcements with. Whether you use first names for pastors. These details are invisible to you and completely invisible to a tool that has never met you.

Things we never say

Just as useful. Maybe your church avoids insider language and three-letter ministry acronyms. Maybe you never use exclamation points in headings. Maybe you do not say "don't miss it" because it reads as pressure. Write the list. Every item removes a future correction.

Two or three real examples

Paste in the full text of two or three past bulletins or emails you were genuinely happy with. This matters more than the adjectives. A tool learns your rhythm far better from a real example than from any description of it. Examples are the difference between a draft that is close and a draft that is right.

Save this document somewhere you can find it in five seconds. You will paste it at the top of every prompt from now on. It does not expire. Revisit it once or twice a year, or when a new communications person comes on, and otherwise leave it alone.

Step two: gather the week's information into one simple input

The second time-sink is not writing — it is hunting. Announcements arrive by text, by hallway conversation, in three different email threads. Trying to draft while still gathering is what turns a ten-minute job into a Saturday-night job.

So separate the two. Keep one running note for the week — a document, a shared form, a single message thread — and the rule is simple: every announcement goes there, in plain words, as it comes up. Ministry leaders add their own items directly. By the time you sit down to draft, your input already exists. For each item you only need four things:

• What it is — the event, update, or invitation, in one plain sentence.
• Who it is for — everyone, parents, students, a specific group.
• The when and where — date, time, location, with no ambiguity.
• The one action — register, show up, reply, sign up at the table.

That is the entire input. Messy bullet points are fine. The tool does not need polish from you — it needs facts. Polish is its job.

You are not asking AI to know what to say. You are asking it to assemble what you already decided to say, in the voice you already have.

Step three: the 10-minute generation pass

Now the part that is actually fast. Open your AI tool and build the prompt in three layers, in this order.

1. Paste the voice profile first. Lead with "Here is how our church communicates. Match this voice exactly," then the whole profile, examples included.
2. Give the assignment. "Using only the information below, write our Sunday bulletin announcements. One short paragraph per item. Lead with the action where it helps. Do not invent details I did not give you."
3. Paste this week's input. Your gathered note from step two, exactly as it is.

The instruction "do not invent details I did not give you" is small and important. Tools are eager to be helpful and will happily add a time, a room number, or a contact name that sounds plausible and is wrong. Telling it not to, every time, keeps your bulletin honest.

The midweek email and the announcement slide are the same input, three minutes more. Add a line: "Now adapt the same announcements into a warm midweek email — short intro, the three most important items only, one closing line." For the slide: "Now write the single most important item as one announcement slide — under fifteen words, action included." Same facts, same voice, three formats. That is the whole point of the voice profile doing the heavy lifting up front.

Step four: the human edit pass — never skip this

The draft is not the bulletin. It is a strong first draft, and it still needs a person. Budget five minutes and read with three questions in mind.

• Is every fact correct? Check every date, time, location, and name against your input. This is non-negotiable. A bulletin that sends people to the wrong room costs more trust than it ever saved time.
• Does it sound like us? Read one section aloud. If a phrase makes you pause, change it — and consider adding that correction to your voice profile so it does not return next week.
• Is anything missing or overdone? Tools sometimes inflate a small item or flatten an important one. You know which announcement actually matters this week. Give it the weight it deserves.

The edit pass is where the bulletin becomes yours. The tool got you to ninety percent in ten minutes; the last ten percent is human judgment, and it always will be.

What stays fully human

Some parts of your communication should never be generated, and naming them protects what matters.

The pastor's note stays human — start to finish. When a pastor writes a few lines to the congregation, the value is not the prose; it is that their actual heart is on the page. The moment that becomes a generated draft, your people are reading a performance of pastoral care instead of the real thing, and they can usually tell. The same holds for anything pastoral: a word of comfort after a loss in the church family, a sensitive update, a personal thank-you. AI can format the calendar around those words. It does not write them.

The simple test: if a member would assume those sentences came straight from a person who knows them, a person needs to have actually written them. Use AI for the administrative scaffolding. Keep the pastoral voice unmistakably your own.

Keeping it consistent week to week

The first week feels slower because you are building the voice profile. From week two on, the rhythm is genuinely ten minutes: the input is already gathered, the profile is already written, the prompt is the same three layers every time. Save your prompt as a template so you are never rebuilding it.

Two habits keep the quality from drifting. First, when you catch a recurring correction in the edit pass, add it to the voice profile. The profile should get a little smarter every month. Second, hold the standard. The temptation, once this is fast, is to skip the edit pass on a busy week. Do not. Ten minutes plus a five-minute read is the deal — the read is what keeps the bulletin trustworthy and unmistakably yours.

Done this way, the weekly bulletin stops being the thing that eats Saturday. It becomes a short, calm task — and the result still sounds like the church your people already know and love.

Want a head start? The voice-profile worksheet and a ready-to-use bulletin prompt template are in our resource library — free, no strings.