What Gets a Site Plan Rejected at Completeness Check in Austin

An estimated half a million dollars a month. Roughly $546,000, to be exact. That is the carrying cost for a multifamily redevelopment project stuck in Austin's site plan review process, per illustrative estimates in the McKinsey assessment presented to City Council in August 2023. Greenfield projects bleed an estimated $37,000 a month. Single-family redevelopments run about $9,700.

A lot of that time starts building at the completeness check, the 10-business-day pass/fail that decides whether your application enters formal review. The city's own Site Plan Performance Metrics tell the story. From October 2024 through October 2025, the share of applications passing completeness on initial submission averaged roughly 16 percent. The city's published target is 25 percent. That target was not met in any month of that 13-month window.

The rejection is rarely a missing signature. It is usually a missing exhibit, detail, or design the applicant did not know was required at the completeness check stage.

How the Completeness Check Is Organized

The city's Consolidated Site Plan Completeness Check Submittal Checklist runs six pages, organized by review discipline: Addressing, Austin Energy, Austin Water, City Arborist, Environmental, Floodplain, Regional Stormwater Management Program, Right-of-Way, Site Plan, Transportation, and Water Quality and Drainage Engineering. Eleven disciplines. More than 90 line-item requirements across them.

Most firms work from the consolidated checklist and treat it as the full picture. It is a reasonable starting point. Individual departments also publish their own completeness requirements that go beyond what the consolidated form captures. Austin Water's department-specific checklist alone runs several pages, with infrastructure exhibits, service extension requests, and utility easement documentation in detail the consolidated form does not carry. Firms that work only from the consolidated checklist sometimes miss department-level requirements, and those are the misses that add weeks.

The Conditional Trigger Problem

Many required items only activate when a site-specific condition is true. Work from a flat checklist and you will complete every line item you can see. The items you cannot see, the ones that only apply when your site has certain characteristics, are the ones that send your application back.

The checklist functions more like a decision tree than a flat list. Its branches depend on facts about the site that the form itself does not evaluate for you.

Watershed classification determines whether you need water quality volume exhibits, environmental setback documentation, and erosion hazard zone analysis. A site in the Barton Springs Zone or a Critical Water Quality Zone faces requirements that do not apply in the Suburban watershed.

Compatibility proximity. Under the Land Development Code's compatibility standards (LDC 25-2, Subchapter C, Article 10), proximity to a single-family-zoned property activates setback and height requirements, with documentation required at completeness. The trigger is zoning-based. A parcel zoned single-family activates the standard regardless of what is actually built there.

Heritage trees trigger a tree survey and Environmental Resource Inventory beyond the standard tree plan. Miss the heritage evaluation and the entire tree and vegetation package comes back.

Austin Water service requirements trigger infrastructure exhibits, service extension documentation, and utility easement plans, with conditional branching based on whether you are connecting to existing infrastructure, extending lines, or in a service gap area.

The 45-Day Clock

Each rejection eats the applicant's time. The completeness check phase counts against a 45-day window to reach formal submission. Each rejection consumes 10 or more business days. Two rejections and you have used almost half the window on a phase that was supposed to be quick.

The conditional triggers compound this. A firm that finds out at the completeness window that it is missing a Watershed Protection supplement or an Austin Water service extension exhibit cannot just assemble the documents. It has to go back to the site analysis, figure out which conditions were not evaluated, pull the right department checklists, and produce exhibits that may require engineering work. That is a two-week fix while carrying costs accumulate.

The effect carries into the back end. The city's metrics show permits issued in FY2025 averaged roughly six review cycles, against a target of four. Each extra cycle adds weeks. Once an application gets behind, it tends to stay behind.

A Compatibility Trigger in Action: 1609 Matthews Lane

The completeness check does not generate public case records the way a Board of Adjustment hearing does. Plans that get rejected at completeness get sent back quietly as administrative notices. But the 1609 Matthews Lane BOA case (C15-2022-0060) shows how the conditional trigger mechanism works in practice. It is worth a closer look because the same trigger catches firms at completeness all the time.

