Owner's representative drawing review on a conventional project has one client and one reviewing relationship: the owner hires someone to check the set before it goes to bid. A public-private partnership doesn't have that single relationship. The public sponsor hands delivery to a special purpose vehicle, which self-performs design-build through its own contractor, financed by lenders who appoint their own technical reviewer to protect the debt. Three parties are now looking at the same drawings, each for a different reason, and none of those reasons is "does this set actually coordinate across disciplines the way the public sponsor needs it to." That gap is exactly where an owner-side drawing review still has to sit, even on a project where it looks, on paper, like someone else is already covering it.
Why the structure changes who's actually checking the set
Most P3s in the U.S. are structured as design-build-finance-operate-maintain concessions running 30-plus years, where a private consortium — the special purpose vehicle, or SPV — takes on design, construction, financing, and long-term operations in exchange for payment from the public sponsor over the life of the concession. That single structural fact changes the review picture completely. On a conventional public project, the owner hires the design team, hires the contractor, and can hire an independent reviewer to sit between them with a direct, unambiguous mandate: catch what's wrong before it costs the owner money. On a P3, the public sponsor doesn't hold either of those relationships. The SPV holds them. The public sponsor's role shifts from "party managing the design and construction" to "party accepting a finished facility and making payments against its performance" — which means the sponsor's visibility into the drawings themselves depends entirely on what review rights it wrote into the concession agreement, not on the kind of direct access a conventional owner takes for granted.
The Independent Engineer is reviewing for the lenders, not for the sponsor
Every P3 financed with debt has an Independent Engineer — sometimes called a lender's technical advisor — appointed to protect the lenders' interest in the project, not the public sponsor's. The Independent Engineer reviews the design, certifies construction milestones as they're reached, and verifies that the design meets applicable standards and that cost estimates reflect actual site conditions, all so the lender group can be confident the debt it's funding is backed by a project that will actually get built and actually generate the payments needed to service it.
That's a real, substantive technical review — and it's easy for a public sponsor's team to assume it covers the coordination question too. It doesn't, structurally, because it isn't scoped to. An Independent Engineer's mandate is drawdown certification and standards compliance for the lenders' benefit; a cross-discipline coordination conflict that doesn't threaten a milestone certification or violate a code standard on its face can clear that review without ever being flagged as the kind of finding a public sponsor would want to know about before it becomes a change order, an operations-phase deduction, or a dispute at handback.
The Independent Engineer answers to the lender group and is scoped to protect the debt — milestone certification, standards compliance, cost-estimate reasonableness. A coordination conflict that doesn't threaten any of those three things can pass an IE review clean and still turn into exactly the kind of RFI, field conflict, or change order a public sponsor would have wanted caught before the set was final.
Where the public sponsor's own review rights actually sit
What review access the public sponsor has over the SPV's drawings is a matter of what got negotiated into the concession agreement, not something that exists by default the way it does on a design-bid-build project where the owner holds the design contract directly. Sponsors that build in explicit design-review milestones — points at which the SPV has to submit drawings for sponsor review and comment before proceeding, not just for lender milestone certification — are the ones with an actual mechanism to catch coordination conflicts before they're locked into a permitted, financed set. Sponsors that rely on the Independent Engineer's review standing in for their own are the ones most likely to discover a coordination gap only once it surfaces as an RFI during construction or, worse, as a performance failure once the facility is operating.
Availability payments make a missed coordination conflict a sponsor problem twice
Under an availability payment structure — the dominant model for U.S. social-infrastructure and transportation P3s — the public sponsor pays the SPV over the concession term for keeping the facility available and performing to spec, with payments reduced when the SPV fails performance standards. Construction cost and schedule risk sit with the private side under this model; the sponsor generally isn't the one writing a change order check when a coordination conflict surfaces during construction. But a conflict that wasn't caught in design and instead surfaces as a performance shortfall once the facility is operating — a mechanical system that can't hit its spec because of a clash nobody resolved, a life-safety detail that doesn't perform the way the drawings implied — turns into an availability deduction the sponsor absorbs indirectly, through the service it isn't fully getting, for the rest of the concession term. The construction-phase risk transfer that makes P3 delivery attractive to a public sponsor doesn't extend to protecting the sponsor from a coordination failure that shows up as an operations-phase performance problem instead.
Handback requirements bring the same question back at the other end
Most concession agreements carry handback provisions — condition and performance requirements the facility has to meet when it reverts to the public sponsor at the end of the term. A coordination conflict baked into the original design doesn't necessarily disappear over a 30-year operating period; it can persist as a standing maintenance or performance issue that the sponsor only fully inherits at handback, well after the SPV and its Independent Engineer are gone. A sponsor with its own coordination review early, against its own drawing set, has a documented basis for what the facility was supposed to deliver — useful leverage at handback that a sponsor relying entirely on the SPV's own record doesn't have.
Key takeaways
- A P3's SPV, its Independent Engineer, and the public sponsor all look at the design — but only the sponsor's own review is actually scoped to catch cross-discipline coordination conflicts on the sponsor's behalf.
- The Independent Engineer protects the lenders: milestone certification, standards compliance, cost-estimate reasonableness. A coordination conflict can clear that review without being flagged.
- A public sponsor's review access exists only to the extent it was negotiated into the concession agreement — it isn't automatic the way direct design-team oversight is on a conventional project.
- Under an availability payment structure, a missed coordination conflict that surfaces as an operations-phase performance shortfall becomes a sponsor cost through deductions, even though construction-phase risk sits with the private side.
- Handback provisions mean a coordination conflict baked into the original design can still be the sponsor's problem decades later — an independent record of what the drawings were supposed to deliver is leverage the sponsor won't have otherwise.
None of this argues against the P3 delivery model — risk transfer for construction cost and schedule is a large part of why sponsors choose it. It argues for writing explicit, independent design-review rights into the concession agreement rather than assuming the Independent Engineer's lender-focused review covers ground it was never scoped to cover. Building an owner's representative drawing review into the project team from day one covers how to set that access up before delivery terms are locked in, and the same continuity challenge shows up on multi-phase owner's representative programs, where the sponsor is again the only party with visibility across a delivery structure other parties can exit. Public sponsors weighing how a P3 review differs from a standard procurement should also see construction document review services for public agencies for how qualifications-based selection and records-law exposure apply regardless of delivery method.
Frequently Asked Questions
Does the lender's Independent Engineer replace the need for an owner's representative drawing review on a P3?
No. The Independent Engineer is appointed to protect the lenders' interest — certifying construction milestones, verifying standards compliance, and confirming cost estimates are reasonable. A cross-discipline coordination conflict that doesn't threaten a milestone certification or violate a code standard outright can pass that review without being flagged as a problem for the public sponsor.
Who actually controls whether a public sponsor can review the SPV's drawings on a P3?
Whatever review rights got negotiated into the concession agreement. Unlike a conventional project where the owner holds the design contract directly, a P3 sponsor has no automatic access to the SPV's drawings — sponsors that want a real coordination check need to write explicit design-review milestones into the agreement before it's signed.
How does an availability payment structure change who bears the cost of a missed coordination conflict?
Construction-phase cost and schedule risk typically sits with the private side under availability payment P3s. But a conflict that wasn't caught in design and instead surfaces as an operations-phase performance shortfall — a system that can't meet spec because of an unresolved clash — becomes an availability payment deduction the public sponsor absorbs through reduced service, for the remainder of the concession term.
Why does handback make coordination review relevant even decades after construction?
Concession agreements typically require the facility to meet specific condition and performance standards when it reverts to the public sponsor at the end of the term. A coordination conflict from the original design can persist as a standing issue the sponsor only fully inherits at handback — a sponsor with its own early review has a documented basis for what the facility was supposed to deliver, which is leverage at that point that relying solely on the SPV's own record doesn't provide.
Is a P3's design-build entity's own QA/QC review enough to catch coordination conflicts?
It's scoped to the SPV's own delivery obligations, not to the public sponsor's interest independently. An internal QA/QC process checking its own team's work carries the same limitation any self-reviewed set does — it isn't an independent check performed on the sponsor's behalf, which is the gap a sponsor-side review is meant to close.