Nobody Reads the Church Bulletin: How to Turn Weekly Announcements Into a 90-Second Audio Track With Text to Speech (2026)

1) Why Announcements Get Lost (and Why Audio Helps)

Announcements usually live in several places at once: the printed bulletin, a slide on the screen, a church app, an email and the pastor's spoken notes. Vendors that sell church audio tools describe the same problem in their own marketing, which is that announcements end up "trapped" in bulletins, slides and emails, and that church websites rarely give members a simple audio version they can play after Sunday. Treat that as a vendor's framing rather than research, but it matches what most church offices see: the information exists, and people still do not take it in.

Audio helps for three practical reasons.

• People listen while doing something else. Driving, cooking and walking are moments when nobody opens a PDF.
• Sound carries tone. A friendly, steady voice reading "Youth night moves to Thursday" lands differently from a line of small print.
• It helps members who find print difficult. Older members, people with low vision and people reading in a second language often prefer to hear it.

2) What Belongs in a 90-Second Announcement Track

A spoken announcement is not a bulletin read aloud. Ninety seconds is roughly 200 to 230 spoken words at a calm pace, so you have room for about four to six items. Choose with a simple rule: include what a person must act on or show up for in the next two weeks.

Keep private information out of any audio you publish. A track on a public website can be heard by anyone, so follow the same rules you already use for the bulletin and the website.

3) A Script Template You Can Reuse Every Week

A fixed shape makes the track easy to write and easy to follow. Use this order:

1. Greeting (one sentence): "Hello from [Church Name]. Here are this week's announcements for [date range]."
2. Top item: the one thing you most want people to remember, with the day, time and place.
3. Two to four short items: one sentence each, then a single action ("Sign up at the welcome table").
4. Repeat the top item: one short sentence, because listeners cannot scroll back.
5. Closing line: where to find the full details, and a blessing or sign-off in your usual style.

Write for the ear. Short sentences, dates said as people say them ("this Thursday, October twenty-ninth, at seven"), and no abbreviations. Read the script aloud once yourself; if you stumble, the listener will too.

4) Names, Dates and Room Numbers: Getting Them Said Right

Churches are full of words that a text-to-speech voice may stumble on: staff names, Hebrew and Greek terms, saints, hymn titles and building names. Fix them before you publish.

• Spell it the way it sounds. Replace "Fr. Szymański" with a phonetic spelling in the script, then keep a small pronunciation list in a shared document.
• Write numbers out. "Room 204" can become "room two oh four", and "7:00 PM" becomes "seven in the evening".
• Add pauses. A comma or a new line between items gives the voice a natural breath.
• Always listen once. Do the full listen at normal speed before you publish, every week.

For a deeper method, see our guide on fixing pronunciation of names and acronyms.

5) Choosing a Voice That Suits Your Church

Pick one voice and keep it. Members come to recognise it the way they recognise a regular reader. A warm, medium-paced voice usually fits announcements better than a dramatic one. Audition two or three voices on the same paragraph and ask a few members which one they would be happy to hear every week.

If you would like the track to sound like a real person from your church, only use a recording of someone who has clearly agreed, in writing, to have their voice cloned for this purpose. Do not clone a pastor or staff member without that consent. Browse the stock options on the SpeakSay voices page if you prefer to avoid that question altogether.

6) Where to Publish the Track

• Your website's announcements page: embed the audio player above the written list so both are in one place.
• The weekly email: link to the audio with a line such as "Prefer to listen? 90 seconds."
• A phone line or voicemail greeting, if your church has one.
• Social media: a short clip with a still image and captions.
• Sunday service: play it on the screens before the service starts, with the text displayed.

Always keep the written version as well. Audio is an addition, not a replacement.

7) The 20-Minute Weekly Routine

1. Tuesday (5 min): the office collects announcements and picks the top item.
2. Wednesday (7 min): a volunteer fills in the script template and checks names and dates.
3. Wednesday (3 min): generate the audio in text to speech and listen once.
4. Thursday (5 min): post it to the website, add it to the email and queue the social clip.

Save each week's script in a folder. After a month you will have a ready archive and a template that writes itself.

8) What Audio Should Not Replace

• Emergency or safety notices. Use your normal calling or texting tree for urgent changes.
• Pastoral care. A synthetic voice is for logistics, not for bereavement or sensitive news.
• Accessibility obligations. Keep text versions and any accommodations your community needs.
• Transparency. Say once on the page that the track is read by an AI voice. Most members will not mind, and honesty builds trust.

Related reading: turning sermons into a midweek podcast and pre-recorded tracks for the Christmas program. With the season coming, a clear audio announcement track is a good thing to have running before December.

9) Frequently Asked Questions

Aim for 60 to 90 seconds, which is roughly 150 to 230 words. Longer tracks tend to lose listeners, so move detail to the written version.

It is good practice. A single line on the page, such as "Read by an AI voice", keeps things honest and avoids surprises.

Yes, if that person gives clear written consent to the cloning and to how the audio will be used. Otherwise, use a stock voice.

You can play the track before the service begins. For live moments during the service, a person speaking is still the better choice.

Respell it phonetically in the script, regenerate the audio and listen again. Keep a small shared list so you fix each name only once.