Most guides to manufactured housing software features list criteria nobody can actually test. "Industry expertise" and "effective resident communication" are not things you can verify in a demo. If you are comparing manufactured housing property management software, the question is not which vendor has the longest feature list. It is whether the system can model the way your portfolio actually operates.

These twelve tests are built for that. Each one is something you can make a vendor show you on screen, and the answers tell you whether a platform was built for lot-and-home operations or adapted from multifamily.

Why Generic Evaluation Criteria Fail

Every vendor in this category claims the same nouns. Accounting, leasing, maintenance, reporting, resident portal. Read four product pages and you will struggle to tell them apart, because at that level of abstraction they are the same. The differences live in the data model. And the data model only shows up when you ask specific questions.

A platform either holds home ownership status as a structured field that drives billing and reporting, or it holds it as a comment somebody typed. Both platforms will tell you they "track homes." Only one of them will hold up across a portfolio spanning two states with different requirements.

So the framework below is deliberately concrete. No criterion appears unless you can ask a vendor to demonstrate it live and watch what happens.

The Operational Areas Software Has to Cover

Before the tests, the domain. Manufactured housing operations break into nine areas, and most platforms cover several of them well and the rest thinly.

The areas a platform does not cover do not disappear. They move into spreadsheets, and the spreadsheets are where the errors are.

The Twelve Tests

1. Split billing on one ledger
Can one resident record carry lot rent, home rent, a loan payment, submetered water and a pet fee as separate charge types, each posting to its own GL account?

Ask to see the ledger. Not the invoice, which can be assembled from anything.

2. Payment application order
Try this live. Pay half of what a resident owes and watch where it lands. Which charge clears first, and can you change it?

This sounds pedantic. It is not. Payment allocation rules can differ by jurisdiction and by lease, so ask whether the order is configurable and whether it can vary by community. Get it wrong across a portfolio and you spend weeks unpicking misapplied payments, usually during an audit.

3. Home as a tracked asset
VIN or serial number, HUD label number, data plate details, manufacturer, make, model, year, dimensions, wind zone. All of it on a home record that links to the homesite without being welded to it.

Then the follow-up that catches people out: what happens to that record when the resident buys the home?

4. Ownership status as a field, not a note
The test nobody thinks to ask, and the one that matters most.

Is tenant-owned versus park-owned a structured field driving billing and reporting? Or is it something a manager typed into a comment box in 2019?

It affects your financing directly. Fannie Mae's manufactured housing communities term sheet states that the percentage of park-owned homes generally may not exceed 25%, with up to 35% allowed alongside a business plan to reduce the percentage over time. If you cannot produce that ratio on demand, answering a lender's question about your portfolio mix becomes much harder than it should be.

It can also drive notice logic, since requirements vary by state and sometimes within a state depending on who owns the home. Our guide to Iowa's Chapter 562B requirements works through one state end to end and shows the shape of the problem.

5. Home inventory and sales
Buying, rehabbing and selling homes is a retail business bolted onto a leasing one. Can a home be held as inventory with a cost basis, accumulate rehab and transport costs, and sell with margin recognised?

Many property management platforms have no inventory model whatsoever. That is why so many home sales programmes run out of Excel.

6. Chattel note servicing
Skip this one if you do not finance home sales. Plenty of operators evaluate for it, buy it, and never use it.

If you do finance: amortisation schedule, principal and interest split, interest income recognition, recorded lien and its eventual release. Ask to see an amortisation schedule on screen rather than described.

7. Utility submetering end to end
Meter register per homesite, read capture in the field, consumption calculation, rate application, charge posting, variance report.

The variance report is where the money is. Ask how anomalous consumption surfaces and what a manager can do with it once it does, because a leak on a submetered line is pure margin loss until somebody notices. Plenty of platforms will show you a consumption chart. Far fewer will connect that chart to the maintenance queue.

8. Allocation where submeters do not exist
Not every community is metered, and not every community can be. Can the platform allocate a master-metered bill by occupancy, home size or a custom formula, and hold different methods for different communities? One rule for the whole portfolio stops working once you own communities in more than one state, since permitted allocation methods and markups vary.

