How to Manage HOA Dues, Violations, and Communications

An HOA without process becomes a lawsuit waiting to happen. The board that runs violations on text-message gut-feel is the board that loses the small claims case in March, the one where the homeowner's attorney shows up with a binder of CC&R sections you've enforced inconsistently for six years. Dues are paid late because nobody bothered to set up autopay. Violation notices go out from the property manager's personal email and get lost. The ARC committee approves a fence color in February and denies the same color in August because nobody wrote down what was decided. The reserve fund is an Excel sheet on the treasurer's laptop that hasn't been backed up since 2024.

The job of HOA management software is not to make any of this exciting. It is to make it boring. Predictable. Defensible in court. The community that runs on documented process — autopay for dues, photo-evidenced violation notices with timestamps, ARC applications with neighbor notification, a real homeowner portal — is the community where the board sleeps at night and the homeowners actually trust the people running the place.

This is the playbook. Five steps, end to end, for running dues, violations, ARC, communications, and vendors without writing a check to a litigator.

Dues are the easiest fight to avoid and the one most boards lose. The fix is structural: every homeowner gets autopay enrollment as the default at closing, with a paper opt-out for the holdouts who insist on mailing checks. Autopay collects on the 1st, late fees attach on the 11th, and the late fee amount is whatever your CC&Rs say — not whatever the treasurer feels like that month. If the CC&Rs say $25 or 10% of the unpaid balance, that is the number, and it goes in the platform as a configured rule, not a judgment call.

The lien process is governed by state law, and it varies. California requires a pre-lien notice 30 days before recording. Texas allows assessment liens but requires specific notice language under the Texas Property Code. Florida's Chapter 720 has its own escalation timeline. Build the lien workflow once, in writing, with the exact notice templates your attorney has approved, and run every delinquent account through the same sequence: 30-day notice, 60-day notice, intent-to-lien, recorded lien, collection. Same letters, same timing, every time. Inconsistent enforcement is the single fastest way to lose in court — a homeowner's attorney does not need to prove their client paid on time, only that you went after them harder than you went after Mrs. Henderson on the corner lot.

In Deelo, the dues record lives on the homeowner's CRM contact, with a payment history, autopay status, and current balance. The Automation app fires the 30/60/90-day notices on schedule. Late fees post automatically per the CC&R-defined rule. The Invoicing app produces the statement. There is no separate spreadsheet, no separate lien tracker, no separate email thread.

Every violation that ends up in litigation has the same fact pattern: inconsistent enforcement, no photo evidence, no documented escalation, and a notice the homeowner says they never received. Fix all four with one workflow.

The sequence is non-negotiable: courtesy notice (no fine, 14 days to cure), second notice (small fine, 14 more days, hearing offered), formal fine (if uncured, with hearing rights notice in the language your state requires), board hearing (homeowner gets to speak before further fines stack), continuing violation fines (per-day or per-week if your CC&Rs allow), and finally referral to legal counsel for injunction or lien. Photo evidence at every step — geotagged, timestamped, captured by the property manager or roving inspector, attached to the violation record in the platform. A trash can left out for a week is documented with seven daily photos, not one.

Escalation cadence matters because it proves you treated this homeowner the same as the next. Configure the violation workflow once: Day 0 inspection finds the issue, Day 1 courtesy notice goes out via email and certified mail, Day 15 second notice with $50 fine, Day 29 formal $100 fine and hearing offer, Day 45 board hearing, Day 60 continuing $25/day until cured. Same cadence for the trampoline-in-the-front-yard violation as for the unapproved paint color. Your attorney will thank you. The judge will too. In Deelo, the violation record sits on the homeowner's CRM contact, photos attach to the record, the Automation app fires each escalation notice on the right day, and the Docs app generates the certified-mail-ready PDF with the right CC&R citation.

