Conditions of Approval: What Developers Must Know (and How to Find Them Before Bid)

In short:

• Conditions of approval are the list of requirements a city or county attaches to an approved land use application — often adding 5–40% to total project cost.
• Across our scan of approved rezones nationwide, roughly 47% come with conditions of approval; the median approved rezone carries 8 conditions.
• cityminutes indexes conditions of approval as structured data across the 3,142-county target coverage map, weekly — a field no incumbent bidding or permit platform currently captures.

→ Search conditions of approval by county at /planning/

Direct answer. Conditions of approval are the list of requirements attached by a planning commission or city council to an approved land use application — rezone, variance, special use, site plan, subdivision, or development agreement. Conditions take the form of commitments the developer must fulfill before permits issue, during construction, or after occupancy. Typical conditions include road dedications, stormwater retention, park fees, affordable housing set-asides, setback increases, landscape buffers, and off-site infrastructure contributions. They can add hundreds of thousands — sometimes tens of millions — to a project's total cost. Most pre-bid data platforms don't capture them at all. This is the single biggest overlooked line item in the US pre-permit intelligence stack.

What are conditions of approval?

When a planning commission or council approves a land use application, the approval is almost never unconditional. The commission attaches a list of specific requirements — called conditions of approval (sometimes "conditions of entitlement," "conditions precedent," or "development standards") — that the developer must satisfy. The conditions become part of the approved ordinance or resolution. Failure to comply can result in permit denial, revocation, or an injunction.

Conditions range from the trivial (a 4-ft sidewalk width instead of 3 ft) to the project-defining (a 20% density reduction, a $5M intersection improvement, an affordable housing set-aside). They're negotiated between staff, the developer, and the commission — often in front of a packed room of neighbors during a hearing that can run past midnight.

Types of conditions

In our national scan, conditions fall into eight broad categories:

• Infrastructure — off-site road improvements, traffic signals, water/sewer extensions, stormwater facilities
• Design standards — setbacks, building height, façade materials, landscape buffers
• Impact fees — cash contributions for parks, schools, affordable housing, public art
• Phasing — the sequence in which a project must be built (phase 1 before phase 2)
• Affordability — inclusionary zoning set-asides, deed-restricted units
• Environmental — tree preservation, wetland protection, open space dedication
• Operational — hours of operation, delivery restrictions, noise limits (common for mixed-use)
• Legal / administrative — deed restrictions, maintenance bonds, homeowner association covenants

The eight categories often overlap. A single approved rezone can carry 20–50 conditions across five categories.

How cities negotiate conditions

The negotiation happens in three stages:

1. Staff-level negotiation (pre-hearing). Planning staff draft proposed conditions in the staff report. The developer's team reviews, pushes back, and may negotiate some out. This is usually the quietest and most efficient stage.
2. Planning commission hearing. The commission can accept staff's proposed conditions, add new ones during the hearing, or strike ones they don't like. Community testimony often shapes this — a vocal neighborhood can add conditions that weren't in the staff draft.
3. Council hearing. The council can modify again. In jurisdictions with conditional rezoning, conditions become legally binding on title through a recorded development agreement.

Each stage is an opportunity for cost to expand. A rezone that arrives at staff review with 12 proposed conditions might leave council with 35.

Real (generic) examples of conditions

Examples from our dataset (anonymized to project type):

• A 220-unit multifamily rezone in a Sunbelt metro: 18 conditions including a $1.2M intersection improvement, a 15% affordable set-aside, and a 40-ft landscape buffer on the north property line.
• A 1.2 MSF data center rezone in a Midwestern county: 32 conditions including on-site water reuse, $12M in substation upgrades, a 500-ft setback from residential, 24-hour noise monitoring, and a 10-year property tax abatement contingent on 250 jobs.
• A 400-lot single-family subdivision: 24 conditions including $3.2M in park fees, 2 traffic signals, a 6-ft masonry wall, and phased construction over 5 years.
• A 15,000-sf retail site plan: 9 conditions including architectural review, hours of operation restrictions, and a 12-ft drive aisle width.

None of these conditions show up on a permit portal or a traditional bidding platform. They show up in the meeting minutes, staff reports, and approved ordinances — documents that cityminutes parses structurally.

