Which HOA Document Controls? (Declaration vs. Bylaws vs. Rules)

A board adopted a rule last year allowing short-term rentals. It seemed reasonable — owners wanted the flexibility, the board voted, the rule went into the handbook. Then someone actually read the CC&Rs, which flatly prohibit rentals under 30 days. So now the community has two of its own documents saying opposite things, and a board that doesn't know which one wins. The rule feels official. The CC&Rs feel older and harder to change. Which HOA document controls?

This question sits underneath an enormous share of the disputes a self-managing board runs into, and the answer is more settled than most boards realize. There's a fixed legal order to your governing documents — a hierarchy — and it's the tool that resolves a genuine conflict between two of them. But here's the part most boards get wrong: the hierarchy is a tie-breaker, not the first move. Before you decide which document controls, confirm the documents actually conflict — and most of the time they don't. Here's how the hierarchy works, when to use it, and the mistake that turns a careful board into one that voids its own valid rules.

This is general information for board members, not legal advice. The structure below is universal; the specifics of each level live in your state's statute and your community's recorded documents — confirm both before you rely on a provision.

Which HOA document controls? The hierarchy, top to bottom

Your governing documents are not a pile of equal rulebooks. They sit in a fixed order of authority, and a lower-level document can never authorize what a higher-level one prohibits. From the top:

1. State statute. The highest authority. Your state's HOA or condominium act overrides every document the association has. If your statute sets a minimum notice period before a fine, a bylaw with a shorter window is unenforceable.
2. Declaration / CC&Rs. The recorded document that runs with the land; it controls over everything below it. Amending it takes the recorded amendment procedure — usually an owner vote at a supermajority — and is recorded against title.
3. Bylaws. The corporate operating rules: board size, meeting notice, officer duties, how the association runs itself. Bylaws must not contradict the CC&Rs or statute. A bylaw can't hand the board authority the CC&Rs withheld.
4. Rules and regulations / policies. The day-to-day operating rules, typically adopted by the board alone. They must not contradict the bylaws, CC&Rs, or statute. This is where boards spend most of their time — and where most hierarchy violations happen.
5. Board resolutions. Formal actions on specific matters — a fine schedule, a contract, an emergency declaration. A resolution operates only within the authority the documents above already grant; it can't expand it.

So in the rental example, the CC&Rs sit above the rule, and the two genuinely conflict — one forbids exactly what the other purports to allow. The rule is void from the moment it was adopted, because the board's rulemaking power is delegated by the CC&Rs and can't contradict them. Lifting the prohibition takes a CC&R amendment and an owner vote, not a board vote.

CC&Rs vs. bylaws vs. rules: reconcile first, rank second

When two provisions seem to disagree, the instinct is to reach for the hierarchy and crown a winner. Resist it. The hierarchy — statute over CC&Rs over bylaws over rules — is a conflict-resolution tool: it decides which document controls only when two provisions genuinely cannot both be true. And in community-association governance, that precondition usually isn't met.

Your governing documents were written at different levels of detail on purpose — the declaration sets the broad framework, the bylaws describe how the corporation runs, the rules fill in the day-to-day specifics. So the same subject routinely shows up in two documents, not to contradict each other but to describe one system at different granularities. When that's what's happening, both provisions are authoritative and neither is subordinated. Reading them together is the answer; ranking them would be the mistake.

So the real first question isn't "which document is higher?" It's "do these two provisions actually conflict — or do they fit together?" Work it in that order:

1. Read both provisions in full and ask whether they can both be true. If they address different aspects of the same rule, or the same rule at different levels of detail, they complement — apply both. You're done. No ranking needed.
2. Only if they genuinely can't both hold — one permits exactly what the other forbids — do you have a real conflict.
3. Now use the hierarchy to resolve that conflict: statute over CC&Rs, CC&Rs over bylaws, bylaws over rules — and a board resolution only within the authority above it already grants. The higher provision controls; the lower yields to the extent of the conflict.
4. If every document is silent, work up the stack — bylaws, then CC&Rs, then statute, then your state's general nonprofit corporation law. The answer is almost always somewhere above you.

The hierarchy still does real work — but only at step 3, once you've confirmed a genuine contest. Reaching for it at step 1 is how boards void provisions that were never in conflict.

A conflict that isn't one

Here's how easily the reflex misfires. Say your declaration gives each unit "a single vote," while your bylaws say voting is "on a percentage basis." A board that ran straight to the hierarchy would rule that the declaration outranks the bylaws — so "single vote" wins and the percentage-basis language is void, of no legal effect.

That would be wrong, and it would quietly break the association's actual voting method. Read the two provisions together and they don't fight. The declaration describes indivisibility — one whole, undividable vote per unit, no matter how many owners are on the title. The bylaws describe that vote's weight — how much it counts, set by the unit's percentage interest. One answers "how many votes?"; the other, "how much is each worth?" Both are true at once: a single, indivisible vote per unit, weighted by that unit's percentage interest.

