What Does the Shipment-to-Placement Gap Mean for Manufactured Housing Operations?

Published September 3, 2026

Research question

Can the Census Manufactured Housing Survey's shipment, dealer inventory, and placement measures help an operator interpret delivery pipelines, or do the aggregate figures conceal too much to explain why a particular home has not reached an occupied site?

Finding

The Manufactured Housing Survey provides monthly and annual information about new manufactured homes, including shipments and status after shipment. It supports research on broad flows when users follow the published definitions, geography, period, and revision practices. It does not identify the cause of delay for a particular home and should not be used to assign responsibility to a manufacturer, transporter, retailer, installer, community, permitting office, utility, or buyer.

For operations, the survey can sharpen a local milestone vocabulary. A separate home-level record should document factory release, transport stages, site readiness, permits, delivery, installation, inspection, utility connection, and placement or occupancy events as locally defined. Aggregate data provides context. The local file explains the case.

Method and evidence scope

We reviewed the Census Manufactured Housing Survey overview, the survey's purpose and published outputs, its frequently asked questions, and methodology materials. We compared the survey's new-home scope with common operating questions about existing inventory and local delivery timelines.

We did not extract or calculate a current shipment-to-placement ratio. Such a calculation would need a named release, period, geography, size category, seasonal-adjustment choice, and treatment of revisions. The research instead identifies the controls required before a number can be used responsibly.

Shipment and placement are not interchangeable

A shipment is tied to the movement of a new manufactured home from the manufacturing system as defined by the survey. Placement describes a later status under survey definitions. Homes can occupy other reported statuses between those events. Treating all shipped homes as immediately placed erases the pipeline the survey is designed to observe.

The survey's frequently asked questions also distinguish manufactured homes from modular homes and describe limits such as the focus on new homes rather than resale or repossessed units. An operations report that mixes used-home moves, park-owned renovations, modular units, and new manufactured-home shipments is not comparable to the survey merely because every row says "home."

Before comparing a local count, write a crosswalk. State which local event is being compared with which survey definition. If no match exists, say so. A local "delivered" field may mean arrival at a staging yard, entrance to the community, placement on a site, or completion of setup. The survey label should not be pasted onto that field without verification.

Release vintage matters

Census notes that shipment statistics may appear rounded when first released and unrounded later. Published series can also be revised. A reproducible extraction therefore records the release date, download date, table name, period, geography, unit, adjustment status, and whether figures were preliminary or revised.

An operator should retain the source file used for a decision instead of replacing it when a newer release arrives. A revision log can show the earlier value, later value, publisher's release, and whether the change affected an internal conclusion. This is particularly important when a dashboard refreshes automatically and removes the evidence behind last month's note.

Monthly comparisons need calendar discipline. A report may refer to shipment month, placement month, or inventory status at a reference point. A twelve-month sum and an annual table may not be interchangeable if the publisher uses different methods or revisions. The source notes decide, not the similarity of the labels.

What broad data can contribute

Aggregate shipment and placement data can help frame questions about whether an observed local pipeline sits within a period of higher or lower broad activity. It can support a research memo about regional movement or the mix of single-section and multi-section new homes, provided the memo states the series and uncertainty.

It cannot identify a bottleneck at one community. A broad gap could reflect many statuses across many markets. The survey does not read a community's site-work schedule, local permit queue, transporter appointment, weather interruption, utility coordination, punch list, buyer paperwork, or occupancy rule. Assigning one of those causes from an aggregate series would be speculation.

The responsible phrasing is limited: a published estimate moved by a stated amount for a defined period and geography. Any explanation should be labeled analysis and supported by additional evidence. If the evidence is absent, the report should leave the cause unresolved.

Build a local milestone record

For each home, assign a stable identifier and record event dates from source documents. Useful fields can include purchase or allocation reference, manufacturer release, carrier and bill of lading, staging location, site-readiness approval, permit milestones, delivery confirmation, installer assignment, inspection stages, utility authorization, corrections, and closeout. The exact fields depend on the operator's role and jurisdiction.

Each date should have a source and status. "Scheduled," "reported complete," "inspected," and "approved" are different. Preserve the responsible party's wording. If a date changes, keep the original plan and the revised date with a reason source. This creates a duration record without inventing causation.

A virtual assistant can chase missing confirmations, reconcile identifiers, maintain the exception queue, and prepare a handoff. The assistant should not direct transport, approve a site, interpret a permit, certify installation, or promise an occupancy date. Those actions belong to authorized parties.

A two-level comparison

This structure discourages a dashboard from combining incomparable counts. It also lets a reviewer locate the exact document behind a local delay without mistaking the national series for an operational service-level standard.

Limitations

The MHS is a sample survey for defined estimates, and sampling error applies. Monthly regional figures may not reflect a state or local market. New-home statistics exclude important parts of many community pipelines, including used homes and some moves. Published status categories may not match internal software fields.

Local records may contain planned dates rather than completed events. Vendors and agencies can use different identifiers. A missing confirmation does not prove that work stopped. This study cannot determine responsibility, contractual performance, compliance, or the expected completion date for a home.

Evidence-led conclusion

The shipment-to-placement gap is a valid aggregate research subject when definitions and release vintages are controlled. It is not a diagnosis of a local delay. Manufactured housing operators gain more by using the survey to clarify terms, then maintaining source-backed milestones for each home. That pairing preserves national context without sacrificing case-level accuracy.

Sources

1. Census Manufactured Housing Survey
2. About the Manufactured Housing Survey
3. Manufactured Housing Survey FAQs
4. Manufactured Housing Survey methodology

Review other MobileHomeBiz research or learn about administrative support.