subdivision-case-brief

Purpose

Summarize a preliminary or final plat, minor subdivision, or lot-line action against the subdivision ordinance, zoning, utilities, and plan so the commission or council can act within the statutory timeline. Most subdivision approvals are ministerial or tightly standard-based: the question is conformance, not preference.

Required inputs

• Application, plat sheets, legal description, and checklists; zoning and overlay designation.
• Subdivision ordinance and engineering standards; adopted plan and street network plan.
• Reviews: public works/engineering, utilities, fire (access, hydrants, water flow), stormwater, floodplain, school or park district, county, and utility franchise comments.
• Infrastructure plans, cost estimates, and security (bond or letter of credit) proposals.
• Title/ownership evidence, easements, and any development agreement.

Workflow

1. Identify the stage and decision type (preliminary, final, minor, replat, vacation) and the statutory shot clock for action; many states deem a plat approved if not acted on in time. Note the date.
2. Standards check: lot dimensions and area, frontage, block length, street width and connectivity, access spacing, sidewalks, utility easements, drainage, floodplain, and tree/open-space requirements. List each as conforms, conforms with condition, or deviates.
3. Utilities and facilities: water and sewer capacity (not just availability), fire flow, stormwater detention and downstream effects, road adequacy, and school or park dedications.
4. Public improvements: who builds, to what standard, with what security, inspection, and warranty. Compare security amount to engineer's estimate plus contingency.
5. Exactions: required dedications or fees must tie to the project's impacts (see exaction-nexus-review). Cite ordinance authority for each.
6. Conditions of approval: write enforceable, specific conditions with timing (before recording, before building permits, before certificate of occupancy). Avoid vague "to staff satisfaction" terms.
7. Hearing notes: notice requirements met, public comments by theme, legal standard the board must apply, and options (approve, approve with conditions, deny with findings, table when allowed).
8. Recording: signatures, tax certification, recording deadline, and what makes the approval void.

Output structure

| Standard | Requirement | Plat shows | Status | Condition | Add: recommendation, proposed findings, list of conditions with timing, public-improvement and security table, and hearing script cues.

Red flags / escalate

• Shot clock about to expire.
• Insufficient utility capacity or fire flow, or flood-prone lots.
• Inadequate legal access or disputed easements.
• Exactions without ordinance authority or nexus.
• Plat conflicts with an adopted street plan, zoning, or a pending annexation.
• Quasi-judicial ex parte contact or conflicts: city attorney review.

Common mistakes

• Denying on grounds outside the ordinance standards.
• Approving without security for public improvements.
• Imposing conditions no one can verify.
• Overlooking that final plat must substantially conform to preliminary.

State-law variance

Plat approval authority, deemed-approval rules, and vested rights vary by state.