Zoning and entitlements are the government approvals that stand between land and a project: compliance with existing zoning or a rezoning, variances and conditional use permits, site plan and plat approvals, and the permits that follow. For a developer, the entitlement path is often the real risk in the deal, harder to underwrite than construction and slower than financing, because it runs through public processes with their own rules, timelines, and politics. Managing that path well is a legal discipline, a project management discipline, and a relationship discipline all at once.
Zoning and entitlements have been part of my practice for years, from large-scale development approvals to the single variance that makes a small project work, and my time as counsel to a board of REALTORS gave me a working feel for how these processes look from every chair in the hearing room. This article maps the system so the first public meeting is not the place you learn it.

Which zoning and entitlements does a project actually need?
Start with what the zoning already permits, because the cheapest entitlement is the one you do not need. Every parcel carries a zoning classification with permitted uses, conditional uses available through a hearing process, and dimensional standards for setbacks, height, density, parking, and coverage. A project that fits within the existing envelope needs administrative approvals: site plan review, building permits, perhaps a plat if land is being divided. A project that does not fit needs discretionary relief, and discretion is where timelines stretch and outcomes become political.
The discretionary tools have distinct legal standards. A variance asks for relief from dimensional standards based on hardship particular to the property, and the legal test is stricter than applicants expect. A conditional or special use permit asks for a use the code allows only with case-by-case approval and conditions. A rezoning or planned development asks to change the rules themselves, the heaviest lift with the broadest discretion. Matching the project to the lightest sufficient tool, or reshaping the project so a lighter tool suffices, is the first strategic decision, and it is worth real analysis before the application is drafted.
How does the public process really work?
The formal sequence is knowable: pre-application meetings with staff, application and completeness review, staff report and recommendation, planning commission hearing, and, for the heavier tools, city council or board approval, each with published notice requirements and comment periods. Staff are the constant through all of it, and the professional relationship with planning staff is the most undervalued asset in development. Staff recommendations frame most outcomes, staff know which conditions the commission will want before the commission does, and an applicant who treats staff as adversaries has volunteered for the hard version of the process.
The public dimension rewards preparation of a different kind. Neighbors show up for traffic, drainage, parking, and change itself, and the hearing is the wrong place to meet them for the first time. Early outreach, a willingness to modify the plan on the points that cost the project little, and accurate, calm answers on the points that cannot move will not eliminate opposition, but they change what the decision-makers see: a professional applicant versus a fight. Commissioners are volunteers and elected officials reading the room as much as the code, and the room is manageable.
What gets negotiated with the municipality, and how?
More than most first-time developers expect. Conditions of approval are drafted language, and drafted language is negotiable: the scope of required improvements, the timing of dedications, the specificity of use restrictions, and the triggers for each obligation all deserve line-by-line attention, because conditions run with the project for its life. Development agreements formalize the larger bargains, trading the developer’s commitments on infrastructure, phasing, or public amenities for the municipality’s commitments on approvals, timing, and sometimes vested rights against future code changes.
There are legal boundaries around the bargaining. Exactions, meaning required dedications and fees, must bear a constitutional relationship to the project’s actual impacts, a doctrine that protects developers from open-ended demands and is worth knowing even when you never invoke it aloud. Incentives run the other direction: tax increment financing, abatements, and district tools can materially change project feasibility, and knowing which tools a municipality has used before tells you what is realistic to ask for. The negotiation is a partnership formation, not a transaction, because the municipality is a counterparty the project will live with for decades.
How should entitlement risk be handled in the underlying land deal?
Structure the land purchase around the zoning and entitlements. Entitlement contingencies conditioning closing on final, unappealed approval of the required permits are standard in development deals, along with extended timelines, extension rights priced with additional deposits, and cooperation obligations requiring the seller to join applications the current owner must sign. Sellers accept these structures when the price reflects entitled value, which is the fundamental trade: the developer’s work creates the value, and the contract decides who bears the risk of the government saying no.
Two calendar disciplines protect everything: appeal periods and vesting. An approval is not final until the appeal window closes, and sophisticated deals define approval accordingly, because a granted permit under appeal is not a permit you can build on. Vesting rules, which vary significantly by state, determine when your project’s rights lock against subsequent code changes, and the difference between applying before and after a pending amendment can be the project. Development rewards optimism about what places can become. The entitlement practice exists to make sure the optimism is enforceable.
Frequently asked questions
How long does entitlement take?
Administrative approvals for conforming projects can run weeks to a few months. Variances and conditional uses commonly run two to six months through hearing. Rezonings and planned developments run six months to years, driven by complexity, opposition, and the municipality’s own calendar. The pre-application meeting is where realistic timing first emerges.
What is the difference between a variance and a rezoning?
A variance is relief from specific dimensional standards for one property based on hardship, leaving the zoning unchanged. A rezoning changes the property’s classification and everything that flows from it. Variances are narrower, faster, and governed by stricter legal tests; rezonings are broader, slower, and more political.
Can a city just deny my project because neighbors oppose it?
For discretionary approvals, opposition legitimately influences outcomes, though decisions must still rest on the applicable standards and a record. For uses and dimensions the code already permits, opposition is not a lawful basis for denial, and the distinction is exactly why the choice of entitlement path matters.
Talk with Lori
Development is a negotiation with a counterparty you’ll live with for decades, and it rewards preparation over confrontation. Municipal work has been part of my practice for years at AEGIS Law, licensed in Missouri, Illinois, Florida, and California. Reach me at ldacosse@aegislaw.com.
By Lori DaCosse, Real Estate, Finance & Corporate Attorney, AEGIS Law
Strategic Engagement
Consult with our Managing Partner.
Ready to review your enterprise risk or legacy strategy? Schedule a direct consultation with Scott Levine using the link below.




