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 once you understand it, "which document controls" stops being a guess and becomes a rule you can apply in about thirty seconds. Here's how the hierarchy works, how to use it, and the mistakes that quietly turn good-faith board decisions into unenforceable ones.

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 the statute requires 14 days' notice before a fine, a bylaw that says 7 days is unenforceable. If the statute gives owners a right to inspect records, a board resolution trying to restrict it is void.
2. Declaration / CC&Rs. The recorded document that runs with the land. It controls over everything below it. Amending it follows the recorded amendment procedure — usually an owner vote at a supermajority threshold — and the amendment 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 — adopting a fine schedule, approving a contract, declaring an emergency. A resolution operates only within the authority the higher documents already grant. It can't expand that authority.

So in the rental example: the CC&Rs sit above the rule. The rule that "allows" short-term rentals is void — not merely unenforceable, void from the moment it was adopted, because the board's rulemaking power is delegated by the CC&Rs and can't be used to contradict them. Lifting that prohibition would require a CC&R amendment, which means an owner vote, not a board vote.

CC&Rs vs. bylaws vs. rules: a quick test for which one wins

When two provisions seem to disagree, don't argue about which feels more authoritative — work from the top down and stop at the first document that addresses the question:

1. Does state statute address it? If yes, statute controls.
2. Does the declaration / CC&Rs address it? If yes, and no statute conflict, the CC&Rs control.
3. Do the bylaws address it? If yes, and nothing above conflicts, the bylaws control.
4. Do the rules address it? If yes, and nothing above conflicts, the rules control.
5. Is everything silent? Statute fills the gap; if statute is also silent, your state's nonprofit corporation act applies.

The first "yes" you reach, starting from the top, is your controlling authority. That's the whole method. The reason CC&Rs vs. bylaws vs. rules trips boards up is that the rules are the documents they touch most — so it feels like the rules are where decisions get made. They aren't. The rules are the bottom of the stack.

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

This is worth saying plainly because it's the single most common version of the question: a board-adopted rule never overrides the CC&Rs. The CC&Rs are higher authority. A rule that conflicts with them is void. If your CC&Rs prohibit commercial vehicles, no rule the board passes can authorize them — that takes a CC&R amendment and an owner vote.

The one place this confuses people is amendments, so here's the rule that resolves it: an amendment inherits the rank of the document it amends. An amendment to the CC&Rs is CC&R-level authority — not a low-ranking afterthought just because it was adopted recently. So when a CC&R amendment conflicts with the original CC&R provision it changed, the amendment controls, because it sits at the same level and is the more recent expression of it. But when that same amendment conflicts with something higher — state statute — the statute still wins. Newer doesn't beat higher; it only beats the same-level provision it was written to replace.

This is also why "the documents are silent" never means "the board can do whatever it wants." If the rules don't address something, you work up the stack — bylaws, then CC&Rs, then statute, then general corporation law. The answer is almost always somewhere above you.

One more layer: statute can quietly override your documents

Here's a situation self-managing boards miss because nothing in their binder changed: the legislature changed the law. Say your state passes a law saying HOAs can't prohibit solar panels, but your CC&Rs prohibit them. You don't have to amend the CC&Rs to comply — when a statute preempts a CC&R provision, the conflicting language is unenforceable from the statute's effective date, full stop. The old language stays printed in the document, but the part that conflicts is void as a matter of law.

The practical move is to have counsel confirm the preemption applies to your specific language, then adopt a board resolution acknowledging it and stop enforcing the dead provision. The point for the hierarchy: your documents are not the final word. The statute above them can change what they're allowed to say without a single word of your CC&Rs being edited.

State statutes are also where the content of the hierarchy varies. The stack structure — statute over CC&Rs over bylaws over rules — is the same everywhere, but what each statute actually mandates differs significantly. 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 the same order of authority — statute over the association's own documents — and each specifies owner rights that documents can't waive. But the specific notice periods, owner-vote thresholds, and protected rights are not the same from state to state. Verify your own state's current statute before concluding any provision is enforceable.

Mistakes boards make with document 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.
• Amending only the rules when the issue is CC&R-level. If the CC&Rs prohibit something, no rule can authorize it. That requires a CC&R amendment — an owner vote, not a board vote.
• 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.
• Forgetting the association — not the board — is the entity. The board directs a perpetual legal entity; it doesn't own it. That framing keeps the hierarchy honest: the board's authority is delegated by documents above it, not inherent.

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 — and that's where it gets slow, because answering "which document controls?" means cross-reading the CC&Rs, the bylaws, the rules, and the amendments at the same time, then checking nothing higher overrides what you found. That's exactly 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, with amendments inheriting their parent's rank — and cites the exact provision it relied on. You see which document controls, and why, without flying blind through four binders to get there. And the conflict you didn't know to look for — a rule that quietly contradicts the CC&Rs, like the rental example this article opened with — BoardPath's conflict finder surfaces on its own, flagging where two of your own documents disagree and naming which one controls. See it in the live demo, or join the founding cohort if you'd rather run your community confidently than guess.