Architectural review

Site visits the committee can actually rely on.

Applications come in through your portal. HOACraft puts the ones that need a site visit on the next drive, shows the request next to the community's design rules, and sends back what the reviewer saw and recommends. The committee still decides.

ACC #202: repaint body in Sedona Coral, site review pending, committee window ends Dec 6

From application to decision

HOACraft handles the part in the middle that usually means a separate trip, a phone camera and an email.

Apply

The homeowner applies in your portal. You push requests that need a visit to HOACraft.

Visit

The request joins the next open-items drive, with its review window, so deadlines aren't missed.

Review

Check it against the design rules on site. Record observations, measurements, photos and a recommendation.

Decide

The committee decides in your system. HOACraft takes the request off the route once you post the decision.

Restrictions check for ACC #202: likely conflict with Design Guidelines section 3.1, Exterior Paint Colors, with the rule quoted
Restrictions check

The rule is on screen before you knock

Before the visit, HOACraft summarizes the application and checks it against that community's design guidelines.

  • Likely conflicts are listed with the section and the quoted text, like a coral-pink repaint against an earth-tone palette.
  • Missing pieces are called out: no color sample, no survey, no site review yet.
  • Rules are per community. Desert Rose paint passes in one community and the same request conflicts in another.
  • It informs the reviewer. It never approves or denies.

Recommendation, not decision

Architectural decisions carry legal weight. HOACraft is built so nobody approves anything by accident.

Field review is advisory

Reviewers choose reviewed, more info needed, recommend approval or recommend denial. None of these changes the request's outcome.

Manager-only decisions

If you record decisions in HOACraft, only a community manager can, with no option preselected and an attestation tick.

Review windows

Each request shows when the committee's window closes, so site visits happen in time.

Application in hand

Plans, color samples, surveys and quotes are listed on the request, so the reviewer knows what was proposed.

Measurements and photos

Heights, setbacks and what's really on site, recorded with the time and the reviewer's name.

Ask the documents

"Can they build a shed?" The answer comes from that community's own guidelines, with the section cited.

What your system receives

Applications in, site reviews out

Your portal keeps the application and the decision. HOACraft does the visit.

  • PUT acc-requestsyou push applications that need a visit
  • acc_request.site_reviewedthe review and recommendation, with rules and photos
  • POST …/decisionyou post the committee's decision
POST · acc_request.site_reviewed
{
  "type": "acc_request.site_reviewed",
  "data": {
    "acc_request": {
      "id": "acc-wce-201",
      "number": 201,
      "status": "siteReviewed",
      "request_type": "fence",
      "title": "Replace rear and side fence",
      "location": {
        "address": "113 Willow Creek Dr",
        "lot_number": "Lot 07"
      },
      "decision": null
    },
    "site_review": {
      "outcome": "recommendApproval",
      "observations": "Old fence runs on the survey line; no easement conflict.",
      "measurements": "Proposed height 6 ft, matches neighbours",
      "rules": [
        {
          "document": "Design Guidelines",
          "section": "3.4",
          "title": "Fences"
        }
      ],
      "by": {
        "id": "staff-dana",
        "name": "Dana Whitfield"
      }
    }
  }
}

Clear the ACC backlog on the next drive

We'll load one community's design guidelines and pending applications and run the first site visits with you.