The three paths to apartment zoning approval in Ohio

Zoning decides what may be built on a piece of land. It also decides who gets to say no, and that is what an investment is exposed to. Three approval paths sit behind most apartment projects, usually introduced as three names. They are three different risks: a schedule, a vote, and a negotiation you then live inside for the life of the property.

The reviewing bodies, and the studies that sit alongside them, are largely common to all three; how a multifamily development deal works puts them in order. Why the same application is routine in one jurisdiction and contested in the next belongs to why a developer builds in six Ohio markets. Which of them a project is on is largely decided by the zoning already sitting on the parcel.

As-of-right approval is a schedule, not a vote

A site is as-of-right, or by right, when the zoning already permits what you intend to build. The question in front of the jurisdiction is compliance, not permission.

Review is administrative. Planning staff and municipal engineering measure the site plan against a written code: setbacks, height, density, parking, landscaping, storm water detention, access, and enough turning room for a fire truck. Comments come back, drawings are revised, and the cycle repeats until the plan conforms. Discretion is narrow: a reviewer is holding a drawing against a standard somebody else wrote.

So the risk is time and cost, not permission. Two things still stop a compliant plan. Utility capacity is physical: a sanitary line with nothing left in it does not care that the zoning is correct. And storm water can force a redesign that costs units — a change to the project that nobody voted on.

A rezoning puts an elected body in the path

A rezoning changes the map. That is an act of legislation, taken by the elected body governing the jurisdiction — a city council, township trustees, a board of county commissioners, depending on where the land sits.

Legislative is the whole difference. That body is not applying a written standard to a set of facts; it is making a policy choice, for reasons that may appear in no code section. Staff and the planning commission can both recommend approval, and the council can still vote no. Approval is not owed: a project meeting every technical standard can be refused by people who do not want it there, and opposition does not have to prove anything.

Nor is a rezoning always final on the night of the vote. Legislative acts can, where local law provides for it, be subject to referendum. A schedule that treats the council vote as the finish line has a gap in it.

Which is why the land contract matters as much as the application. Site control is normally an option or a long diligence period rather than ownership, which lets a developer carry this risk with a deposit instead of the purchase price.

A planned unit development trades flexibility for conditions

A planned unit development — a PUD, or a planned district under whatever name the local code uses — approves a plan rather than a category. That plan and its written text become the rules for the parcel, in place of the district’s schedule of uses and dimensions.

The price is that everything is negotiated, so everything is negotiable. Flexibility on density comes back as commitments: exterior materials, open space, a road built to a public standard, a buffer at a stated depth, a phasing sequence tying buildings to improvements.

The harder half arrives later. Because the plan is the code, a change to the plan is a change to the code. A different unit mix, a building moved to clear an easement, a cladding substitution after prices move — each may require an amendment, in front of the same body, with the same discretion available to it. Flexibility at the front end, rigidity afterwards.

Conditional uses and variances go to a different body

Two mechanisms sit alongside the three paths. A conditional use is one the code contemplates in that district but allows only after case-by-case review against listed standards. A variance is relief from a requirement the project cannot meet.

A variance goes to a board of zoning appeals almost everywhere. A conditional use goes to that board under some codes and to the planning commission under others. Either way the posture is the same, and it is neither administrative nor legislative: a body applying written standards to a record, quasi-judicial rather than making policy.

That is not a technicality. Testimony, expert evidence and written findings do real work, and an appeal runs to the courts on the record the body made. A legislative vote is far harder to disturb afterwards.

Not all relief is equal. Relief from a dimensional standard — a setback, a height, a parking count — is generally judged against a lower bar than relief permitting a use the district does not allow at all. A project depending on a use variance stands on the weakest ground in the system.

The neighbourhood meeting, and what it actually changes

Somewhere alongside the hearings there is a meeting with the neighbours, an area commission, or a civic association — sometimes required by code, often just the right thing to do.

It approves nothing. A supportive room does not bind a council, and a hostile one does not defeat an application by itself. What it changes is the conditions, mostly at the edge of the site: buffer depth and planting, screening along a shared boundary, lighting cutoffs so a parking field does not wash into back yards, construction hours and haul routes, sometimes height stepped down along one property line.

It also changes what elected officials hear, and when. The limit is that some opposition is about the use itself, and no meeting changes that; the value is finding out which kind you have while the land is still under option.

Conditions of approval run with the land

Approval usually arrives with conditions attached, and on larger projects with a development agreement — a contract between the developer and the jurisdiction. Both attach to the property rather than to the person who negotiated them.

That is the part an investor is most likely to miss. Dedicating right-of-way, widening a road, extending a sanitary line, escrowing for an improvement: these survive a sale, and a later owner who was never in the room is bound by them. In a budget they are cost lines. Some are also schedule gates: a certificate of occupancy withheld until a public improvement is accepted leaves the leasing calendar waiting on that improvement.

Conditions also change the project. An approval arriving with fewer units, more parking, or a more expensive facade is a different project from the one that was underwritten, and the difference has to be re-tested rather than absorbed. Our pro formas use untrended rents, so that re-test runs against what the submarket rents for today — there is no assumed rent growth further out in the model to pay for a condition that has already landed. That is a constraint rather than a comfort, and one reason an approved site does not always get built.

Why a developer will pay more for an entitled site

Land has two prices, raw and entitled, and the gap between them is the price of a risk somebody has to carry.

A developer paying up buys the removal of a binary outcome: there is no vote left to lose. It also buys back the schedule spent reaching that vote, which is money: land is carried and design is paid for while nothing is being built.

What is given up is optionality. An entitled site comes with somebody else’s plan and somebody else’s conditions, and if the project you want is not the one approved, you are amending an approval rather than seeking one.

So the diligence on entitled land is documentary. The things to read are the ordinance, the approved plan and its written text, and the development agreement — not the staff report, and not the seller’s summary. They are public records, and the only place the conditions appear in full.

What to ask about a project’s entitlement

• Which path is this on — as-of-right, a rezoning, or a planned district? The answer names the risk before anyone argues the merits.
• What stage is it at, and is it final? A favourable vote can still have an appeal or a referendum window behind it.
• Is investor capital called before or after the approval? Where that sits in the sequence is set out in how a multifamily development deal works.
• What conditions attached, what do they cost, and which of them gate a certificate of occupancy?
• Does the approved plan match the plan the project was underwritten on — unit count, parking ratio, materials?

What an approval does not settle

An entitlement is permission to build. It is not a reason the building works.

An approved site can still miss on cost, on schedule, on lease-up, or on the rate available when short-term construction debt has to be replaced. Those four are a chain rather than four separate probabilities, which is the subject of what happens when a development deal goes wrong; the inputs behind all four sit in a guide to investing in Ohio multifamily real estate.

Entitlements can also be lost after they are won. An approval can lapse if it is not exercised in time, conditions are enforceable against whoever owns the land, and litigation or a referendum can delay a project that already has its vote.

Development is speculative and illiquid, no return is guaranteed, and investors may lose some or all of what they commit. Zoning is jurisdiction-specific, and nothing here is legal advice about a particular parcel; the person to ask about a site is a land use lawyer licensed where the land sits.

The communities that came through this process are on the communities map; how capital is structured around them starts at investing alongside us. To ask about a community’s approvals, put the question to our team.