Orange County HOA article

HOA Architectural Review Committee Process

How OC HOA boards should structure the architectural review committee process for owner modification requests, covering application requirements, review timelines, and appeal procedures.

The architectural review committee (ARC) is the governance mechanism that protects community aesthetics while giving owners a fair path to modify their property. In California, the Davis-Stirling Act (Civil Code §4765) sets baseline requirements for how associations must handle owner modification requests — but most of the operational detail is left to the association’s CC&Rs and architectural guidelines.

Application requirements the board should standardize

Every modification request should include:

  • a completed application form with the owner’s name, unit number, and contact information,
  • a written description of the proposed modification,
  • drawings, photos, or material samples as appropriate for the scope of work,
  • contractor information (if applicable), including license number and insurance,
  • estimated start and completion dates, and
  • acknowledgment of the association’s architectural guidelines.

Standardizing the application prevents incomplete submissions from entering the review queue and causing delays.

Review timeline obligations

Under Civil Code §4765, the association must act on a complete application within 60 days. If the association fails to act within that period, the application is deemed approved by operation of law. The board should:

  • acknowledge receipt of the application within 5 business days,
  • notify the owner if the application is incomplete and specify what is missing,
  • schedule ARC review within 30 days of receiving a complete application, and
  • deliver the written decision within 60 days of receiving the complete application.

Build internal deadlines tighter than the statutory 60-day window to account for committee scheduling and board ratification.

Decision standards

The ARC should evaluate applications against the published architectural guidelines — not personal aesthetic preferences. Decisions should:

  • reference the specific guideline section that supports approval or denial,
  • explain the reason for any denial clearly enough that the owner understands what would need to change for approval,
  • include any conditions of approval (material specifications, color matching, completion deadlines, inspection requirements), and
  • be delivered in writing with the date of the decision.

Vague denials (“not consistent with community standards”) without referencing a specific guideline create legal exposure.

Handling appeals

The CC&Rs or operating rules should define an appeal process. A common structure:

  1. The owner submits a written appeal within 15 days of the denial.
  2. The full board (not just the ARC) reviews the appeal at the next regular board meeting.
  3. The owner may present their case at the meeting.
  4. The board issues a final written decision within 30 days of the appeal hearing.

If the CC&Rs do not specify an appeal process, the board should adopt one through the operating rule change process to avoid ad hoc decisions.

Common ARC pitfalls

  • Inconsistent enforcement: approving a modification for one owner and denying the same modification for another without a documented change in guidelines.
  • Undocumented approvals: verbal approvals from individual board members create disputes when the full committee has not reviewed the request.
  • Scope creep during construction: the owner completes work that differs from what was approved. The ARC should require a post-completion inspection for significant modifications.
  • Missing CC&R authority: the ARC can only enforce standards that are actually in the governing documents. Attempting to enforce standards not in the guidelines undermines the committee’s authority.

Where this article points next

Boards refining their ARC process should also review the CC&R enforcement workflow for handling unapproved modifications, and the homeowner records request process since owners may request copies of prior ARC decisions.

Related articles

Stay inside the same HOA workflow instead of starting the next search from scratch.

These follow-on reads come from the article contract first, with helper fallback only when needed.

  • Governance & Compliance March 26, 2026

    HOA CC&R Enforcement Workflow

    A structured enforcement workflow for OC HOA boards handling CC&R violations, from initial notice through hearing and resolution under Davis-Stirling requirements.

  • Governance & Compliance March 20, 2026

    HOA Rule Change Owner Communication Checklist

    A checklist HOA boards can use when policy or rule changes need to be explained to homeowners with cleaner timing, clearer language, and fewer follow-up surprises.

  • Governance & Compliance March 26, 2026

    HOA Homeowner Records Request Process

    How OC HOA boards should handle homeowner records requests under the Davis-Stirling Act, covering required timelines, permissible redactions, and common board missteps.

First-party board resource

Need a cleaner HOA vendor brief before bids start coming in?

Use the first-party vendor RFP template to turn article guidance into a board-ready scope before you compare print, mail, or communication partners.

This request path is designed for board members, community managers, and committee leads who want a cleaner brief before they approach vendors, compare print partners, or map a resident-facing communication timeline.

  • Each request is consent-based and stored with source metadata instead of relying on imported HOA mailing lists.
  • Validation and failure states stay diagnosable without exposing raw lead details in the browser.
  • The delivery path ends on a real thank-you and resource experience rather than a dead-end placeholder.