Cost impact on pro forma

Across our dataset, conditions add roughly 5–40% to total project cost:

• Small residential rezones: 5–12% cost impact
• Large mixed-use: 8–20%
• Data centers and industrial: 10–25% (higher for infrastructure-heavy conditions)
• Contested urban infill: 20–40% (where NIMBY pressure drives conditional reductions in density)

Underwriting a project without knowing the conditions is underwriting blind. The sophisticated developers we've talked to have workflows to surface conditions during diligence — but those workflows are expensive and jurisdiction-specific.

How to surface conditions of approval at bid stage

For pre-construction BD teams at commercial GCs, knowing the conditions before you bid changes everything. You can:

• Scope accurately. Conditions often change scope (e.g., an additional 500 LF of road, different façade materials, extra utility runs). Pricing without knowing the condition is pricing wrong.
• Identify cost risk. A contested project with expansive conditions is a higher-risk bid; pricing should reflect it.
• Sequence the work. Phasing conditions dictate what can be built when, which affects sub sequencing and cash flow.
• Negotiate with the owner. Knowing the owner's condition list lets you propose solutions upfront (e.g., an alternative intersection design that satisfies the traffic condition at lower cost).

The problem has always been: how do you get the conditions? Most pre-con BD teams rely on either the owner handing them over (spotty), calling the planning department (time-intensive), or reading the agenda packet themselves (doesn't scale).

cityminutes solves this by parsing public planning commission and council agenda weekly and extracting conditions of approval as structured data. Nationwide. All 3,142 counties. Weekly refresh. The field no incumbent captures.

The cityminutes 4-field wedge

Conditions of approval is one of four fields both shovels+ReZone and boardwalkai acknowledge are valuable but neither extracts:

1. Conditions of approval (this post)
2. Community objections — the opposition patterns, NIMBY signals, risk intelligence
3. Hearing outcomes — planning commission vote records, council decisions, denials + approvals
4. Staff recommendations — planning staff position (predicts commission vote in ~80% of cases)

Together, they're the "pre-permit data layer" — structured, searchable, nationwide. No other tool has them.

Frequently Asked Questions

What is a condition of approval in planning?

A condition of approval is a requirement attached by a planning commission or council to an approved land use application. It takes the form of commitments the developer must fulfill — infrastructure, design, fees, phasing, affordability, environmental. Failure to comply can result in permit denial or revocation.

What's the difference between conditions of approval and a development agreement?

A development agreement is a negotiated contract between a city and a developer that often codifies conditions of approval plus additional mutual commitments (vesting, phasing, tax sharing). Conditions of approval can exist without a DA; a DA usually contains conditions as a schedule.

Do conditions of approval expire?

Some do. Many jurisdictions include sunset clauses — if permits aren't pulled within 1–3 years of approval, the entitlement (and its conditions) lapses. Other conditions run with the land and bind future owners in perpetuity.

How do I find conditions of approval for a specific project?

Three ways: (1) read the approved ordinance or resolution in the jurisdiction's minutes, (2) request the final development agreement from the planning department, (3) search cityminutes' structured feed at /planning/{state}/{county}/ — we parse conditions from staff reports, hearings, and adopted ordinances across the 3,142-county target coverage map.

Can conditions of approval be modified after adoption?

Yes, usually via a formal amendment process similar to a minor modification or major modification depending on the change. Some modifications require a new planning commission hearing.

Are conditions of approval public records?

Yes. Conditions of approval are part of public adopted ordinances, resolutions, or recorded development agreements. They're always discoverable but often hard to find in practice — which is the problem cityminutes solves.

Related posts

• Planning Commission Meetings: The Complete Guide
• What is a Rezone Application?
• The 2026 Data Center Construction Pipeline Report
• Austin / Travis County Conditions of Approval Tracker

CTA

See conditions of approval before you bid.

cityminutes parses conditions of approval from public planning commission, weekly. The field no other platform captures.

Book a demo →

---

Author bio: Josh Dance is the founder of cityminutes.ai. He spent 4 years reading planning commission agendas by hand before building the first structured national feed of conditions of approval.