When to Use & Trade-Offs (Value-for-Money Test)

A public-private partnership (P3) is a heavyweight delivery vehicle — long-term, capital-intensive, and procurement-intensive — that earns its complexity only on a narrow band of projects. This article is the decision filter: when a P3 (typically DBFOM/DBFM) is the right call for a healthcare facility, when a conventional delivery method serves better, and how owners formally test the proposition through a value-for-money (VfM) analysis. It assumes you already understand the DBFOM structure, concession/risk/financing mechanics, and FM scope split covered by the sibling Articles in this Part; here the focus is purely the go / no-go and method-selection judgment.

P3 is a public-sector tool, not a generic delivery method

P3 belongs to public owners — state and provincial health authorities, public hospital systems, academic medical centers tied to a public university, county and municipal health districts, and federal facilities (VA, military medical commands). The defining premise is that a public sponsor wants a facility built, financed, and kept in good working order for decades, but prefers to pay for it through long-run availability payments rather than fund the capital up front and self-perform lifecycle maintenance.

That premise rarely fits a private not-for-profit or investor-owned health system in the US. Those owners already access tax-exempt or corporate debt at rates that beat private-consortium financing, they treat real estate and facilities as a core competency, and they value the speed and control of conventional delivery (CMAR, design-build, or design-bid-build). For most US private healthcare construction, P3 is simply not the question on the table.

So the first test is structural, not financial:

Is the sponsor a public body with the legal authority to enter a long-term concession? Many US states still lack enabling P3 legislation that covers social/vertical infrastructure (as opposed to roads and bridges). No enabling statute, no P3.
Does the sponsor genuinely want to offload lifecycle operation, or only to procure construction? If only construction, P3 is the wrong tool and a design-build or CMAR contract is the honest answer.

The international evidence base for healthcare P3 is far deeper than the US one. Canada (especially Ontario, British Columbia, and Quebec under Infrastructure Ontario / "AFP" branding), the UK (the now-discontinued PFI/PF2 hospital programs), and Australia (state health-infrastructure P3s) have delivered scores of acute-care hospitals through availability-based concessions. US healthcare P3 activity concentrates in public university medical centers, VA facilities, and the occasional state or county hospital — and even there it remains the exception.

Scale and bundling are the threshold conditions

P3 carries large fixed transaction costs: multi-stage procurement, external legal/financial/technical advisors on both sides, lender due diligence, and a special-purpose vehicle (SPV) that must be capitalized and governed. Those costs are roughly fixed regardless of project size, so they only amortize sensibly across a large capital program. As a rule of thumb, healthcare P3s pencil out at the scale of a new or substantially replacement hospital or a major tower/campus, not a renovation, a fit-out, or a single department.

Two conditions, taken together, are what actually justify the model:

Sufficient capital scale — large enough that the transaction overhead is a small fraction of total value, and large enough to attract competitive consortium and lender interest.
A meaningful bundle of lifecycle scope worth transferring — i.e., the project genuinely benefits from binding the designer-builder to the long-run maintainer/operator so that whole-life cost is optimized rather than first cost.

If either condition is missing, P3 loses its rationale. A large project with no lifecycle bundle is better served by design-build; a project with rich lifecycle value but small scale cannot absorb the transaction cost.

Threshold perspective	P3 is plausible when…	P3 is a poor fit when…
Capital scale	New/replacement hospital, major tower or campus	Renovation, fit-out, single-department or service-line project
Sponsor type	Public authority with concession power	Private not-for-profit / investor-owned system
Lifecycle intent	Sponsor wants 20–35 yr maintained-asset outcome	Sponsor wants construction only
Financing premise	Off-balance / availability-payment funding is the goal	Sponsor has cheaper tax-exempt/corporate debt and wants to use it
Risk appetite	Willing to pay a premium to transfer lifecycle + cost-overrun risk	Owner can absorb and manage these risks more cheaply itself

The core trade-off: whole-life optimization and risk transfer vs. cost of capital and flexibility

Every P3 decision is a balance of a handful of competing forces. Understanding which way each one points for a given project is the substance of the analysis.

What P3 buys you

Whole-life-cost discipline. Because the same consortium designs, builds, and maintains for the concession term, it is incentivized to invest in durable systems, maintainable details, and energy performance rather than cutting first cost at the expense of operating cost. This is the single strongest argument for healthcare P3, where building systems (HVAC for ASHRAE 170 pressure/air-change compliance, normal/essential electrical per NEC 517 and NFPA 99/110, medical gas, life safety per NFPA 101) are expensive to operate and punishing to neglect.
Genuine risk transfer. Design errors, construction cost overruns, schedule slippage, and long-run maintenance/performance risk move to the private partner — and, critically, stay there, because availability payments are reduced (deducted) when the facility falls short of contracted condition or availability standards.