Two of the most failure-prone seams in hospital delivery sit at the edges of the construction contract: the boundary between what the contractor builds and what the owner buys, and the boundary between when the building is "done" and when it can actually admit a patient. This article defines the furnish/install taxonomy for equipment, FF&E, and technology, then shows how to write the contract backward from go-live so that beneficial occupancy, phased turnover, commissioning, and regulatory survey acceptance are enforceable milestones rather than afterthoughts. Both chapters are governance instruments, not procurement trivia: get them wrong and a finished building sits empty waiting on a circuit that was never designed or a survey that was never sequenced.

Why the scope boundary and the activation boundary are governance problems

A hospital is not delivered when construction is substantially complete. It is delivered when it is licensed, surveyed, commissioned, equipped, staffed, IT-integrated, and ready to admit a patient. Both the furnish/install boundary and the activation timeline determine whether that final stretch is a controlled handoff or a scramble.

The unifying failure mode is the same in both cases: orphaned scope falling into a seam. On the equipment side, the seam is between the construction contract and the owner's procurement — an imaging unit arrives but its dedicated circuit, data drop, or floor reinforcement was never designed. On the activation side, the seam is between physical completion and licensed occupancy — the building is structurally "finished" but commissioning, surveys, and IT validation were never built into the schedule or the payment terms, so go-live slips. In each case the remedy is the same discipline: name every responsibility explicitly, in writing, in a version-controlled instrument reviewed at every gate.

Note that the delivery method (DBB, CMAR, DB, IPD) and the broader contracting, procurement, and risk-allocation strategy — including bonding, separate-prime statutes, and payment mechanics — are governed elsewhere. This article assumes those decisions are made and focuses on the two scope/activation boundaries the contract must close.

The furnish/install taxonomy (CFCI / OFCI / OFOI)

Every item destined for the building must be classified by who furnishes it and who installs it. Ambiguity in this classification is the single largest source of dropped hospital scope. The taxonomy resolves it.

Class Furnished by Installed by Typical hospital items
CFCI — Contractor-Furnished, Contractor-Installed Contractor Contractor Built-in casework, headwalls, surgical lights, ceiling-mounted booms, fixed sterilizers, nurse-station millwork
OFCI — Owner-Furnished, Contractor-Installed Owner / vendor Contractor Major imaging (CT, MRI) where the contractor preps infrastructure and the owner/vendor coordinates final placement
OFOI (also seen as FOIC, "Furnished and Installed by Owner/Customer") Owner Owner Movable medical equipment, beds, patient monitors, IT endpoints, infusion pumps, carts

The decisive issue for OFOI and OFCI items is infrastructure design dependency: the building must be designed around the selected equipment's power, data, structural, shielding, plumbing, medical-gas, and HVAC requirements — not a generic placeholder. Several examples carry no margin for late change:

When the selected unit's requirements are not fixed before construction proceeds, the building is either over-built (wasted capacity) or — far more common and far more damaging — under-built, requiring rework discovered at installation or, worse, at survey.

The furnish/install responsibility matrix as the controlling instrument

The taxonomy lives inside a single, comprehensive furnish/install responsibility matrix that spans every equipment, FF&E, and technology item, organized by room and by system. This matrix is the controlling instrument for the entire scope boundary — it should be version-controlled and reviewed at every design and procurement gate, with deviations resolved before the gate closes.

Each line should capture, at minimum: