Builder & ARC

Land bankers can track each builder's credit and covenants and see who is on pace to miss a takedown, and builders holding a facility get their own statement and can request development draws from the builder portal.

• Each builder carries guarantors, financial statements by period, and covenants such as minimum tangible net worth and maximum leverage, with compliance worked out from the latest statement. Overdue compliance certificates land on the weekly pack's attention list.
• Pace risk compares each builder's sales pace with the takedowns still owed and flags who will miss one 60 or 90 days out.
• Builders see a statement covering deposits paid, applied, and at risk, go-hard and expiry dates, extensions left, carry invoices, invested capital, and the next takedown with the capital it needs, and can download it.
• A builder whose facility is linked to a development project can submit draws against that project from the builder portal, and funded draws post to the facility's invested capital.

Builder sales teams can manage their own incentives and mark which of their lots are model homes from the builder portal, instead of asking the developer to make the change.

• Reps see every incentive running against their builders and edit the ones that are theirs alone, while developer incentives that include them are listed and marked as the developer's.
• Builder ARC, sales, and superintendent users can mark a lot as a model home or remove the status once it sells, and answering yes to a community's model home question on an ARC submittal marks the lot automatically.
• Both are turned on per community.

Reviewers can attach conditions and variances to an approval and hold both the final sign off and the deposit refund until they are cleared, and every fee a builder owes now runs through one ledger with statements on both sides.

• Builders clear their open conditions in the builder portal and attach photographs or documents as evidence.
• The fee wallet handles automatic draws, holds that need approval, refunds that need a second signer, reversals, and reconciliation against the ledger.
• Builders get a fee register with their own statements and refund history, and the community exports the ledger to its accounting system.
• A reviewer who approves over a repetition block has to record why, and the override stays with the decision.

Every file on a site plan or a master plan now lives in one library with its full version history, and the home that was finally approved is sealed into a certificate the HOA package carries.

• Files are versioned with the current one in front, marked visible to builders or internal only, archived with a reason and restorable, and every download is logged.
• The current documents download as a single packet with a manifest, and a required attachment checklist shows what a submittal is still missing.
• A birth certificate is issued at final pass, at close, or by hand, recording the approved home and the guideline versions it was judged under, and HOA lot packages carry those certificates with the documents of record.
• Square footage compliance now compares the marketing number against the number ARC approved and flags plans and submittals whose figures disagree.

Builders can submit fence and pool requests through the builder portal, and the community's rules about which homesites may have them are enforced at submittal rather than discovered at inspection.

• Each community defines the form, and a rule that refuses a submittal is quoted beside the field it names.
• Lot flags let a community bar a pool or a fence on specific homesites, and reviewers edit those flags straight from the request queue.
• Conditions attached to a request gate that request only, so a pool condition never holds up the house.
• The queue shows which communities still need their fence and pool inspection templates in place.

Every ARC denial now rests on a cited guideline clause, reviewers can see what is waiting and for how long, and repetition rules are enforced the same way everywhere a plan is shown.

• A clause library is built by pasting in the guidelines, and decision templates write the language around the clause a denial cites.
• The review clock shows what is waiting and how long it has waited, and warns before a deemed approval window closes without approving anything itself.
• An attention queue flags construction seen without an approved plan or running ahead of an open condition, and a confirmed flag becomes a compliance inspection.
• Monotony gains an advisory city overlay pack, material proximity weighting, and wall color groups scoped per community, and the public site is checked against the same rule so a buyer is never shown a plan that would be refused.

Community managers can now see every home that is under or over the square footage its section requires in one report, instead of checking plans lot by lot against the deed restrictions.

• The report reads each section's minimum and maximum and lists the homes that miss it, with the shortfall or overage shown per lot.
• A dashboard widget surfaces current compliance without opening the report, and the same figures carry into the construction report.

Inspectors and field staff can keep working where there is no signal. Compliance inspections and drive mode notes are captured on the device and submitted on their own once the connection comes back.

