Washington HOA Notice Rules: Communicating With Homeowners
Email deliverability, what has to go out as official legal notice versus a casual update, whether your state actually accepts email for that notice, and why using a personal Gmail account for HOA business is a quiet liability waiting to surface.
Showing rules for homeowners associations. We haven't researched condominium rules for this state yet.
Washington at a Glance
Owner consent required
Likely the cleanest, most explicit statutory model in the entire dataset. RCW 64.90.515: electronic notice to a unit owner or board member is effective ONLY IF the recipient has consented IN A RECORD to electronic notices and designated the address/system.
"Official notice" and "casual update" are not the same email
Every board sends two kinds of messages, whether or not it thinks about them that way. A newsletter, a maintenance reminder, a heads-up about the pool schedule — none of that has a legal delivery method attached to it. Send it however you like.
An official notice is different. Meeting notices, violation notices, fine notices, assessment and lien notices — these are usually required by your state's HOA statute or by your governing documents, and the method of delivery can determine whether the underlying action is legally valid at all. A fine imposed after a notice that didn't meet the statutory delivery requirement isn't just poorly communicated — it may not be enforceable.
⚠ Common mistake: Assuming that because your board "always emails everyone" and nobody has complained, that practice would hold up if a homeowner actually challenged a fine or a foreclosure. The two situations look identical right up until someone has a reason to contest it — and by then, the notice already went out the way it went out.
Does your state accept email for official notice?
This is genuinely one of the more variable topics in HOA law, and there is no single national answer. Some states require the homeowner to affirmatively consent before email counts. Some only require the homeowner to have designated an email address, with no separate consent step. Some require the association's own bylaws to authorize electronic notice as a method before it's available to anyone. A few states allow email broadly but carve out specific notice types — delinquency, foreclosure, enforcement actions — that must always go out by certified or registered mail regardless. And at least one state treats email as something the association must send in addition to mail, never as a replacement for it.
Washington — Notice-Type Distinctions
The statute expressly says that if another provision prescribes different or additional notice requirements, THOSE REQUIREMENTS GOVERN over the general electronic-notice rule.
Washington — Consent, Revocation & Fallback
Textbook example: consent must be in a record; owner can revoke consent in a record; consent is AUTOMATICALLY REVOKED after two consecutive failed electronic transmissions once the failure becomes known to the responsible person; other notice methods remain available regardless. The older HOA statute (RCW 64.38.110) has the same structure and expressly operates notwithstanding inconsistent governing documents.
Meeting-notice timing, election-ballot mechanics, and violation/fine procedure each have their own state-specific rules covered in the rest of this guide series — this page is specifically about whether the delivery method of email itself satisfies a statutory notice requirement, which is a separate question from how much notice is required or what the notice has to say.
⚠ Common mistake: Confusing a state's electronic MEETING or electronic VOTING statute with an electronic NOTICE-delivery statute. A state that lets a board hold a meeting over video call, or lets an owner cast a ballot electronically, has not necessarily said anything about whether an email satisfies a statutory notice requirement — these are different legal questions, and several states regulate one without regulating the other.
The quiet liability: a personal Gmail account for HOA business
It's the default almost every self-managed board falls into. Someone volunteers as secretary or president, and HOA email just starts flowing through their personal Gmail account because setting up anything else feels like overkill for a volunteer job. It works, right up until it doesn't.
A few ways this actually bites a board later:
- No institutional record. When that board member rotates off, the association's entire communication history — every notice, every reply, every "we discussed this at the meeting" — often leaves with them, because it never lived anywhere but their inbox.
- Personal exposure in a dispute. If a homeowner ever challenges a fine or a board decision, the association's official communications may become discoverable — and if those communications are mixed in with someone's actual personal email, separating the two is its own headache, and the board member's private correspondence can end up more exposed than they expected.
- Deliverability limits that have nothing to do with content. Gmail caps BCC at 100 recipients per message and 500 sends per day. A board that hits that ceiling isn't failing to communicate because of what it wrote — it's failing because of infrastructure it never chose.
- No proof of delivery. If a notice's validity ever depends on when and how it was sent, "I'm pretty sure I emailed it" from a personal account is a much weaker position than a dated, logged send from a dedicated system.
None of this means a volunteer board did anything wrong by starting this way — it's the obvious default. It just means the risk accumulates quietly, and the fix (a dedicated board address that isn't tied to one person's personal account) is small compared to the problem it prevents.
Why HOA emails end up in spam — the short version
When a board asks why half the neighborhood missed the meeting notice, the actual cause is almost never the wording. Mailbox providers decide inbox placement in milliseconds, on signals a sender never sees directly. Three of those signals matter most:
SPF — who's allowed to send
A DNS record listing which servers may send mail for a domain. Without it, a receiving server can't distinguish a legitimate notice from someone forging the sender's address, so it treats both with suspicion.
DKIM — proof it wasn't altered
A cryptographic signature on the message. The receiving server checks it against a published key, confirming the message really came from the claimed domain and arrived unmodified.
DMARC — what to do on failure
A policy telling receiving servers how to handle mail that fails SPF or DKIM, plus reporting on who's sending as that domain. Since February 2024, Gmail and Yahoo have expected bulk senders to publish one.
A volunteer BCC-ing 140 homeowners from a personal Gmail account doesn't have any of these three things in place — not because the board did anything wrong, but because a personal inbox was never built to authenticate itself as an organization's mail. That's a structural gap, not a content problem, and it's worth understanding even if you decide to keep managing communication in-house.
A practical starting point
Whatever tools your board ends up using, a few habits reduce the risk described above regardless of platform:
- Keep board communication in a dedicated address (
board@yourhoa.comor similar) that survives turnover — not a personal inbox that leaves with whoever currently holds it. - Know which of your outgoing messages are statutory notices, and check this guide's state reference before assuming email alone satisfies the requirement for that specific notice type.
- For anything with legal weight — violations, fines, liens — keep a record of exactly when and how it was sent, not just that it was sent.
- Where your state requires certified or registered mail for a specific notice type, don't substitute email even if the homeowner has always been responsive by email in the past — the requirement doesn't bend to convenience.
State-by-State Quick Reference
Select your state below. This reference is specifically about whether email satisfies a statutory notice-delivery requirement — it's a different question from meeting timing, election mechanics, or violation procedure, which are covered elsewhere in this guide series.
| Model Owner consent required | Likely the cleanest, most explicit statutory model in the entire dataset. RCW 64.90.515: electronic notice to a unit owner or board member is effective ONLY IF the recipient has consented IN A RECORD to electronic notices and designated the address/system. |
| Notice-type distinctions | The statute expressly says that if another provision prescribes different or additional notice requirements, THOSE REQUIREMENTS GOVERN over the general electronic-notice rule. |
| Consent, revocation & fallback | Textbook example: consent must be in a record; owner can revoke consent in a record; consent is AUTOMATICALLY REVOKED after two consecutive failed electronic transmissions once the failure becomes known to the responsible person; other notice methods remain available regardless. The older HOA statute (RCW 64.38.110) has the same structure and expressly operates notwithstanding inconsistent governing documents. |
| Citation | RCW 64.90.515 (consent in a record, revocable, two-consecutive-failure automatic revocation); RCW 64.38.110 (parallel provision, older HOAs, overrides inconsistent governing documents) |
One way software helps here
Whatever your state requires, a dedicated board email address and an authenticated sending system solve the deliverability and record-keeping half of this problem — though they don't substitute for knowing which notices your state treats as requiring something more than email. Formtabulous includes board email forwarding and authenticated group sending on every plan.
See how it works →Washington — Common Questions
This article is general information about HOA communication practices and electronic notice statutes, and is not legal advice. Requirements vary significantly by state, by notice type, and by your specific governing documents. Consult a qualified attorney before relying on email as sufficient notice for anything with legal or financial consequences for a homeowner.