How to run church announcements without a dying group chat

What "good" looks like for church announcements

A working system does four things:

1. One current source for each update (not three copies that drift)
2. The right audience (public vs members vs one ministry)
3. An action when needed (RSVP, form, reply)
4. A place to find it later (searchable post or wiki page, not scrollback)

Group chat can still carry "doors open, we're short one usher." It should not be the archive for how baptism class works.

Step 1: Split announcements by audience

Before you write anything, label the update:

• Public: Service time changes, special services open to the neighborhood, give campaigns you want shared
• All members: Potluck details, congregational meetings, building projects that affect Sunday
• Ministry subset: Youth overnight packing list, choir rehearsal moves, care team schedules

Public updates belong on the website (and maybe a shareable post). Member updates belong in the member home. Subset updates go to that group's space so the whole church is not noise-flooded.

Step 2: Write with a fixed template

Paste this into every announcement draft:

Headline (outcome in plain words)
When / where
Who it's for
What to do (RSVP, form, show up, ignore if N/A)
Owner (who to contact)
Link or attachment (one primary)

Example:

Nursery volunteers needed this Sunday
Sunday 9:00–11:30 a.m., Room 12
For approved nursery team members
Tap RSVP if you can take a shift; reply to Jordan with questions
Form: Nursery shift signup

Short beats clever. If the headline needs a joke to make sense, rewrite the headline.

Step 3: Pick the channel by job, not habit

The mistake is choosing WhatsApp because it is open on your phone. Choose the channel that matches whether people must find this again next month.

Step 4: Run a weekly announcement hour

Block 30–45 minutes on the same day each week (many churches use Tuesday or Wednesday).

Agenda:

1. Collect inputs from ministry leads in one form or shared list (deadline Monday night).
2. Cut anything that is not time-bound or actionable.
3. Publish public site edits first if times or visit info changed.
4. Publish member posts and events second.
5. Send ministry-only notes last.
6. Skim last week's posts and update any details that are stale.

Protect the hour. Random midweek "can you blast this?" requests become next week's batch unless safety is involved.

Step 5: Attach actions so chat does not become the database

Every announcement that needs a response should include one clear action tool:

• RSVP for "are you coming"
• Form for volunteers, interests, or intake fields you must store
• Reply/message only when a human conversation is the point

If you ask people to "comment yes," you will re-count screenshots on Saturday night. Put the count in an event RSVP list you can open on a phone in the lobby.

Step 6: Keep a tiny wiki for repeats

Announcements die. Processes repeat. Capture the repeats:

• How check-in works
• Who has keys
• Standard potluck setup
• New-member class outline
• Brand folder / logo use

When the annual event returns, the announcement links to the wiki page instead of rewriting tribal knowledge from memory. New volunteers ramp faster when the instructions outlive the chat that trained last year's team.

Sample month using this playbook

Week 1: Publish fall kickoff on the public events page; member post with RSVP for volunteer roles; wiki updated with setup checklist.

Week 2: Member post for congregational meeting; form for childcare signup; no chat blast beyond a one-line pointer to the post.

Week 3: Public site visit page updated for time change; member reminder post; ushers briefed from the same post.

Week 4: Review completed events and old announcements; update anything still relevant; review which ministry leads missed the Monday intake deadline.

You will still have exceptions. The playbook exists so exceptions do not become the system.

Where Guava fits (without boiling the ocean)

Guava gives churches a public site and a private member home together. You can post announcements where members already belong, run events with RSVP, collect forms, message people, and keep wiki pages for recurring ops. New-post email notifications help members see updates without living in a chat thread. Free covers a Guava address up to 50 members; Plus adds your domain, unlimited members, branding removal, and Mailchimp/Kit if you sync lists there.

This playbook runs on posts, events, forms, and a clear public/private split.

Playbook checklist

• Audience labeled before drafting
• Template fields filled (when, who, action, owner)
• Public vs member channel chosen on purpose
• RSVP or form attached when a response is required
• Recurring instructions live on a wiki page
• Weekly announcement hour on the calendar
• Chat reserved for same-day pings

Next step

Run one announcement hour this week with the template above. Move a single recurring process into a wiki page and link it from your member post. If you want the public church site and member home in one place, start on the church website builder.

Useful next steps

• Start with a church template
• Review your church website pages
• Improve volunteer signup forms