Skip to main content
Apollo NZ GlobalStart Project Brief

Development & Humanitarian Infrastructure · Free programme-scale guide

Pilot Project vs Full Rollout for Modular Housing Programmes

A pilot is useful only if it tests the things that could fail at scale. This guide shows how to use the first units to validate design, factory production, freight, assembly, utilities, local acceptance, maintenance and handover before a larger programme is released.

Planning guidance — final supplied configuration remains project-specific.
Pilot modular housing project before larger development rollout
01

Define what the pilot is meant to prove

Write down the uncertainties the pilot must resolve: dwelling layout, climate comfort, structural interfaces, local approvals, shipping, unloading, assembly duration, utility connections, finishes, user feedback, maintenance or supplier QA.

A pilot that merely demonstrates that a unit can be built is too narrow for a large programme.

02

Use the real supply chain

Where practical, the pilot should use the intended production factory, packing method, shipping route, receiving process and local installation team. Testing an easier route can hide problems that will reappear during rollout.

03

Measure repeatability

Record labour, tools, lifting time, defects, damaged items, missing parts, drawing queries, local rework and service-connection issues. These records help convert the pilot into a controlled repeat process rather than relying on memory.

04

Capture user and operator feedback

For housing, include household use, privacy, storage, thermal comfort, ventilation, kitchen and bathroom function. For community buildings, include cleaning, staffing, service access and maintenance. Distinguish preferences from genuine operational problems.

05

Release the rollout only after changes are frozen

Close pilot issues, update drawings and specifications, confirm the approved bill of materials, packing method, installation documents, inspection plan, spare-parts list and change-control process before larger production batches begin.

Comparison reference

Pilot-to-rollout decision gate

Planning criterionPilot evidenceReady for rollout whenHold rollout when
DesignUser and project-team feedback recordedCritical layout / performance issues closedMajor unresolved design changes remain
ManufacturingDefects and tolerances recordedQA controls and approved configuration frozenRepeated factory defects remain unresolved
LogisticsPacking, damage, unloading and storage reviewedRoute and handling method provenDamage / access / lifting assumptions remain uncertain
AssemblyLabour, sequence, tools and supervision recordedRepeatable installation method documentedHigh rework or unclear instructions remain
OperationsUtilities, maintenance and spares reviewedLocal operators can support the assetCritical parts or service capability remain unavailable

The appropriate pilot size depends on project complexity and risk. A pilot does not replace local approvals, technical review or contractual acceptance requirements.

Move from knowledge to project

Apply this guidance to the actual site.

Start Project Brief
Project