Skip to main content
CityMinutes.ai

Wedge field 1 of 4

Conditions of Approval

Numbered conditional clauses imposed on every approved project — affordable set-asides, traffic impact fees, setbacks, dedications, phasing triggers. Extracted as structured data from every US planning commission, weekly.

Definition

What it is

When a planning commission or city council approves a rezoning, variance, site plan, or development agreement, they almost never approve it clean. They attach a list of conditions the applicant must satisfy before the approval runs with the land — infrastructure commitments, setbacks, fees in lieu, affordable set-asides, tree-preservation ratios, traffic mitigation obligations, school-site donations, park dedications, phasing requirements, and the dozens of other commitments that quietly rewrite the pro forma.

Each of those conditions is a number that flows into an IRR model. A 200-unit affordable carve-out can swing project economics by 4–9% on an otherwise pencil-thin deal. A $4.2M traffic fee either kills a deal or doesn't. No permit feed carries this data — permits are terminal documents and conditions only exist in searchable form inside meeting minutes and staff reports.

Real example

City of Phoenix Planning Commission, Z-2025-1142

Salt River Mixed-Use Corridor. Applicant requested rezoning of a 42-acre parcel from Industrial to Mixed-Use Residential. Commission approved 6–1, conditioned on a minimum 50-ft setback from the Salt River ordinary high-water mark; 200 units of deed-restricted affordable housing at 60–80% AMI; a $4.2M traffic impact fee escrowed before certificate of occupancy; a 15% tree-canopy restoration plan approved by the city arborist before grading; and completion of a dedicated left-turn pocket on 40th Street by the end of Phase 1.

{
  "case_number": "Z-2025-1142",
  "jurisdiction_id": "az-maricopa-phoenix",
  "applicant": "Salt River Mixed-Use Partners LLC",
  "outcome": "approved_with_conditions",
  "vote": { "yes": 6, "no": 1 },
  "conditions": [
    {
      "condition_id": "Z-2025-1142-C01",
      "category": "setback",
      "raw_text": "Minimum 50-ft building setback from the Salt River ordinary high-water mark.",
      "source_pdf_page": 14
    },
    {
      "condition_id": "Z-2025-1142-C02",
      "category": "affordable",
      "raw_text": "200 units of deed-restricted affordable housing at 60–80% AMI.",
      "source_pdf_page": 14
    },
    {
      "condition_id": "Z-2025-1142-C03",
      "category": "fee",
      "dollar_value": 4200000,
      "deadline": "before_co_phase_1",
      "raw_text": "$4.2M traffic impact fee escrowed before certificate of occupancy on the first building.",
      "source_pdf_page": 15
    },
    {
      "condition_id": "Z-2025-1142-C04",
      "category": "tree",
      "raw_text": "15% tree-canopy restoration plan approved by the city arborist before grading.",
      "source_pdf_page": 15
    }
  ]
}

Why it matters

The most under-appreciated variable in entitlement underwriting

For Land Acquisition, conditions are the single largest gap between what an entitlement memo says a parcel can do and what it will actually deliver after commission. For Developers & Investors, they're a live diligence checklist on acquisition targets — every condition on a comparable rezone in the same jurisdiction is forward-leading signal on what your own deal will get hit with. For Pre-Construction BD, conditions surface the off-site infrastructure scope the owner will need to bid out — early warning for specialty trades.

Conditions of approval — FAQ

  • What is a condition of approval?

    A condition of approval is a requirement attached to a land-use approval that the applicant must satisfy before the approval runs with the land. Conditions are imposed by a planning commission or city council when they approve a rezoning, variance, site plan, PUD, or development agreement. Examples include affordable-housing set-asides, traffic impact fees, infrastructure commitments, setbacks, tree-preservation mandates, and phasing triggers.
  • Why is this not in a permit feed?

    Permits are terminal documents. The conditions exist in meeting minutes, staff reports, and the official record of the approving body — not in the permit itself. By the time a permit is issued, the conditions have already been baked into the project; permit data has no way to surface them.
  • How does cityminutes extract conditions of approval?

    Double extraction: an LLM structured extractor pulls the condition list from staff reports and meeting minutes, and a rules-based template extractor targets Granicus, Legistar, CivicClerk, and Accela schemas. Disagreements route to human QA. Per-condition full-text accuracy target is ≥97%; categorical tagging accuracy is ≥92%.
  • What format is the data delivered in?

    Structured JSON: condition_id, category enum, dollar_value (where extractable), deadline, dependency, raw_text, and source_pdf_page. Plus full-text search across every condition and CSV export. Every condition links back to the canonical source PDF and page with a last_updated timestamp.
  • Which personas care most about conditions of approval?

    Critical for Land Acquisition (P1) and Developers & Investors (P4) — conditions are the most under-appreciated variable in entitlement underwriting. High for Pre-Construction BD (P1B) — conditions surface the off-site infrastructure work the owner will need to bid out.
  • Are conditions of approval available for all 3,142 counties?

    Active extraction is live in the top 50 metros by planning-commission velocity, with rolling expansion to all 3,142 US counties over 12 months. Live per-county freshness on /coverage.

Field 1 of 4

Get the conditions feed wired into your underwriting.

Weekly conditions of approval from every US planning commission, with parcel join keys, dollar-value tagging, and source PDF link-back.