The email subject line is always the same: "Can I paint my door navy blue?" Half the board wants to say yes. The other half remembers the 2014 fence fight. Welcome to ARC — Architectural Review Committee work — the HOA job that generates the most neighbor drama per square foot.
This guide explains how volunteer boards should handle HOA ARC requests: what to require in submissions, how to decide consistently, and how to document approvals so the next sale does not reopen a five-year-old paint color debate.
What ARC is (and what it is not)
ARC reviews proposed changes to exterior appearance or common elements — paint, fences, roofs, landscaping structures, solar panels, sheds, and similar modifications defined in your CC&Rs.
ARC is not building code enforcement (that is the city). It is not maintenance ticketing (that is ops). It is covenant consistency — keeping the community look predictable for everyone who read the rules before they bought.
Your CC&Rs may call it Architectural Committee, Design Review, or ACC. The name varies; the job is the same.
Publish a clear submission checklist
Before reviewing a single application, post a one-page ARC submission guide residents can download:
- Application form fields (owner name, address, project description)
- Photos of current condition and mockups where possible
- Material specs — paint brand/color code, fence height, roof product
- Contractor info if required
- Fee if your documents allow application fees
- Timeline — "decisions within 30 days of complete submission"
Incomplete applications get a hold email listing missing items — not a denial. That keeps the process fair and fast.
Run major guideline updates through your board document review workflow before publishing.
The review workflow that scales
For each complete submission:
- Log the request with date received and assigned reviewer
- Check CC&Rs and design guidelines — cite the section that applies
- Drive-by or photo review — compare to submitted materials
- Committee discussion — use a single thread or in-app comments, not side texts
- Vote or delegate per your documents (some boards require full board vote; others delegate to ARC)
- Issue written decision — approved, approved with conditions, or denied with reason
- Archive photos, decision letter, and inspection notes when work completes
KindHOA tracks ARC requests with statuses, attachments, and history so "was that fence approved?" takes 10 seconds, not three inbox searches.
Approval letters vs. denial letters
Approvals should state:
- What was approved (specific colors, dimensions, materials)
- Conditions — "stain only, no solid paint"; "remove within 30 days if noncompliant"
- Expiration — approvals often lapse if work does not start within 12 months
Denials must be factual and cite authority — not "we don't like it." Example: "Proposed 8-foot fence exceeds 6-foot limit in Design Guideline §4.2."
Offer a path to revise and resubmit. Many disputes are fixable with a shorter fence or alternate color from the approved palette.
Timelines and owner expectations
Most governing documents require decisions within 30–45 days of a complete application. Silence helps nobody — if you need an extension, email the owner with a new date.
During construction, a quick completion photo on file prevents "that deck is six inches too tall" arguments at resale.
When ARC decisions go wrong (and how to avoid lawsuits)
Common pitfalls:
- Retroactive approvals after work is done — sets a terrible precedent
- Neighbor voting without documented criteria — feels arbitrary in court
- Inconsistent palettes — navy approved on Oak Street, denied on Maple
- Mixing ARC with violations — unfinished unapproved work is an ARC compliance issue; cite the approval denial, then escalate through violation notices only if work proceeds without approval
Selective enforcement destroys board credibility. See How to Run a Self-Managed HOA Without Getting Sued.
ARC and maintenance overlap
Sometimes a request is both — "replace rotted deck boards" may need ARC if railings change height or materials. Train residents to submit ARC first when exterior appearance changes; use maintenance tickets for pure repairs that restore like-for-like.
The bottom line
Good ARC process is boring: clear checklist, complete applications, written decisions, photo archive. Residents get predictability; boards get defensible records.
KindHOA includes ARC request tracking on the free Good Neighbor plan — photos, statuses, and board comments in one place. Review your full ops stack in the software feature checklist.
Related reading
- HOA Board Document Review Workflow
- How to Write an HOA Violation Notice
- Self-Managed HOA Software Feature Checklist
- Self-Managed HOA Checklist
ARC authority and timelines come from your CC&Rs — confirm procedures with association counsel for edge cases.