How to Get Efficient Service Delivery Out of Public Private Partnerships (Without the Headache)

The phone rings at 2:30 on a Tuesday. It’s your finance director, and you already know that tone. Capital reserves are flat. The arterial road upgrade just slipped back onto the wait list. And the council wants to know—again—how far the letters PPP can stretch before the next election.

Take a breath before you answer. There is a version of public private partnerships for efficient service delivery that actually works. It looks nothing like the glossy investor deck. There are no drone shots of shimmering hospitals. Instead, it looks like a whole lot of unglamorous process design, which is precisely where most deals go to die.

Let’s unpack the real problem first, because it isn’t the acronym.

The Problem Isn’t the Private Sector

Most PPP failures don’t happen at financial close. They happen in year four, after the opening euphoria fades and a contractor discovers the drainage design didn’t quite match the geology. Suddenly nobody can remember exactly who took the ground-condition risk. The lawyers get involved. Service quality dips. The media smells blood.

Here’s the kicker: the private sector partner is rarely the villain. The real culprit is usually a public authority that structured the deal around a spreadsheet rather than around behavior.

When you sign a 25-year contract, you are not buying a bridge or a hospital or a water treatment plant. You’re buying a stream of decisions that a future management team will make on your behalf, under pressure you can’t fully predict. That’s why the contract matters less than the incentive architecture around it. Get the incentives right, and the contract basically administers itself. Get them wrong, and your best lawyers won’t save you.

Three Failure Patterns to Unlearn

Before we dive into the how-to, you need to recognize what usually breaks. After decades of watching deals across transport, health, water and social infrastructure, these three patterns show up over and over:

Pattern one: The output spec was actually an input spec. The authority specified the thickness of the asphalt, the brand of the MRI machine, and the number of janitors per floor. Then a fat consultant billed them for “innovation” that the spec made impossible.

Pattern two: Risk was transferred on paper, retained in reality. The private partner “took” the patronage risk, but when revenues fell, the government quietly renegotiated rather than watch the project go bankrupt. Everyone knew this would happen from day one.

Pattern three: Nobody in the public sector was left holding the operational knowledge. Two years after close, the best procurement officers got promoted. The contract landed in the hands of a generalist with an overflowing inbox. The private partner, meanwhile, had a full-time contract management team. Guess who steered the relationship?

Memorize those three patterns. Every step below is basically an antidote to one of them.

Step 1: Define the Service, Not the Asset

Here’s the first discipline: write the outcome before you draw the asset. Don’t start with “a 12-meter-wide bridge with two lanes and a cycle path.” Start with “a reliable crossing that moves 14,000 vehicles and 800 cyclists per day, with 99.5% availability during peak hours.”

That shift in language changes everything downstream. When you specify an asset, the private partner builds it, hands it over, and shrugs when it performs poorly. When you specify an outcome, the private partner owns the problem of how to achieve it.

Fix the outcome, then let the market propose the solution. You’ll be stunned at how often the private sector finds a cheaper way to deliver the same result—sometimes with a completely different asset. One water utility in Australia avoided an entire desalination plant by fixing leaks and changing pricing signals. That’s the kind of outcome a good output spec makes possible.

Step 2: Build a Business Case That Survives Contact with Reality

Public private partnerships for efficient service delivery are only justified when they deliver better value than the public sector doing the job alone. That’s not a political statement; it’s arithmetic.

You need a public sector comparator—a detailed estimate of what the project would cost if government delivered it conventionally. Then you compare that against the proposed PPP cost, adjusted for risk transfer, innovation potential, and the time value of money.

This sounds obvious. In practice, it’s often theater. The comparator gets padded to make the PPP look good, or the PPP gets a rosy discount rate that flatters the numbers. Either way, the decision is made before the analysis, and the analysis just becomes a costume.

Don’t do that. Build a brutal, honest business case. If the PPP doesn’t beat the comparator through genuine efficiency gains, cancel the project and move on. The IMF’s guidance on public private partnerships is a useful place to check your assumptions, especially around fiscal affordability and hidden liabilities. Treat affordability as a hard constraint, not a negotiating variable.

Step 3: Allocate Risk According to Control, Not Negotiating Power

Risk allocation is where deals are won and lost. The golden rule is simple: allocate each risk to the party best able to control it.

That sounds like management consulting nonsense, so let’s make it concrete. Construction cost overruns? The private partner controls construction, so they carry that risk. Patronage on a toll road? The government controls zoning, competing infrastructure and broader transport policy, so the government probably carries a meaningful share of that risk. Inflation? Whoever has the better ability to forecast and hedge carries it.

The mistake happens when risk becomes a bargaining chip. One side pushes risk onto the other not because it makes sense, but because the other side is desperate. Then the whole allocation collapses in year five, and everyone ends up in arbitration.

That table is a starting point, not gospel. Every project has its own quirks. But if your risk register shows clean, single-column ownership for every single risk, you’re probably fooling yourself. The messy middle is normal. Expect it.

Step 4: Stop Confusing Financial Close with Success

Here’s the industry joke: a banker, an engineer, and a public works director are looking at a toll bridge. The banker says, “We financed it.” The engineer says, “We built it.” The public works director says, “It’s been open for 30 days, and nobody’s sued anyone yet. Looks like a success.”

Everyone laughs, and then they all renegotiate the toll rates by Christmas. Jokes in infrastructure are funny because they’re structurally honest.

Financial close is the beginning of the relationship, not the end of it. Yet most public authorities treat the signing ceremony like a finish line. Champagne gets popped. Photos get taken. And then the contract gets filed in a drawer for three years.

Break that instinct. The day after financial close, you need to stand up a dedicated contract management function with the same caliber of people who ran the procurement. They need budget, authority, and a direct line to elected officials. This is not a retirement posting for a mid-level bureaucrat. It’s the single most important job in the project.

Step 5: Build a Payment Mechanism with Teeth

A PPP payment mechanism is the list of rules that determines how much the private partner actually gets paid, month by month. It should reward performance and punish failure. In theory.

In practice, most payment mechanisms are written by engineers who love detail and lawyers who love ambiguity. The result is a 90-page document that nobody can actually operate.

Ask yourself a simple question: if service delivery drops by 20%, does the private partner’s revenue drop by 20%? If the answer is “not really,” your payment mechanism is decorative.

Payment mechanisms work best when they’re simple, measurable, and automatic. Availability payments should be abated automatically when the asset isn’t available. Performance deductions should be tied to verifiable customer outcomes. And deductions should hurt enough to change behavior, but not so much that they push the partner into financial distress. You’re trying to align interests, not bleed the partner dry.

This is the heart of getting better service delivery from any partnership structure—money conversationally attached to results.

Step 6: Plan for Renegotiation Before You Sign

Every PPP will face renegotiation. Not might. Will. Materially. Because the contract is 25 years long, and nobody can predict technology, demographics, or political priorities that far ahead.

The question is whether renegotiation will be structured or chaotic.

A structured renegotiation process has ground rules agreed in advance. It includes transparent change protocols, a clear valuation methodology, and a dispute resolution ladder