A homeowner wants to build a deck. They submit something. Six weeks later nobody has responded, they build it anyway, and the association discovers it when a neighbour complains.

Every part of that sequence is a process failure, and the one that usually causes the most damage is the six weeks of silence.

Architectural review is an area where community associations can create serious enforceability problems, not because the standards were necessarily wrong, but because the process was not followed, not recorded, or not applied consistently.

This covers what a complete submission looks like, how the decision window works, what conditional approvals and denials require, and what happens when work goes ahead without approval.

Where the Authority Comes From

Before any of the process, the authority matters, because a decision made without it may not be enforceable.

• The declaration or CC&Rs. The governing documents create the review body, define its scope, and set out what requires approval. An association cannot review what its documents do not give it authority over.

• The committee's constitution. Most declarations specify how the committee is appointed, how many members it must have, and who appoints them. A committee that does not match the requirements in the governing documents may create a question about whether it has authority to make the decision.

• Adopted guidelines. Many associations adopt architectural guidelines under authority in the declaration. Where they exist, they are what homeowners are actually measured against, and they need to have been adopted properly.

• State law. Statutes in many states address community association governance, and some address architectural authority directly. Florida is a useful example: under Fla. Stat. §720.3035, an association's authority to review and approve plans is permitted only to the extent it is specifically stated or reasonably inferred in the declaration or in published guidelines authorised by it, and the association must reasonably and equitably apply and enforce those standards on all parcel owners. Requirements differ by state, and the distinction between Florida's condominium and homeowners' association frameworks shows why the applicable chapter matters.

Two practical consequences. A manager taking on a new community should read the declaration's architectural provisions before processing a single request. And where the committee is not properly constituted under the documents, that is a governance problem to fix before it becomes a disputed decision.

What a Complete Submission Contains

Most delay is caused by incomplete submissions, and most incomplete submissions are caused by nobody saying what complete means.

Publish the requirements. A working list:

• Owner name, property address and contact details

• A description of the proposed work

• Dimensions and location on the lot, usually on a plot plan or survey

• Materials, colours and finishes, with samples or specifications

• Elevations or drawings where the work is structural or visible

• The contractor, where one is engaged

• Proposed start and completion dates

• Any permits obtained or applied for

• Neighbour acknowledgement, where the documents require it

Say what happens to an incomplete submission. Whether the review period starts on receipt or on completeness is a significant question, and the answer should come from the governing documents rather than from practice. Where the documents are silent, the association should take advice on when the review period begins rather than assume that completeness resets the clock. Any intake procedure should also be communicated to homeowners in advance and applied consistently.

Acknowledge receipt, with a date. This simple step can prevent avoidable disputes about whether a request was received and when the review period began. The homeowner knows their request arrived, and the association has a record of when the clock started.

The Decision Window

This is where associations most often create problems for themselves.

Governing documents commonly specify a period within which the committee must respond. What happens at the end of that period is the critical question, and it varies:

• Some documents provide that a request is deemed approved if not acted on

• Some provide that it is deemed denied

• Some are silent, leaving the position to be argued

• Some state statutes address the question directly

Find out which applies to each community you manage, and put it in the calendar. A manager handling several associations under different declarations cannot rely on a general rule, because there isn't one.

Where silence may operate as approval, the review period is not an administrative target. It is a deadline with a consequence, and missing it may result in the request being deemed approved, depending on the governing documents or applicable law, even though the committee never issued an affirmative approval.

Three practical steps:

• Diary every request on receipt, with the response deadline calculated from the applicable provision.

• Escalate before the deadline, not after. A committee that cannot reach a quorum needs to know a week out, not two days late.

• Record the decision date, not just the decision.

Approving, Conditioning and Denying

• Approval should state what was approved, specifically. "Approved as submitted" is fine when the submission was specific. It is worthless when the submission said "new fence."

• Conditional approval is the most useful tool and the most commonly mishandled. Conditions need to be capable of being complied with and checked: a stated material, a stated colour, a setback distance, a completion deadline. "Subject to being tasteful" is not a condition. Every condition should be something you could later confirm was met or not met.

• Denial requires the most care. It should state the specific provision or guideline the proposal does not meet, what the problem is, and whether an amended submission would be considered. A denial that says only "does not meet community standards" is difficult to defend and difficult for the homeowner to act on.

• Consistency is the real test. A decision that departs from how similar requests were treated needs a reason recorded at the time. This is covered in more detail below, because it is where most enforceability is lost.

Appeals and Reconsideration

Many governing documents provide a route to appeal a committee decision to the board, and some state statutes address hearing rights.

Where a route exists, the denial should say so: what the homeowner can do, by when, and to whom. A homeowner who is not told they can appeal, and later discovers they could have, has a legitimate grievance separate from the merits of the decision.

Where the board hears an appeal, the record matters. What was submitted, what the committee decided and why, what the homeowner argued, and what the board concluded. A board decision with no recorded reasoning is hard to rely on if the matter goes further.

When Work Goes Ahead Without Approval

Three situations, and they are not the same.

1. Work started without any submission. The homeowner never asked.

2. Work started after submission but before a decision. Sometimes because the review period had expired and the homeowner believed it was approved, which brings the decision window question back into play.

3. Work that departs from what was approved. Approved as one thing, built as another. Common with materials and dimensions.

