Florida HOA architectural review is the operational surface where owners and boards collide most predictably. An owner wants to paint their house, install a fence, put up a pergola, replace a roof, add a solar panel, fly a flag. The board or ARB committee reviews, approves, denies, or conditions. If the procedure is clean, the outcome usually holds. If the procedure is sloppy, the owner gets an unlimited extension on their cure window + a potential selective-enforcement defense.

F.S. 720.3035 sets the statutory floor. Declaration + rules + ARB procedure fill in everything else within that floor. This post is the operational playbook from application intake through appeal.

Beat 1: pre-application education

Before an application arrives, the CAM + board should maintain:

• A current ARB design standards document, circulated to new owners
• A plain-English summary of what requires ARB review vs what does not (fence yes, fence repair maybe, fence paint no, etc)
• Clear information about the 720.3035 specific-reasons rule so owners know the board cannot deny on vague "aesthetic" grounds

Education at this beat closes 30-40% of would-be applications that are actually not-ARB-triggering or would-not-have-been-approved anyway.

Beat 2: application intake

An application arrives via the association's intake channel (ARB portal, email, paper form). Same-day intake actions:

• Log receipt timestamp. The statutory review clock starts now.
• Acknowledge in writing. Include the decision deadline computed from receipt + the declaration's review window (commonly 30-45 days).
• Check completeness. Incomplete applications (missing plans, missing contractor info, missing materials spec) can be returned for resubmission, but a return stops the clock only if your declaration explicitly allows it. If the declaration says "the ARB shall approve or deny within 30 days of receipt," a return does not reset the clock; you have 30 days from original receipt to decide on what you have.

A default-approval risk exists when the declaration says the ARB's failure to decide within the window means approval. Most FL HOA declarations DO contain this language, explicitly or by common-law default. Treating the clock as soft is the single most common intake failure.

Beat 3: preemption check

Several categories are PRE-EMPTED by Florida law + cannot be denied on standard ARB grounds regardless of what the declaration says:

• Solar panels + solar water heaters per F.S. 163.04 + F.S. 720.3075(2) solar-access pre-emption. Board can regulate specific placement for function (not aesthetics); cannot deny the installation outright.
• Flag display per F.S. 720.304(2) flag display rights. Board regulates manner of display + easement placement but cannot ban.
• Rental restrictions per F.S. 720.3075 rental-restriction timing when the restriction would apply retroactively to existing owners.

A first-pass ARB review that tries to deny a solar application on aesthetic grounds, or a rental modification on "occupancy" grounds, invites a pre-suit mediation demand the association will lose. Train the ARB committee to recognize these categories BEFORE substantive review.

Beat 4: maintenance vs alteration classification

Not everything needs ARB review. Per F.S. 720.304 + declaration standards for maintenance vs alteration, a like-for-like replacement of an existing feature is typically maintenance (not reviewable). A material change in dimension, material, or placement is an alteration (reviewable).

Operational classifier:

• Same material + same dimension + same color = maintenance
• Different material OR different dimension OR different color = alteration
• Different placement = alteration
• Addition of a new feature = alteration

This classification matters at two points: intake (do we even review) + enforcement (can we enforce a violation for failing to apply).

Beat 5: substantive review

For applications that pass the preemption + alteration checks, the ARB runs substantive review:

• Compliance with declaration architectural standards
• Compliance with the ARB design guidelines document
• Specific-reasons rule: any denial must cite the specific standard + specific way the application fails to meet it. "Does not match the community aesthetic" is NOT a specific reason. "Proposed fence is 8 feet and declaration maximum is 6 feet" IS.

The specific-reasons rule per 720.3035 is the single biggest defense against a selective-enforcement challenge. An approval based on a specific standard can be enforced; a denial based on a specific standard can hold. A vague "we don't like it" decision on either direction is vulnerable.

Beat 6: decision within window

The ARB must decide before the statutory + declaration window expires. The decision must be in writing, must cite the specific standard applied, and must reach the applicant via the same channel the application came in (usually email for portal submissions).

If the ARB approves with conditions (e.g., "approved provided the fence is 6 feet not 8"), the conditions must be explicit + the applicant must confirm acceptance before the installation proceeds. A conditional approval with a subsequent unapproved modification is grounds for enforcement but only if the conditions were clear.

Beat 7: appeal or reconsideration

Most FL HOA declarations include an appeal procedure to the full board after an ARB denial. Time limits apply; the appeal window is usually 15-30 days from the ARB decision.

The board on appeal:

• Re-reviews under the same specific-reasons rule
• Can approve, deny, or modify the ARB decision
• The board's decision is typically final within the association

After the board appeal, the applicant's next procedural step is F.S. 720.311 pre-suit mediation or (for certain categories) regulatory complaint to DBPR. See the enforcement escalation playbook for the cross-link to dispute resolution.

Beat 8: enforcement of approved terms

Once approved (conditional or not), the ARB's role shifts to enforcement:

• Inspection that the installed work matches the approved plans
• Violation notice if it does not
• Cure window + fine procedure if the violation persists (per the enforcement escalation playbook)

A CAM who approves an application, notes the conditions, and never inspects is setting up a later violation that can't be cleanly enforced because the record is thin. Inspection closes the loop.

The default-approval clock: the single biggest failure mode

If you remember only one thing from this post: the statutory + declaration review clock is absolute. An ARB that misses the decision window risks default approval on an application it would have denied. Once default approval is asserted, unwinding it requires the association to initiate a challenge + prevail, which is expensive + rarely succeeds.

Keep the clock visible. Calendar entries. CAM dashboard widgets. A standing ARB meeting cadence that triggers decisions before any application can age past the window. Whatever the operational solution, the clock is the measurement.

Five ARB failure modes

Observed patterns in post-denial pre-suit mediation demands:

1. Solar panel aesthetic denial. ARB denies citing "does not match neighborhood" without acknowledging 163.04 pre-emption. Reversed at mediation.
2. Clock missed on a borderline application. Decision on day 32 when the declaration gives 30 days. Owner claims default approval; association cannot enforce conditional standards it would have applied.
3. Denial without a specific standard cited. "Does not meet community aesthetic" without reference to the declaration's specific architectural requirements. Owner files appeal; board finds nothing to uphold.
4. Conditional approval with vague conditions. "Approved provided the color is tasteful." Owner installs; ARB claims violation; owner says conditions were unenforceably vague.
5. No post-installation inspection. ARB approves with conditions, never checks. Owner installs variant A; two years later ARB notices + issues violation; owner defends on longstanding-unenforced grounds.

Bottom line

Florida HOA architectural review is a statute-governed workflow with specific timing, specific-reasons rules, and narrow pre-emption carve-outs. A board + CAM + ARB committee that runs the workflow on a checklist approve or deny cleanly within the window + sustain both approvals + denials on challenge. A committee that treats ARB as a subjective exercise creates the exact default-approval + selective-enforcement exposure the statute is structured to surface.

The clock matters. The specific reason matters. The preemption categories matter. Do the work; the statute does the rest.

This post is an operational walkthrough, not legal advice. For any specific ARB application or denial dispute, consult a licensed Florida attorney familiar with HOA architectural review

• covenant enforcement.