A member communication plan you'll actually use

A communication plan sounds like the sort of thing that needs a consultant, a workshop and a spreadsheet the size of a wall, and it honestly doesn't. Strip away the important-sounding language and it's just a handful of decisions you're already making, only right now you're making them by accident: who you're actually talking to, what you're telling them, where you're telling it, how often, and whose job it is to send it. Most groups never write any of that down, so it happens on the fly - whoever's holding the phone fires off a message when they remember, the things that really matter get buried under the things that don't, and the quiet half of your members slowly forget you exist. Writing it down doesn't make you corporate or stiff. It just means the decisions get made on purpose, once, instead of in a panic at eleven at night.

Let me carry one example through the whole thing so it stays concrete. Say you help run Relawan Sigap Semarang, a community volunteering group - around 220 registered volunteers, a core of maybe 40 to 60 who turn out for most things, and a long tail of a hundred-odd who signed up once, meant well, and haven't been seen since. The group does flood-response deployments when the rains come, a monthly blood-donation drive, the occasional food distribution and clean-up. And like almost every group this size, it runs its entire communication life through one WhatsApp group and the good memory of two or three coordinators. It works, mostly. But it's fragile, and it quietly leaks people, and a plan is how you stop both.

Here's the pattern worth naming before we go further, because nearly everyone does it and almost nobody notices: most groups over-communicate to the keen and under-communicate the essentials. The active core get twenty messages a week in the group chat and are perfectly happy about it. The reserve hundred hear nothing for three months, mute the group somewhere along the way, and then get a frantic flood call-out at 6am that lands in a chat they stopped looking at back in April. The chatter is loud and the important stuff is quiet, which is exactly backwards. Almost everything below is really about fixing that one imbalance.

Start with who you're actually talking to

You are not talking to "members", or "volunteers", as one lump. That's the first and most useful shift. You're talking to several different groups who want quite different things from you, and a message that's spot-on for one of them is often wrong for another. For Relawan Sigap the honest split is roughly four groups: the brand-new sign-ups who don't yet know how anything works, the active core who already know more than you do and just need the practical details, the big reserve group who are barely tuned in and need a reason to come back, and the coordinators themselves, who need a different conversation again because they're running the thing rather than attending it.

You don't need to get clever about this or build ten finely-sliced segments - that's a good way to make a simple job miserable. Three or four groups is plenty for almost anyone. The point of naming them at all is that once you have, a lot of your communication problems explain themselves. The reason your reserve volunteers never show up isn't that they're flaky; it's that the only thing they ever hear from you is a panic. The reason the core feel over-messaged is that they're getting everything aimed at everyone. Sort the people first, and the rest of the plan gets easier.

Sort your messages by what actually matters

Every group, whatever it does, sends roughly five kinds of message, and it helps enormously to separate them out because they don't deserve equal footing:

• Welcome. The first thing a new volunteer hears after signing up. Genuinely one of the most important messages you'll ever send, and one of the most neglected - most groups reply with an automated receipt and then silence.
• News and updates. What the group did, who it helped, what's coming - the ongoing story that keeps people feeling part of something. Nice to have, easy to overdo.
• Events and trainings. The blood drive on the 14th, the flood-response refresher, the working bee - anything people need to plan their diary around.
• Renewal or re-registration. The yearly moment where people confirm they're still in, update their phone number, re-sign the waiver. Dull, essential, and forgotten until it's late.
• Urgent call-outs. "River's rising in Genuk, we need 15 people at the posko by 7am." The messages where minutes matter and a missed one has a real cost.

Now look at those five again, because there's a hierarchy hiding in them. The welcome, the renewal and the urgent call-out are the ones that genuinely can't afford to fail - they're the essentials. The news and the general chatter are lovely, and they do real work keeping people warm, but nobody's world falls apart if a monthly update goes out a week late. Yet in most groups it's precisely the news and chatter that fill the channels, while the essentials get one rushed line in a busy group chat and hope. If you fix nothing else, protect the essentials and let the nice-to-haves take a back seat.

Match each message to a channel

This is where the plan earns its keep, because the right message on the wrong channel may as well not have been sent. A heartfelt welcome buried as message 47 in a group chat isn't a welcome. An urgent flood call-out sent by email - which half your volunteers will read that evening, if at all - isn't urgent. The job is to match each of your five message types to the channel that actually suits it, and the broad shape tends to look like this: email for the things people can read at their leisure and might want to keep, WhatsApp for the day-to-day and the community feel, SMS for the genuinely urgent, and in-person for the things that only really work face to face.

I won't try to cram the detail of each channel into this piece, partly because there's genuinely a lot of it and partly because it deserves its own room. The regular news and the impact stories - the newsletter side of things - I've written up separately with a stack of ideas for what to actually put in one. The urgent-and-instant end, WhatsApp and SMS, has its own quirks worth getting right (which list you broadcast to, when a group chat helps and when it's a liability, why the muted-chat problem bites relawan groups especially hard), and that's covered in the piece on using SMS and WhatsApp for member communication. For the plan itself, all you need is the decision: for each message type, which channel, first choice and backup.

