Ask any nonprofit committee coordinator what eats up their week, and "keeping everyone informed" rarely tops the list of official responsibilities, but it quietly consumes more time than almost anything else. A decision gets made in a meeting three volunteers missed. A deadline moves and half the committee finds out, half doesn't. Someone asks a question in the group text that was already answered two weeks ago in a different thread.
None of this is anyone's fault, exactly. It's what happens when a committee's "communication system" is really just whatever channel felt convenient in the moment: email, a group text, a Facebook group, word of mouth at the last meeting. Each one works fine on its own. The problem is that none of them are the one place everyone knows to check.
Why communication quietly breaks down as committees grow
In a five-person committee that's been together for years, this mostly doesn't matter. Everyone already knows everyone, informal channels work, and gaps get filled in naturally at the next meeting. The trouble starts as a committee gets bigger, turns over volunteers more often, or takes on more going on at once.
A few patterns show up almost every time:
- Information lives with whoever remembers to share it. If the coordinator forgets to forward an update, or a volunteer misses the one meeting where something was announced, there's no backup. The information just doesn't reach them.
- New volunteers start from zero. Someone who joins mid-project has no way to catch up on what's already been communicated, short of asking around and hoping someone remembers to fill them in.
- Urgent and routine look identical. A reminder about snacks for Saturday and "the venue fell through, we need a new plan by Friday" often arrive in the same inbox, in the same font, with the same level of visual urgency, which is to say, none.
- The coordinator becomes a single point of failure. When there's no shared record, the coordinator ends up as the de facto keeper of institutional memory, repeating the same updates to different people at different times.
None of these are communication failures in the sense of anyone doing anything wrong. They're structural: a predictable result of communicating through channels that were never designed to be a shared, persistent record.
Push communication vs. a place people can check
Most committees rely almost entirely on push communication: emails, texts, and messages sent out and hoped for the best. Push communication has a hidden assumption baked in: that the recipient was paying attention at the exact moment it arrived, in the right inbox, and didn't miss it in the noise.
The alternative isn't more push. It's giving your committee a pull option too: one stable place volunteers already know to check, where the current, important information lives whether or not they saw it the moment it was posted. Push gets something in front of people quickly. Pull makes sure it's still findable a week later, or for someone who joined after it was sent.
Healthy committee communication uses both, but most struggling committees are relying on push alone, and wondering why things keep falling through the cracks.
What a good "pull" channel actually needs
It doesn't have to be complicated, and it doesn't need to be another app volunteers have to remember to open. But whatever it is, it needs a few specific properties to actually solve the problem:
- One canonical location. Not a pinned post in one of four group chats: a single place that's understood, organization-wide, to be where official updates live.
- Priority signaling. A way to tell "FYI, no action needed" apart from "urgent, please respond" at a glance, without reading the whole message first.
- Persistence. Updates should still be there next week, next month, and for whoever joins the committee six months from now, not scrolled past and gone.
- Low friction to check. If checking it takes more effort than just asking the coordinator directly, volunteers will keep asking the coordinator directly, and the system won't get used.
A quick gut check: if a new volunteer joined your committee today, could they find out what's happened in the last month, decisions made, deadlines that moved, anything important, without tracking someone down and asking? If the honest answer is no, that's the gap worth closing first.
Email threads vs. a shared announcements system
| Email / Group Text | Shared Announcements | |
|---|---|---|
| Reaches new volunteers | No, starts from zero | Yes, visible history |
| Urgency is visible | Not really, everything looks the same | Yes, if flagged by priority |
| Findable later | Buried in scrollback | Stays put, searchable |
| Coordinator burden | High, often re-explains in person | Lower, post once, it stays visible |
| Best fit | Time-sensitive, one-off pings | Anything worth remembering |
The two aren't actually in competition. A well-run committee still uses quick messages for genuinely time-sensitive pings. The mistake is using push channels for everything, including the things that need to stick around and be findable later.
A few practical habits, regardless of what tool you use
You don't need new software to get most of the way there. A shared document, a pinned note, or a simple bulletin can work if the habits around it are solid:
- Pin what actually matters. If everything is pinned, nothing is. Reserve it for decisions, deadline changes, and anything a volunteer would be upset to have missed.
- Use a real priority label, not just tone. "Normal," "important," and "urgent" (or similar) let people triage without reading every word first.
- Post decisions where they were made, not just verbally at the meeting. If it only exists in the heads of whoever attended, it doesn't exist for anyone else.
- Resist the urge to over-communicate. A channel that posts constantly trains people to stop checking it. Reserve it for things worth their attention.
- Make the first stop for new volunteers "go read the last month of updates," not "someone will fill you in eventually."
This is exactly the gap we built the announcements feature in ComitySpace to close: a pinned, priority-flagged space that lives right on every volunteer's dashboard, so updates don't depend on who happened to see an email at the right moment. But the underlying habit matters more than the specific tool: give your committee one place they can trust is current, and a lot of the "why didn't anyone tell me" friction quietly disappears on its own.
Communication problems on a committee rarely look like communication problems from the inside. They look like missed deadlines, repeated questions, and volunteers who feel a step behind. Usually, the fix isn't more messages. It's making sure the important ones have somewhere to live.