• A banner shows when work is being held on the device, and a pending list shows exactly what is still waiting to go up.
• A queued submission cannot post twice if the device retries, so reconnecting after a long day in the field does not create duplicate inspections.
• Photos attached to a note are resized on the device, which stops long inspection sessions from crashing phones.

ARC reviewers get more ways to define what counts as repetition, and builders can attest their way past a soft block instead of calling the community manager.

• A scheme match mode flags repeated color and material schemes even when the plans differ, and a plan-or-scheme mode catches either.
• Fields a community does not treat as part of monotony can be left out of the repetition scan.
• Where a rule is a soft block rather than a hard one, the builder can attest and continue, and the attestation is recorded on the submission.
• The ARC Status report uses the same repetition calculation as the monotony map, so the report and the map cannot disagree.

Communities can now set monotony rules per homesite type, so a narrow front street and an estate section are held to different separation requirements instead of one rule stretched across everything.

• Monotony is measured by the distance between homes, which matches how most deed restrictions are written and takes the guesswork out of counting intervening lots.
• The repetition map shows each homesite's ARC status alongside the rule being applied, so a reviewer sees approvals and conflicts together.

Builders can now generate a QR code from the builder portal that opens Community Copilot on a specific home or homesite, ready for yard signs, riders, and model home collateral.

• The code is produced per address, so a sign in front of a home opens that home rather than a community landing page.
• Builders generate their own codes without routing the request through the developer's marketing team.

Builders now see the reason an ARC submittal was rejected instead of only its status, and communities can add their own fields to a color and material scheme so a submittal captures what the guidelines actually ask for.

• The approved scheme is tracked on the homesite and drawn on the repetition map, so a reviewer can see where a scheme has already been used before approving it next door.
• Monotony checks show the range being measured on the map, and submittals carry the neighborhood so a review queue can be worked one neighborhood at a time.
• Submittals capture a square footage breakdown, so minimum size rules can be checked against the figures on the plan rather than a single total.
• Brick is handled as its own exterior material, so masonry selections no longer have to be recorded as something else.

Communities can now define their own fields on an ARC submission and require builders to complete them at submittal, including fields that draw from the community's own material and color lists. Reviewers see the same fields on the review screen and in reporting.

• A custom field can be scoped to one material category, so a roofing field offers roofing products and nothing else.
• Communities can extend the standard material categories with their own, rather than forcing products into categories that do not describe them.
• Field labels follow each community's own terminology through submittal, review, and reporting, so a builder sees the same words that appear in the guidelines.
• Required custom fields are enforced when a submission is made, so a review does not stall waiting on a missing selection.

Communities organized into neighborhoods can now carry that breakdown through reporting. Builder performance, inventory supply, construction status, starts and completes, lot fees, section performance, takedowns, and district reports all show the neighborhood a homesite sits in.

• The weekly report and the inventory health and sellout views break out by neighborhood alongside section, lot type, and builder.
• Floorplans are assigned to the neighborhoods where they are offered, so plan lists reflect what is actually available in each part of the community.
• Approved color and material schemes can be scoped to a neighborhood, so a builder submitting there is offered only the schemes approved for it.
• Neighborhood carries across on homesite imports, so a new section arrives already assigned.

Builders active in more than one community can now switch their dashboard, land pipeline, cash flow projection, and takedown schedule into a company-wide view spanning every community they build in, instead of checking each one separately.

• Inventory health and sellout pacing roll up across communities, so a builder can see where its lot position is thinnest overall.
• Sales pace can be measured against raw elapsed months rather than the standard divisor, for a like-for-like comparison between communities of different ages.
• The builder portal can be set to show only lots that have reached their takedown date, so what a builder sees matches the lots it actually controls.

Communities that track porch conformance on ARC submissions now get a running count of conforming and non-conforming porches, plus a breakdown showing where the misses are concentrated.

• Quick stats show the conforming share across approved and conditionally approved homesites, so a community can see whether the standard is holding.
• The breakdown table splits porch conformance by neighborhood and lot type, so enforcement can be aimed at the builders and sections that need it.

Community managers can now run property compliance end to end - inspect a homesite in the field, record what is out of compliance against the community guidelines, and send the builder or owner a corrections request with a dated report attached. Every notice and response is tracked in one place instead of living in an inbox.