The relawan case makes the stakes unusually plain, which is why I like it. For a book club, getting the channel wrong means someone misses a meetup - a shame, not a disaster. For Relawan Sigap, getting the urgent call-out on the wrong channel means fewer hands at the posko when the water's rising, and that's a genuinely different order of problem. So when you're deciding channels, spend most of your thought on the essentials - especially the urgent one - and don't lose sleep over which channel carries the monthly update. If it goes out and people read it, it did its job.

Decide how often, and resist the urge to send more

Frequency is where good intentions do the most damage. The instinct, once you've decided to communicate better, is to communicate more - and more is usually worse, because the fastest way to train someone to ignore you is to message them constantly about things that don't concern them. Every message that wasn't worth their time spends a little of the attention you'll badly need the day you send the one that is. Once someone has quietly filed you under noise, they stop reading the important ones too, and you've engineered your own emergency.

So put a sensible cadence against each message type and then hold the line. For Relawan Sigap that might be: a welcome that goes out within a day or two of someone signing up, a proper update every fortnight to once a month (not more), events announced 2 to 3 weeks ahead with a single reminder a couple of days before, renewal handled once a year over three light touches across 3 to 4 weeks, and urgent call-outs sent only when they're genuinely urgent - which is the whole point of keeping the other channels quiet enough that an urgent message still cuts through. The reserve hundred, especially, want less from you, not more: a monthly update and a clear way back in beats a daily drip they'll mute inside a week.

Say who owns each one

A plan with no name against each line isn't a plan, it's a wish. This is the part groups skip and it's the part that decides whether any of it survives contact with a busy month. If "someone" is meant to send the welcome, no-one does. If the monthly update depends on whichever coordinator happens to feel inspired, it goes out in January, again in March, and never in between. Put a specific person against each message type - not because you're being bureaucratic, but because a named owner is the only thing that reliably turns a good intention into a message that actually goes out.

It doesn't have to be the same person for everything, and it's healthier if it isn't. At Relawan Sigap you might have one coordinator who owns the welcome and intake, another who looks after the fortnightly update, whoever's running a given event owning its announcements, and a clear duty coordinator for urgent call-outs so there's never a moment where a flood alert is waiting on everyone to assume someone else has got it. Spreading the ownership does two things at once: it stops the whole communication life of the group resting on one tired person, and it means each message has someone who genuinely cares whether it went out. That's worth more than any tool.

The plan on one page

Here's the whole thing as a single table, filled in with the Relawan Sigap example so you can see the shape of it. Copy it, swap in your own groups and channels and names, and you've got a communication plan - which most organisations many times your size still don't have written down anywhere.

Don't over-engineer the thing when you fill in your own. Five rows is enough for almost any group, and if you find yourself adding a tenth message type you're probably inventing work rather than describing it. The value isn't in the completeness, it's in the fact that the decisions now exist somewhere other than in one person's head - so a new coordinator can pick it up, so nothing important falls through a gap, and so you can look at it in a quiet moment and notice that, yes, you really are sending your reserve volunteers precisely nothing.

Where these plans go wrong

A few failure modes are common enough to name, so you can catch them early. The first is the one we opened with - drowning the keen and starving the essentials - and it's insidious because it feels like you're communicating a lot, which you are, just at the wrong people. The second is the plan that lives in a document nobody reads: a plan is only worth the behaviour it changes, so if it's not shaping who sends what this week, it's decoration. The third, and the one that quietly kills relawan groups specifically, is never testing the urgent channel until the emergency - discovering at 6am mid-flood that a third of your broadcast list changed their number last year and half muted the group is not the moment you want that news. Send a low-stakes "reply if you got this" call-out once a quarter and you'll find the gaps while they're still cheap to fix.

The last one is the tired coordinator carrying the lot, which no clever plan solves on its own - it's solved by the ownership column above, by genuinely handing pieces of it to different people even when doing it yourself would be faster this week. A group where one person is the entire communication system has a hard ceiling on how big and how durable it can get, and when that person burns out (and they will, quietly, without making a fuss about it), an awful lot goes quiet at once.

Start rough, and improve one line at a time

You do not need to get this perfect before it's useful. A five-row table half-filled and actually followed beats a beautiful communication strategy you're still polishing six months from now. Write down what you're already doing, be honest about the gaps it exposes, fix the most painful one first - for a lot of groups that's the welcome, or the fact that the reserve list never hears a friendly word - and leave the rest for later. This is the same steady, unglamorous work that sits underneath keeping people involved at all, which is why it pairs so closely with the broader ideas for keeping members engaged; a communication plan is really just engagement with the decisions written down. Do the simple version, watch what changes, and add one thing at a time….

A fair bit of this is what Anggota is built to take the friction out of - a proper record of who's in which group so the right message reaches the right people, a welcome that goes out automatically the moment someone signs up, renewal reminders that don't depend on anyone remembering, and one place to reach your volunteers rather than a group chat and a good memory. If that sounds useful you're welcome to try it for free and see how it fits. And if you'd sooner take the framework and run it through whatever you already use - a shared doc, your email tool, the WhatsApp groups you've already got - that's genuinely fine too, because the plan is the valuable part and it works whatever tool carries it.