Precise architectural drafting for single-family projects in Austin’s SF-3 zoning district means addressing the city’s Residential Compatibility Standards (RCS) not just in gross design layout, but in the granular drawing conventions, code call-outs, and calculation diagrams required for plan review approval. The adopted Austin Land Development Code (LDC), enforced through Development Services Department (DSD) review, hinges on dimensioned height planes, setback encroachments, fenestration calculations, and environmental overlays-often with unique drawing-sheet expectations and localized code amendments.

Detailing RCS Height Plane Compliance on Sections & Elevations in Austin SF-3

The backbone of Residential Compatibility Standards enforcement in Austin’s SF-3 districts is the graphical and dimensional adherence to RCS height planes, documented according to LDC 25-2-770(C)(2) and local staff interpretations. Because height plane violations are frequent plan-review rejection points, the way these constraints appear on your sections, elevations, and dedicated diagrams determines permit velocity.

Section Cuts and Elevation Conventions for Height Plane Documentation

Every residential project bordering "protected properties" in Austin is subject to a carefully dimensioned side setback height plane: “an inwardly sloping 45-degree angle setback plane begins at a horizontal line 15 feet above the side property line at a 25-foot setback for the first 40 feet of lot depth, then turns and continues from the rear property line at the same elevation” (LDC 25-2-770(C)(2)(b), source).

  • Section views must include a vertical elevation datum originating at the calculated Average Natural Grade (ANG)-typically the average of the highest and lowest grades adjacent to each building face, per LDC Subchapter F and amplified by local DSD interpretations.
  • Height Compliance Diagrams are often their own sheet or dedicated detail, showing a heavy dashed line at the 15-ft mark directly above the side property line, a 25-ft offset, and a precisely rendered 45-degree plane, extended through the buildable envelope. This is not optional: missing this diagram is a common redline prompting “Provide Height Plane Diagram per LDC 25-2-770(C)(2); show calculation of ANG” in Austin.

Average Natural Grade (ANG) Determination and Its Implications in Drawing

The chief point of confusion-and a cause of repeated rejections-lies in establishing the project’s ANG datum. LDC’s Subchapter F “measuring building height” provision is clear: “the vertical measurement between the average of the highest and lowest grades adjacent to the building and the highest point of the structure” (see library.municode.com), with a specific caveat: if located in the 100-year floodplain, always use the natural grade rather than finished grade. This demands that:

  • Topographic spot elevations are called out every 10-20 ft along building edges on plans and site sections.
  • Detailed tabulation of “highest adjacent” and “lowest adjacent” spot grades appears directly on either the site plan or the dedicated height compliance sheet, with arithmetic shown.
    E.g., “ANG = ((Elevation 502.8’ + Elevation 496.3’)/2) = 499.55’ above sea level”.

Dimensioning to Critical Structure Points: Top Plate, Eave, Ridgeline

Every elevation and section must explicitly dimension from the ANG to primary elements of the structure:

  • Top plate and eave: If the top plate or eave projects nearer to the 45-degree plane than the ridge, this is the point of measurement and graphical intersection for compliance analysis.
  • Ridgeline: Maximum roof height is verified here, but even overhangs must remain inside the height/setback plane except for permitted encroachments (see below).

Austin code enforcement is razor-sharp here: drawings missing explicit vertical dimensions (“Measurement from ANG to eave not shown”) are routinely flagged for correction.

Graphical Representation of Protected Adjacent Property and RCS Height Plane

On both elevations and sections, include:

  • Bold or colored call-out for “Protected Property Line”-demarcating exactly which side yards activate RCS constraints, as ambiguity may lead to a redline: “Clarify which property lines are protected; provide adjacency diagram.”
  • Shaded 45-degree height plane overlays-drawn in contrasting lineweights/hatching, labeled as “RCS Height Plane per LDC 25-2-770(C)(2)(b).”
  • Roof Overhang Exception: LDC 25-2-770(C)(2)(d) allows a roof eave or overhang to extend up to 2'-0" beyond the height plane, graphically dimensioned and labeled: “Eave projects 24" max. beyond height plane per LDC 25-2-770(C)(2)(d).”
  • Protected projection call-outs: Gabled roofs (max. 30' horizontal) and dormers (max. 15' horizontal per side) may project through the height plane, but must be dimensioned and scheduled with total width shown to avoid redline correction.

Common Plan Review Redlines: ANG and Height Plane Issues

  • “Incorrect Average Natural Grade-provide tabulation of spot elevations with calculations.”
  • “Height plane diagrams missing from sections/elevations-add as per LDC 25-2-770(C)(2).”
  • “Roof overhang projection exceeds 2’ maximum into the height plane; dimension all eaves.”
  • “Rear setback plane not shown over 40’ lot depth-provide full buildable envelope section.”

