Adjacent properties
Parcel adjacency, ownership relationships, and recorded changes.
Portfolio watchlists monitor reviewed properties, entities, markets, and source updates without losing the evidence trail. Portfolio teams get watchlists, adjacency, and source updates in one reviewed surface.
Parcel adjacency, ownership relationships, and recorded changes.
Reviewed deed and entity updates within scope.
Cell-level changes in source availability or QA state.
Team-shared watchlists with packet context attached.
Source-triggered notifications routed by workflow.
Owned parcels, target adjacencies, and entity watchlists registered.
Each monitored market bound to a reviewed source with clear rights and readiness status.
Deed, assessor, SoS, and permit updates land as packet revisions — not silent overwrites.
Material changes surface in the watchlist where the team already works.
Updates route to the right analyst by workflow and entity scope.
| Priority | Property | Market | Why surfaced | Confidence | Verdict |
|---|---|---|---|---|---|
| High | Ownership change | reviewed market | Deed recorded on adjacent parcel · related to portfolio entity | Source-backed | Reviewed |
| Medium | Source coverage | reviewed market | Assessor source status improved · county now customer-ready | Source-backed | Reviewed |
| Medium | Adjacency | Travis, TX | New parcel split recorded · assemblage candidate updated | Needs review | In QA |
| Change type | Source signal | Surface |
|---|---|---|
| Deed recorded | REC-DED update on monitored parcel | Watchlist + packet revision |
| Entity update | SoS-ENT amendment on monitored entity | Owner watchlist + related-property graph |
| Assessor review | ASR-PARC value or use-code change | Packet revision with prior value preserved |
| Permit activity | PMT-BLD where source is reviewed | Watchlist with permit ledger |
| Coverage change | Cell becomes customer-ready or degrades | Access review updated |
Acren ranks commercial property research priority. It does not infer disposition, hardship, or willingness to transact.
Every recommendation must carry supporting records, field-level rights status, and verification gaps.
Customers are responsible for verifying records before outreach, capital, or workflow decisions.
Customer-visible, generalized, internal-only, and suppressed fields stay visible as product controls.
Bring your portfolio and the adjacencies that matter. Acren binds them to reviewed sources and surfaces changes where the team already works.