May 2026

Every community's weekly report can now carry a written briefing on the week - what sold, which builders and sections drove it, why contracts cancelled, and how the year is tracking - produced automatically and delivered alongside the report sales teams already receive.

• The briefing is built on figures computed directly from the community's records - gross sales, cancellations, net sales, closings, year-to-date totals, active contracts, and inventory by status - so the narrative and the numbers always agree.
• The briefing is marked beta while it is tuned, and users opt in individually, so it reaches the people who want it without changing anyone else's report.
• The emailed weekly report now opens with a summary block: year-to-date net sales, starts, and closings, plus the week's gross sales, cancellations, net sales, and closings.
• Visitor totals now include group tours and realtor groups, so traffic counts reflect everyone who came through the door.

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.

Homesite pricing, section completion, and buyer detail can now flow into Pipsy directly from a builder's own systems, so inventory and schedules stay current without anyone rekeying them.

• Builder-published lot pricing refreshes on a schedule, so the pricing in reporting and on the public map matches the builder's system of record.
• Development teams can post section completion from their own systems, keeping takedown and delivery schedules aligned with where construction actually is.
• Buyer postal code is captured on reservations, feeding buyer origin analysis from the moment a homesite is held.

Buyers can now shop the community map by homesite type. Lots are colored by type with a legend to match, and the filter bar narrows inventory by type or acreage instead of price alone.

• At wider zoom the map colors by neighborhood, so the shape of the community reads before a buyer picks a single homesite.
• Buyers can sort by smallest homesite or most bedrooms, and status labels use each community's own words for what is available.
• Developer-sold homesites and resale listings each have their own toggle, and one tab lists everything currently available.
• Marketing teams set the order amenities appear in by dragging them into place, and can hide the filter bar or upcoming sections for placements that should stay simple.

Lot contracts, their takedown schedules, and the instructions behind them are now managed in one place, and each contract carries its earnest money position next to its pricing and fee terms. A contract's economics can be read without assembling them from separate screens.

• Earnest money is recorded on the contract and on each section, so deposits held are visible alongside the pricing and fees they offset.
• Sections carry the county they sit in, which flows through district and fee reporting.
• Takedown reports show the community behind each contract, so an operator running several communities can work from a single list.
• Sales managers get their own view of sections, and a takedown schedule no longer has to match a fixed lot count to be saved.

Builders now get an automatic reminder ahead of every scheduled takedown listing the lots coming due, how many remain on the contract, and a link to start the request. Communities can also keep a standing list of people notified before closings.

• The reminder goes out a set number of business days ahead, configurable per client, and only to builder contacts with takedown rights.
• Closing notifications go out two weeks before an estimated closing date to a recipient list set per community.
• New ARC submissions notify the reviewers responsible for them as soon as they land.
• Delivery notices were reformatted so the lots, addresses, and deadlines read clearly in an email.

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.

District reimbursement reporting now breaks out by builder and by lot type, and every table can be run on either the contract sale price or the final closing price.

• The builder and lot type table sits alongside the existing district totals, so a reimbursement package can be assembled builder by builder.
• Switching to closing price uses the figure actually recorded at closing rather than the price written at contract.

Reserved homesites now appear on the lot status map with the date the hold was placed, and a premium homesite progress table tracks how each premium lot is moving by premium type and amount.

• Communities can add their own fields to a reservation and hide contract fields they never use, either everywhere or for a single community.
• The premium table summarizes how many premium homesites there are and what they carry in premium, next to their current status.
• Homesites sold to custom builders now count as developer lots on the lot status map, so the split between builder and developer inventory is accurate.

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.

Communities can hide homesite fields they never use, and the change history on a homesite now names the person behind every edit with the before and after values side by side.

• Any additional field a community has defined can be charted in buyer analysis, and buyers can be filtered by home type.
• The change log is laid out so an edit and its effect are legible at a glance instead of requiring interpretation.

Marketing teams can now see every homesite flagged into the listing feed, resales included, with lot number and neighborhood, so a listing missing from a portal can be traced back to its source.

• The table sits with the rest of a community's web inventory, listing each homesite that was manually flagged for the feed.
• Homesite photos that no longer resolve are cleared automatically, so listings do not publish with missing images.