Plan reviewers expect rigorous graphical and dimensional evidence of compliance, not narrative descriptions alone. Every critical building element (top plate, eave, ridge, projection) must be measured back to the ANG, with visual confirmation that no part of the structure intrudes into the protected zone (except as specifically allowed).

Dimensioning RCS Horizontal Setbacks and Allowable Projections on Site Plans for Austin SF-3

Horizontal control of structures under Austin’s RCS provisions intensifies the importance of accurate, fully dimensioned site plans. Austin Land Development Code Section 25-2-555 establishes that for SF-3:

  • Front setback: 25'-0” (from property line)
  • Side setback: 5'-0” each side
  • Rear setback: 10'-0”

However, RCS introduces additional setback lines relating to protected properties, and Austin LDC Section 25-2-770(C)(1) requires that these compatibility setbacks be explicitly dimensioned and depicted.

Site Plan Layout: Delineating Buildable Envelope and RCS Setbacks

Clear dashed lines must outline not only standard SF-3 setbacks but also the 25-ft RCS compatibility setback measured from a protected property line. Standard notation conventions:

  • Property lines: Bold, solid lines with bearings and lengths called out
  • Zoning setback lines: Medium-weight dashed lines, labeled "SF-3 Setback 25’/5’/10’"
  • RCS compatibility setback lines: Red, bold dashed lines or unique hatching, labeled “RCS Setback per LDC 25-2-770(C)(1)”
  • Building footprint: Heavy solid outline; dotted outline or tone for projecting elements (eaves, porches, etc.)

Detailing and Dimensioning Allowable Projections

  • Eaves and Overhangs: Up to 2'-0" into setback (measured perpendicular from wall)-dimension each on site plan and annotate, e.g., “EAVE: 2’ MAX INTO SETBACK PER 25-2-774(D)(1)”
  • Chimneys, Sills, Pilasters, etc.: Up to 2'-0" projection-each encroachment must be explicitly dimensioned.
  • Uncovered Porches/Stoops/Steps: Up to 3'-0" into front or rear yards-label and provide spot dimensions, e.g., distance from porch edge to property line.
  • Mechanical Units/AC Pads: May project up to 2’-3’; mechanical details should reference SF-3 zoning and local amendments (often checked for conformance by plan reviewers: “Mechanical pad encroachment exceeds allowance-revise dimension or relocate.”)

Common Redlines and Reviewer Comments

  • “Site plan lacks labeled setback lines-provide dimensioned setbacks for SF-3 and RCS (LDC 25-2-770).”
  • “Eave/porch projections not dimensioned-show all projections into setback zones with call-outs.”
  • “Proposed building footprint exceeds allowed encroachment into side/rear setback.”

Ambiguity in setback depictions or incomplete projections will routinely result in back-and-forth with reviewers, lengthening review timelines.

Drawing-Sheet Conventions and Detail Organization

  • Site Plan Sheet Title: “SITE PLAN - SETBACKS & PROJECTIONS”
  • Projections rendered in dotted/dashed outlines, keyed to a “Projection Allowance Legend.”
  • Enlarged details for complex encroachment zones (e.g., “PORCH PROJECTION DETAIL, Scale: 1/2” = 1’-0””).
  • Material call-outs: “EAVE = VENTED SOFFIT, FIRE-RATED PLYWOOD PER IRC R302.2 & CITY AMENDMENTS”

Plan sets adhering to these conventions accelerate reviewer understanding and reduce iterative corrections.

Fenestration and Transparency Calculation & Detailing on Austin SF-3 Elevations

Fenestration limits under Austin’s RCS provide a rare example of vertical and transparency-based code constraints for privacy and compatibility. Drawing sets must include explicit calculations and graphic documentation to address:

LDC Section 25-2-1067(C)(3): “the area of fenestration above 15 feet on a wall facing a protected property may not exceed 25% of the wall area (above 15 feet)”.

Calculating and Illustrating Compliance

  • Identify applicable walls: Any wall, or portion, “facing” a protected property triggers calculations-Austin DSD interprets this as including not just parallel but obliquely-oriented walls (as referenced in DSD pre-submittal guidance).
  • Dimension wall area above 15 ft: Elevation drawings must clearly mark the 15’ plane (dimension from ANG, not finished grade), shade or color walls above this, and include a labeled call-out: “WALL AREA ABOVE 15' = XX SF, PER LDC 25-2-1067(C)(3)”
  • Tabulate allowable fenestration: Wall area × 25% = “max glass area above 15’.” Provide this arithmetic in an annotation or “FENESTRATION AREA TABLE” on the elevation sheet.
  • Dimension and total window/door openings above 15’: Every relevant opening must be dimensioned (width × height), shaded, and tallied. Missed dimensions are a frequent redline cause: “Window area above 15’ not dimensioned/calculated-provide.”

Developing a “Fenestration Area Calculation” Diagram

  • Use hatching or color fills to differentiate transparent vs. opaque areas above 15’
  • Include a summary table:
    • Total wall area above 15’
    • Allowed max fenestration (25%)
    • Proposed fenestration (sum)
    • Compliance confirmation (“Proposed = X SF < Y SF = allowed”)
  • Glass type notation: “Shaded windows = OBSCURE GLAZING, LOCATION PER SCHEDULE.” DSD expects special notation of obscured glass (not counted toward privacy reductions in some cases)-failure to label is often flagged.

Integrating Calculations with Window Schedules

Window schedules must reference corresponding elevation keynotes and include columns for:

  • Window location (Elevation/Key)
  • Sill/head height, overall area (sf)
  • Glazing type (clear/obscure/tempered): “GLAZING TYPE: Obscure”
  • Notations for safety and energy code requirements (IRC R308, IBC 2406-tempering and impact requirements)

Schedules without area calculations linked to corresponding window openings above 15’ prompt DSD redlines for missing transparency documentation.

Common Plan Review Redlines and Preventative Measures

  • “Fenestration area calculation not provided above 15’-show per LDC 25-2-1067(C)(3).”
  • “Area of windows/doors not dimensioned or totaled-revise elevation and schedule.”
  • “Incorrect wall area calculation above 15’-show how measured from ANG.”
  • “Openings facing protected property not shown; clarify which elevations are subject to 25% limit.”
  • “Obscure glazing not specifically noted-add call-outs to plans and schedule.”

Complete, cross-referenced documentation-calculations on elevations, call-outs, and integrated window schedules-is required to clear DSD’s transparency review.

Integrating Impervious Cover Calculations and Stormwater Notes on Austin SF-3 Site Plans

The City of Austin’s environmental standards enforce strict impervious cover limits and stormwater controls in SF-3 zoning, codified through LDC 25-2-770(C)(5) and Chapter 25-8. These requirements are evaluated directly off the submitted site plans.

Impervious Cover Calculation: “Site Data Table” and Graphic Representation

  • Maximum impervious cover: 45% of net lot area (SF-3)-per LDC Section 25-2-492
  • Site Data Table (Mandatory): Tabulate existing and proposed conditions, broken out by:
    • Building footprint (SF)
    • Paved driveways/walks (SF)
    • Patios and decks (impervious) (SF)
    • Other (mechanical pads, etc.) (SF)
    • Total impervious proposed (sum-a second line for % of site)
  • Table(s) typically appear in the lower right corner of the first or second site plan sheet, with a boxed “Impervious Coverage Calculation per LDC 25-2-770(C)(5)” call-out. Omission or outdated numbers are routinely flagged: “Update Site Data Table to reflect true impervious cover-show calculations.”

Graphical Delineation: Use two distinct hatches or colors-one for impervious (solid, crosshatch, or dark gray), one for pervious (open, stipple, or green). Provide a “Legend: Impervious / Pervious” box directly on the plan. Each area must be traceable to a measurement line or area tag. Overlays of lot boundaries, setback lines, and environmental buffers are shown with lighter dashed lines for clarity.

Stormwater Notes and Austin-Specific Environmental Callouts

  • Erosion Control Measures (ECMs): “SILT FENCE, LOCATION PER PLAN; INSTALL PRIOR TO ANY SOIL DISTURBANCE PER ECM 1.4.4.” - leader lines from notes to specific fence/riser/sediment basin locations.
  • Tree Protection Plan (TPP): Dripline fencing, root zone protection, and all preservation notes per Environmental Criteria Manual. Include legend for "Tree Protection Fence (Orange)". Omit, and DSD will redline “Provide ECM-compliant Tree Protection Plan.”
  • Stormwater Detention/Retention: Even for single-family, features like swales, rain gardens, and required surface flow arrows should be noted: “SURFACE RUNOFF TO (E) DRAINAGE EASEMENT; SEE C3.2 FOR DETENTION DETAIL.” Annotate as needed (reference LDC § 25-8-213, Chapter 25-8 Article 9).
  • “Erosion Control Note Must Read: ‘All ECMs must be in place and maintained at all times during construction; no alteration to tree protection zones.’” (Direct copy required on face of site plan, not tucked in specs.)

Common Plan Review Redlines and Drawing Responses

  • “Impervious cover calculation incomplete or missing-submit updated Site Data Table with all areas labeled on plan.”
  • “Tree protection measures insufficient-show fencing location and add detail per ECM standards.”
  • “Stormwater management features not identified-add drainage flow arrows, label detention/retention as required.”

Every site plan must include both arithmetic and visual proof of impervious cover compliance, and Austin reviewers expect environmental notes and boundaries on the drawing, not just referenced in specs or supplemental sheets.