Blindly applying "declaration over bylaws" would have thrown out a valid, load-bearing rule the community votes under every year — the cost of ranking before you've confirmed a real conflict. None of this weakens the hierarchy: when a rule genuinely permits what the CC&Rs forbid, the CC&Rs win, every time. The change is only in the order of operations. Reconcile first; rank second.

Does a rule override the CC&Rs? No — and a key exception about amendments

This is worth saying plainly, because it's the most common version of the question: a board-adopted rule never overrides the CC&Rs. A rule that genuinely conflicts with them — permits what they forbid — is void, and fixing it takes a CC&R amendment and an owner vote, not a board vote. But mind the distinction from the last section: a rule that merely adds detail to a CC&R provision (setting the pool hours the CC&Rs left to the board) isn't overriding anything — it's complementary. "Override" is only when the rule permits what the CC&Rs forbid, and there the CC&Rs win.

The one place this genuinely confuses people is amendments, so here's the rule: an amendment inherits the rank of the document it amends. An amendment to the CC&Rs carries CC&R-level authority — not a low rank just because it was adopted recently. So when it conflicts with the original CC&R provision it changed, the amendment controls, as the more recent expression at the same level. But against something higher — state statute — the statute still wins. Newer beats the same-level provision it replaced; it never beats higher.

One more layer: the statute above your documents can change

Your documents aren't the final word — the statute above them can shift under you. If the legislature passes a law that conflicts with a CC&R provision (say, one protecting solar panels your CC&Rs prohibit), that provision becomes unenforceable from the law's effective date without a word of your CC&Rs being edited; have counsel confirm the preemption, then stop enforcing the dead language. This is also where the content of the hierarchy varies by state. The stack structure — statute over CC&Rs over bylaws over rules — is the same everywhere, but what each statute mandates isn't. Florida's HOA act (FS 720) and condo act (FS 718), California's Davis-Stirling Act (Civil Code §4205), and Nevada's NRS 116 all establish that same order — statute over the association's own documents — yet their specific notice periods, owner-vote thresholds, and protected rights differ. Verify your own state's current statute before concluding any provision is enforceable.

Mistakes boards make with document hierarchy

• Declaring a conflict that isn't one. The mistake this article is built around: two provisions describe the same rule at different levels of detail, a board treats them as contradictory, and "resolves" the phantom conflict by voiding the lower one — often invalidating a rule the community actually relies on. Reconcile before you rank; only a genuine, irreconcilable conflict calls for the hierarchy.
• Adopting a rule that contradicts the CC&Rs. The most common violation, and the most costly, because the rule is void from the start — not voidable later. Every action taken under it is exposed. (More on the limits of board rulemaking: can your HOA board legally make that rule?)
• Treating the bylaws as the top document. Boards do this because the bylaws govern board operations, so they feel central. They aren't the top. The CC&Rs control over the bylaws, and the statute controls over both.
• Using a board resolution to override an owner-vote requirement. If the CC&Rs require an owner vote to amend a provision, a board resolution purporting to amend it is void no matter how unanimous the board was.
• Ignoring a statutory right because the documents are silent. Your governing documents don't have to repeat a statutory right for it to apply. If the statute creates the right and your documents say nothing, the right still exists.

When to call counsel

The hierarchy resolves most everyday conflicts, but a few situations call for a lawyer before the board acts:

• A document provision and a statute provision directly conflict and you're unsure which controls or how to fix it.
• Before adopting any rule that might restrict a CC&R-level owner right.
• Before any amendment — CC&Rs and bylaws each have required procedures that, if not followed exactly, can void the amendment.
• When a homeowner challenges a board action specifically on hierarchy grounds.
• When a change in state law may have preempted a provision you've been enforcing.

Knowing the hierarchy is half the job. The other half is applying it to your documents without over-applying it — cross-reading the CC&Rs, bylaws, rules, and amendments at once, deciding whether two provisions actually conflict or merely complement each other, then checking whether anything higher overrides. Get that judgment wrong in either direction and you either miss a real conflict or void a rule that was never broken.

That's the work BoardPath's Boardroom does. Ask it a governance question and it answers from your own uploaded documents, ranked in the correct order of authority — statute over CC&Rs over bylaws over rules, amendments inheriting their parent's rank — and cites the exact provision it relied on. Where two provisions fit together, it reads them together instead of crowning a false winner; where they genuinely conflict, its conflict finder surfaces the clash and names which one controls. You see which document controls, and why — without flying blind through four binders, and without throwing out a rule that only looked like a contradiction. See it in the live demo, or join the founding cohort if you'd rather run your community confidently than guess.