October 2026

Land bankers can now take every takedown from the builder's first draft through settlement and cash received inside Pipsy, and accept cash in lieu when a builder owes lots that do not exist yet.

• Builders draft takedown requests and preview each one before they submit, can require their own approver to sign off first, or can send requests straight from their own system. The review queue flags anything out of phase order, priced on an old pricing version, or touching a lot on hold, and a lot can be held with a reason the builder sees.
• Each facility keeps dated pricing versions by lot type, section, or phase, and the version in force on the closing date prices the takedown. Out-of-order premiums are charged when a builder takes lots ahead of phase and refunded once the earlier phase catches up. Lot contracts accrue interest on an actual/365 or actual/360 basis, and section escalations can move when the escalator starts accruing.
• Settlement is recorded step by step with the date, reference, and documents for each item, cash received is tracked against each takedown with short and late payments flagged, and a final takedown opens a closeout checklist that must be cleared before the facility closes. Cash in lieu is held as a balance and allocated to real lots later, so the builder is never billed twice for the same lot.
• Outside counsel and escrow or title officers get their own sign-in showing only the facilities assigned to them, with takedowns and documents but no dollar figures. LotTrust roles are granted per facility, and every change is kept with its before and after in an exportable audit package that can be put on legal hold.

Land bankers can now handle the parts of a facility that come up once it is live inside Pipsy: crediting deposits to takedowns, taking a builder through default and cure, and holding the schedule to contractual delivery dates.

• Deposits are credited to takedowns as they fund, refunds follow the refundable-until date and whether the option fee is refundable, and the facility shows deposits applied, refunded, at risk, and forfeited. Option fee invoices go out alongside carry invoices, and marking one paid records the deposit.
• A notice of default carries the reason, cure period, and cure-by date, goes out for signature, and ends cured, partly terminated with named lots released, or fully lapsed. Reminders go out ahead of the cure date.
• Delivery dates are set per schedule row or section and checked against the construction forecast, so a facility flags delivery at risk when the forecast runs past the contract date, and takedown relief can be granted as an amendment in one step.
• Carry can float on SOFR or CPI with a spread and a floor instead of prime, facility documents live in a document vault, and an existing book of facilities and takedown schedules can be imported from a spreadsheet.

Land bankers and their accounting teams can now see where every facility stands, what cash is coming, and what to post for the month from one set of numbers, instead of checking each report against their own model.

• The takedown position board shows, for every facility and lot type, what the schedule required, what was taken, credit for lots taken early, the next takedown actually owed, and months of cover. The same figures drive the facility page, the approval queue, reminders, and the weekly pack.
• A 13-week cash calendar and a monthly capital forecast show takedowns, deposits, invoices, and capital returned on the contract schedule or at the builder's actual sales pace, alongside month-over-month book movement, a risk ranking for every facility, and a builder scorecard covering pace, payment, and default history.
• Every LotTrust report sits in one library, and any report view can be saved with its columns, filters, and grouping and shared with colleagues.
• The month-end close ties takedowns, deposits, invoices, and invested capital to a journal that exports to NetSuite or a spreadsheet, with GL accounts mapped per facility or entity, review and approval by separate people, and locked periods. Bank statements import and match each wire to the takedown, invoice, or deposit it paid, and a data warehouse can pull only what changed since its last pull.

Construction managers can now run RFIs, submittals, change orders, and contractor insurance on the project itself, and send a weekly construction report without assembling it by hand.

• Each project and phase has an RFI log and a submittal register showing who has the ball, with due dates, responses, attachments, and a scan for anything overdue.
• Every vendor carries a certificate of insurance with carrier, limits, and expiry, plus prequalification, license, and W-9. An expired certificate blocks pay application approval and shows on draw readiness, alongside missing lien waivers and failed inspections.
• Change orders are tracked as owner or subcontractor changes, contractors can submit them from the vendor portal, and the change order log prints and goes out for signature.
• The weekly construction report covers the forecast, quantities, inspections, weather, and photos as a document or an email, and claimed weather days are compared with observed rainfall at the project's location.

Buyers can see the community in 3D on the public map, with every home drawn at its current stage of construction, so a homesite reads in the context of what is going up around it.

