Mandate context
The reason the property belongs or does not belong in the team’s acquisition agenda.
Acren explains why a property surfaced, who appears connected, what records support the read, what is uncertain, and what the next diligence step should be.
The reason the property belongs or does not belong in the team’s acquisition agenda.
Owner/entity context with relationship labels and source references where display rights allow.
Recorder, assessor, tax roll, state entity filing, permit, environmental, market, and QA status where available.
Missing or conflicting fields remain visible so the team knows what to verify before underwriting.
A clear route into comps, broker calls, lease research, expense review, owner verification, watchlist, or pass workflows.
| Buyer moment | Memo answers | Still outside the memo |
|---|---|---|
| Pipeline review | Which leads deserve time and why | Final pursuit decision |
| Owner research | Who appears connected and what supports the read | Authority, legal review, and contact path |
| Diligence assignment | What should be checked next | Sales comps, lease research, expenses, site work, and underwriting |
| Investment decision | What the record can and cannot support | Price, terms, returns, and investment judgment |
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.
The public sample uses illustrative records only and shows how the memo format keeps the recommendation and evidence together.