County property records
Recorder, assessor, and clerk records reviewed by jurisdiction.
Most commercial property data products ship records. Acren uses records to help buyers build a better deal lead queue, then keeps the source, field meaning, coverage status, display rule, confidence, and open question attached to the lead.
A record can exist and still be unsafe to rely on. A buyer needs to know what source produced it, whether the field can be displayed, what the field actually means, and what must still be checked before outreach, comps, lease research, expense review, or underwriting.
Recorder, assessor, and clerk records reviewed by jurisdiction.
Parcel boundaries, classifications, assessment history.
Secretary-of-state filings and entity registrations.
Recorded conveyances and lien instruments.
Where reviewed sources are available.
Vendor and partner inputs that pass rights and QA review.
| Attribute | Where it lives | Surface |
|---|---|---|
| Source ID | Per-record metadata | Customer-visible |
| Source class | Per-record metadata | Customer-visible |
| Source review status | Per-record metadata | Customer-visible |
| Field-level meaning | Ontology + record | Customer-visible |
| Field-level display rule | Rights review | Drives display |
| Confidence label | Resolver output | Customer-visible |
| Verification gap | Per-record annotation | Customer-visible |
| Cell readiness state | Coverage model | Customer-visible |
| Provenance chain | Pipeline output | Customer-visible on demand |
Each field is tagged customer-visible, generalized, internal-only, or suppressed. The rules are enforced at query and export time, and they are set by rights review — not by the customer. The same field can be customer-visible in one cell and generalized in another, depending on what the source allows in that jurisdiction.
“If a data product cannot tell you the gap behind a record, you are not buying data. You are buying a conclusion. The gap is the part worth paying for.”
| Field | Starting rule | What changes it |
|---|---|---|
| Recorded owner of record | Customer-visible (always) | n/a — recorder source class is public-by-default. |
| Entity officer / agent | Customer-visible | May drop to generalized in jurisdictions with restricted access. |
| Permit type + date | Generalized | Becomes visible after per-agency rights review. |
| Zoning class | Generalized | Becomes visible with a reviewed source feed (rare). |
| Sale price | Customer-visible in disclosure states | Suppressed in non-disclosure states. |
| Operator distinct from owner | Generalized | Becomes visible with a reviewed operator source. |
| Beneficial owner | Internal only | Becomes visible with a reviewed beneficial-ownership source. |
| Code-enforcement record | Internal only (always) | Not surfaced to customers — noise + sensitivity. |
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.
Coverage is reviewed by state license, source rights, field quality, display rules, and QA posture. An access review confirms which fields can support customer-visible deal lead research today and which still need review.