Define the community boundary
Reconcile parcels, use classification, addresses, and ownership so a community boundary is reviewable.
Manufactured housing leads with owner, operator, and site-count questions labeled.
Acren helps MHC teams find source-backed community leads from community boundaries, parcel grouping, recorded ownership, operator clues, site-count status, and permit evidence where available. The opportunity memo makes uncertainty visible instead of hiding it.
Manufactured housing recommendation reasons Acren can support.
Label site-count status
Separate source-backed counts from where-available fields and counts that need analyst confirmation.
Separate owner and operator
Use land records and entity filings as the evidence anchor, then label operator clues with confidence.
Review adjacent parcels
Surface ownership-linked adjacency and assemblage questions without overstating community size.
Use permits where available
Treat permit history as a local source layer with issuing-authority limits and explicit gaps.
Route next diligence
Promising MHC leads should move to comps, broker calls, utility review, site-count confirmation, and expense underwriting.
Common verification gaps.
Site count
Often source-dependent; unsupported counts should remain a gap.
Community boundary
Multi-parcel communities need explicit reconciliation and a boundary note.
Operator vs. owner
Disambiguated and confidence-labeled because land owner, operator, and manager can differ.
Permit coverage
Varies by local issuing authority and should be treated as where-available.
Opportunity memo preview
opportunity memo · source-backed
MHC lead · reviewed market · community + parcel match within reviewed source set.
- Why it surfaced
- Community identity, parcel grouping, and owner trail fit the target criteria.
- Supporting records
- REC-DED · ASR-PARC · SOS-ENT
- Confidence
- Source-backed
- Open questions
- Site count, utility posture, sales comps, and expense assumptions need customer review.
- Owner / entity context
- Confidence-labeled entity match; related-property links surfaced.
- Source status
- Reviewed per source class
- Display rules
- Customer-visible fields only; suppressed fields internal-only.
- Next diligence step
- Save to universe; confirm site count; pull comps and expense assumptions.
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
- 1 · Identify community
Reconcile parcels and use codes into a community record.
- 2 · Group parcels
Multi-parcel communities resolved explicitly — no silent collapse.
- 3 · Attach entity
Operator and ownership entities disambiguated and confidence-labeled.
- 4 · Surface gaps
Site count and permit history surfaced as where-available.
- 5 · Review
Weak community grouping or operator/owner ambiguity routed to analyst.
Field-by-field status in manufactured housing.
| Field | Typical status | Notes |
|---|---|---|
| Community identification | Customer-visible | Parcels + use code reconciled |
| Operator vs. owner | Customer-visible · confidence-labeled | Disambiguated explicitly |
| Community boundary | Customer-visible with review note | Multi-parcel resolved explicitly |
| Site count | Where-available | Rarely public; analyst confirmation often required |
| Permit history | Where source is reviewed | Customer-visible by jurisdiction |
| Resident / tenant data | Out of scope | Not surfaced |
What Acren does not know.
Rent roll and occupancy
Acren routes the lead into operator, broker, and diligence review. It does not invent operating performance.
NOI, expenses, and insurance
Those remain customer diligence inputs before underwriting.
Utilities, condition, and capex
Source clues can help where available, but inspections and operating review remain separate diligence.
Market value and proprietary comps
Use sales comps, broker color, and underwriting tools after the lead surfaces.
Seller willingness
Acren ranks research priority, not transaction intent or owner willingness.
How accurate is site count?+
Source-dependent. Where public records disagree or are silent, the field is labeled where-available with a gap.
Operator vs. owner — which is shown?+
Both, when reviewed sources support them. Each carries a confidence label and supporting records.
Is resident data available?+
No. Resident and tenant data are out of scope.
Manufactured housing diligence realities.
Community ID
Boundary first
Parcels and use codes need to line up before a packet is reviewable.
Common gap
Operator
Operator can differ from land owner and needs a separate confidence label.
Site count status
Where-available
Source-dependent. Acren refuses to estimate.
Resident data
Out of scope
Resident and tenant records are not part of the research workflow.
“Site count without a reviewed source is a guess. Acren ships the gap before it ships a number.”
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.
Manufactured housing
Scope MHC leads for your jurisdictions.
Bring your target counties. Acren checks whether parcel, entity, and local source records can support a reviewable community opportunity memo.
Continue
See how each opportunity keeps the source trail attached.