Engineers outline minor/major subdivision tracks, timelines and warranty rules; council asks about tiny homes and developer metrics

Daniel Hill, director of engineering, briefed the committee on subdivision procedures and enforcement. He said minor subdivisions fall into three administrative tracks (administrative minor, administrative with waived public hearing, and public-hearing minor) and described common thresholds: administrative review typically covers five lots or fewer (or 10 lots in some classifications), two acres or less, no public infrastructure, and no need for code waivers.

"Basically, [a major subdivision is] anything that's not a minor subdivision," Hill said, summarizing the code distinction. He estimated the parish receives about 200 to 250 minor-subdivision filings annually and 12 to 18 major-subdivision applications per year. Hill recommended predevelopment meetings (not required by code) to reduce later changes and noted code-prescribed time gates: once a submittal is complete the ordinance often requires processing within specified calendar-day windows (for example, a 14-day processing step for certain minor approvals).

On major subdivisions Hill said two public hearings are required (concept plan and final plat/construction plan). Concept plans are meant to establish layout and land-use intent; detailed design for drainage, traffic and infrastructure comes later. Hill warned that if later design work shows required drainage or detention will not fit the space allocated on the concept plan, developers may need to remove lots or otherwise change the layout.

Hill described inspection, acceptance and warranty processes: after construction staff inspects for compliance with approved plans and the parish imposes a warranty obligation prior to dedication. "Parish code says we can establish a warranty period of a minimum of 24 months," Hill said. If the parish pulls an obligation because the work fails and the cost to repair exceeds the held obligation, staff said the parish would pay to fix critical failures and then pursue legal action to recover additional costs.

Council members raised regional-impact concerns. Councilman Phillips asked whether drainage reductions required on-site might shift run-off to the broader region and whether staff evaluate how subdivisions interface with regional systems. Hill said staff does evaluate regional impacts as feasible and bases the analysis on staff evaluation and code requirements. Council members asked whether the parish publishes internal metrics showing how complete developer submissions are; staff said they track missing documents and timelines internally and will share data on specific cases upon request but do not publish a public completeness score.

The committee also discussed housing types. Ross Lyon earlier told members the parish generally does not regulate dwelling size so long as a structure meets construction and occupancy standards, meaning tiny homes built to residential code could be permitted; garden-home developments exist under PUD zoning but require larger sites (about 30 acres) and may be limited by market and site suitability.

No formal approvals were taken; the session was an informational briefing aimed at clarifying process timelines, appeals and enforcement obligations.