FIELD NOTE 04
Modular delivery
In modular delivery, manage the interfaces before they manage you
Why the highest-risk work often sits between scopes, companies, locations, and phases.
Modular delivery compresses field time by moving work into a controlled manufacturing environment. It also increases the importance of defining every boundary between the module and the world around it.
The interface is where assumptions collide
Inside a well-defined scope, teams usually know their standards and deliverables. At an interface, two parties may both believe the other owns the same connection, clearance, test, document, or decision. The issue may remain invisible until installation, when options are fewer and change is expensive.
Typical interfaces include module-to-host utilities, vendor equipment-to-building services, factory testing-to-site acceptance, and design responsibility across the modular supplier, engineer of record, and construction trades.
Turn boundaries into managed deliverables
An interface register should describe the physical or information boundary, the two accountable parties, the required input, the acceptance evidence, and the date by which ambiguity must be removed. This is more actionable than recording a broad coordination risk.
- Use drawings and marked-up details to make the boundary visible.
- Assign one coordinating owner even when technical ownership is shared.
- Tie open interfaces to design reviews, procurement releases, FAT readiness, and site mobilization gates.
- Escalate assumptions that affect access, utilities, code compliance, or commissioning sequence.
Factory completion is not site readiness
A module can be ready to ship while the receiving site is not ready to accept, connect, protect, or commission it. A credible integrated schedule therefore treats site readiness as its own stream of deliverables, with measurable entry criteria before shipment and mobilization.
This is where visual site verification, logistics planning, access checks, temporary services, and responsibility matrices protect the promise of modular speed.
Close interfaces with evidence
Verbal alignment is progress, but it is not closure. An interface is closed when the agreed condition is reflected in the controlled design, commercial scope, schedule, and acceptance plan. That discipline prevents the same ambiguity from reappearing in another phase.
The result is not simply fewer issues. It is a project team that can preserve speed because the boundaries of the system are understood early.