Compounding Code Constraints: How Austin's Regulations Interact Across Disciplines

CSW Development, the applicant behind the 319-unit mixed-use development at 2428 W. Ben White Blvd., had already been in site plan review for 20 months when city staff changed their reading of the code. The project straddled two watersheds, and mid-review it was decided that each portion of the site had to meet separate water quality standards rather than the single standard the applicant had already designed to. Redesigning would have cost $2.5 million and eliminated roughly 100 units.

The applicant's attorney, Steve Drenner, took the dispute to the Planning Commission. Commissioner Joao Paulo Connolly, voting to overrule staff, put a name on the problem: "What we are witnessing right now is exactly the graveyard where so much of Austin's housing goes to die."

The graveyard Connolly described is not staffed by bad reviewers. It is staffed by competent reviewers who each see one discipline. A drainage engineer knows detention sizing. A transportation reviewer knows driveway spacing. An arborist knows critical root zone (CRZ) radii. What none of them see is which rules from other disciplines will collide with theirs on the same site.

A 2023 McKinsey report commissioned by the city quantified the damage. The average Austin site plan goes through five formal review cycles. Eleven departments with multiple review disciplines within each — drainage, fire, zoning, environmental, transportation, utilities, and more — means hundreds of staff touch every application. Each discipline applies its own regulations and code sections. Each signs off independently. Nearly 80 percent of applicants wait longer than one year. Multifamily carrying costs run $546,000 per month. Customer satisfaction: 3 out of 10.

Keith Mars, the current Austin Development Services (ADS) Director, named the mechanism in the Austin Chronicle on April 2, 2026: "Sometimes there are inherently conflicts. If the Fire Department says, 'We need this turning radius for this road,' and Austin Energy says, 'Well, we need a transformer in that area,' and we're like, 'Okay, but that's where the building needs to go' — we need to be able to identify that early."

Identifying it early means knowing which interactions exist. Austin's site plan review has dozens of cross-discipline constraint interactions that are predictable, documented in code, and routinely missed because no single reviewer's scope includes both sides. Nobody has cataloged them. Here are three of the most common.

Compatibility Buffer vs. Detention Placement

At 600 Cumberland Road, an Affordability Unlocked project proposed condominiums with ground-floor retail. Enhanced Transit Oriented Development (ETOD) compatibility standards (LDC 25-2-654(H)) imposed a 25-foot buffer and a 60-foot height limit within 50 feet of the adjacent single-family-zoned property. The applicant's variance application stated the buffer "removes approximately 31% of developable site area, preventing parking garage circulation geometry."

That 31 percent doesn't just shrink the building footprint. It removes the area where stormwater detention would go. Neighbors opposing the variance cited drainage and flooding as their primary concern, but neither side had a reviewer assigned to the question of where detention was supposed to go once the buffer consumed the rear of the lot.

Under LDC 25-2-1051 through 25-2-1063, the compatibility buffer prohibits structures — and Austin's interpretation of "structures" includes detention walls, water quality ponds, and even flush-to-grade drainage improvements. A February 2021 Planning Commission case required a compatibility variance for drainage improvements within the 25-foot setback that were flush to the ground with a berm and landscaping screen. Still prohibited.

The 2024 Citywide Compatibility reform confirms the problem was real: it had to carve out an exception allowing "walls that are part of stormwater or other critical infrastructure" in the buffer. For projects still subject to ETOD or pre-reform compatibility standards, the prohibition stands.

The interaction is geometric. Compatibility buffers take the strip of lot area closest to the triggering property. Detention ponds need the lowest point of the site, which on many Austin lots is at the rear — adjacent to that same triggering property. Push the buffer onto the site; the detention has nowhere to go. Shrink the detention; the water quality review fails. The drainage reviewer doesn't see the compatibility constraint. The zoning reviewer doesn't size the detention. Nobody owns both sides.

At 600 Cumberland, the variance request was postponed three times and withdrawn. The project is proceeding under alternative density bonus programs that sidestep the compatibility pathway entirely.

Heritage Trees vs. Building Setbacks

The Goodmans' front yard at 3706 Meadowbank Drive held two heritage trees. Their CRZs covered the same ground that LDC 25-2-1604 required for the garage. The tree protection rules said the CRZ was inviolable. The garage placement rule said the parking structure goes behind the building facade. Both rules applied. Both couldn't be satisfied. The Board of Adjustment granted a variance unanimously on March 11, 2024, and the Goodmans built the garage — but only after going through a formal hearing process for a conflict that was baked into the lot geometry from the start.

The permanent supportive housing project at 819 Tillery Street showed the same interaction at a different scale. LifeWorks proposed 120 multifamily units for youth exiting foster care on a 1-acre portion of a 13-acre site with 47 heritage trees. Tree 3510, a 32-inch pecan in fair condition with poor structural integrity, sat centrally within the buildable envelope.

The applicant's alternative layout analysis made the trade-off plain: preserving the tree required a fire lane redesign and a loss of 12 to 27 housing units depending on the configuration. The arborist's mandate was to protect the tree. The fire marshal's requirement was to clear the lane. Neither reviewer's scope included the other's constraint.

The Environmental Commission approved removal May 7, 2025. The Planning Commission followed May 27, 2025. The project lost months to a conflict that was visible in the site geometry from the day the application was filed.

Heritage tree CRZs function as de facto setbacks. A 32-inch tree has a CRZ radius of roughly 16 feet. Place that tree near a property line, and 16 feet of developable area is gone before the building setback, fire lane, and utility corridor take their shares.

The tree reviewer sees the CRZ. The building reviewer sees the setback. The fire reviewer sees the lane width. Each discipline's constraint is satisfied in isolation. The site plan that satisfies all three may not exist for that lot geometry.

Protected Trees vs. Sidewalk Alignment

Environmental Criteria Manual (ECM) 3.5.3 permits narrowing sidewalks to four feet when adjacent to a street curb, or three feet otherwise, to avoid encroaching on a protected tree's CRZ. A minimum distance of three feet must be kept between curb and tree.

Read that provision carefully. The city wrote a permanent code exception because the conflict between tree protection and sidewalk width recurs on enough Austin streets that reviewers needed a standing rule for it.

The mechanics: a standard sidewalk in Austin is five to six feet wide. A protected tree's CRZ extends from the trunk in a radius proportional to the trunk diameter. When a tree sits between the curb and the right-of-way line, the CRZ can consume the entire sidewalk corridor.

The transportation reviewer requires the sidewalk. The environmental reviewer protects the CRZ. ECM 3.5.3 lets them split the difference with a narrower walk. But the narrower walk may not satisfy ADA requirements on that block, sending the project to a third reviewer with a third set of constraints.

The code accommodation itself is the evidence. Rules don't get permanent exceptions for problems that don't recur.

The Problem Is Structural

These three examples are not anomalies. They are what happens when regulations written by and for different departments get enforced against the same area of a project by reviewers who are siloed from each other as a nature of the process as it exists today.

The compatibility reviewer does not size detention ponds. The tree reviewer does not check sidewalk widths. The environmental reviewer does not measure building setbacks. Each one does their job correctly. The site plan still fails — not because anyone made an error, but because the review process has no step where someone checks all the disciplines against the same site at the same time.

Austin recognizes this. The McKinsey report called for interdepartmental conflict resolution, and department leadership has described the mechanism publicly. Solving it requires coordination across every discipline that touches a site plan, which is what makes it hard. But cities like Austin are increasingly realizing the work is worth doing. The alternative is the graveyard Connolly named.