A proposed 10-unit development in South Austin, 8 attached townhomes and 2 detached homes, ran into compatibility setbacks under LDC 25-2-1063 because of a neighboring mini-storage facility. The storage operation had sat on SF-zoned land since 1984. Because compatibility evaluates adjacent zoning rather than actual use, the 25-foot setback collapsed developable area to roughly 40 percent of the lot.

The team at Heimsath Architects had not missed the trigger through carelessness. The trigger itself is counterintuitive. A facility that has operated commercially for nearly four decades, on SF-zoned land, activates residential compatibility standards next door. "At the end of the day, there isn't a hardship here," Board Member Darryl Pruett said when the BOA initially denied the variance in September 2022. The board reversed itself two months later.

The same evaluation happens, or fails to happen, at the completeness check stage. A firm assembling a package sees compatibility documentation as a line item and checks it off based on what the adjacent properties look like. The real evaluation requires pulling the zoning of every parcel within the compatibility trigger distance and checking whether any qualify. Skip it, and the application gets sent back.

The Coordination Challenge

Austin's site plan review involves an unusually broad set of disciplines. The McKinsey assessment noted that of the 41 specialties involved in full review, 11 are formally assigned in AMANDA for the completeness check, with the others coming in during formal review. The Compendium called this "possible gaps in the completeness check review," a candid acknowledgment of how complex coordination becomes across so many departments.

Forty-seven code sections are reviewed by two or more specialties. Utilities alone is reviewed by nine. Access by ten. Grading by eight. When multiple disciplines evaluate the same code section, applicants can receive different completeness expectations depending on which reviewer they reach.

City staff, in interviews conducted for the McKinsey assessment, described "inconsistent review in terms of involvement, scope, and level of detail" at the completeness phase. That is a frank assessment from inside the department about a coordination problem most major U.S. permitting operations face. With Austin Development Services staff turnover at 13 percent in 2022 and average reviewer tenure of roughly 1.8 years against a 1-to-1.5-year learning curve, consistency is genuinely difficult to maintain. Customer workshops with more than 20 organizations named "lack of clarity regarding required documents and standards for completeness" as the top pain point at intake.

What the City Has Done

Austin has been actively addressing this. Under the "Transforming Site Plan Review" program launched in October 2023, the city reduced the completeness check intake form from 12 pages to 5 as part of Initiative 16. The broader reform has produced real results across the entire review process. Initial review cycle times dropped 56 percent, from 87 to 99 days down to 32 days. Follow-up cycles fell from 50 days to under 15. Of the program's 45 initiatives, the majority are now complete.

Those are meaningful improvements that reflect substantial effort by Austin Development Services and its partner departments. The streamlined checklist is easier to work with than what it replaced.

A shorter checklist with conditional branching is still a decision tree, though. The department-specific supplements still exist. The conditional triggers still depend on site facts the form cannot evaluate for the applicant. A shorter form makes the paperwork faster. It does not tell you which exhibits your specific site triggers.

The Bottom Line

The completeness check is not really a paperwork problem. It is a site analysis problem dressed up as paperwork. Every rejection traces back to a site-specific condition that did not get evaluated before the package was assembled. A watershed that was not checked. A heritage tree that was not surveyed. An adjacent zoning designation that was not pulled. A utility service area that was not confirmed.

The math is unforgiving. Sixteen percent first-pass approval. Six review cycles per permit. Carrying costs measured in hundreds of thousands per month. A rejection at completeness is not a clerical setback. On a multifamily deal, it is a six-figure event dressed up as a missing exhibit.

The firms that move through completeness on the first cycle do the same things in a different order. They evaluate the site before they start drawing, not after the checklist comes back. They identify the triggers first. Then they assemble the package the triggers require.

That order is the whole game. At completeness, the site analysis carries as much weight as the paperwork, and a passing package is what happens when both are ready at the same time.