• Inspections are built from reusable templates tied to community guidelines, so the same standards are applied at every homesite.
• Inspectors can work a section lot by lot from a compliance map that shows what is open, corrected, or overdue, including from a vehicle in the field.
• Builders receive a corrections request itemizing each finding, and their responses are recorded against the original inspection.
• Inspection results and material summaries generate as formatted PDF reports, with a distribution log showing who was notified and when.

The ARC submission form and the reviewer queue both got a round of work: builders are shown a cleaner set of choices, and reviewers can sort completed submissions by whether the fee has been paid and by the week the decision was issued.

• Retired materials and colors no longer appear as options on a new submission.
• Material and color lists are consolidated so the same product is not offered several different ways.
• The completed review tab filters by fee status and by weekly reporting period, so the weekly ARC report can be pulled straight from the queue.
• Communities that call their district something other than a MUD can now apply their own name everywhere it appears.

Monotony rules are now configured community by community rather than applied uniformly, and a community that does not restrict repetition can turn the check off entirely. Reviewers stop seeing conflicts that do not apply to the property in front of them.

• Elevation, color, and material repetition are judged against the spacing rules set for that specific community.
• The repetition map reads both the builder's submitted selections and the homesite record, so a repeat is caught no matter which side it was entered on.

A new data check flags homesites where the square footage shown in marketing does not match the square footage on the approved ARC submission, so listing pages and approval records stop drifting apart.

• The data quality report lists each mismatch with both figures side by side, so the wrong one can be corrected at the source.
• Total square footage now carries across on floorplan imports, giving the comparison a reliable figure to check against.
• ARC screens read square footage from the approved submission rather than the marketing record.

Developers and builders now work the same community map in lot pool mode. Developers see which lots are released to the pool and who is holding them, and builders see what is open to them and can reserve a homesite directly from the map.

• The map runs in a developer view or a builder view, so each side reads the pool from its own position without a separate report.
• A reservation is placed from the map and carries a start and end date, so a hold on a lot has a defined term rather than sitting open indefinitely.
• Lot pricing is carried into the pool view, so a builder can weigh cost while choosing from what is available.

Community managers can now maintain the approved color and material schemes for a community and set the defaults on each elevation, so an architectural submittal arrives pre-filled with what the builder actually intends to build.

• Schemes are created and edited in one place, with the colors and materials that make each one up held together.
• Every elevation carries its default colors and materials, and those values fill in automatically when a builder submits a lot, leaving reviewers to check the exceptions rather than re-read the whole submittal.
• The elevation list on a submittal narrows to the elevations that belong to the plan chosen, so a builder cannot submit a combination that does not exist.
• A material outside the approved list can be typed in directly when a builder needs a one-off.

Builders can now open their own lot contracts in Pipsy and read the takedown terms and fee structures that apply to them, instead of asking the developer for a copy every time a question comes up.

• Each builder sees the contracts it is a party to and nothing else, so one portal serves every builder in the community.
• Additional fee structures are supported on a contract, so the view reflects how the deal was actually written rather than a standard template.
• Developers are kept in a single list, so the counterparty on a contract is chosen consistently across land development and lot takedown deals.

Inventory reporting now separates lots a builder already holds from lots that are genuinely open, and adds sale velocity and move-in timing by home type, so supply conversations with builders start from the same numbers.

• A builder assigned only column runs through the inventory health and sellout reports, so committed lots no longer read as available supply.
• Builder inventory supply adds sale velocity by home type and an expected move-in date on every row.
• Supply and demand charts can be read with direct sales included or excluded, and absorption is calculated the same way in the chart as in the table behind it.
• Homes that have arrived on site are called out and color coded in delivery tracking.

Community managers can now pause a builder's architectural submissions in a specific community, so a builder that is out of compliance cannot keep sending new homes through review until the issue is settled.

• The pause is set community by community, so a builder can keep working where it is in good standing while it is held in one place.
• The block applies at submission, which keeps paused work out of the review queue instead of leaving reviewers to sort it out.