In each case, the association's position depends on the governing documents, applicable statute and the enforcement record. What the process should produce is a clear, dated record of what was submitted, what was decided and when, so that the question of what was authorised is a matter of fact.

Enforcement itself, including notice requirements and any hearing rights, is governed by the documents and by state law, and the remedies available differ substantially between jurisdictions. That is a question to take advice on rather than resolve from a general process.

Selective Enforcement Is the Real Risk

This is the part worth understanding properly.

Selective enforcement, waiver and estoppel have all been addressed in community association case law, and the specific rules vary by jurisdiction. In some states the point is now statutory: Florida requires associations and their architectural committees to reasonably and equitably apply and enforce architectural standards on all parcel owners. The practical effect is that an association which has not enforced a standard consistently may find it harder to enforce against a particular homeowner.

The same principle appears across property types. As the guide to rule enforcement and violation tracking puts it in a manufactured housing context: if several properties have unapproved structures and you have noticed one, you may create an argument for the other owners that the rule has not been enforced consistently.

What that means for architectural review:

• Know what is already out there. An association enforcing a standard should know how many existing non-compliant installations it is choosing not to pursue.

• Record every decision, including the permissive ones. An approval granted as an exception needs a recorded reason, or it becomes evidence that the standard is not really the standard.

• Be able to answer the comparison question. "You approved that one" is the first thing a homeowner says. The answer has to be either a distinguishing fact or an acknowledgement, and both need the record.

• Treat a change of position as a change of position. An association that decides to start enforcing a previously ignored standard is in a different situation from one that has always enforced it, and that usually calls for advice before the first notice goes out.

What to Keep

For every request:

• The submission as received, with the receipt date

• Any request for further information and the response

• The date the review period started and when it expired

• The decision, its date, and the reasoning

• Any conditions attached, in checkable terms

• The decision letter as sent, with delivery evidence

• Any appeal, and its outcome

• Completion confirmation or inspection, where required

• Any subsequent enforcement action

The test: for any structure in the community, can you produce the file showing whether it was approved, on what terms, and when? Where the answer is no, the association's position on that structure rests on memory.

Where the Process Breaks Down

• No stated submission requirements. Homeowners submit whatever they think is relevant and the review period starts on an incomplete file.

• Receipt not acknowledged or dated. Nobody can establish when the clock started.

• The review deadline not diaried. The most expensive failure, where silence may operate as approval.

• Vague conditions. Conditions that cannot be checked cannot be enforced.

• Denials without reasons. Hard to defend, and they give the homeowner nothing to work with.

• Appeal rights not communicated. A separate grievance regardless of the decision's merits.

• Decisions made outside the committee. A manager or board member approving something informally, outside the process the documents require.

• No record of exceptions. Approvals granted as one-offs with no reason recorded, which later read as inconsistency.

Frequently Asked Questions

1. What should an architectural review submission include?
Owner and property details, a description of the proposed work, dimensions and location on the lot, materials, colours and finishes, drawings or elevations where relevant, contractor details, proposed dates, permit status, and any neighbour acknowledgement the governing documents require. The association should publish its requirements so homeowners know what a complete submission looks like.

2. What happens if the committee does not respond in time?
It depends on the governing documents and applicable state law. Some provide that a request is deemed approved if not acted on within the stated period, some provide the opposite, and some are silent. Managers handling several communities should establish which applies to each and diary the deadline accordingly.

3. Can an architectural approval be given with conditions?
Generally yes, where the governing documents permit it. Conditions should be specific enough to be checked later, such as a stated material, colour, dimension or completion date. Conditions expressed as general standards are difficult to enforce.

4. What should a denial say?
The specific provision or guideline the proposal does not meet, what the problem is, whether an amended submission would be considered, and any right to appeal with the deadline and process. A denial citing only general community standards is difficult for the homeowner to act on and difficult for the association to defend.

5. What can an association do about work built without approval?
The position depends on the governing documents, applicable state law and the association's enforcement record. Remedies and the procedure for pursuing them differ substantially by jurisdiction, and this is a question to take advice on rather than resolve from a general process.

6. Why does inconsistent enforcement matter?
Selective enforcement, waiver and estoppel have been addressed in community association case law, and in some states the duty is statutory. Florida, for example, requires architectural standards to be applied and enforced reasonably and equitably on all parcel owners. An association that has not enforced a standard consistently may find it harder to enforce against a particular homeowner, which is why the record of every decision, including permissive ones, matters.

The Process Is the Authority

An architectural standard is only as strong as the process that applies it.

A committee properly constituted under the documents, a published submission requirement, an acknowledged receipt with a date, a decision within the applicable window, reasons recorded, and a file that shows how every similar request was treated. Where that exists, a disputed decision is answered by producing the record.

Where it does not, the association is defending a standard it may not be able to show it applied consistently, and that is a much harder position than the merits of any individual case.

RIOO keeps community records, resident communications and property data in one platform, so a request, the decision made on it and any subsequent enforcement remain attached to the property they relate to. That sits across community manager portal and service requests and task management.

Note: Guidance in this article is general and does not constitute legal advice. Architectural review authority, submission and decision requirements, deemed approval provisions, appeal rights, enforcement remedies and hearing procedures are set by each association's governing documents and by state law, and differ substantially between jurisdictions and communities. Confirm the requirements that apply to each community, and take legal advice before pursuing enforcement.