Trust & technology
Build status & roadmap
A dated view of what the product is becoming, with implementation progress kept distinct from release availability.
Search the public guides. Your search stays in this browser.
On this page
How to read the status.
Pilot means controlled use with the pilot firm. Implemented / validating means code or a testing workflow exists, but it is not a promise that every supplied build contains it. Planned / gated means work or verification remains before it can be offered as a completed capability.
This snapshot was reviewed on October 5, 2026. It is not a live service-status page, and it makes no delivery-date commitments. Confirm the build and scope supplied to your firm.
The current product foundation.
Scroll horizontally to read the full table.
| Area | Status | Scope |
|---|---|---|
| Desktop report workspace | Pilot | Windows/Mac report preparation, cloud access, narrative assistance and report checks. |
| Workspace administration | Pilot foundation; continuing development | Invitations, roles, seats and administrative activity. |
| Fieldwork | Implemented / validating | Native iPhone/iPad testing and browser collection, reviewed imports and offline preparation. |
| Room and floor-plan capture | Implemented / validating | Supported-device capture and appraiser review of measurements and geometry. |
| Protected storage and recovery | Implemented / validating | Device storage protection, crash recovery, retained revisions and recoverable archives; confirm build coverage. |
| Subscriptions | Implemented / gated | Billing requires separate operational activation and agreed commercial terms. |
What has to be proven next.
Distribution and operational readiness
Validate each packaged desktop release, complete the supported-device matrix and exercise update and recovery paths. Mobile testing and Windows distribution have their own acceptance gates. Automatic desktop updates are not a current offering.
Report completeness and delivery
Expand supported report content and deterministic UAD/MISMO mappings, verify consistency between data, exhibits and PDF, and establish the required delivery and acceptance evidence.
Firm rollout
Use pilot feedback to refine field collection, import review and report writing. Agree on onboarding, billing, support and data-handling commitments before broader availability.
Standards work has explicit limits.
UAD 3.6 is the development direction, with MISMO-based data adapters and validation work. Support for a subset of fields or an official sample does not establish complete authoring or delivery support.
Complete UCDP delivery packaging, GSE software-provider verification and lender/vendor acceptance are not claimed here.
What this docs center will track.
Updates should explain newly available behavior, the affected applications, any changed data flow and remaining limitations. Model changes and security-boundary changes belong in the relevant guide; material data-processing changes also require a privacy-policy review.
For a planned evaluation, start with availability and offerings or contact the product team.