Where the authority to deny comes from
A denial is only as strong as the document it rests on. Your declaration and adopted design guidelines define what the committee may review and the standard it must apply. A denial that cites a standard nobody actually wrote down is the easiest kind to overturn, so the first question is never whether the board dislikes the proposal — it is which written provision the proposal fails.
Boards often ask whether they can deny a request without giving a reason. In some states the answer is plainly no: California, Florida, and Texas (for subdivisions over 40 lots) all require a written denial that states the basis. In most other states the statute is silent and your governing documents control — but even there, a reasonless denial is a bad habit. General duties of reasonableness and non-arbitrary, uniform enforcement still apply, and a denial with no stated basis is nearly impossible to defend a year later when nobody remembers the discussion.
What makes a denial defensible
The states that regulate denials most closely all converge on the same four elements, and they are good practice everywhere. First, put the decision in writing. Second, cite the specific guideline section or covenant the proposal violates — quote it, do not paraphrase it. Third, name the specific nonconforming aspect of the proposal, in measurable terms where possible: a fence height, a material, a setback. Fourth, give the owner a path forward — the changes that would make the proposal approvable, plus whatever reconsideration or hearing rights your statute or documents provide.
The fifth element is consistency, and it is decided before the letter is written. Apply the same standard the same way to every owner. Nevada's statute states the principle bluntly: a rule that is not uniformly enforced under similar circumstances may not be enforced against any owner. Before voting, check how the committee handled the last few comparable requests. Our guide on selective enforcement covers this in depth.
DEFENSIBLE DENIAL CHECKLIST [ ] Decision made by the body your documents authorize (ARC or board) [ ] Decision recorded with a date, in minutes or a committee record [ ] Written notice sent to the owner [ ] Exact provision cited and quoted (guideline section or covenant) [ ] Specific nonconforming aspect named, in measurable terms [ ] Changes required for approval stated, if any would work [ ] Reconsideration or hearing rights described, per statute or documents [ ] Checked against prior decisions on similar requests [ ] Full file retained: application, plans, photos, guideline version, letter
Denial reasons that lose
Vague aesthetics is the most common losing argument. Terms like harmony, fit, or community character carry weight only if your adopted documents define them. One California HOA law firm, MBK Chapman, puts it flatly: unless a vague aesthetic term is defined in the governing documents, such objections have no legal weight. Florida wrote the same idea into statute in 2024 — a denial must state the specific rule relied on and the specific nonconforming aspect, so a generic does-not-conform-to-guidelines letter fails on its face.
Inconsistency is the second. Denying a pergola this year after approving three identical ones is what the same practitioner guidance calls textbook arbitrariness, and in Nevada it can render the rule unenforceable against everyone. If a genuine difference distinguishes the requests — lot conditions, a guideline amendment adopted in between — say so in the letter and the minutes.
Third, reasons that live outside the documents: personality disputes, speculation about property values, or concerns your guidelines never mention. If the concern is legitimate, the fix is to amend the guidelines prospectively, not to invent a standard mid-review.
State rules on written denials
Statutes sort into two groups. California, Florida, and Texas prescribe what the denial itself must contain. Most other states impose no owner-facing written-reasons rule, relying instead on general reasonableness or uniform-enforcement duties, record-retention requirements, and whatever your governing documents say. Note the scope limits: the Texas regime applies only to subdivisions with more than 40 lots outside the declarant-control period, and Washington's current chapter is repealed effective January 1, 2028, after which associations fall under WUCIOA (RCW 64.90).
A caution about secondary sources: two citations widely repeated on law-firm blogs — a North Carolina architectural-standards mandate at § 47F-3-102(11), and a Virginia 45-day decision deadline at § 55.1-1811 — do not survive a check of the actual statute text. The first is a late-fee provision; the second does not exist. Read the statute itself, or ask counsel to.
This table reflects statutes as of July 2026. It is operational guidance, not legal advice; statutes change, and states not listed have their own rules. Verify the current text and consult association counsel before relying on any entry here.
| State | What the law requires for an architectural denial | Statute / authority |
|---|---|---|
| California | Decision must be written, in good faith, and not unreasonable, arbitrary, or capricious. A disapproval must explain the reason and describe the reconsideration procedure; the applicant is entitled to reconsideration at an open board meeting, unless the board (or a body with the same membership) already decided at a compliant open meeting. | Cal. Civ. Code § 4765 |
| Florida | Denial must be a written notice stating with specificity the rule or covenant relied on and the specific nonconforming aspect of the proposal. An owner harmed by an unreasonable, knowing, and willful infringement may recover damages plus costs and reasonable attorney's fees. | Fla. Stat. § 720.3035(4) |
| Texas | For subdivisions over 40 lots (outside the declarant-controlled period), a written denial must describe the basis in reasonable detail, state any changes required for approval, and inform the owner of a 30-day window to request a hearing, which the board must hold within 30 days of the request. | Tex. Prop. Code § 209.00505 |
| Arizona | Approval of a construction project's architectural designs, plans, and amendments may not be unreasonably withheld; the statute itself does not require written reasons or a specific cure or appeal procedure — those come from the governing documents. | Ariz. Rev. Stat. § 33-1817 |
| Colorado | No owner-facing written-reasons requirement, but the association must retain records of board or committee actions approving or denying architectural requests, and its enforcement policy must provide a fair, impartial fact-finding process with notice and an opportunity to be heard — expressly reaching architectural requirements. | Colo. Rev. Stat. §§ 38-33.3-317(1)(m), 38-33.3-209.5 |
| Georgia | No statutory written-decision or stated-reasons requirement; the Property Owners' Association Act gives the association, or an architectural control committee it appoints, broad power to grant or withhold approval of exterior-appearance changes. | Ga. Code Ann. § 44-3-231(a)(3) |
| Nevada | No architectural-specific written-decision statute, but all rules must be reasonably related to their purpose, consistent with the governing documents, non-arbitrary, and uniformly enforced under the same or similar circumstances — a rule not uniformly enforced may not be enforced against any owner. | Nev. Rev. Stat. § 116.31065 |
| North Carolina | No statutory architectural-review or written-decision requirement; reasonableness derives from the governing documents and case law (e.g., Armstrong v. Ledges). Subsection (11) of the powers statute is a late-fee provision, not an architectural-standards mandate. | N.C. Gen. Stat. § 47F-3-102 |
| Virginia | No ARC-specific written-decision section exists in the Property Owners' Association Act; architectural review is governed by the declaration, though the Act grants owner-favorable rights for solar devices (§ 55.1-1820.1) and EV charging stations (§ 55.1-1823.1). | Va. Code § 55.1-1800 et seq. |
| Washington | No written-reasons requirement, but the association must retain the materials relied on to approve or deny an architectural request for seven years after the decision. This chapter is repealed effective January 1, 2028, after which associations fall under WUCIOA (RCW 64.90). | Wash. Rev. Code § 64.38.045 |
An annotated denial letter
The annotated template below covers the strictest statutes, so it works as a floor anywhere. The WHY THIS CLAUSE notes explain what each paragraph is doing; they are for the board, not the owner, so a clean, fill-in-ready version with the annotations already removed is available to download as PDF or DOCX below. Replace the bracketed merge fields, drop the state-specific appeal language that does not apply to you, send it the way your documents require, and keep a copy in the case file.
[ASSOCIATION NAME] [DATE] Re: Architectural request #[REQUEST NUMBER] — [PROPERTY ADDRESS] Dear [OWNER NAME], The Architectural Review Committee met on [DECISION DATE] and reviewed your request, received on [SUBMISSION DATE], to [DESCRIPTION OF PROPOSED CHANGE]. [WHY THIS CLAUSE: Puts the decision date and review timeline on paper. If your documents or a statute impose a decision deadline, this line proves you met it.] The Committee has denied the request as submitted. [WHY THIS CLAUSE: An unambiguous decision. "As submitted" signals the door is open to a revised proposal, not a permanent no.] The basis for this denial is Section [SECTION NUMBER] of the [DESIGN GUIDELINES / DECLARATION], which provides: "[QUOTE THE EXACT PROVISION]." Your proposal does not conform because [SPECIFIC NONCONFORMING ASPECT — e.g., the proposed fence is 8 feet tall where Section 4.2 permits a maximum of 6 feet]. [WHY THIS CLAUSE: The core of a defensible denial — the exact provision, quoted, plus the specific way the proposal fails it. Florida (Fla. Stat. § 720.3035(4)) requires exactly this specificity, and Texas (Tex. Prop. Code § 209.00505) requires the basis in reasonable detail. "Does not conform to community standards" alone is not enough anywhere it matters.] The Committee would consider a revised proposal that [CHANGES REQUIRED FOR APPROVAL — e.g., reduces the fence height to 6 feet and uses a material listed in Appendix B]. You may resubmit at any time through the standard application process. [WHY THIS CLAUSE: The cure path. Texas requires the letter to state changes required for approval, and everywhere else it turns a dispute into a to-do list.] If you believe this decision is in error, you may request [RECONSIDERATION / A HEARING] by [APPEAL PROCEDURE FROM YOUR DOCUMENTS OR STATUTE — e.g., written request to the board within 30 days]. [CALIFORNIA: describe reconsideration by the board at an open board meeting. TEXAS, OVER-40-LOT ASSOCIATIONS: state the 30-day window to request a hearing, which the board holds within 30 days.] [WHY THIS CLAUSE: Appeal rights. California requires the denial letter itself to describe the reconsideration procedure; Texas requires notice of the hearing window. Where no statute applies, state whatever your documents provide.] This decision applies the same standards the Committee applies to all requests under Section [SECTION NUMBER]. [WHY THIS CLAUSE: Puts uniform application on the record. Include it only if it is true — check your prior approvals first.] Sincerely, [NAME], [TITLE] On behalf of the Architectural Review Committee, [ASSOCIATION NAME] [WHY THIS CLAUSE: Sign as the committee or board acting in its official capacity, not as an individual neighbor.]
ARC denial letter template
The denial letter with the WHY THIS CLAUSE annotations removed — fill-in fields for the merge data, ready to complete and send.
Documenting the decision
Write the file as if someone else will read it in three years, because someone might. Colorado requires associations to retain records of every board or committee action approving or denying an architectural request, and Washington requires the materials relied on to be kept for seven years after the decision. Those are floors, not ceilings. Keep the application as submitted, the plans, any photos, the version of the guidelines in force on the decision date, the minutes or committee record, and the letter itself.
The most valuable record is the one boards rarely keep: a running log of past architectural decisions. When the next similar request arrives, that log is what lets you either approve consistently or articulate a real, documented distinction — which is the entire defense against an arbitrariness claim. A dated, per-lot decision history is worth more than any single well-written letter.
Where ViolationFlow fits
ViolationFlow tracks ARC requests with deadlines alongside violation cases, one case per lot, so a small self-managed board has the whole review on a dated timeline: when the application arrived, when the committee decided, and when the denial letter went out. Notices are sent from templates and every send is logged, so the question of whether the owner was actually told, and when, has a recorded answer.
When a denial is challenged — at a California reconsideration, a Texas hearing, or just a tense annual meeting — the timeline exports to PDF for the board packet or association counsel. Owners can follow their own request through a private link, which resolves most did-you-even-look-at-it disputes before they start. Nothing advances or sends automatically; every step is an explicit board action, which is exactly how architectural decisions should be made.
Frequently asked questions
- Can an HOA deny an architectural request without giving a reason?
- In some states, no. California, Florida, and Texas (for subdivisions over 40 lots) require a written denial stating the basis. Elsewhere the statute is usually silent and your governing documents control — but general reasonableness and uniform-enforcement duties still apply, and a reasonless denial is very hard to defend later.
- What should an ARC denial letter include?
- The decision date, the specific guideline or covenant provision relied on (quoted, not paraphrased), the specific way the proposal fails it, the changes that would make it approvable, and the owner's reconsideration or hearing rights. That satisfies the strictest statutes and is sound practice everywhere.
- Can we deny a request because it doesn't fit the character of the neighborhood?
- Only if that standard is defined in your adopted documents. Practitioner guidance is blunt that undefined aesthetic terms like fit or harmony have no legal weight, and Florida's statute requires the specific rule and specific nonconforming aspect — generic aesthetic language fails on its face there.
- What if we approved a similar project for another owner last year?
- Treat it as a serious problem for the denial. Unequal application of identical rules is textbook arbitrariness, and Nevada's statute makes a non-uniformly-enforced rule unenforceable against any owner. Either document a genuine difference between the two requests, or approve.
- How long should we keep ARC records?
- Long enough to defend the decision. Washington requires the materials relied on to be kept for seven years; Colorado requires records of approve-and-deny actions as association records. Keeping the full file — application, plans, minutes, letter — indefinitely costs almost nothing.
- Does the Texas hearing requirement apply to every association?
- No. Tex. Prop. Code § 209.00505 applies only to property owners' associations whose subdivision has more than 40 lots, and not during the declarant-controlled development period. Smaller Texas associations look to their governing documents for any denial and appeal procedure.