CC&R enforcement and violation letters — a process that survives an angry lawyer

Every enforcement action traces to a specific provision — cite the CC&R article and section in every notice, because an unciteable violation is an opinion. Check that the rule was validly adopted (some rules require a recorded amendment, not just a board vote), that your state's notice-and-hearing requirements are met, and that the association has enforced this rule before — selective enforcement, where the board fines the fence it dislikes and ignores the three it likes, is the most common defense that actually works.

Four rungs, each with a cure period. First, the courtesy notice: friendly, factual, cites the provision, states what compliance looks like and by when — most violations end here, and the tone of this letter sets whether the rest of the process is administrative or adversarial. Second, the formal notice of violation: the same facts, a firmer frame, the fine schedule that applies if uncured, and the owner's right to a hearing. Third, the hearing and fine: most states require the opportunity to be heard before a fine is levied — the board hears the owner, decides, and communicates the decision in writing. Fourth, escalation beyond fines: suspension of privileges where the documents allow, then counsel — at which point the file you built is the case.

Cure periods should be stated in days, on the letter, and honored to the day. A ladder the board skips rungs on is worse than no ladder, because it documents inconsistency.

The property address and date of observation. A factual description of the condition — “trailer parked in driveway since at least July 12,” not “eyesore.” The specific CC&R or rule provision, quoted or cited by section. What compliance looks like, concretely. The deadline to cure, in days and as a date. What happens next if uncured, including the fine amounts from the adopted schedule. How to respond or request a hearing, and who to contact. Photographs attached, dated. Nothing else: no editorializing, no history of the neighbor dispute, no adjectives a lawyer can read aloud sarcastically.

Fines must come from a published schedule adopted by the board and distributed to owners — an amount invented per incident is the second most common way a fine dies. Keep amounts modest and escalating; the goal of the process is cure, and a fine is the process failing profitably.

For every violation: the photos with dates, every notice sent with the date it was sent and how, the owner's responses, the hearing record and decision, and the cure date or the fine ledger. Attached to the home, not to the volunteer — the test is whether a board elected three years from now can reconstruct the whole file without phoning anyone. A folder of Word documents named FinalNotice2_REVISED fails this test the day the secretary moves.

Architectural review requests belong in the same system for the same reason: an approval granted by email in 2024 is the defense to a violation letter in 2027, provided anyone can find it.

The GatherAMS HOA edition runs this exact process as a queue: violations logged against the home with photo evidence and a category, notices that escalate on the ladder with the cure date tracked, every letter stored against the address, fines posting to the home's ledger, and ARC requests routed to a recorded board decision. The letters are yours — the system's contribution is that nothing about the process depends on which volunteer is running it. The live demo HOA has a seeded violations queue you can walk through before believing any of this.