Enforcement & Violations · Rules & Regulations
Rules and Regulations in Practice
Rules are the board’s most-used governance tool and, by a wide margin, its most lawsuit-generating one. The first time a homeowner sues an association, it is more often over a rule than over an assessment, an insurance decision, or a contract. This article works through the rule lifecycle the way it actually happens — adopting a new one, enforcing an existing one, recognizing one that overreaches, and defending one a homeowner says was never properly published.
The Bottom Line
The board can adopt and change Rules and Regulations by board action — generally without a membership vote — but only within the bounds the Declaration sets. A rule lives at the second-to-lowest tier of the governance hierarchy: it can implement the Declaration or fill a genuine gap, but it can never amend, contradict, or expand the Declaration. A rule that tries to do so is ultra vires — beyond the board’s authority — and is, in practical terms, no rule at all. And even a substantively valid rule fails in court if the board enforced it selectively or never published it before enforcing it. This piece is the application companion to The Limits of Board Rulemaking: that article explains the doctrine; this one shows the doctrine running in the real world, scenario by scenario.
The Diagnostic Question: “Where Does This Come From?”
Before a board adopts a rule or enforces one, it should be able to answer a single question CIC-SC teaches as the master diagnostic: where does this come from? If the answer is the recorded Declaration, the board is enforcing a covenant that runs with the land and was priced into every purchase. If the answer is “a board resolution from 2019,” the board is enforcing a rule — valid only if it implements the Declaration or fills a genuine gap, and only if it survives the ten enforceability criteria below.
Rules and Regulations are the day-to-day layer of governance: pool hours, parking, pets, trash placement, architectural standards, noise, holiday lighting, sign placement. The Declaration grants the board authority to adopt them. What the Declaration does not grant, the board cannot create by rule. That single sentence resolves the majority of the disputes that follow.
Scenario 1 — The Board Wants a New Rule
A board faces a new community problem: cut-through parking has made the private streets a hazard. Or owners have started listing units for weekend stays. Or the first electric-vehicle owner wants to run a charging line across a common-area wall. Or a resident is flying a camera drone over backyards. In each case the board’s instinct is right — adopt a rule — but the instinct has to run through a fixed sequence, and the very first step is the one boards most often skip.
Step zero: confirm authority before drafting anything.
For an established topic — pool hours, trash placement — the Declaration almost certainly grants rule-making authority and the authority question is easy. For a new topic — short-term rentals, EV charging, drone use — confirming authority is the single most important step in the entire process. The board must pull the recorded Declaration and confirm it grants rule-making authority over the subject. If the Declaration is silent on the underlying right, a rule restricting that right may be an attempt to amend the Declaration by board action — which the board cannot do.
The seven-step adoption sequence.
The mechanics are not complicated, but they must be followed in order. Skipping a step is precisely how an enforceable rule becomes an unenforceable one.
The rule-adoption sequence (Book 1, Figure 1.3). Steps 1, 6, and 7 are the ones that decide enforcement lawsuits.
A drafting discipline that wins.
At Step 2, draft the operative text so an ordinary owner can know what is expected and an enforcer can apply it evenly. Avoid words like “reasonable” and “appropriate” in the operative language — those are the words that lose lawsuits, because they hand a judge the discretion to decide the board acted arbitrarily. A parking rule that says “no parking that creates an unreasonable hazard” is far weaker than one that says “no parking on the painted fire lane or within 15 feet of a hydrant.”
Scenario 2 — Enforcing an Existing Rule
A homeowner is in violation of an adopted rule — say, the new fire-lane parking rule from Scenario 1. Before the board issues a notice, it should run the rule through the ten enforceability criteria as a live checklist. These criteria, distilled from Hyatt and Stubblefield’s Community Association Law treatise across decades of enforcement litigation, are the test a court will apply. Missing any one of the ten creates an opening for a homeowner challenge.
The ten enforceability criteria (Book 1, § 1.7.1). The two cream cells — uniform application and prior written communication — are where most enforcement cases are actually lost.
Running the fire-lane rule through the grid: it was adopted under the Declaration’s parking-rule authority (1, 2), it addresses a genuine safety hazard and is narrowly drawn to the fire lane (3, 4), it went through a noticed open meeting (6), it was published with an effective date (7), and it conflicts with no statute and targets no individual (8, 9, 10). The only live question is criterion 5 — uniformity. That is the question the board must answer before sending a single notice, and it is the subject of Scenario 4.
Scenario 3 — A Rule That Overreaches
A board, frustrated by a few problem tenants, votes to adopt a rule: “No unit may be leased.” The Declaration says nothing about leasing one way or the other — it neither permits nor restricts it. Separately, a different board adopts a rule banning all pets, in a community whose Declaration expressly permits one dog or cat per home. Both boards believe they are acting within the day-to-day rule-making power. Both are wrong, and in the same way.
The right move.
If the board genuinely needs a leasing or pet restriction, the path is not a board vote on a rule — it is a members’ vote to amend the Declaration. The board proposes; the owners decide at the threshold the Declaration sets (commonly two-thirds or three-quarters of the voting interests), and the amendment is then recorded. A board that adopts the restriction as a “rule” to avoid the harder member-vote path has not saved time; it has manufactured a lawsuit it will lose. See The Limits of Board Rulemaking for the doctrinal line between a rule and an amendment, and The Declaration (CC&Rs) in Practice for the amendment mechanics.
Scenario 4 — A Homeowner Challenges the Fine: “The Rule Was Never Published”
The board fines an owner for a violation. The owner appears at the hearing and argues not that the conduct didn’t happen, but that the rule was never properly published — they say they never received written notice of it, and the board cannot produce a record showing the rule was distributed to owners with an effective date. This is criterion 7, and it is a complete defense if the owner is right.
A rule must be communicated to all owners in writing before enforcement begins. A rule sitting in a binder in the management office, or buried in minutes no owner ever received, has not been published. The right move is preventive: the secretary’s file should contain proof of publication — the dated mailing, email blast, or portal posting, with the effective date stated — for every rule the board intends to enforce. If that proof does not exist, the board should re-publish the rule, set a forward effective date, and pursue only violations occurring after that date. It cannot retroactively cure the publication defect for the existing fine.
The parallel defect is selective enforcement (criterion 5), and it is the single most reliable way for an association to lose a rule-enforcement lawsuit: the board cited the owner who complained and ignored three others committing the same violation over the past year. The prevention is mechanical. Before any enforcement action, have the manager pull a violation history for that rule across the entire community for the trailing 12 months. If enforcement has been inconsistent, fix the inconsistency first — by noticing the others, or by adopting a clean go-forward enforcement date — before pursuing the new violation. A consistently published rule with a clean enforcement history is a fine that sticks; a selectively enforced one is a fine waiting to be reversed. See Selective Enforcement Voids a Valid Rule.
Texas: The Statutory Overlay
Presumption of reasonableness — § 202.004.
Texas Property Code Chapter 202 governs the construction and enforcement of restrictive covenants, and § 202.004 provides that a restrictive covenant is presumed reasonable, and an exercise of discretionary authority by a property owners’ association concerning a restrictive covenant is presumed reasonable unless the court determines it was arbitrary, capricious, or discriminatory. This presumption is a meaningful advantage — but it attaches to a properly adopted, properly authorized restriction. It does not rescue an ultra vires rule, and it does not cure selective enforcement; criteria 2, 5, and 9 still control.
Open meetings — § 209.0051.
The meeting at which a rule is adopted must comply with the open-meeting framework of § 209.0051: posted notice in advance, the meeting open to members, and a recorded vote. A rule adopted at an improperly noticed meeting is procedurally defective under criterion 6 before its content is ever examined.
Notice and a hearing before enforcement — §§ 209.006 and 209.0064.
Before the association may charge a fine or pursue enforcement, § 209.006 requires written notice describing the violation, stating the amount of any proposed fine, and informing the owner of the right to request a hearing. The owner is entitled to a cure period — under § 209.0064 the relevant cure window is 45 days, not 30. Enforcing a valid rule without delivering this notice and honoring the cure period is a due-process failure that voids the enforcement regardless of how sound the rule is.
Florida: The Statutory Overlay
HOAs — § 720.305.
Florida Statutes § 720.305 authorizes fines and suspensions for rule violations but conditions them on process: the fine may not be imposed without first giving the parcel owner at least 14 days’ written notice and an opportunity for a hearing before an independent committee of other owners who are not officers, directors, or employees, or their relatives. If the committee does not approve the fine, it cannot be levied. Rule adoption and meeting notice obligations sit in § 720.303, which also governs the meetings at which board action — including rule adoption — is taken.
Condominiums — § 718.303 and § 718.112.
For condominiums, § 718.303 imposes the parallel fine-and-hearing structure: a fine or suspension may not be imposed without at least 14 days’ notice and a hearing before a committee of unit owners who are not board members or their relatives, and the committee must agree before the fine is levied. The board’s authority to adopt rules — and the limit that rules regulating unit use must be reasonable and within the bounds of the Declaration — runs through § 718.112 and the recorded Declaration. As in Texas, a Florida board cannot use a rule to impose a use restriction the Declaration reserves to a members’ amendment.
Why Rules Generate the Most Lawsuits
Rules touch every owner’s daily life, which is why they are litigated more than any other governance act. The pattern in the case law is consistent: associations rarely lose because the underlying concern was illegitimate. They lose because a step in the lifecycle was skipped — authority was never confirmed, the rule overreached the Declaration, it was never published, or it was enforced against one owner and not the next. Every one of those is a process failure, and every one is preventable with a checklist run before the board acts. The discipline is unforgiving but simple: adopt within authority, in the open, on the record; publish before you enforce; and enforce everyone the same.
Key Takeaways
- Rules change by board action — but only within the Declaration’s bounds. The board can amend the rulebook; it cannot amend the Declaration through the rulebook.
- Confirm authority before drafting. For new topics — short-term rentals, EV charging, drone use — the “where does this come from?” question is the most important step in the whole sequence.
- Run the seven-step adoption sequence in order. Identify and confirm authority, draft, notice, hold the open meeting, adopt by recorded vote, publish with an effective date, apply uniformly. Skipping a step is how an enforceable rule becomes unenforceable.
- Treat the ten criteria as a live checklist before enforcing. Missing any one creates an opening for challenge; uniform application and prior written publication are where most cases are lost.
- An ultra vires rule is no rule at all. A pet ban where the Declaration permits pets, or a leasing ban the Declaration never mentions, is void — and every fine under it is void. Those restrictions belong to a members’ amendment.
- Publish before you enforce, and enforce everyone the same. Keep dated proof of publication, and pull a 12-month violation history before issuing notice. Selective enforcement is fatal.
- Notice and a hearing are statutory. TX § 209.006 / § 209.0064 (45-day cure); FL § 720.305 / § 718.303 (14-day notice + independent hearing committee). No fine sticks without them.