9. Violation and enforcement audit trail
Dated notice, rule cited, cure period, photographic evidence, escalation history, all hanging off the homesite and retrievable three years later when someone asks.

A generic warning letter may leave gaps when you later need to reconstruct what happened. The record needs to show which rule was cited, what the breach was, and what cure period was given.

10. Lease terms and pad lease protections
Can the platform hold and report on lease term, renewal status, notice periods and grace periods per community?

This matters beyond day-to-day compliance. Freddie Mac's paper on tenant protections in manufactured housing communities sets out the eight minimum pad lease protections identified by FHFA under its Duty to Serve mandate, including a one-year renewable lease term absent good cause for non-renewal, 30 days' written notice of rent increases, and a five-day grace period with a right to cure. Where state law does not require them, community owners can adopt them voluntarily. Demonstrating that you have requires reporting on them.

11. Occupancy measured in homesites
Does reporting count occupied homesites against total and usable homesites, rather than counting homes? These are different numbers. Track the wrong one and infill performance is invisible.

12. Multi-entity consolidation and revenue segmentation
Many portfolios hold each community in a separate legal entity. Can the platform run intercompany fees, allocations and eliminations and produce consolidated financials?

And can the P&L separate lot revenue, home rental revenue, home sale margin, utility recovery and ancillary income by community without anyone re-mapping accounts by hand?

How to Weight the Tests

The more of these a platform demonstrates without spreadsheets, custom development or a second system, the better the fit. But they are not equal, and treating them as equal is how buyers end up paying for capability they will never use.

• Tests one through four carry the most weight:
  They are structural. Much of what follows depends on the data model, and a platform that cannot separate the home from the homesite will not produce correct segmentation or correct occupancy figures no matter how good the rest of it looks.

• Tests five and six only matter if you are in those businesses:
  If you own no homes and finance nothing, skip them. I would argue test six is the single most over-bought capability in this category.

• Tests seven through twelve are where a large share of the operational margin opportunity sits:
  They will not stop you buying a platform. They determine whether it earns its cost back.

Questions for the Demo

Give these to every vendor and compare answers side by side.

1. Show me a resident ledger carrying lot rent, home rent, a submetered utility charge and a loan payment.

2. Show me the home record. Where does the VIN live? The HUD label?

3. A resident sells their home to a buyer we have not approved. Walk me through what the system does.

4. A submeter reads 40% above its trailing average. How does the system flag it, and can that exception trigger a work order or review workflow?

5. We own the home on site 42. The resident owns the home on site 43. Show me how the record differs.

6. Show me occupied homesites against usable homesites for one community.

7. Show me consolidated financials across three entities with intercompany eliminations.

8. Which of the above are native, which are configurations, and which need a partner integration?

The last one matters most. Given enough configuration, almost any platform can do almost anything. What you are trying to establish is what you are buying versus what you are building. Where a capability turns out to be a configuration rather than a feature, ask to see the workflow configuration tools themselves, not just the finished result.

What It Costs, and What Is Not in the Quote

Pricing here is opaque. Most vendors quote on enquiry, and published rates rarely cover manufactured housing.
The structures you will encounter:

Per homesite per month:
The most common model, almost always with a monthly minimum that makes small portfolios expensive per site.

Per community:
Rarer. Good if your communities are large, punishing if you own a lot of small ones.

Tiered platform fee plus modules:
Utility billing, screening, e-signature and payment processing frequently price separately.

ERP licensing plus application:
Where the platform sits on an enterprise system, licensing is often per named user rather than per homesite, which flips the maths at scale.

Then there is everything outside the headline number. Ask about each directly:

• Implementation and data migration, usually the largest first-year line

• Payment processing margin, which on a decent-sized portfolio can quietly exceed the software fee

• Per-bill utility billing charges

• E-signature per envelope

• Additional entity fees in multi-entity structures

• Historical data conversion beyond a stated number of years

Build a three-year model at your actual homesite count before comparing headline rates.

Implementation and Data Migration

