Define the community boundary
Reconcile parcels, use classification, addresses, and ownership so a community boundary is reviewable.
AC-MHC · MANUFACTURED HOUSING
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.
By Acren ResearchUpdated August 27, 2026
Manufactured housing recommendation reasons Acren can support.
Label site-count status
Separate source-backed counts from source dependent 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 step
Promising MHC leads should move to comps, broker conversations, utility review, site-count confirmation, and expense underwriting.
Common open questions.
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 source dependent.
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-facing fields only; withheld fields stay internal.
- Next 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 open questions
- →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 shown as open questions.
- 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-facing | Parcels + use code reconciled |
| Operator vs. owner | Customer-facing · confidence-labeled | Disambiguated explicitly |
| Community boundary | Customer-facing with review note | Multi-parcel resolved explicitly |
| Site count | Source dependent | Rarely public; analyst confirmation often required |
| Permit history | Where source is reviewed | Customer-facing 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 deeper diligence.
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 shown as an open question.
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
Source dependent
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
Responsible boundary
Responsible boundary. Not for FCRA-regulated use. Acren organizes commercial-property and business-entity records and ranks research priority from recorded evidence. It does not predict intent, provide valuation or underwriting, or support consumer-eligibility decisions.
Responsible use
Source trail required
Every recommendation must carry source trails, field-level rights status, and open questions.
Responsible use
Review before action
Customers are responsible for verifying records before outreach, capital, or workflow decisions.
Responsible use
Display rules built in
Customer-facing, summarized, internal-only, and withheld 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.
Next step
Start with your market and buy box.
Responsible boundary. Not for FCRA-regulated use. Acren organizes commercial-property and business-entity records and ranks research priority from recorded evidence. It does not predict intent, provide valuation or underwriting, or support consumer-eligibility decisions.