What ARC tracking is for
Architectural review (ARC, ACC, or design review) is how associations approve changes to exteriors, structures, and other regulated improvements — decks, paint colors, roofs, solar, fences, lighting, and similar work.
For small self-managed associations, ARC often runs on email threads and a folder of PDFs. That works until an owner starts work without approval, claims they never heard back, or a new board inherits half-finished requests with no dates.
Tracking ARC as cases — not as loose email — gives the committee a due date, a status, a place for plans and photos, and a written decision on the record.
Intake: what to capture on day one
Lot or unit, owner name and email, a clear request title (“deck extension,” “roof shingle replacement”), description of the work, and any required attachments (plans, material samples, photos of existing conditions).
Set a response due date consistent with your architectural guidelines (many documents specify a review window). Assign a board or committee member so requests do not sit unowned.
Confirm whether the request is complete. Incomplete applications should be marked pending documents with a dated note of what is missing — not silently ignored.
During review
Log committee questions and owner replies on the same case timeline. If you ask for a revised drawing, the date of that request matters if the owner later alleges delay.
Keep board-only notes separate from what the owner can see. Owners need the decision and the conditions; they do not need internal debate.
Use a consistent ARC response template for status updates: under review, need more information, approved with conditions, or denied — with the due date for the next board action when applicable.
If the owner starts work before approval, open a related violation case rather than burying enforcement inside the ARC email thread. Mixing approval and enforcement in one unstructured thread creates messy hearings later.
Decisions and the permanent record
Record the decision (approved, approved with conditions, denied) with date and who acted under board authority. Attach the stamped plan or conditions list to the case.
Notify the owner in writing. Prefer an association-logged channel so you can show the decision letter was sent.
Close the ARC case when the decision is final. If conditions require inspection after construction, either keep a clear open task or open a follow-up case rather than leaving “approved” cases open forever without a next step.
Owner communication without homeowner accounts
Small associations rarely want every owner to create software accounts. A practical pattern is login-less case links: the owner receives a secure link to view their ARC case status and submit a response or additional documents.
That keeps the conversation on the case timeline instead of across personal inboxes, while still avoiding a homeowner portal rollout.
Common failure modes in small associations
Requests arrive only as photos in a board member’s text messages. There is no submission date, no assigned reviewer, and no place to attach the final decision letter.
The architectural guidelines say the committee has thirty days, but nobody tracks the clock. An owner starts work after “waiting long enough,” and the board has no dated proof of when materials were complete.
Approvals are announced verbally at a meeting and never written to the owner. Later, the board and the owner remember different conditions.
A denied request is not distinguished from an incomplete one. The owner thinks they were rejected; the committee thinks it is still waiting for a color sample.
How ViolationFlow handles ARC
ViolationFlow tracks ARC requests as cases alongside violations: lot linkage, due dates, statuses (including approved/denied), templated notices (including an ARC response template), photo and file attachments, owner case links, and timeline PDF export.
Escalation ladders and fines are aimed at enforcement; ARC decisions are still human committee work. The product’s job is the record — so a volunteer board can show when a request arrived, what was asked, and what was decided.
For self-managed associations that already track violations in the same tool, having ARC on the same lot history means the next board can see both the fence dispute and the deck approval without hunting through old email accounts.
Frequently asked questions
- Should ARC requests use the same system as violations?
- Using one case system for both keeps lot history in one place. Keep statuses and templates distinct so an approval request is not confused with a fine track.
- How do we handle incomplete applications?
- Mark the case pending documents, list what is missing, date that request, and pause the review clock according to your guidelines until materials arrive.
- Do homeowners need logins for ARC?
- Not necessarily. Many small associations use email notices plus a secure link to view the case and respond, without creating homeowner accounts.
- What should we export for an ARC dispute?
- The case timeline: submission date, requests for more information, owner responses, decision date, conditions, and copies of notices sent.