The Architectural Review Committee is where most boards quietly get sloppy. A homeowner emails a paint chip to a board member, the board member texts the committee chair, the committee chair forgets, six weeks pass, the homeowner paints anyway, and now you have a violation that started as an approval delay your own committee caused. Then the next homeowner submits the exact same paint color and gets denied because Susan on the committee has changed her mind.

Fix this with a real ARC application form, a real review queue, and a real decision log. Every request — paint color, fence material, roof type, landscaping change, solar panel installation, satellite dish, addition, deck — submits through the same intake form with photos, dimensions, materials, contractor info, and proposed start date. The form goes into a queue with a documented review SLA (most CC&Rs require 30-45 days; some states impose statutory limits). Neighbor notification, where required, fires automatically to adjacent lots with comment windows. The committee meets, votes, and the decision plus reasoning is logged on the application. Approved applications include any conditions ('approved subject to matching the existing roof shingle within Sherwin-Williams 6082-6085 range'). Denied applications cite the specific CC&R section and architectural guideline.

And — critically — the decision log is searchable. Next time someone asks for Sherwin-Williams 6082, you can pull every prior approval and denial of that color in 30 seconds. That is what consistency looks like in court. In Deelo, ARC applications are a custom CRM record with photo attachments, a review pipeline with stages (submitted, under review, neighbor notification, board vote, decided), and the Automation app fires the SLA reminder on Day 25 to the committee chair if the application is still open.

If homeowners do not have a self-service portal, the board does not have a CRM — it has a switchboard. Every payment question, statement request, work order, and pool-key reissue becomes a phone call to the property manager. The portal solves this: one login, all the things.

A functional homeowner portal includes statement and payment history (download last 24 months as PDF), autopay management, work order requests with photo upload (sprinkler broken at 1432 Maple, photo attached, routed to the landscaping vendor), ARC application submission and status tracking, document library with the CC&Rs, bylaws, current budget, reserve study, board meeting minutes, and the violation history for that homeowner's lot. Newsletter delivery and emergency notifications flow through the same system — pool closure for chemical balance, water shutoff notice from the city, board meeting agenda 72 hours before the meeting (required by sunshine laws in most states).

Emergency notifications need a different channel than the monthly newsletter. SMS for urgent — 'Mandatory boil-water notice in effect, see attached.' Email for routine — 'Holiday lighting guidelines reminder.' Both logged on the homeowner's record so when somebody claims they never got the notice, you can pull the delivery receipt. In Deelo, the portal is a CRM-linked client portal, the document library is the Docs app, work orders route to the Field Service app, and the broadcast goes through the Automation app's email and SMS nodes with delivery tracking.

The board does not run the pool. The pool company runs the pool. The board's job is to choose the right pool company, hold them accountable to the contract, and rotate to a new one when the current one stops returning calls. Same for landscaping, security patrol, gate access, elevator service, roof inspection, irrigation, pest control, snow removal, and any of the twenty other vendors a typical community runs.

Vendor management has four moving pieces: contracts with renewal dates and insurance certificate expirations (W-9, COI, license, bond — all on file, all tracked for expiration), work orders generated from homeowner requests or scheduled maintenance, invoices reconciled against actual completed work (not just submitted), and the RFP cycle when a contract is up. The board that runs an annual RFP for the landscaping contract gets a 15-30% better price most years. The board that auto-renews because nobody put it on the calendar is the board paying $80,000 for $60,000 of work.

Reserve fund tracking lives next to vendor management because every major component — roof, paving, pool resurfacing, painting — has a useful life and a replacement cost in the reserve study. The reserve study gets updated every 3-5 years (some states require it). Component-level tracking means you know that the pool was resurfaced in 2019 with a 10-year useful life, so it goes in the 2029 capital budget, not as a surprise special assessment in 2027. In Deelo, vendors are CRM contacts with custom fields for COI expiration, work orders are Field Service tickets, contracts and reserve studies are Docs records with renewal date custom fields, and the Automation app pings the board 60 days before any contract or COI expires.