Somewhere right now, an HOA management company is demoing software that promises to send violation notices, assessment letters, and lien warnings automatically—no manager review required. It looks efficient. It probably is, right up until an auto-generated pre-lien notice goes out with the wrong amount owed, a cure date that doesn't satisfy the statutory minimum, or a missing required disclosure. At that point, "efficient" becomes a legal defect, and the management company owns it.
What Davis-Stirling actually requires before you send that letter
The Davis-Stirling Common Interest Development Act isn't vague about owner communications. Specific letter types carry specific, mandatory requirements—and getting them wrong doesn't just create an angry homeowner. It can void the action entirely.
Consider the pre-lien notice under Civil Code §5660. Before an association can record a lien for delinquent assessments, it must send a written notice by certified mail that includes: the amount of the delinquency, a breakdown of amounts owed (including interest, collection costs, and attorney's fees), the method of calculation, the right to dispute under §5665, and an offer to participate in the association's payment plan. Miss any element, miscalculate the figure, or send to the wrong address of record, and the lien is legally defective.
The disciplinary hearing process under Civil Code §5855 requires written notice to the member no less than 10 days before any hearing that could result in a fine or suspension of privileges. That notice must state the nature of the alleged violation, the date, time, and location of the hearing, and the member's right to attend and be heard.
An AI system pulling from an account ledger that hasn't been reconciled, or applying a template that hasn't been updated after a statutory amendment, will produce a letter that looks correct and is legally wrong. Auto-send means that letter is already in the homeowner's mailbox before anyone finds out.
The specific failure modes that create liability
Auto-send AI tools fail in predictable ways that human review catches in seconds. The risk isn't that AI drafts are bad—it's that errors compound silently when there's no checkpoint.
| Failure Mode | Auto-Send Outcome | Human-in-the-Loop Outcome | |---|---|---| | Ledger not yet reconciled; balance overstated | §5660 notice sent with wrong amount; lien defective | Manager flags discrepancy, holds notice pending reconciliation | | Cure period template uses 10 days; ordinance requires 14 | Violation notice legally insufficient | Manager catches date, corrects before send | | Homeowner's mailing address updated in portal but not synced to letter queue | Notice sent to old address; no valid delivery | Manager confirms address of record before approving | | Association amended its fine schedule; AI still using prior version | Wrong fine amount stated; creates estoppel exposure | Manager references current schedule, updates draft | | Pre-lien notice missing payment plan offer required by §5665 | Notice fatally defective; lien unenforceable | Manager checks disclosure checklist, adds required language |
Each of these is a real scenario. Industry forums have documented auto-sent lien notices where the certified amount didn't match the ledger, where cure periods were miscalculated, and where required offers of internal dispute resolution were absent. In each case, the management company had to either re-send corrected notices (restarting statutory timelines), counsel the association to abandon the collection action, or defend a claim.
Human approval isn't friction — it's the compliance layer
The proptech HOA compliance conversation often frames manager review as the bottleneck that automation is meant to eliminate. That framing is backwards for any communication with legal consequence.
Human approval on a §5660 pre-lien notice is not friction any more than a surgeon confirming the correct surgical site is friction. It is the verification step that makes the prior work valid. The AI drafting the notice is doing real work—pulling account data, structuring the disclosure, formatting the letter, routing it to the right queue. That part should be automated. The approval is where a licensed or credentialed manager confirms that the output is accurate, complete, and legally sufficient before it carries the association's authority.
This is the meaningful distinction between AI HOA management software that augments manager judgment and software that replaces it. Replacing judgment on ministerial tasks (scheduling reminders, categorizing emails, generating routine reports) is appropriate and low-risk. Replacing judgment on legally consequential owner communications is not a feature. It's a liability transfer to the management company.
When a letter goes out under auto-send and contains a defect, the question isn't whether the AI made a mistake. The question is why there was no human review on a document with statutory requirements. That answer is hard to defend to a client board, to an attorney, or to a court.
What a governed AI drafting workflow actually looks like
An approval-gated workflow doesn't mean managers type every letter from scratch. It means AI does the drafting and humans do the certifying.
In practice, a governed workflow for a §5660 pre-lien notice looks like this:
- Trigger: Account reaches delinquency threshold after the pre-collection demand process under §5650 has been satisfied.
- AI draft generation: System pulls current ledger balance, itemizes assessments, interest, and fees, applies the association's collection policy, and populates the §5660 disclosure template including the §5665 payment plan offer.
- Manager review queue: Draft is routed to the assigned manager with a checklist: balance confirmed against reconciled ledger, mailing address verified against address of record, cure period compliant with governing documents and statute, all required disclosures present.
- Approval and send: Manager approves, system logs the approving manager, timestamp, and document version. Letter generates to certified mail queue.
- Audit trail: Full record retained at the HOA level—who drafted, who approved, what version was sent, when.
This workflow is faster than drafting manually. It is not slower than auto-send in any way that matters. The manager review step on a well-structured AI draft takes two to four minutes. The legal exposure avoided is not measurable in minutes.
For HOA automation risk management, the audit trail element is underappreciated. When a homeowner disputes a lien six months later, the management company can produce the exact document sent, the manager who approved it, and the checklist confirmations that accompanied approval. That record is the difference between a defensible position and a credibility problem.
What to do now
-
Audit your current communication workflows. Identify every letter type your software can send automatically. For each one, determine whether it has statutory requirements under Davis-Stirling or your governing documents. Any letter with legal consequence should have a human approval gate—no exceptions.
-
Build a disclosure checklist for your highest-risk letter types. At minimum: §5660 pre-lien notices, §5855 disciplinary hearing notices, assessment increase notifications under §5615, and any communication that cites a specific dollar amount owed. The checklist should be part of the approval workflow, not optional.
-
Verify that your AI drafting tool operates at the HOA level. Each community's data—ledger balances, governing documents, fine schedules, owner address records—should be scoped to that community. Cross-community data bleed in AI-generated letters is a real failure mode in platforms that don't enforce HOA-level data boundaries.
-
Evaluate software vendors on approval workflow design, not just automation depth. When demoing AI HOA management software, ask specifically: where does the human approval step occur, what does the manager see at review, and what is logged when approval is given? A vendor that treats approval as optional or positions it as a setting to turn off is telling you something important about their liability model.
-
Document your policy. Put in writing that your management company requires human approval on all legally consequential owner communications. This is a professional standard position, and it belongs in your operations manual, your client contracts, and your onboarding materials for new managers.