Modular Home Inspection Checklist: Factory to Final Walkthrough

A modular project is inspected at multiple stages by different parties for different purposes. The owner’s quality plan should connect approved documents, factory evidence, site inspections, delivery condition, set interfaces, system testing, corrections, warranties, and final acceptance.

Use this guide when: Use to coordinate qualified inspectors and contract acceptance; it is not a substitute for required code or professional inspections.

Decision snapshot

Create an inspection responsibility matrix

List the inspections required by the project's approving authorities and contracts, then identify who requests, performs, records, and closes each one. Factory inspections, site inspections, lender inspections, and an owner's independent inspection can have different purposes. Passing one does not automatically satisfy the others.

The ICC's off-site construction resources describe factory and site oversight within varying state and local systems. California's factory-built housing program provides one concrete state example of manufacturing oversight and installation guidance; other jurisdictions can assign responsibilities differently. Confirm the actual process with the authorities responsible for the parcel and product.

For each inspection, record the trigger and what must remain visible. Some work needs review before it is concealed or before the next trade proceeds. A schedule that says only “inspection at the end” can miss those dependencies.

Give the project owner a readable matrix showing the inspection, responsible party, required documents, result, and correction status. This helps the owner ask informed questions without assuming the inspector's technical role. It also makes gaps visible when the manufacturer and site builder each believe the other party is arranging a required check.

Preserve pre-delivery evidence

Obtain the factory documentation required for the project, including approval identifiers, relevant inspection records, module identification, and the accepted plans. Check that the records correspond to the modules actually being delivered, rather than a similar model or earlier design.

Ask how work concealed in the factory is documented and accepted by the relevant program. Photographs can help explain a condition, but they do not replace an inspection or certification that the authority requires. Preserve them with dates, module identifiers, and context so they remain understandable.

Record unresolved factory items before shipment and determine who will complete them, where, and under what approval. A note that an item will be “finished on site” should identify the scope and responsible party. Otherwise unfinished work can become a dispute after the manufacturer and local trades have moved to different tasks.

Confirm how transportation damage is reported and who inspects on arrival. Keep the pre-shipment condition evidence accessible to the people performing that check. The purpose is a traceable handoff from factory to transporter to site team, not an assumption that factory approval guarantees the condition after travel.

Inspect foundation and delivery interfaces

Before delivery, verify that the foundation has the required approvals and that its dimensions, elevations, bearing points, and connection provisions match the accepted module information. The qualified project team determines the measurements and acceptance criteria. A completed pour or visible foundation wall is not by itself evidence that the interface is ready.

Check utility and service locations against coordinated drawings. Misplaced penetrations can become difficult to correct once modules are set. Confirm that the parties responsible for the factory and site sides have accepted any design revisions affecting those interfaces.

On arrival, the designated team should document module identity, packaging condition, visible damage, and discrepancies through the agreed process. Owners can preserve observations from authorized safe areas, but should not enter transport, lifting, or unfinished work zones to investigate.

Distinguish a delivery condition report from a code inspection and from contractual acceptance. Signing a delivery document can have specific consequences under the agreement, so understand what the form states before the day arrives. Where damage or mismatch is found, notify the responsible parties promptly and record the decision about repair, further assessment, or holding the affected work.

Observe set and connection completion

After placement, the site work must complete the building's structural and service connections according to approved documents and applicable inspections. Ask the builder which connections remain open for inspection and when they will be concealed. Finish trim should not hide unresolved work simply to make progress appear complete.

Coordinate structural, electrical, plumbing, mechanical, and enclosure responsibilities at module joints. A seam can involve several systems, each with a different trade and acceptance requirement. The matrix should make those handoffs explicit so every trade knows what must be completed before the next activity.

Weather protection deserves its own follow-through. Temporary coverings, permanent flashing, roof completion, and site drainage may occur at different times. The Building America drainage guidance illustrates why water needs a managed route away from the foundation; the project's enclosure and drainage design supplies the specific requirements.

An owner walkthrough can identify questions about visible finish damage, doors, or incomplete items, but it does not replace technical inspections. Record observations by location and photo where permitted, then route them to the responsible builder or inspector. Avoid diagnosing a structural condition from appearance alone; request the appropriate professional assessment.

Close with testing and traceable corrections

Final closeout should show which inspections and system tests are complete, which corrections remain, and whether the relevant authority has issued the required occupancy approval. Delivery, set completion, and a visually finished interior are separate milestones from lawful occupancy.

Use a correction log with a specific description, location, responsible party, target date, and acceptance evidence. “Plumbing issue fixed” is difficult to verify. A record identifying the affected fixture, repair, required test, and person who accepted it is more useful. Keep warranty issues and code corrections distinguishable even when the same contractor handles both.

Arrange the owner's orientation for equipment controls, shutoffs, maintenance, warranties, and service contacts. Confirm that manuals and records match installed models. Demonstrations should be performed by the appropriate trades; a homeowner should not be asked to prove the safety of technical systems through improvised testing.

Retain the final plan set, inspection results, correction closeout, occupancy documentation, and relevant factory records in a retrievable package. If some contractual items remain after occupancy, record their status and the agreed completion route. A complete inspection process leaves evidence of what was checked and resolved, rather than only a collection of appointment dates.

Action checklist

• Inspection scope and authority matrix
• Current approved documents and labels
• Foundation acceptance record
• Delivery-condition photos and notices
• Set/connection inspection evidence
• Numbered punch list and verified closeout

Working worksheet

Record these fields in the same working document so the decision can be reviewed and handed off:

1. Item and location
2. Requirement or reference
3. Observed condition
4. Responsible party and due date
5. Verification evidence

Common failure patterns

• Assuming a code signoff is a complete contract-quality inspection
• Waiting until finishes conceal interfaces
• Closing punch items from promises rather than verification

Connect this work

Sequence required reviews in the permit and approval map, verify pre-delivery conditions with the site checklist, and manage scope corrections through the change-order workflow.