Board Communication That Members Actually Read

Ask a board why members are disengaged and you'll usually hear that people don't read anything. Ask members and you'll hear that they never know what's going on.

Both are true, and they're the same problem seen from two directions.

The unofficial channel problem

Most communities have a neighborhood Facebook group, or a Nextdoor presence, or a group text with 60 people on it. None of these were chosen. They accumulated.

The board posts official notices somewhere official, and the actual conversation about those notices happens somewhere else entirely — usually somewhere the board doesn't control, can't archive, and only hears about secondhand when it has gone badly.

You are not going to win that fight by insisting on the official channel. What works is being the fastest source of accurate information. If the board's announcement consistently arrives before the speculation starts, people gradually reorient toward it. If it arrives three days later as a correction, they won't.

Match the channel to the urgency

Using one channel for everything is why people tune out.

| Type | Channel | Why | |---|---|---| | Emergency — pool closed, water shut off, gate broken | SMS | The only channel with near-immediate open rates | | Time-sensitive — meeting tomorrow, registration closes Friday | Email + in-app | Enough lead time to act | | Routine — minutes, newsletters, updates | Email digest | Batched so it doesn't dilute the urgent stuff | | Reference — rules, bylaws, forms, contacts | Website | Findable later without searching an inbox |

The failure mode is texting people about the newsletter. Do that twice and your emergency messages get muted along with everything else.

Write for someone reading on a phone, in a hurry

Community announcements are read standing in a kitchen with a child asking for something. Write accordingly:

• Lead with the decision or the action. Not the background. The board's deliberation process is interesting to the board.
• Put the date and the ask in the first two lines.
• One topic per message. Bundling five things guarantees four go unread.
• Use a subject line that says what happened. "Pool closed Saturday for repairs" beats "Community Update — July."
• Say what it costs them. People skim for impact on their own week.

Compare:

Following the Board's regular meeting on the 14th, and after review of three vendor proposals received in response to our RFP, the Board voted to approve the resurfacing of the tennis courts…

Courts closed August 4–15 for resurfacing. The board approved the work at the July meeting. Pickleball lines are being added. Details below.

Same information. The second one gets read.

Pick a cadence and hold it

Communities that send unpredictably train members to ignore them, because nothing is ever expected. A regular monthly digest on a fixed date — the first Monday, say — plus urgent messages as needed, works better than sporadic bursts.

Predictability also protects your urgent channel. If members know the routine stuff arrives on a schedule, an off-schedule message reads as genuinely important.

Keep the list clean

The single most common cause of "we told everyone" turning out to be false is a distribution list that hasn't been maintained. Households sell, emails change, new families move in and nobody adds them.

Make roster maintenance somebody's actual job. Ideally, make it a byproduct of something that already happens — pool registration, dues renewal — so it can't silently rot.

Close the loop on decisions

The complaint underneath most engagement problems isn't the decision. It's learning about it after the fact.

Publish the agenda before the meeting, publish the decisions after, and when something is genuinely divisive, say what the disagreement was. Boards under-communicate on contested items precisely when transparency matters most — and the resulting vacuum gets filled by the Facebook group, uncharitably.

---

Gather Commons gives boards email and SMS announcements, a public site for reference material, and a member directory that stays current because it's attached to the things members already do. See how it fits together or what it costs.