Boards routinely discover, at an annual meeting, that owners had no idea about a project that was announced three times. The board is frustrated — it was in the newsletter. The owners are frustrated — nobody told us.
Both are right. It was sent, and it was not received. Those are different things, and the gap between them causes a large share of the conflict in community associations.
The quarterly newsletter problem
The standard association newsletter fails in a specific way: it batches everything into one long document at a cadence too slow to be useful. A pool closure announced in a March newsletter is forgotten by the June closure. Urgent items arrive alongside trivia, so owners learn the document has a low hit rate and stop opening it.
Worse, quarterly timing means genuinely time-sensitive information either waits — becoming useless — or goes out separately, which trains owners that the important things come by other channels anyway.
Sort communications by what they need to do
Most association messages fall into three types, and they need different handling.
Urgent and operational. Water shutoff tomorrow, gate is broken, snow removal tonight, move your car. Needs to arrive within hours and be read immediately. Short, single-subject, sent by text or email with an unmissable subject line. Never bundled with anything else.
Scheduled and procedural. Meeting notices, budget adoption, assessment changes, annual meeting and elections. Statutory timing requirements often apply. These need a reliable, documented channel — and repetition, because the first notice will be missed by many.
Contextual. Project updates, seasonal reminders, welcome notes, an explanation of why the landscaping contract changed. This is what a newsletter is genuinely good for, and it is fine at a slower cadence because nothing depends on same-day receipt.
The common failure is putting all three in one document at the cadence of the third.
Frequency
Monthly beats quarterly for the contextual layer. It is short enough to write consistently and frequent enough that owners develop a habit. Operational messages go out as needed — but ration them, because an association that emails constantly gets filtered.
A workable rhythm: one short monthly update, statutory notices on their required schedule, and urgent messages only when genuinely urgent.
Format
A few things reliably improve whether a message is read:
- Say the thing in the subject line. "Water shut off Tuesday 9am–2pm, Buildings C and D" outperforms "Important community update" by an enormous margin.
- Put the action in the first sentence. Owners scan. If what they must do is in paragraph four, it is not read.
- One message, one subject. Bundling a pool closure with a reminder about trash cans means half the readers absorb one and miss the other.
- Keep it short. Four sentences read completely is better than four hundred words skimmed.
- Write plainly. "Per Article 12.4 of the Declaration, the Board has resolved to undertake remediation" is worse in every respect than "We are repairing the retaining wall behind Building B starting 3 March."
Channel, and the one that still works
Email reaches most owners and creates a record, which matters for notices. But addresses go stale — owners change jobs, inherit an address from a prior owner’s records, or route association mail to a folder they never open. Audit your list annually against ownership records.
Text works for genuinely urgent operational messages and has far higher immediate read rates. It requires opt-in and should be reserved strictly for urgency; the moment it becomes routine, people opt out.
The portal is where things should live — documents, minutes, the archive of past notices. It is not a push channel. Nobody logs in to check for news.
And physical posting still works better than boards expect. A laminated notice at the mailboxes, the gate, and the clubhouse reaches the owners your email list has lost, and it reaches renters who are frequently not on the list at all.
Renters
In communities with meaningful rental occupancy, the association often communicates only with owners, many of whom do not live there. The people who need to know about the water shutoff are the tenants.
Where governing documents permit, maintain tenant contact information through a registration requirement, and send operational notices to residents as well as owners. Governance and financial matters still go to owners; operational ones should reach whoever is actually in the building.
A test worth running
At the next annual meeting, ask for a show of hands: who read the last monthly update? It is uncomfortable and genuinely informative. If a quarter of the room raises a hand, the problem is not that owners are disengaged — it is that the communications are not landing, and that is fixable.
Written by the management team at Premier Property Management. General information for Utah community associations — not legal, tax, or insurance advice for your association.