Timelines vary more than anyone wants to admit. A single-state portfolio with clean data can go live in a matter of months. Add home sales, chattel notes, utility billing or multiple entities and it stretches. The variable is rarely the software. It is the state of the data you are bringing across.

Six migration objects are specific to this category, and generic implementation plans miss all of them:

• Home master records with VIN, HUD label, year, dimensions and current ownership status

• Open chattel balances with amortisation schedules and remaining terms

• Recorded lienholders for every tenant-owned home

• Submeter registers with last read date and reading, because a gap here becomes a billing dispute in month one

• Homesite-level violation history, since escalation depends on what came before

• Park-owned home cost basis, including acquisition, transport, set and rehab

Ask how each one is handled. The answers tell you more about a vendor's real MH experience than the demo does.

Matching the Platform to the Portfolio

Brand matters less than portfolio shape.

• One community, all tenant-owned homes, no submetering:
  A general property management platform is fine. You do not need home inventory, chattel servicing or multi-entity consolidation, and paying for them is waste.

• Several communities, some park-owned homes, submetered utilities:
  This is where general platforms start to strain. Tests one, three, four and seven are the minimum, and a spreadsheet workaround for any of them will eat more staff time than the software saves.

• Active home sales with community-held financing:
  Tests five and six stop being optional. Without inventory costing and loan servicing in the same system as the ledger, the home business and the rental business never reconcile cleanly.

• Multi-state portfolio, entity per community:
  Tests four, nine and twelve dominate. Records that reflect differing state requirements, enforcement history that outlives the manager who created it, and consolidation that does not happen in Excel afterwards.

• Mixed portfolio across MH, RV, self-storage or multifamily:
  Here the MH-only specialists become a constraint rather than an advantage. Look for platforms that model multiple asset types natively.

Conclusion

The evaluation problem in this category is not a shortage of options. It is that vendor pages describe the same abstractions, and buyers have no way to tell which platform actually models a homesite and a home as separate things.

The twelve tests solve that, and they take one demo to run. A vendor who can demonstrate the first four live is worth serious consideration whatever the brand, because everything else rests on the data model. A vendor who answers them in the abstract is describing a roadmap rather than a product.

Two things worth insisting on. Ask what is native and what is configured, because that difference does not appear in the demo. It appears six months into implementation. And build a three-year cost model at your real homesite count, because per-site headline rates and the invoice you eventually receive are rarely the same number.

Run the tests. Take notes. Compare the answers, not the brochures.

RIOO is a property management platform built natively on Oracle NetSuite for property teams managing complex, multi-entity portfolios.

Frequently Asked Questions

1. What features should manufactured housing software have?
At minimum: split billing across lot rent, home rent and utilities on one ledger; homes tracked as assets with VIN and HUD label; tenant-owned versus park-owned as a structured field; utility submetering with variance reporting; a violation audit trail; occupancy measured in homesites; and multi-entity consolidation. Home inventory and chattel servicing matter only if you sell or finance homes.

2. How do I evaluate manufactured housing software?
Run the twelve tests above in a demo and make the vendor demonstrate each one on screen rather than describe it. Weight the first four most heavily, because they test the data model and much of what follows depends on it. Then ask which capabilities are native, which are configurations and which require a partner integration.

3. Can I use regular property management software for a mobile home park?
For a simple portfolio of tenant-owned homes on rented homesites, often yes. It becomes harder once you own homes, sell homes, finance those sales or submeter utilities, because many multifamily platforms model one asset producing one charge and have limited inventory or loan-servicing capability.

4. Why does tenant-owned versus park-owned matter in software?
Because it drives billing, reporting and financing eligibility. Park-owned homes generate a second rent charge and sit on your balance sheet. Fannie Mae's manufactured housing communities term sheet states that park-owned homes generally may not exceed 25%, with up to 35% allowed alongside a reduction plan, so the ratio has to be reportable on demand.

How long does implementation take?
It varies widely. A single-state portfolio with clean data can go live in a matter of months. Home sales, chattel notes, utility billing or multiple entities extend it. The constraint is usually data readiness rather than configuration, particularly home records, open loan balances, recorded lienholders and submeter last-reads.