Navigating Austin's Plan Review & Local Code Amendments for RCS Compliance in SF-3 Drawings

Technical mastery of plan set assembly and localized code referencing is the linchpin for efficiently steering SF-3 residential projects through Austin’s DSD review. The 2024 International Residential Code (IRC) with city amendments governs the technical side of the drawing set, but local overlays and workflow are just as critical.

Incorporating Austin-Adopted Code Editions and Local Amendments

  • Code Reference Sheet: A "General Notes - Austin Specific" sheet is expected at the front of every plan set, with explicit references:
    • “All work per 2024 IRC as adopted & locally amended by the City of Austin (LDC 25-12); 2021 IECC w/local amendments; LDC 25-2-770 for RCS provisions.”
    • “SF-3 Zoning-Family Residence District. All dimensional standards by LDC 25-2-555.”
    • Recording of overlay districts or Neighborhood Plan (NP) if applicable.
  • Outdated code references or missing local amendment references (“Reference to 2015 IRC-revise to 2024 IRC per current adoption.”) are near-automatic redlines.

Organizing the Drawing Set and Critical Sheet Call-Outs

  • Title Sheet: Full project address, legal description, zoning (“ZONE: SF-3-FAMILY RESIDENCE”), project data table, full index, and code references.
  • Sheet Set Order: Site Plan; Existing Conditions; Floor Plans; Building Elevations; Building Sections (with RCS Height Plane Diagrams); Wall Sections/Details; Window/Door Schedules; MEP Drawings; Environmental/Site Details.
  • “General Notes - Austin” Sheet: Key zoning, building, fire, and accessibility standards called out so reviewers can cross-check easily. Example:
    • “Maximum impervious cover: 45% per LDC 25-2-492; see ‘Site Data Table’ on A1.2.”
    • “All eaves to comply with 2’ max encroachment per LDC 25-2-774(D)(1).”
    • “Fire separation distances and assemblies per IRC R302 and local amendments.”
    • “All new windows at less than 18” above floor or adjacent to doorways to be tempered per IRC R308.”

Responding to Common Plan Review Redlines from DSD

  • “Provide documentation of compliance with LDC Section 25-2-770 regarding two-family residential use.”
    • Response: Add zoning analysis table and narrative, reference compliance on General Notes sheet.
  • “Clarify fire separation distance between structures as per IRC Table R302.1(1).”
    • Response: Dimension all building-to-property line and building-to-building distances on site and floor plans, with note: “Fire-Resistant Assemblies as Noted on Wall Sections.”
  • “Specify insulation values for walls and ceilings to meet IECC requirements.”
    • Response: Annotate wall/roof sections as “2x6 stud wall: R-20 batt; attic insulation: R-49 blown.”
  • “Height plane compliance details incomplete-add RCS Height Plane Diagram per 25-2-770(C)(2); include ANG calculation.”
  • “Impervious calculations do not sum or exceed maximum-revise Site Data Table and graphically show all impervious area.”

Each DSD comment should be answered in a “Response to Comments” report, but more fundamentally, the drawing set must be revised to physically highlight changes (revision cloud, delta triangle, annotation in sheet index: “REVISED PER DSD COMMENTS 3/15/25”). City staff will cross-check against these guided callouts at their next review.

Best Practices: Proactive Documentation and Drawing Strategies for Austin Plan Review

  • Master “General Notes - Austin” Sheet: Consolidate all code, local amendment, and zoning dimensional restrictions in one visible place.
  • Detailed Legends and Expanded Title Blocks: Sheet-by-sheet, every regulatory overlay, setback, RCS envelope, and fenestration limit should be referenced in call-outs or legends for minimum reviewer interpretation effort.
  • Cross-Referencing Between Sheets: Plan, section, and schedule cross-references (e.g., “See RCS Height Plane Diagram on A3.2 for compliance With LDC 25-2-770(C)(2)(b)”) enable reviewers to quickly confirm technical details.
  • In-Sheet Calculations and Area Diagrams: No calculations “by separate document”-DSD expects arithmetic and analysis visible on the submitted sheets.

Organized documentation sharply reduces rounds of “clarify, resubmit” and the resulting schedule impacts on residential projects.

Conclusion

Drafting for Residential Compatibility Standards compliance in Austin’s SF-3 districts mandates a precise, drawing-based translation of LDC and local amendment requirements-a process realized through rigorously documented height plane sections, setback encroachment details, fenestration area diagrams, and impervious cover calculations, all thoroughly annotated within the context of Austin's adopted code editions and plan review workflow. Fast, successful submittals depend not only on code knowledge but on the implementation of city-specific drawing-sheet strategies, clear legends, and responsive correction cycles that minimize reviewer guesswork and maximize permit efficiency. Kingsway Drafting & Design delivers these standards as the core of every residential project submittal in Austin and beyond.