The Role of Public-Private Partnerships in Urban Renewal Initiatives

What counts as a public benefit

When a city gives a private partner something of value, such as land, a tax reduction, extra building height or a streamlined approval, it usually wants something back. Those returns are often called public benefits. Typical examples include:

• a share of housing units priced for lower-income households
• publicly accessible open space, plazas or park improvements
• space for a school, clinic, library branch or community facility
• improvements to streets, sidewalks and utilities beyond what the project itself needs
• local hiring or contracting commitments
• design features such as public art, ground-floor shops or accessible entrances
• environmental measures such as stormwater management or cleanup of contaminated land

Which benefits make sense depends on what the community needs, what the project can afford and what local law allows. In some places the law restricts what a city may demand from a developer; in others, negotiation is wide open.

Why benefits are linked to something the city gives

Public benefits are not free for the developer. Each one reduces the money a project can earn or raises its cost. If a city asks for too much, a project may not go ahead. If it asks for too little, the public gives away value without a fair return.

That is why benefits are usually connected to a tradeoff. For example, a city might allow more floor area through density bonuses in exchange for affordable units. It might offer a long-term lease on public land at reduced rent, or a property tax break through tax abatements, with conditions attached. The more the city gives, the more it can reasonably ask. Careful cities try to estimate what the developer’s costs and returns look like before deciding where the line is.

A hypothetical example of the arithmetic

Numbers show how a simple benefit clause works. The following is invented for illustration only.

Suppose a city agrees to let a developer build 200 apartments, and the agreement requires that 15 percent be set aside as affordable units. Fifteen percent of 200 is 30 units. The other 170 are market-rate.

Now suppose the clause is changed to say the developer must set aside 15 percent of units, but the project is later redesigned to 160 apartments. Fifteen percent of 160 is 24 units, so the affordable total falls from 30 to 24 even though the percentage is unchanged. If the city cared about the number of units, the clause should have said so, for instance by stating a minimum of 30 units regardless of redesign. Small drafting choices change the outcome.

This example also raises questions the percentage alone does not answer. How affordable are the units, and for which income range? For how many years? Are they similar in size and quality to the others? Where are they located within the building?

Writing benefits that can be enforced

Vague language is the most common weakness. Compare two clauses:

• “The developer will make efforts to provide affordable housing.”
• “The developer will provide at least 30 rental units reserved for households earning no more than a stated share of area median income, at rents capped by a stated formula, for at least a stated number of years.”

The second is far easier to monitor. Strong benefit clauses tend to share several traits.

1. Specific and measurable. Quantities, dates, standards and definitions are stated.
2. Tied to milestones. Benefits arrive with the project, not years afterward. For instance, a public plaza should open before or alongside the buildings, not after the last unit sells.
3. Recorded against the property. Long-term obligations are often attached to the land title so they bind future owners, subject to local law.
4. Assigned to someone for monitoring. A named city office is responsible for checking compliance.
5. Paired with remedies. The agreement states what happens if the developer falls short, such as fines, withholding of permits or recovery of subsidies.

The limits of enforcement

Even well-drafted terms are hard to enforce, and it is worth being candid about why.

Cities may lack staff. Monitoring affordable units for decades requires someone to verify tenant incomes, rents and building condition year after year. Understaffed offices may check rarely.

Remedies can be unattractive. Penalties small relative to the profit from violating the term may simply be treated as a cost of doing business. Harsher remedies, such as taking back a building, can be legally complicated and politically painful, and may harm the very tenants the term was meant to protect.

Leverage fades over time. A city has the most bargaining power before approvals and land transfer. Afterward, the developer already has what it needed, and the city’s main threat is a lawsuit.

Ownership changes. If a building is sold or refinanced, new owners or lenders may not fully understand the obligations, and the original developer may no longer exist as a viable entity.

Conditions shift. If market conditions turn, a developer may ask to reduce benefits to keep a project alive. Cities then face a hard choice between accepting less and watching the project stall.

Benefits can be hollow. A plaza that is formally public but little used, or a community room that no organization can afford to run, technically satisfies a clause without delivering much. Operating and maintenance funding deserve as much thought as construction, as the question of maintenance funding for public spaces shows.

Making the process more likely to deliver

• Involve residents early. People who live nearby can tell the city which benefits matter, and can notice when promises are not kept. Community participation before the deal is signed is more useful than a protest afterward.
• Publish the terms. Public benefit commitments should be available for residents to read and track.
• Require regular reporting. Annual reports from the owner, with audits where appropriate, make quiet noncompliance harder.
• Hold security. Some agreements require a bond, deposit or letter of credit so the city has money available if the developer defaults.
• Plan for review. Build in points where outcomes are evaluated and adjustments can be considered.
• Keep expectations modest. A project can usually carry only so much. Choosing a few priorities and doing them well generally beats a long list of weakly defined promises.

Honest trade-offs

Public benefit requirements can improve what a project gives the community, and they can also raise the cost of building, which may reduce how much is built or slow its pace. Economists and planners disagree about how large these effects are in different markets. There is no formula that guarantees a fair deal, and results differ across places. What can be said with confidence is that a benefit written in plain, measurable language, backed by a real monitoring plan, is more likely to be delivered than one left to goodwill.