Running an HOA Architectural Review Process That Actually Works

Quick reference:

• An ARC decision that isn't documented is a liability — if a homeowner challenges a denial, the board needs a written record showing the review was consistent with the CC&Rs and applied uniformly
• Response time matters: most CC&Rs set a deemed-approved window (30-60 days) after which an unanswered application is automatically approved — missing that window can create enforcement problems
• The ARC's job is to apply the architectural standards in the CC&Rs, not to exercise personal taste — every decision should cite the specific CC&R section it's based on

Architectural review is one of the areas where informal HOA governance creates the most legal exposure. A board member approves a fence over a phone call, a homeowner builds something that wasn't what they described, and two years later the HOA is trying to enforce against a "permitted" project with no paper trail. Getting the ARC process documented and consistent is not bureaucracy for its own sake — it's the foundation of defensible enforcement.

Why ARC Process Failures Are Common

Most ARC problems share a common root: the process was never written down clearly enough to be followed consistently.

Informal approvals — a board member gives a verbal okay, a neighbor says they "talked to someone on the board" — are the most common source of problems. When an enforcement issue arises later, the informal approval becomes a factual dispute that the HOA almost always loses.

Inconsistent criteria are the second major failure mode. If the ARC approved a gray fence for one homeowner but denied a gray fence for another without documented reasoning, the second homeowner has a legitimate basis to challenge the denial. Selective enforcement claims are among the most successful legal challenges homeowners bring against HOAs.

Missed review windows are a process failure with automatic consequences. Most CC&Rs include a deemed-approved clause — if the HOA does not respond within a specified period (commonly 30 to 60 days), the application is automatically approved regardless of what the project is. An ARC that loses track of pending applications can inadvertently approve something it would have rejected.

ARC Workflow — Step by Step

A consistent workflow eliminates most of these failure modes. Build your process around these five steps and apply them to every application without exception:

| Step | Action | Timeline | |------|--------|----------| | 1 | Application received | Day 0 | | 2 | Acknowledgment sent to homeowner | Within 3 business days | | 3 | ARC committee review | Days 3–21 | | 4 | Written decision issued | By Day 30 | | 5 | Outcome recorded in HOA records | Same day as decision |

The acknowledgment in Step 2 is often skipped, but it matters. It confirms to the homeowner that their application is in the system, starts the communication record, and tells them when to expect a decision. It also protects the HOA — if a homeowner later claims they never received a response, the acknowledgment email or letter establishes that the process started.

The 30-day decision window in Step 4 should be set conservatively relative to your CC&Rs' deemed-approved deadline. If your CC&Rs specify 60 days, issue decisions by Day 30 — don't work up to the edge of the window.

What an ARC Application Should Require

A complete application is one you can evaluate without going back to the homeowner for clarification. Require all of the following at submission:

• Project description — what the homeowner intends to build, install, or change, in plain language
• Materials and colors — specific product names or manufacturer color codes, not descriptions like "brown" or "natural"
• Dimensions — height, length, and footprint for fences, structures, and additions
• Contractor information — name and license number if the work will be done by a third party (relevant for compliance tracking and neighbor notice)
• Neighbor impact statement — for projects that visually or structurally affect adjacent lots, a brief statement of how the homeowner addressed neighbor concerns
• Site plan — for additions, sheds, or any structure that changes the footprint of the lot; a sketch is acceptable for minor projects

An incomplete application should not start the review clock. Send an incomplete notice within your three-business-day acknowledgment window explaining what is missing and what must be resubmitted. Do not begin the formal review until the application is complete — this also protects the deemed-approved clock.

Approvals With Conditions

Not every application is a clean yes or no. A conditional approval is a valid outcome: you approve the project subject to modifications that bring it into compliance with the CC&Rs.

Common conditions include:

• Substituting a compliant color or material for a non-compliant one the homeowner specified
• Reducing dimensions to comply with the setback or height requirements in the architectural standards
• Requiring that the homeowner use a licensed contractor
• Requiring a post-completion inspection

