Big churches solve the reminder problem with software: an automated text three days out, an email the morning of, a follow-up nudge for anyone who has not opened either one. Small churches usually do not have that tool, and buying one just to remind twenty families about a fall festival is a strange trade. The good news is that a small congregation does not need the automation. It needs a rhythm.
A rhythm means the same three or four things happen every time there is an event on the calendar, in the same order, done by people who already know the names on the list. It is slower than a mass blast. It is also more personal, and for a room of sixty to two hundred people, personal beats fast almost every time.
Why the mass blast instinct fails at this size
A mass email works when the list is large enough that a low reply rate still produces enough bodies in the room. At a church of a hundred and twenty, a twenty percent open rate on an email nobody asked for is twenty-four people glancing at a subject line, most of whom will forget it by Thursday. The instinct to broadcast comes from software built for scale you do not have. What you actually have is a list short enough to work by hand — which is an advantage, not a limitation, if you use it that way.
Start from the registration list, not a group text
The reminder has to start somewhere, and the honest starting point is whoever actually signed up, not a guess at who might come. If your event has registrations recorded in one place, print that list the week the reminders start. Anyone missing a phone number or an email address gets flagged first — you cannot remind someone you cannot reach, and finding that out three days before the event is too late to fix it.
The same discipline that keeps an event from sliding into a dozen scattered spreadsheets applies here. One list, kept current, beats three copies floating around in different inboxes, each one a little more out of date than the last.
Split the list into three piles
Not everyone needs the same reminder. Sorting the list first saves real time later.
- Confirmed and reliable. They said yes and they always show. A bulletin mention or a single postcard is plenty.
- Registered but quiet. They signed up weeks ago and you have heard nothing since. This is the pile worth a phone call, because silence is not the same as a no.
- Interested but not yet registered. Someone mentioned it after service. A short, specific ask — “are you still planning to come Saturday?” — closes the loop faster than a general announcement ever will.
Three piles keep the volunteer team from calling ninety people when fifteen calls and one bulletin insert would have done the job.
The phone call script that does not feel like a script
A reminder call works best when it is short and specific, not warm in a way that eats ten minutes per family. “Hi, this is Karen from the front desk — just confirming you're still planning to join us for the fall cookout Saturday at eleven?” takes under a minute and gets a clear answer. If the answer is no, that is useful information too — it tells you the actual headcount instead of the hopeful one, which matters for food and seating.
Write the script down once and hand it to whoever is calling. It keeps the tone consistent across three different volunteers, and it means nobody has to improvise an opener while holding a clipboard.
The bulletin insert and the paper sign-up as backup
Not every reminder needs a phone. A printed insert in the Sunday bulletin two weeks out, a repeat the week before, and a table at the back where people can re-confirm on paper covers the confirmed and reliable pile without anyone spending a phone minute on it. This is the least glamorous part of the rhythm and the part that actually reaches the most people, because it rides along with something people already show up for.
Build the calendar backward from event day
Work backward from the event the same way you would build the weekly admin rhythm that keeps ordinary Sundays from slipping. Two weeks out: bulletin mention, first pass at the registration list. One week out: phone calls to the quiet pile. Two or three days out: a last call to anyone still unconfirmed, plus a final headcount to whoever is buying the food. Put those dates on the actual calendar, not in someone's head, so the rhythm survives the week the regular volunteer is out sick.
Assign owners the way you would a serving rotation
“Someone should call the quiet pile” is a wish, not a plan. Split the list of names across two or three people, write their names next to the names they own, and check in once, a day or two before the deadline. This is the same principle behind a fair serving rotation: work only gets done reliably when a specific person is responsible for a specific, bounded piece of it, not when it is everyone's job in general.
SundayBridge keeps the registration list, the people attached to it, and their contact details in one place, so the person making calls is working from one accurate list instead of hunting through old sign-up sheets — it will not place the call or send the text for you; the reminder itself is still a conversation someone on your team has by hand.
What to skip, so the rhythm does not collapse
The fastest way to kill a manual reminder system is to make it too thorough. You do not need a call, a text, an email, and a bulletin mention for the same person about the same event — pick the one or two channels that fit each pile and stop there. A volunteer who feels obligated to reach everyone through every channel burns out after one event and the whole rhythm quietly stops. Better to run a smaller, repeatable version every time than an exhaustive one that only happens twice.
It also helps to resist the urge to remind too early. A reminder sent a month out gets forgotten before it does any good; the useful window is roughly two weeks to two days before the event, when someone can still act on it without it slipping their mind again.
Close the loop after the event, too
A reminder rhythm that stops the day of the event misses half the point. Anyone who registered and did not show is worth a short, low-pressure follow-up — not a guilt trip, just a note that you missed them and hope to see them next time. That is the same instinct behind following up after a big Sunday: the event is not the finish line, and the people who almost came are often the easiest ones to bring back if someone reaches out while it is still fresh.