Austin Waterfront Overlay: what the WO combining district does to your zoning

It overrides the rest of Title 25

Most overlays add requirements on top of base zoning. The Waterfront Overlay goes further, and §25-2-711(C) says so in one sentence:

The requirements of this division supersede the other provisions of this title, to the extent of conflict.

So on a WO site, looking up the base district in §25-2-492 and stopping is not finishing the job. Where the overlay and the base district disagree, the overlay wins.

The clearest illustration is already on this hub. A Rainey Street lot can be zoned CBD — a district whose table entry reads 350 feet — and still be capped at 40 feet for a residential or mixed-use building, because the Rainey Street subdistrict regulations say so.

Sixteen named subdistricts

The overlay is not uniform. It is divided into sixteen subdistricts, each with its own regulations at §§25-2-731 to 746:

• Auditorium Shores
• Balcones Rock Cliff
• Butler Shores
• East Riverside
• Festival Beach
• Lamar
• Montopolis / River Terrace
• North Shore Central
• Rainey Street
• Red Bluff
• South Lakeshore
• South Shore Central
• Travis Heights
• University / Deep Eddy
• Zilker Park
• City Hall

The subdistrict is where the numbers live. The general provisions on this page tell you how the system works; they do not tell you what you may build. For that you need the subdistrict your site sits in.

How a Waterfront Overlay variance actually runs

The route is unusual — three bodies, in order:

1. The applicant requests a variance from the Small Area Planning Joint Committee of the Planning Commission and the Zoning and Platting Commission (which §25-2-712 calls "the board").
2. The board may recommend approval only if the project and variance are consistent with the goals and policies of the Town Lake Corridor Study — naming environmental protection, aesthetic enhancement and traffic — and the variance is the minimum required by the peculiarities of the tract.
3. The director forwards the recommendation to the Land Use Commission, which grants or denies on those same criteria.

An interested party may then appeal the Land Use Commission's decision — grant or denial — to Council under Chapter 25-1, Article 7, Division 1.

Note what the test is not. There is no hardship standard and no "all reasonable use" language here. The question is consistency with a plan document, plus minimality.

The goals are operative, not decorative

§25-2-710 opens by requiring that decisions "shall be guided at all stages by the goals and policies of the Town Lake Corridor Study". Because the variance test in §25-2-713 then asks whether a proposal is consistent with those same goals, the goals section is doing real work rather than setting a tone. It includes:

• eliminating industrial uses from the confluence of Longhorn Dam;
• phasing out resource extraction;
• providing the public visual and physical access to the Colorado River;
• mitigation for new development affecting identified landforms; and
• maintenance of natural shorelines and bluffs, except where subdistrict regulations require otherwise or stabilisation is necessary.

What the overlay does not reach

Two exclusions in §25-2-711(B). The first is short: a community events use is outside the division entirely.

The second is a grandfather clause pinned to mid-July 1986. The division does not apply to construction or reconstruction where, before those dates:

• a building permit was issued (before 18 July 1986);
• a certificate of occupancy was issued (before 18 July 1986);
• a site plan was approved (before 17 July 1986), including a phased or special permit site plan;
• a site plan was filed as a condition of zoning and previously approved by Council or the Town Lake Task Force (before 17 July 1986); or
• building plans were filed (before 17 July 1986).

The one-day gap between the permit and site plan dates is in the ordinance, not a transcription slip on our part.