• Homes appear as slabs, framing, roofed, or finished based on their start and completion dates, sized to the lot and dressed with trees, traffic, and people on the sidewalks.
• Each homesite is tagged as a corner lot, a cul-de-sac lot, backing onto open space, or by the direction its backyard faces, and buyers can filter homesites by those tags.
• A sun and shade study shows where the sun sits over the community by month and hour, and a community timeline slider shows the community building out over time.
• A guided camera tour flies between amenities, and amenity pins open a photo gallery.

Community and development staff can log infrastructure problems that do not belong to a lot, such as a downed stop sign or ten light poles that need paint, pin each location on the map, and close them out one pin at a time.

• Each issue carries a priority, photographs, and one or more map pins, and its progress is the share of pins completed.
• Issues can be raised straight from Drive Mode while driving the community.
• Drive Mode notes now offer one-tap site issues such as tidy lot, turn port-a-potty, remove debris, and add trash bin, and the list can be set per community.

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.

Capital partners can pull their own capital account statement for any period and see the returns on each facility they hold, without waiting for a statement to be prepared and sent.

• Statements cover last quarter, quarter to date, year to date, since inception, or a custom period, with a roll-forward preview and a downloadable document that always match.
• Each facility shows contributions and distributions per investor, with the multiple and IRR both at book and projected, valuing the remaining lots at the average funded price.
• Joint venture statements now carry the correct opening balance when run since inception.

Development teams can track stormwater inspections and environmental permits on the project, and follow each phase through municipal acceptance to bond release.

• Stormwater inspections are logged weekly and after half an inch of rain, deficiencies carry a corrective-by date, and permits such as 404, species, and notices of intent and termination are tracked with the project.
• Electric, gas, and telecom are tracked per phase from design through energized, and feed the lot readiness utilities check.
• Each phase moves through the municipal walk, punch, acceptance, and maintenance period to bond reduction and release, and bonds can be edited with exposure summarized across projects.
• Uploading a new version of a project document keeps the old one as history, and documents can be tied to a phase.

Development teams can move project data in and out of the systems they already use, sending approved costs to accounting and bringing in schedules and pay applications instead of retyping them.

• Budget lines carry cost codes and GL accounts, and approved pay applications export as payables and funded draws as journal entries for Sage Intacct, QuickBooks, Yardi, or a generic spreadsheet.
• Microsoft Project and Primavera P6 schedules import as milestones with their predecessors, checked before anything is written, and next month's file moves the same milestones.
• A pay application can be filled from the contractor's G703, either uploaded or pasted, with every match reviewed before it is saved.
• Default notices, change orders, and facility amendments go out for electronic signature and are marked signed when they come back.

One inventory map can now cover several communities with a switcher between them, and a builder can host the community map on its own website showing only its own homes and homesites.

• A multi-community embed offers an All view that merges every community, and leads and activity are tagged with the community they came from.
• A builder-locked embed limits every list, count, and filter to that builder. Other builders' lots stay drawn as part of the site plan but cannot be opened, and a visitor cannot widen the lock from the address bar.

Communities can draw their trail network on the public map, so buyers see where the walking and nature trails run in relation to each homesite.

• Trails are drawn in an on-map route editor or imported from a KML or GeoJSON file, and each trail has its own name and color.
• The public map shows a trail legend, and trails can be switched off for an individual community.

Each community's public map can now be set up on its own from the community's settings, including a map-only view for a community that has no homes listed yet.

• Starting zoom, maximum zoom, the zoom used when a home opens, rotation, the drone aerial, section outlines, boundary shading, legend contents, and every lot status color can be set per community.
• Turning off the list leaves the map filling the widget on desktop and on phones.
• Base map points of interest can be hidden, and a Reset Filters button brings a buyer back to the community's starting view.
• An Incentives Only toggle narrows the list and map to homes carrying an incentive, and a link or embed can open with it already turned on.

Builders can mark floorplan elevations that are only offered in one community, and buyers can browse premium homesites on their own, so the homes and lots a community sells as special read that way online.

• Elevations flagged as exclusive to the community carry a badge on the floorplan and home cards.
• A Premium Homesites button and a site type filter pull premium lots into their own list, with a badge color that matches the map legend.
• Floorplans can carry a maximum garage size, so a plan offered with a two or three car garage reads that way to buyers.
• Homes without a price can be kept off the available list, and printed brochures can include homes already ordered, with their expected delivery dates.

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.