Most self-managed HOAs handle architectural review through email — applications get lost, deadlines get missed, and decisions go undocumented. There's a better way.
A homeowner wants to build a deck. They read through the CC&Rs, find the section on architectural improvements, and email the board requesting approval. The email goes to the general HOA address. It sits unread for four days because the board member who typically handles it is traveling. A week later, another board member sees it and forwards it to the architectural review committee — which is two people, one of whom responds that they need to schedule a time to review.
Three weeks later, the homeowner still doesn't have an answer. They call a board member directly. The board member looks for the email, can't find it in the inbox, asks to have it forwarded again. They discuss. They agree to approve it. Someone says they'll send the homeowner an email. No one notes when the decision was made or what specifically was approved.
Four months later, the homeowner's contractor finishes the deck. A neighbor complains it doesn't match the application. The board looks for records of what was approved. There are none.
This is architectural review by email — and it's how most self-managed HOAs handle it.
The architectural review committee (ARC) — whether it's a dedicated committee or the board functioning in that role — is one of the most legally exposed functions of HOA governance. The reasons:
Homeowners have property rights. A homeowner who is denied approval for an improvement has the right to understand why, to appeal the decision, and — in many states — to pursue legal remedies if the denial was arbitrary or discriminatory. A verbal "we don't think that works" is not a defensible denial.
The HOA has liability for damage during construction. If the HOA approves an improvement without inspecting the contractor's insurance and the contractor damages adjacent property, the HOA may share liability for being cavalier about who it authorized to work in the community.
Approvals run with the property. When a homeowner who received approval for an improvement sells their home, the next buyer takes on that improvement with the approval status it had. If the approval was verbal and undocumented, the new buyer's HOA file has a gap — and any dispute about the improvement becomes much harder to resolve.
Inconsistent review creates fair treatment exposure. If one homeowner's deck application was approved in three days and another's was denied after six weeks of silence, the difference in treatment looks arbitrary — even if there were legitimate reasons for the outcome difference.
A structured ARC process isn't bureaucracy for its own sake. It protects the HOA, protects homeowners, and creates a record that makes every future decision easier.
An architectural review application should capture:
Project information:
Supporting documents:
Define what a complete application requires and reject incomplete applications immediately, with a clear explanation of what's missing. An incomplete application that sits in review for four weeks — only to be returned for a missing site plan — wastes everyone's time and frustrates homeowners.
Within 48 hours of receiving an application, someone designated to receive ARC applications should verify completeness:
If complete: acknowledge receipt, confirm the review timeline. If incomplete: return immediately with the specific items needed, restarting the timeline when the complete application is received.
This step requires an assigned person, not an inbox. Applications that go to the general HOA email without an assigned reviewer will sit until someone happens to check.
The designated reviewer (or committee) evaluates the application against the applicable criteria in the governing documents:
From the CC&Rs:
From the architectural guidelines (if adopted):
The criteria should be applied consistently. If a 6-foot wooden privacy fence was approved for Unit 14, a 6-foot wooden privacy fence from Unit 22 should be treated the same unless there's a legitimate, documentable distinction (e.g., Unit 22's proposed fence is closer to a shared utility easement).
All three possible outcomes — approve, deny, approve with conditions — require written documentation.
Approval:
Conditional approval:
Denial:
A denial without a specific reason and governing document citation is legally vulnerable and feels arbitrary to the homeowner. "The committee doesn't feel this is in keeping with the community aesthetic" is not a compliant denial in most jurisdictions. "The proposed fence height of 7 feet exceeds the 6-foot maximum specified in Section 12.3(b) of the CC&Rs" is.
Communicate the decision in writing within the timeline your governing documents specify. Most CC&Rs or state HOA statutes specify a maximum review period — typically 30–45 days. If the HOA doesn't respond within this period, many CC&Rs specify that the application is deemed approved.
Missing a response deadline is one of the most avoidable governance failures in HOA management, and it happens regularly when reviews are tracked by email rather than by a system that sends reminders.
For significant improvements — additions, structural changes, major hardscape — a post-approval inspection confirms:
This inspection is the closing of the loop. Document the inspection date, inspector name, and outcome. If the improvement as built deviates from what was approved, initiate a conversation with the homeowner about how to resolve the discrepancy before it becomes a formal violation.
Most state HOA statutes and CC&Rs specify how long the ARC has to respond to an application. This is a hard deadline in many jurisdictions — exceed it and the application may be legally deemed approved.
Common timelines:
If your CC&Rs specify a 30-day review period and the ARC takes 45 days to respond, the homeowner may be legally entitled to proceed with the project regardless of the outcome. That is a scenario entirely within your control to prevent — by tracking applications and their deadlines in a system that reminds reviewers when decisions are due.
When the CC&Rs say "improvements must be consistent with the community aesthetic" and there are no written architectural guidelines, the ARC has enormous discretion — but that discretion creates risk. Decisions that appear inconsistent look arbitrary. Decisions that appear inconsistent across demographic lines create discrimination exposure.
Written architectural guidelines with specific criteria for common improvement types reduce the ARC's exposure and give homeowners a clear understanding of what will and won't be approved before they submit.
A board member who tells a homeowner "yeah, that sounds fine" at a neighborhood event has not issued an ARC approval. When the homeowner builds the improvement and a neighbor complains, there's no record of what was approved or what it was based on.
All approvals must be in writing, with a description of what was approved and any conditions. "But I said it was fine" doesn't survive a homeowner dispute.
When applications are tracked by email, the review period can expire without anyone noticing. This is especially common with volunteer boards where everyone assumes someone else is tracking the timeline.
A dedicated tracking system — even a simple spreadsheet with application date, decision deadline, and status — prevents this. A purpose-built system sends automated reminders.
Most state HOA statutes require that homeowners have the right to a hearing or appeal before a denial is final. If your ARC process doesn't include a documented appeal path, you may be non-compliant.
The appeal process should be defined in writing: who hears the appeal, what the timeline is, what evidence can be submitted, and how the decision is communicated.
If your community lacks formal architectural guidelines, the ARC process will be inconsistent — because reviewers will be making judgment calls against vague CC&R standards rather than specific criteria.
An architectural guidelines document doesn't have to be elaborate. For a small community, it might cover:
Decks and patios: Approved materials, maximum area as percentage of lot, setback requirements, required inspections.
Fences: Maximum height by location (front yard vs. rear), approved materials and colors, restrictions on visibility-blocking fences near intersections.
Storage structures (sheds): Maximum square footage, required setback from property lines, restrictions on visibility from street.
Exterior paint and finishes: Approved color palette (or criteria for what's approvable), requirements for matching existing trim and siding colors.
Additions and structural changes: Process for structural additions, additional documentation required (building permits, engineer approval), post-construction inspection requirement.
Solar panels: Placement requirements, visibility restrictions, approval process.
This document is adopted by board resolution (not by homeowner vote, typically) and becomes the operational policy for ARC reviews. It makes every review faster — because the criteria are written down — and every denial more defensible — because the denial cites the written criteria.
Modern HOA management platforms change architectural review from an email-based process to a trackable workflow:
For a self-managed board handling 20–30 ARC applications per year, the time savings from this shift is measured in hours per application rather than minutes. The legal protection from having complete, searchable records for every decision is harder to quantify but real.
The architectural review process works best when homeowners experience it as helpful rather than adversarial. A few practices that shift the perception:
Publish your criteria. Homeowners who know the rules before they submit an application save everyone time. The ones who design their deck around the CC&Rs submit approvable applications. The ones who don't know the rules submit applications that require extensive revision or denial.
Be responsive. Homeowners with pending applications are living with construction uncertainty. A quick acknowledgment that the application was received and is in review costs nothing and reduces anxiety.
Be specific in denials. A denial that explains exactly what needs to change for the project to be approvable gives the homeowner a clear path forward. A denial that says "inconsistent with community character" leaves them frustrated and confused.
Approve quickly when there's no issue. Applications that clearly comply with all criteria should be approved in days, not weeks. Holding compliant applications for the monthly meeting schedule frustrates homeowners and delays their projects for no reason.
Architectural review that works well is fast for compliant applications, clear about criteria, and fair in its decisions. That's achievable — with a process, a tracking system, and written criteria.
LotWize includes a full architectural review workflow — structured submissions, deadline tracking, and permanent approval records tied to each property.
AI-powered tools purpose-built for self-managed HOA boards. Violations, dues, meetings, and documents — all in one place.
More guides for HOA boards
Before a buyer makes an offer in an HOA community, they do research. What they find — or don't find — shapes their offer price, their confidence, and sometimes whether they make an offer at all.
A closed Facebook group feels like community communication. It isn't. Here's the difference between social media and a website — and what the board is giving up by treating them as the same thing.
A community website isn't a brochure — it's a governance tool. Here are the nine pages and features that actually reduce board workload and build homeowner trust, and what happens when they're missing.