Assessor parcel files
Parcel IDs, classifications, characteristics, related parcels.
Property resolution, with lineage preserved.
How Acren reconciles parcels, APN histories, and building envelopes across assessor, recorder, and permit records into one canonical property node — with full lineage retained. Splits, merges, condos, and ground leases are first-class, not edge cases hidden in a normalization script.
Inputs.
Recorder filings
Conveyances, mortgages, assignments, splits, replats.
Permit records
Building, electrical, and use-change permits where reviewed.
Imagery deltas
Used to corroborate envelope changes, never as primary record.
Address normalization
Cross-source address normalization with reviewable rules.
Property nodes before packets.
Property records rarely arrive as clean assets. Acren links parcels, addresses, assessor records, recorder references, use classifications, and source records into confidence-labeled property nodes before any record can become a sample opportunity memo.
- Parcel canonicalization
Cross-source parcel ID reconciliation with APN history.
- Lineage build
Splits, merges, replats stitched into a directed lineage graph.
- Envelope reconciliation
Permit + assessor + imagery triangulated to a building envelope.
- Asset class assignment
Class detected; confidence labeled; reviewer override supported.
- Owner binding
Owner-of-record bound to entity graph at edge weight.
- QA + promotion
Reviewed gates; cell promoted to customer-visible only on pass.
Edge case handling.
| Case | How Acren handles it | Why it matters |
|---|---|---|
| Parcel split | Lineage edge from parent to children; parent retired with date | Historical research needs to traverse the split |
| Parcel merge | Merged child carries every parent + timestamp | Avoids silent loss of source records |
| Replat | Replat event recorded; pre/post parcels both reachable | Title and survey work depend on this |
| Condominium | Unit-level parcels rolled into building envelope with unit map | Owner identity exists per unit, not per building |
| Ground lease | Fee vs. leasehold separated; ownership stack per interest | Conflating them is the most common manual error |
| Multi-parcel facility | Facility roll-up with explicit parcel-grouping evidence | Storage / MHC / RV depend on this being defensible |
Opportunity memo preview
conf · 0.92 · source-backed
Property node · reviewed parcel · reviewed market · self-storage facility.
- Canonical parcel
- Current parcel identifier retained.
- APN lineage
- Prior parcel identifiers remain resolvable after splits or merges.
- Assessor record
- Use code and assessment context retained with source posture.
- Recorder record
- Recorded deed · owner-of-record context
- Permit context
- PMT-BLD context retained where local coverage is reviewed.
- Envelope reconciliation
- Permit + assessor + imagery agree within tolerance
- Asset class
- Self-storage · reviewer-confirmed
- Verification gaps
- Rentable area not source-confirmed.
- Display posture
- Customer-visible fields only; suppressed fields internal-only.
Next action
- →Review packetInspect every supporting record
- →Save to universeAdd to reviewed acquisition set
- →Move to needs researchFlag verification gaps
- →Assign analystRoute to team workflow
- →MonitorWatch for source updates
What if assessor and recorder disagree on the parcel?+
Both records are retained on the node with a labeled disagreement. The product never silently picks a winner; the analyst can.
Why imagery only as corroboration?+
Imagery is high-signal for envelope changes and low-signal for legal-record questions. Primary record stays with the agency that issued it.
Can the canonical parcel change over time?+
Yes — splits, merges, replats happen. Lineage is preserved so prior identifiers remain resolvable.
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.
Property methodology
See property resolution in your jurisdictions.
Access reviews include parcel and facility reconciliation readiness.
Continue
See how each opportunity keeps the source trail attached.