HOA Modification Request Tracking: Why ARC Approvals Go Wrong

The Deck That Was Already Built

An owner emails the board in March asking to build a deck. She attaches a sketch. A director replies, "Looks fine to me, but let me check with the others."

Nobody checks with the others.

In June the deck is finished. In July a neighbour complains that it encroaches on a sightline. The board looks for the approval and finds one email, from one director, containing the words "looks fine to me."

Now what? Tell her to remove a $14,000 deck built in reliance on a board member's reply? Or accept it and explain to the neighbour — and to everyone who followed the proper process — why this one was waved through?

There is no good answer at that point. The good answers were all available in March.

Architectural Review Is a Deadline Business

Here is the thing most boards miss: modification requests are governed by clocks, not just by taste.

Most governing documents — and in many states, statute — specify a response window. Thirty days, forty-five, sixty. Miss it and the request may be deemed approved by default, regardless of whether the committee ever met, regardless of what it would have decided.

Boards lose architectural cases not because they made the wrong call, but because they never made a call at all inside the window. The request landed in a personal inbox during someone's holiday and surfaced eight weeks later.

This is why HOA modification request tracking is a fundamentally different problem from violations. A violation has no deadline pressing on you. An ARC request starts a countdown against the association the moment it arrives.

The Intake Problem

Nearly every ARC failure traces back to intake. Requests arrive:

as an email to whichever director the owner happens to know
as a paper form handed over at the mailbox
as a text message with a photo of a paint chip
verbally, at a barbecue, which is the worst of all

If a request can arrive four different ways, there is no such thing as "the date it was received," and without that date the clock is unmanageable.

Fix intake first. One channel, one form, one timestamp. Everything else in architectural review gets easier once a request cannot enter the system informally. When an owner emails a director directly, the reply should be warm and unambiguous: "Happy to help — please submit it through the request form so the clock starts properly and the committee sees it."

What a Complete Request Contains

A committee cannot decide on a sketch and a hope. Define, publish, and require:

What is being changed, described in plain language.
Dimensions and materials. "New fence" is not a request. "Six-foot cedar privacy fence, west boundary, 40 linear feet" is.
A site plan or survey showing placement relative to boundaries and easements.
Colours and finishes, with actual samples or manufacturer codes.
Contractor and licence details, where the work needs permits.
An expected start and completion date.

Publish this as a checklist. Incomplete submissions should be returned within a few days with the specific missing item named — and be clear in your documents about whether an incomplete request starts the clock. In many communities it does, which is precisely why fast triage matters more than fast decisions.

Write Down the Reasons, Not Just the Verdicts

An approval is easy. A denial is where associations get sued.

A defensible denial cites:

The specific provision relied on, by article and section.
The specific aspect that fails — height, colour, material, setback, not simply "the design."
What would make it approvable, where that exists. "A four-foot fence in the same material would be approved" is enormously more useful, and far more defensible, than "denied."
The appeal route and deadline.

That third point is worth dwelling on. Committees that reply with a path forward see dramatically fewer escalations, because the owner still has a way to get what they want. A flat denial leaves them with only two options: give up, or fight.

The Records That Save You in Year Six

Approvals do not expire from memory the way violations do — they expire silently, which is worse. Five years on, a new board sees a shed that seems to breach the setback rule. Was it approved? Under what conditions? By whom?

Keep, permanently and attached to the property rather than the person:

The original request, with all attachments as submitted.
The date received and the date decided.
Who voted and how.
The written decision, including conditions attached to approval.
Any variance granted, with the reasoning.
Completion confirmation, ideally with a photo.

That last item is routinely skipped and routinely regretted. Approval to build a fence in cedar is not evidence that a cedar fence was built. Photograph the finished work and close the file.

Conditions Need an Owner

"Approved, provided the trim is repainted to match within 60 days" is a perfectly good decision that becomes worthless if nobody checks in 60 days.

Every conditional approval needs a follow-up date and a named person responsible. Otherwise conditions quietly become approvals, and you have taught the community that conditions are decorative. Systems with configurable request types and status workflows handle this well, because the condition becomes an open item with a due date rather than a sentence in a letter.

A Workable ARC Process for a Small Board

You don't need a committee of seven and a 40-page design guide.

One intake form, one channel, automatic timestamp.
Triage within five days — complete or incomplete, communicated either way.
A standing review slot, monthly, on the calendar whether or not there's a queue.
Decisions in writing, always, with reasons.
A follow-up date on every condition.
A photo on completion, filed against the property.

Six steps. The clock never runs out, owners always know where they stand, and in five years someone can answer why the shed on Maple is where it is.

Frequently Asked Questions

What happens if we miss the response deadline? In many jurisdictions and under many governing documents, the request is deemed approved. Check your documents and your state statute — and treat the deadline as immovable regardless of what you find.

Can we deny a request because we don't like how it looks? Only if your documents grant aesthetic discretion, and even then the safer denials cite published standards rather than taste. Vague, subjective denials are the most frequently overturned.

Do we need an architectural committee, or can the board decide? Whatever your documents specify. If they require a committee, board-only decisions can be challenged on procedure alone, independent of the merits.

An owner started work before approval. Now what? Follow your violation process, not your ARC process — it's an enforcement matter at that point. Then decide the underlying request on its merits, separately. Conflating the two weakens both.

Should approvals transfer to new owners? Attach approvals to the property, not the person. A buyer inherits the approved condition, and your records need to show it or you will be re-litigating a 2019 decision with someone who wasn't there.

The Short Version

Architectural review goes wrong in the gap between "someone asked" and "someone decided." Close that gap with a single intake point, a visible clock, and written reasons, and the hard cases become merely difficult rather than expensive.

If you want to see how request workflows, documents, and property history sit together in one platform, take a look at community management in HOAfy.