This is how Neighbors.fyi works for residents.
Start a free community for your HOA
Get help·5 min read·Updated May 17, 2026

Architectural review

How to submit a modification request, what each status means, and the ways your request and the committee’s response stay tied together in one place.

On this page

Submitting a request

From /architectural, the form at the top takes a title, a category, a description, the property the change is for, and any supporting documents. The property selector only shows properties you’re actively linked to as owner or resident.

The default category list covers the usual modifications: addition / remodel, deck / patio, driveway, exterior paint, fence, landscaping, pool / spa, roofing, shed / outbuilding, solar panels, window / door replacement, and other. Your admin can customize this list and attach category-specific instructions or document prompts (“please include a site plan,” etc.).

Plans and photos

Documents are stored in a private bucket. They’re only visible to the requester, the committee reviewing the request, and staff. Each document URL is signed at render time so the link in your card is fresh.

You can attach a primary file (a drawing, a photo) and additional documents with their own descriptions. Adding more documents during the back-and-forth is part of the normal flow. See Editing below.

How review flows

Requests move through seven possible statuses. The “Active” section on the page contains the first four:

submitted. The request has been filed and is waiting for the committee to pick it up. under_review. The committee is actively working on it. needs_updates. The committee responded asking for something more (revised drawings, additional info). updates_submitted. You sent the requested updates back; the committee should re-review.

The “Past” section contains the three terminal statuses: approved, conditionally_approved (approved with admin-supplied conditions you’ll see in the notes), and denied.

Comments and back-and-forth

Every request has a comment thread underneath the card. You can post; the committee (or admins) can reply. Co-residents at the same property can also comment, since arch decisions affect everyone on the title or lease.

When you post, admins are notified. When staff posts, you’re notified. The thread is the canonical record. Anything important the committee tells you should land here so it doesn’t evaporate in a hallway conversation.

Review fees

Some communities charge a per-category review fee. If your community has Stripe payments configured and the category you picked has a non-zero fee, you’ll be sent through Stripe Checkout right after submission. The fee amount is snapshotted at submit time, so if the board later raises the fee, your row keeps the original amount.

If your community doesn’t use Stripe (or the category has no fee), submission just goes straight to the committee for review.

Editing or withdrawing

While your request is in submitted or needs_updates, you can edit everything: title, category, description, documents. After it moves to under_review, edits are locked because the committee is actively working from the version they have.

Editing during needs_updates re-submits automatically
Edits to a needs_updates request flip the status to updates_submitted as part of the save. You don’t need to separately notify the committee; they’ll see the new state in their queue and an “updates ready for re-review” notification fires.

Withdrawing the request also works while it’s in submitted or needs_updates. Withdrawal removes the request entirely (not just hides it).

Like what you’re reading?
Start a free community