The conditions must be in writing, clearly stated in the approval letter, and the homeowner must acknowledge them in writing before beginning work. "Acknowledged" means a signed return of the conditional approval, not a phone call. Without that acknowledgment, you have no record that the homeowner agreed to the conditions before they started building.

Denials — How to Do It Right

A vague denial is more legally vulnerable than a specific one. "Does not fit the character of the community" is not a defensible standard. A denial that cites the specific CC&R provision violated, explains precisely what the project does not comply with, and tells the homeowner what a compliant version would look like is far harder to challenge.

Structure every denial letter the same way:

First: Identify the CC&R section or architectural standard the project violates, by number. "Section 4.3(b) of the Declaration prohibits fences exceeding six feet in height within the front yard setback."

Second: Explain specifically how the homeowner's project violates that standard. "The proposed fence is eight feet tall and would be located three feet from the front property line."

Third: Where possible, explain what a compliant version of the project would look like. "A fence of six feet or less, located behind the rear building line, would be eligible for ARC approval."

Not every denied project has a compliant version — sometimes the CC&Rs simply prohibit what the homeowner wants. In those cases, say so plainly: "The proposed solar panel installation on the front-facing roof slope is not permissible under Section 5.1 of the Declaration." Avoid language that implies the ARC has personal objections. The decision is the CC&Rs', not the committee members'.

Record Keeping

Every ARC decision — approval, conditional approval, or denial — must be filed as a complete package:

• The original application (with all supporting materials)
• The acknowledgment letter
• Any requests for additional information
• The written decision letter
• The homeowner's acknowledgment of conditions (if applicable)
• Any post-completion inspection notes

Keep these records for the retention period specified in your governing documents, or for at least three years if your documents are silent. When the HOA later needs to enforce an ARC condition or pursue a homeowner who built without approval, these records are the foundation of the enforcement case. Missing records shift the factual dispute in the homeowner's favor.

Boards managing ARC applications through purpose-built HOA architectural review software can track applications, automate acknowledgment letters, and log decisions in one place — dramatically reducing the risk of missed deadlines and lost paperwork. Complete ARC records also feed directly into HOA document management for long-term retention and retrieval.

Frequently Asked Questions

Q: What happens if the ARC doesn't respond within the CC&Rs' deadline?

In most cases, the application is automatically deemed approved. This is the most common enforcement trap in ARC management — if you miss the response window, you may have inadvertently approved a project you would have rejected, and the homeowner can proceed with legal cover. The only defenses available to the HOA are narrow: if the application was incomplete at submission and the review clock never properly started, or if state law provides a different outcome than the CC&Rs. Neither of these is a reliable safety net. The fix is a workflow with hard deadlines and an assigned reviewer responsible for tracking the queue.

Q: Can an ARC approval be revoked if the homeowner builds something different?

Yes. An ARC approval is for the specific project as submitted and approved. If the homeowner builds something materially different — a different color, different dimensions, different materials — the approval does not cover what was actually built. The HOA can pursue enforcement for the as-built deviation. This is why the original application materials matter: they establish the baseline for what was approved. When a post-completion inspection reveals a deviation, the inspection notes and original application are the enforcement record.

Q: Does every HOA have to have an architectural review committee?

Not every HOA is required to have a standing committee — some governing documents vest ARC authority directly in the board. What every HOA with architectural standards in its CC&Rs must have is a documented process for reviewing applications against those standards. Whether that process runs through a committee, a subset of the board, or the full board, the documentation and consistency requirements are the same. If your CC&Rs establish an ARC as a separate committee, you must staff and operate it — you cannot consolidate those decisions into board meetings without a governing document amendment.

Q: Can a board member approve ARC requests on their own home?

No. This is a direct conflict of interest, and most governing documents explicitly prohibit it. A board member who submits an ARC application for their own property should recuse themselves from the review entirely — they should not participate in the committee discussion, should not be present during the deliberation, and should not vote on the outcome. The remaining committee members or board members review and decide the application without them. Document the recusal in the ARC record. A board member who approves their own ARC application, even informally, has created a significant legal exposure for the association.