What Actually Happens During Site Plan Review in Austin
A McKinsey team spent months inside Austin Development Services (formerly Austin Development Services Department) in 2023 and came back with a number worth understanding: the average site plan application goes through five formal review cycles, each one consuming a week of work from twenty city employees. Eighty-one percent of applicants submitted revisions at least three times. By 2022, average end-to-end timelines had reached 345 days per application.
Austin's site plan review is best understood as a single application running through many independent departmental reviews at the same time. Most of the elapsed time isn't spent waiting on any one reviewer. It's spent moving between cycles, because a revision that satisfies one department's comments can introduce a new question for another. Knowing which departments will look at your plan, and where their jurisdictions naturally overlap, is the most useful thing an applicant can understand before first submission.
The McKinsey compendium found that the city's reviewing departments were working against overlapping regulations and code provisions without a clear mechanism for reconciling them between departments. The consultants described the system as characterized by "inconsistent processes, multiple, sometimes outdated technologies, and ad-hoc cross-departmental coordination." These findings helped catalyze the reform effort now underway. Mayor Watson wrote in his April 2024 newsletter: "When I first started asking about what needed my attention at City Hall, not a single person said to me, 'Watson, don't touch the development review process. It's working great.'"
Who Actually Reviews Your Plan
Applicants typically expect five or six departments to touch their site plan. The actual number is closer to eleven, with most of those departments housing multiple separate review disciplines.
The departments that review every full site plan include Development Services (zoning, site plan compliance), Austin Transportation (driveway access, TIA requirements, right-of-way), Austin Water (water and wastewater service, easements), the Watershed Protection Department (drainage, water quality, floodplain), Austin Fire Department (fire apparatus access, turning radii, hydrant placement), and Austin Energy (electrical service, transformer placement, clearance zones). These six are always at the table.
Conditionally triggered reviewers add more. The City Arborist reviews when protected trees are on site. Parks reviews when parkland dedication or trail connections apply. Historic Preservation reviews when the site falls in a historic district or involves a landmark. Urban Design reviews when the site is in the downtown or west campus geographies. The triggers for each are scattered through the code, and the application itself doesn't tell you which will activate.
The overlapping jurisdiction is where coordination challenges concentrate. Both the 2015 Zucker Report and McKinsey's 2023 analysis found dozens of provisions in the Land Development Code and Technical Criteria Manuals that direct two or more departments to make decisions on the same subject — McKinsey counted 47 such regulations. Parking is reviewed by both Transportation and Development Services. Fire lane widths interact with environmental setback requirements. Driveway placement falls under both Transportation and Development Services. Impervious cover is checked by Watershed Protection, but the site layout driving those numbers is shaped by compatibility setbacks (Development Services), fire access (Fire), and utility placement (Austin Energy and Austin Water). A single design decision ripples across four or five reviewers who each see only their piece.
The Fire Truck and the Transformer
Keith Mars, who spent sixteen years inside Austin's Development Services Department before becoming its director, describes a specific example that captures the coordination challenge. The Fire Department requires certain turning radii for fire apparatus access lanes. Austin Energy requires transformer pad placements with specific clearance zones. On a multifamily site plan, both requirements often land on the same corner of the site.
Before the recent reforms, neither department could easily see the other's comments. No central case manager existed to flag the collision. "When we would have 10 other departments involved, there was no central case manager," Mars told the Austin Chronicle. "Sometimes there are inherently conflicts."
The applicant received both comment letters on the same day. One said widen the turning radius. The other said don't move the transformer pad. Resolving the conflict meant going back to each department separately, and each round counted as another formal review cycle. Both reviewers were applying their specific regulations correctly. The process simply didn't give them a way to see each other's work before comments went out.
How the Update Cycle Clock Works
Comments land, and the applicant enters the update cycle. The city tracks these as U0 (initial submission), U1 (first response to comments), U2 (second response), and so on. Each update has a response deadline that tightens as the cycle progresses: 30 business days for U1, 20 for U2, 15 for U3, and 15 for each subsequent update (BCM 15.1).
Miss a deadline and the application goes inactive. Reactivation requires a fee and restarts the clock. The deadlines sound generous until you factor in what each update requires: revising the plan to address every department's comments at once, resubmitting, and waiting for the next round. When two departments' comments point in different directions, the applicant has to coordinate a resolution across both before the clock runs out.
McKinsey's data makes the cycle visible in aggregate. In 2022, initial review cycles averaged 87 days. Follow-up cycles averaged 50 days. City review time increased 85 percent from 2021 to 2023, even as applicant response time fell 15 percent over the same period — a signal that everyone in the system was working hard inside an architecture that needed updating.
What the Reform Effort Is Changing
The city recognized the coordination problem and has been actively working to fix it.
Change of use applications are among the most routine site plan actions. A business changes what it does in a building. Previously, that filing required sign-off from 11 separate reviewing disciplines, with a typical timeline of two months. In October 2025, the city cut the reviewing disciplines to 3, dropping the timeline to roughly two weeks. That kind of streamlining shows what's possible when the process is redesigned around what each project actually needs.
The broader Phase 1 reform results are significant. Initial review times dropped from 87 days to 32 days — a 56 percent reduction — and follow-up cycle times from 50 days to under 15. The gains came from assigning dedicated case managers, requiring 30-60-90 phase check-ins across departments, and consolidating comment letters. The reform initiative's branding captures the goal: "One City, One Voice."
Council Member Paige Ellis introduced a resolution in December 2022 to create a "site plan lite" track for 3-to-16-unit residential projects after discovering that five-unit developments were routed through the same full review as large commercial. "People can't live in the pipeline," she said. Council Member Chito Vela added a 90-business-day target and stated the core problem on the record: "The greatest burden the site plan review process places on a development is often not the fees or the direct cost to comply with regulations, but the fact that it can take 1-2 years for a project to get through the site plan review."
What Falls Through the Cracks
When reviews run in parallel without cross-checking, things can slip through even with diligent reviewers.
In January 2024, Austin's Development Services approved a site plan for Avalon Pointe, a 142-unit student housing project at 2610 Hume Place near the UT campus. Fourteen months later, during an unrelated site visit, city planners noticed that the approved plan violated University Neighborhood Overlay requirements for street trees, lampposts, and pedestrian clear zone width. They also discovered that a 10-foot private easement serving a neighboring business's sewer line had disappeared between drafts. It had appeared in earlier versions of the plan and was gone from the final approved version.
"Sixteen years, I've never seen anything like it," said Keith Mars, director of Development Services, per the Austin Monitor.
The plan had passed five rounds of departmental comments. Walter Wukasch, real estate agent for affected neighboring landlords, asked: "I don't know if removal was accidental or intended to mislead city staff." Tim Finley, representing a neighboring property owner, was more direct: "Why? How? Where did the private easement go?"
The Planning Commission ultimately reversed the staff rejection of the site plan, an extremely rare exercise of authority. The commission approved the project despite the outstanding easement conflict, which commissioners acknowledged was outside their jurisdiction to resolve. Commission Chair Claire Hempel summed it up: "I really would hate the thought of this project pausing or going away, especially given where we are with tariffs and price increases."
Cases like this illustrate why cross-department visibility matters. It's not that reviewers aren't thorough — it's that each department's review is scoped to its own discipline, and some issues only become visible when you look across all of them at once.
A Familiar Diagnosis, Now Being Addressed
The coordination challenge Austin is tackling is not new, and the city deserves credit for confronting it head-on. The 2015 Zucker Report called the development review process "labyrinthine" and flagged the same overlapping jurisdictional issues McKinsey would document eight years later. Researchers described Austin's complaints as "the worst we have seen in our national studies." The report produced 464 recommendations. A 2019 city audit confirmed that the process remained slow. McKinsey in 2023 provided the detailed structural analysis that gave the current reform effort its foundation.
The carrying costs are real. McKinsey quantified them at roughly $546,000 per month in delay costs for a multifamily development, $37,000 per month for greenfield, and $9,700 per month for single-family redevelopment. Builder Cody Carr, who has completed more than 200 homes in Austin, put it plainly: "Time kills missing middle and small projects."
The city has been candid about the scale of the work. Council Member Harper-Madison, at the August 2023 hearing where McKinsey presented its findings, acknowledged: "It's a mess, and they are right to be mad at us." Nixta Taqueria's co-owner Edgar Rico, whose East Austin restaurant was shut down by an overheating meter and then told to restart the full permitting process, told KUT Radio: "They essentially gave us a death sentence." That willingness to name the problem publicly is part of what makes the reform effort credible.
What This Means for Your Next Submission
The reforms are real, and the trajectory is encouraging. Initial review times cut by 56 percent. Dedicated case managers for multifamily projects. Consolidated comment letters. The 30-60-90 phase check-ins that surface cross-department conflicts earlier in the process. Austin is doing the work, and the data shows it.
The practical takeaway for applicants is straightforward: the process rewards those who understand the coordination landscape before they submit. Knowing which departments will review your plan, where their jurisdictions overlap, and which design decisions will ripple across multiple reviewers lets you resolve conflicts on paper instead of discovering them in cycle three. The applicants who move through review fastest aren't the ones with perfect design from the start — they're the ones who anticipated where the Fire Department and Austin Energy would collide, where the compatibility setback would constrain the detention pond, and where the tree survey would reshape the site layout before any reviewer had to tell them.
That preparation has always been the difference between a three-cycle approval and a nine-cycle approval. With Austin's reforms building real coordination infrastructure on the city side, the applicants who meet that effort halfway — by understanding the process and front-loading the cross-department work — will be the ones who benefit most. Site plan review isn't a wall to push through. It's a system to work alongside, and Austin is making it easier to do that every cycle.