Define coverage cells
Use state, county, asset class, source class, field set, display rules, and QA status as the core cell.
Why county source coverage matters in off-market CRE research.
Commercial property research breaks down when teams treat coverage as a national yes/no. The useful question is county-by-county: which sources are available, which fields are reliable, what can be displayed, and which gaps should stay attached to the packet?
Coverage is not a logo on a data vendor slide.
A source can exist nationally while the local field quality varies county by county. Recorder source status, assessor field names, parcel joins, entity-source readiness, and permit availability all change the reliability of a research packet. Acren keeps those coverage differences visible instead of smoothing them into a single claim.
- Coverage varies by county, source, asset class, and field.
- Display rights can differ from collection rights.
- A coverage gap should travel with the packet until it is resolved.
- The product should show readiness, not imply complete coverage.
The coverage questions that matter.
| Question | Why it matters | Packet output |
|---|---|---|
| Is the source available? | A county may have an assessor site but no usable parcel export or permit feed. | Source class marked customer-ready, source-dependent, or not enabled. |
| Is the field stable? | Same-named fields can mean different things across counties. | Field meaning and source date attached. |
| Is the join reliable? | Parcel, owner, and entity joins can fail on format, stale records, or split parcels. | Confidence label attached to the relationship. |
| Can the field be displayed? | Collection permission does not automatically mean customer-visible permission. | Display rules set per field. |
| Is QA complete? | A feed can be technically ingested but not ready for customer action. | QA status and verification gap remain visible. |
Coverage readiness
Coverage readiness · customer records omitted
| State | County | Asset class | Source | Field quality | Display | QA | Feed |
|---|---|---|---|---|---|---|---|
| FL | Polk | Industrial | Customer-ready | In QA | Customer-ready | Reviewed | Customer-ready |
| FL | Lee | Self-storage | Customer-ready | Field review | Generalized | In QA | In QA |
| FL | Orange | Multifamily | Source identified | Field review | Rights review | Field review | Not enabled |
How to make coverage operational.
Attach source dates
A stale record may still be useful, but the date should be visible to the reviewer.
Separate ingest from readiness
A feed can be collected, parsed, and still not customer-ready.
Keep gaps visible
Missing local ownership, debt, tax, permit, code, and zoning fields should be shown as verification gaps.
Promote conservatively
A cell becomes customer-ready only after source coverage, field quality, display rules, and QA checks pass.
Review after source changes
County websites, endpoints, and field meanings change. A coverage registry should track source status and field-level gaps.
Can a team use national data as a baseline?+
Yes, but national baseline coverage should be distinguished from local record coverage. Acren treats local official-source gaps as packet-level verification gaps.
Does county coverage mean every field is customer-ready?+
No. Field quality, source status, display rules, and QA readiness are reviewed separately.
Why not hide gaps from the customer?+
Gaps are operationally useful. They tell the analyst what to verify before action and help prevent unsupported claims.
Responsible use
Research priority, not seller intent
Acren ranks commercial property research priority. It does not infer disposition, hardship, or willingness to transact.
Responsible use
Source evidence required
Every recommendation must carry supporting records, field-level rights status, and verification gaps.
Responsible use
Verification before action
Customers are responsible for verifying records before outreach, capital, or workflow decisions.
Responsible use
Display rules built in
Customer-visible, generalized, internal-only, and suppressed fields stay visible as product controls.
Continue
Review readiness before expanding a market.
An access review confirms which cells are usable today and which should remain source-dependent or in QA.
Continue
See how each opportunity keeps the source trail attached.