Announcement loops that people can actually read

People arrive early. The screen is already on. What they see in those ten or fifteen minutes is often the only announcement most of the room will absorb. If the loop is a wall of dates, three QR codes, and last month’s potluck, they will look at their phone instead.

Announcement slides are not worship lyrics and they are not the sermon. They are a short, readable loop — or a short click-through — that hands off cleanly when the first song starts. The job is one idea per frame, type large enough from the back row, and a mid-week owner so Sunday is not a scavenger hunt.

This page is about the slides themselves. For the person who also runs lyrics and scripture alone, see running Sunday slides with one volunteer. For how slides fit the rest of the service, see how church presentation software works.

One idea per frame

A good announcement slide says one thing: the event, the date, the time, and who it is for. If you need a second thought — what to bring, where to park — that is a second slide or a line on the bulletin.

Cramming a monthly calendar onto one 16:9 frame is how type shrinks to a size nobody can read. The loop can hold six or eight simple slides. It cannot hold six or eight dense posters.

Write the slide as if someone will see it for eight seconds while talking to a neighbor:

• A short headline (“Youth dinner, this Wednesday”)
• One supporting line (“6:30 p.m., fellowship hall, bring a friend”)
• Optional: a single next step (“Sign up at the welcome table”)

If the pastor wants the newsletter paragraph, keep it in the newsletter. The screen is a pointer, not an archive. A photo can carry a slide. A logo in every corner cannot. Leave margin. The projector will crop more than your laptop preview suggests.

Loop versus click-through

A loop runs itself before the service and sometimes in the lobby. Nobody clicks. Each slide holds for a few seconds, then the next one appears, then it starts over.

A click-through is a stack the operator advances — welcome, two announcements the pastor will speak, then the first song.

Most rooms need both, and they are not the same deck.

The pre-service loop is for people finding a seat. It should be safe to ignore. It should not include a countdown that ends during sound check, a “please stand” cue, or a lyric. When the service starts, the operator needs one action that kills the loop and lands on the first worship slide. That handoff matters more than a pretty transition.

The click-through is for spoken announcements. Those slides stay up while someone talks. They do not rotate under the speaker. If you put spoken items in the loop, the pastor will be on item three while the screen is still on item one.

Lobby TVs can run the same loop, or a shorter version without “welcome to worship” frames that only make sense in the room. Someone has to start them. A TV that still shows last week’s slides is worse than a TV that is off.

If you are one volunteer, prefer a loop that starts with a single button and a click-through of three spoken items. Planning beats a last-minute rebuild. That is the same discipline as building the service during the week.

Type size and contrast

If you have to squint on the laptop, the back row has already lost.

Use a large sans-serif. High contrast: light text on a dark field, or dark text on a light field. Avoid thin yellow on a sunset photo. Keep important words out of the lower fifth of the frame, where a pulpit camera or cheap TV overscan will cut them off.

Stand at the back of the room on Saturday and read the slide aloud. If you cannot finish the headline before it advances, the type is too small or the hold time is too short.

Do not decorate the way you would decorate a social post. Motion behind body copy makes the letters swim. If you need a photo, darken it so the type sits on a calmer patch. Line length matters the same way it does on lyric slides: short lines, generous spacing, no justified newsletter columns.

Too many QR codes

A QR code is a next step for one person with a phone and a few extra seconds. It is not a substitute for a readable sentence.

One code per slide is the ceiling. Give it room and a label (“Scan to register”). If the slide also has a date, a paragraph, a logo, and a second code for the giving app, nobody will scan either one.

Many people will not scan during the greeting. They are holding a cup or a child. Put the same next step on the bulletin, at the welcome table, or in a verbal “see Jane in the foyer.”

Do not put a QR code on a two-second loop slide. Hold that frame longer, or move the code to a click-through slide the pastor will leave up. A code that opens last year’s sign-up form trains the room to ignore the screen.

Dates that go stale

The most common announcement failure is not design. It is last Sunday’s date still on the loop.

Prefer a specific date (“Wednesday, September 10”) and a kill date. When the event is over, the slide leaves the loop the same week. Recurring events (“every first Sunday”) still need a human to confirm they are true.

Keep a short list: what is happening in the next two weeks, one standing invitation that does not expire, and nothing whose date you cannot defend. Seasonal slides expire. Put a reminder on the calendar for the Monday after. The person who owns the loop deletes first and designs second.

If your software has a shared library, do not leave twelve versions of “Church picnic” in the folder. The next volunteer will pick the wrong one.

Who owns the content mid-week

Slides do not update themselves. If “someone” owns announcements, nobody owns them.

Name one person. It does not have to be the Sunday operator. It is often a secretary, a pastor, or whoever already writes the bulletin. Their job is to collect asks by a mid-week cutoff — Wednesday noon is a common one — and to say no to late posters that would force a Saturday rebuild.

The Sunday operator should receive a finished loop, not a folder of half-sized JPGs. Specs help: 1920×1080, one idea, type that works from the back. If people send phone screenshots of a Facebook event, the owner remakes the slide or declines it.

Church-owned files, church-owned login. If the loop lives on a personal laptop, the next volunteer cannot fix a stale date. Write one page of notes: which file is this week, how the loop starts, which input the lobby TV uses.

When ministries want “just thirty seconds on the screen,” the owner translates that into one slide or a spoken mention. A one-person team cannot remix the foyer during the last song. That is why one-volunteer Sundays run on a saved order.

Timing, and the handoff to worship

Hold times of six to ten seconds are enough for a simple slide. Longer if there is a QR code. Shorter if the loop feels like a stall. Watch the room: if people look up, read, and look away before the slide changes, you are close.

Start the loop when the first person might walk in — often 10–15 minutes before the scheduled start. Confirm the lobby set if you have one.

The handoff should be boring. The loop is running. The first lyric slide is cued in the operator view, not on the house. On the agreed cue — pastor welcome, first chord, a nod — the operator exits the loop and goes to the first song, or to a clean holding slide, then the song. The house never sees the playlist.

Do not leave a potluck slide up through the opening song. Going to black or a simple logo for a breath is better than the wrong words. Once worship starts, the screen follows the song. Lyrics on the church screen covers that job.

After the service, stop the loop. Note which slide was wrong. Fix it on Monday.

A weekly rhythm keeps the loop honest: Monday, delete expired slides. Mid-week cutoff, new asks in. Thursday or Friday, open the real file on the church computer. Saturday, play the loop on the real projector and rehearse the handoff once. Sunday, start early and click the spoken stack only when someone is talking.

The room will forgive a plain slide. It will not forgive a busy one it cannot read, or last month’s date still looping while the band waits.