Compliance with Austin’s so-called “McMansion” Ordinance-codified across LDC sections such as 25-2-551, 25-2-552, and related chapters-relies on the architectural drafter’s ability to detail, dimension, and annotate projects with precision on construction documents. From impervious cover calculations on site plans to nuanced measurements of building height and floor area, drawings must anticipate both plan-review scrutiny and evolving local code interpretation. The workflow for SF-3 (Family Residence District) submission in Austin demands not only technical accuracy but clearly presented tabular data, code references, and graphic conventions that withstand close review by Austin’s Development Services Department (DSD).

Impervious Cover Detailing and Dimensioning on SF-3 Site Plans

Code Framework: LDC § 25-8-63 and Environmental Criteria Manual

Impervious cover requirements define the percentage of a lot that may be covered with surfaces impenetrable to water, a major focus in Austin’s environmental regulation and a frequent source of DSD plan-review redlines. For SF-3 zones, LDC § 25-8-63 mandates a strict accounting of all impervious areas. This encompasses roofs, driveways, patios, paths, decks (at a reduced factor if spaced), and non-permeable storage zones. Exclusions, such as public sidewalks or multi-use trails, are narrow and specifically listed.

Example code excerpt from LDC § 25-8-63(D)(2):
“Impervious cover includes a surface or ground covering that presents an impenetrable barrier to water … The area of uncovered wood decks with drainage spaces between the decking must be calculated as 50 percent impervious cover if above pervious ground.”

Plan reviewers consistently flag missed features such as compacted gravel paths, large raised decks, or patios “built over existing lawn.” Every square foot exceeding 45% impervious cover triggers either redesign or documentation for special exception.

CAD Layering, Hatching, and Plan-Sheet Table Requirements

Site sheets must graphically distinguish every impervious area. Drafters use layer systems such as IMP_ROOF, IMP_DRIVE, IMP_WALK, and IMP_PATIO. Hatching conventions enhance clarity:

  • Solid fill for roof plan areas-outline matching the structure’s overhang extents (including eaves; dashed line indicating drip line recommended).
  • Diagonal hatch for driveways and parking, with explicit dimension strings showing width and length, and area calculation labeled in or adjacent to the hatch.
  • Cross-hatch or dot-pattern for walkways and patios; annotations note material type (concrete, stone over base, pavers with base) as material composition will affect eligibility for exclusion or area reduction.

All site plans must include a current-format impervious cover table as required by the DSD:

Impervious Surface TypeArea (sq ft)Percentage of Lot
Roof Area__________
Driveway__________
Walkways__________
Patios__________
Total Impervious__________

Each table row must reference, by key or hatch pattern, the site plan area, ensuring a one-to-one review match. For uncovered decks, notation such as “50% of deck area calculated per LDC 25-8-63(D)(2)” should be included.

Dimensioning & Drawing Sheet Call-Outs

  • Dimension strings must indicate the edge-to-edge extents of each surface-roof projections from exterior wall faces, driveway widths at various points, patio lengths, and walkway widths-checked against plan scale for accuracy.
  • Tag each impervious area with a call-out balloon indicating the assigned area tally and corresponding table line item. Example: “Driveway, 11’-0” x 23’-0” = 253 SF, see table Row 2.”
  • Include area subtotals per surface type before the full impervious cover total. On sloped sites or fragmented lots, break out grouped paved areas to facilitate cross-checks by DSD staff.

Common Plan-Review Redlines and Correction Cycles

  • “Driveway and sidewalk areas must be clearly hatched and included in total impervious cover calculation.”
  • “Impervious cover exceeds 45% allowed for SF-3 under LDC 25-2-492(D); revised site calculations required.”
  • “Roof area has not accounted for eaves in total square footage. Revise plan to show measured dimension to dripline, not wall face.”
  • “Tabulation table is missing percentage of lot area for each surface. Add per DSD checklist.”

Code reference language directly quoted (“per LDC 25-8-63, 25-2-492”) should be included on both plan and table for clarity.

Documenting Average Building Height and Wall Height: Elevation and Section Drafting

Establishing the Grade Plane in Austin

Building height for SF-3 zoning is rigorously defined and enforced under LDC 25-2-551 and 25-2-552. The DSD plan-review team expects drawings to demonstrate compliance with all vertical controls through explicit, measured grade planes and clear vertical dimensioning.

The grade plane is the arithmetic average of finished ground levels adjoining the building at all exterior walls. On sloped sites, this can require 4-10 survey points. Drafters should:

  • Annotate site plan or foundation plan with spot elevations at all major corners and grade breaks, each labeled “Finished Grade at Perimeter: Elev = ____ FT.”
  • Provide a calculation box on the elevation sheet: “Average Grade Plane: (E_1 + E_2 + ... + E_n) / n = _____ FT [per IBC 202, LDC 25-2-551(A)].”
  • Reference survey datum used (NAVD88 or equivalent) adjacent to the elevation calculation for plan-review alignment.

Dimensioning Critical Vertical Points

Section and elevation sheets must include:

  • Lowest Adjacent Grade (LAG): Call-out with leader “LAG (per LDC 25-2-551): Elev ____ FT.”
  • Highest Adjacent Grade (HAG): Same format as above.
  • Average Grade Plane (AGP): Heavy dashed line across elevation/section, labeled at each end. Suggest keying in “AGP, Elev ____ FT (ref. Elev Box).”
  • Roof Ridge: Dim string from AGP to roof peak, tagged “Max Height per LDC 25-2-551: ____ FT [Not to exceed 35'-0"].”
  • Wall plate heights and eave heights for wall height enforcement.

Every elevation must show explicit elevation tick marks for the AGP, LAG, HAG, mid-roof or ridge, and eave. Complex stepped foundations or multi-level designs may warrant a call-out detail referencing each disparate wall segment’s reference grade.

Plan-Review Comments and Sheet Annotation

  • “Average grade plane determination required. Provide survey data and calculation per LDC 25-2-551.”
  • “Building height exceeds 35’ maximum per SF-3 (LDC 25-2-552). Revise accordingly or recalculate AGP.”
  • “Missing or unclear vertical dimensions from AGP to highest roof point. Clearly show all critical heights.”

On every drawing sheet depicting elevations or sections, reference the governing standard with a notation: “All heights measured per Austin LDC 25-2-551 and IBC 202. See ‘Zoning Data’ sheet for summary.”

Drawing Convention: Section/Elevation Sheet Example

  • Section tag label: “Sect. A-A, Elevations shown relative to AGP (see calculation).”
  • Tick marks at each critical height (AGP, ridge, eave) with dimension lines extending to relevant points-annotated in feet and inches.
  • Comment bubble at ridge: “Building height: __’-__” above AGP (35’-0” max per LDC 25-2-551).”

Floor Area Ratio (FAR) Calculation and Drafting for SF-3

Accurate Differentiation: Conditioned, Unconditioned, Garage, and Porch Spaces

SF-3 floor area ratio (FAR) compliance is scrutinized at both schematic and permit plan stages in Austin. The LDC 25-2-551 requires:

  • Inclusion of all gross conditioned floor area-measured from exterior wall faces and not omitting interior chases, stairs, or mechanical closets.
  • Precise exclusion of spaces such as unconditioned open porches and garages (unless finished/conditioned).
  • Correct application of partial-credit rules for certain attics, mezzanines, or unfinished spaces with headroom under 7’-0”.

Every floor plan set should:

  • Use CAD layers named FAR_COND, FAR_GARAGE, FAR_PORCH, each space type color-coded or hatch-filled uniquely.
  • Annotate each space with its calculated net area-call-out balloons for “1st Floor Conditioned: __ SF,” “Garage (Unconditioned): __ SF excluded from FAR.”
  • Dimension interior to exterior walls at each level; overall dimension string must match site/building footprint dimensions.
  • Include ceiling heights in plan notes to verify habitable space definitions (see IRC for 7'-0" minimum).

Tabular Presentation: FAR Summary Table and Calculation Box

A dedicated box on the code or zoning sheet must tabulate:

SpaceArea (sq ft)FAR Inclusion
First Floor Conditioned_____Yes
Second Floor Conditioned_____Yes
Garage (Unconditioned)_____No
Front Porch (Open, Unconditioned)_____No
Rear Porch (Screened, Conditioned)_____Yes
Total FAR Area_____ 
Lot Area_____ 
FAR Ratio_____ (max. allowed per LDC 25-2-551)

Immediate adjacency to keyed floor plans prevents plan-reviewer confusion and missed scope. Best practice: tie each row in the table to a plan balloon with matching coded identifier.

Plan-Review Triggers and Corrections

  • “Area tabulation omits stair landing with ceiling height above 7’-0”-must be included in FAR per LDC 25-2-551(D).”
  • “Garage depicted includes mechanical system and insulation; clarify if conditioned or revise area summary.”
  • “Enclosed porch on rear yard must be included in FAR-revise summary table and use labeling.”

Drawing-Sheet Conventions and Take-Off Best Practice

  • Every labeled area must graphically match the boundary of the calculated measurement (wall-to-wall for conditioned).
  • Include dimension strings on plans for both net room dimensions and overall footprint-matched to site plan extents.
  • On each floor plan sheet, add note: “All FAR calculations per Austin LDC 25-2-551 and DSD policy.”

Architectural Projections and Setback/Compatibility Detailing

Drafting Eaves, Balconies, Bay Windows, and Covered Porches Relative to Setbacks

Setback encroachments and compatibility standards are a frequent pain point for both initial permit reviews and field inspections. The SF-3 zone, under LDC § 25-2-555 and the Compatibility Standards (LDC 25-2-556, 25-2-557, and 25-2-777), is explicit about required minimums:

  • Front yard: 25’-0” minimum
  • Interior side yard: 5’-0” minimum
  • Rear yard: 10’-0” minimum

Architectural projections are permitted under defined limits:

  • Eaves or roof overhangs: 2’-0” max projection into required yard (LDC § 25-2-513(A)(1)).
  • Bay or box windows: 2’-0” max projection.
  • Uncovered steps/stoops (≤3'-0" above grade): 3’-0” projection allowed.
  • Covered porches, open on 3 sides: 5’-0” into the front yard in appropriate districts (confirm if qualifies for SF-3).

Drafting Section and Plan Details to Illustrate Compliance

  • All projections must be drawn to scale and dimensioned in both plan and section. Example section call-out: “Eave projection: 1’-6” into side setback (2’-0” max per LDC 25-2-513).”
  • Setback lines must be shown as heavy dashed lines on each site and floor plan, labeled with yard type and required minimum (“5’-0” Side Yard Setback-LDC 25-2-555”).
  • Projection extents should be annotated to physically measure the depth from the main wall face to the outer edge of the projection with end-point dimension lines.
  • On compatibility-plan drawings (as required adjacent to SF-5 or less intense districts), show and dimension the compatibility setback planes: “45° plane from 15’-0” height at side/rear, eave encroachment 2’-0” allowed per LDC 25-2-777(C)(2).”
  • If an exemption is claimed (roof overhangs into plane), include a detail call-out: “Eave within 2’ of compatibility setback plane per LDC § 25-2-777(C)(2).”

Common Plan-Review Redlines Specific to Projections

  • “Eave projects 2'-6" into side yard; exceeds 2'-0" max, must be revised to comply with LDC 25-2-513.”
  • “Porch roof depicted encroaches more than 5’-0” into the front setback-revise or provide clarification if porch is open on required sides.”
  • “Section does not show exact projection depth; dimension from wall face to furthest point required.”

Material call-outs for projections should cite IRC R302.1 for fire separation if within 5’-0” of property lines. Bay windows and balconies often require structural details or note: “Bay window per IBC 1405.4 and LDC 25-2-513, projection < 2’-0”, all materials weather-protected.”

Integrating SF-3 Zoning Compliance, Notes, and Code References on Plan Sheets

Developing a Comprehensive Zoning Data/Code Compliance Sheet

Every Austin SF-3 drawing set that succeeds in DSD runs incorporates a zoning data and code compliance sheet-typically Sheet G-002 or G-003-near the front of the plan set. This “Zoning Data” table synthesizes lot information, setbacks, envelopes, height, FAR, and impervious cover into a format that mirrors the DSD checklist and preemptively addresses common review comments.

  • Project Information Block:
    “Project Address: 1234 Main St, Austin, TX 78704”
    “Zoning: SF-3 Family Residence”
    “Legal Description: Lot 7, Block 2, Travis Heights”
    “Watershed: Barton Springs Zone”
  • Zoning Compliance Table Example (SF-3):
    RequirementCode ReferenceProposedAllowed
    Lot AreaLDC 25-2-492(B)7,320 SF5,750 SF min
    Lot WidthLDC 25-2-492(B)60'-0"50'-0" min
    Front SetbackLDC 25-2-492(D)25'-0"25'-0" min
    Side SetbackLDC 25-2-492(D)5'-0"5'-0" min
    Rear SetbackLDC 25-2-492(D)10'-0"10'-0" min
    Building HeightLDC 25-2-555(C)33'-4"35'-0" max
    Bldg CoverageLDC 25-2-555(D)38%40% max
    Impervious CoverLDC 25-2-492(D)44%45% max
    FARLDC 25-2-551(D)0.41Per code

Direct code citations must accompany every value, and sheet must include hyperlinks or direct references to the City of Austin’s eLaws for the LDC:
“All zoning restrictions per Austin Land Development Code Title 25, especially Chapters 25-2 and 25-8, as amended.”

Pre-Empting Plan-Review Redlines with Correct Notes and Tabular Data

  • Explicitly label each drawing-site, floor, section sheets-with a call-out at border or composition block: “Refer to Sheet G-002 ‘Zoning Data’ for regulations and project-proposed parameters.”
  • Each table entry on ‘Zoning Data’ must cross-correlate to physical locations on site, floor, and elevation plans. Failure to tabulate or reference actual drawn dimensions is a frequent cause for DSD correction cycles.
  • Include typical notes triggered by permit department workflow:
    “Plan sheet dimensions and areas correspond to figures shown in Zoning Data Table. Any deviation in field must be resubmitted for DSD review per City of Austin Plan-Change Policy.”
  • Attach ‘DSD Plan Review Checklist’ as an appendix or supplemental sheet if requested.

Additional Mandatory Notes and Construction Sheet Integration

  • Setbacks: “All structures and projections shown meet required setbacks as defined by LDC § 25-2-492(D), measured perpendicular from property line.”
  • Fire-Resistance: “All exterior walls located less than 5'-0" from a property line constructed to 1-hour fire resistance per IRC R302.1.”
  • Energy/Accessibility: “Envelope assemblies comply with 2024 IECC (Austin Amendments), including R-____ wall, R-____ roof, U-____ glazing.”
  • Height: “Maximum building height not to exceed 35'-0" above averaged grade plane as defined by LDC 25-2-551 and IBC 202; see Elevations/Sections for detailed calculation.”

Drawing Management: Sheet Conventions, Notation, and Plan Submission Workflow

Successful navigation of Austin’s DSD (using AMANDA permitting system) necessitates plan sets that communicate compliance in both numeric and visual format from title block to final detail. Effective strategies:

  • Dedicated ‘Zoning Data’ sheet placed immediately before first site plan sheet to set a reference point for all reviewers.
  • Impeccable cross-referencing between tabular data and keynotes/call-outs-dimension strings, hatch patterns, and notation ‘bubbles’ must triangulate back to compliance tables.
  • Plan sets must anticipate common DSD review requests: “Highlight the proposed structure in plan and elevation for clarity,” and “Provide (or separate) layers for impervious cover summary.”
  • Include a ‘Code Analysis’ narrative if the project includes multiple structures, special circumstances (flag lots, easements), or is subject to Neighborhood Plan Combining District overlay standards.

BIM models or PDF plan sets submitted for review must have all scale-sensitive data highlighted, and data tables must be live-linked or presented immediately adjacent to the corresponding drawings, not appended in specification divisions or separate addenda as is sometimes seen in non-compliant submittals.

Key Drawing-Sheet Call-Out Examples

  • “Impervious cover areas hatched and tabulated per LDC § 25-8-63. See Table X on Sheet C-1.”
  • “Building height dimensioned AGP to ridge. Ref. Calculation, Sheet A-2. Not to exceed max per LDC 25-2-551.”
  • “FAR area keyed to boundaries on Floor Plan. See summary, Sheet G-002.”
  • “Eave projection 1’-11” into side setback. Under 2'-0" legal limit, LDC 25-2-513.”

Addressing Real-World Plan-Review Corrections

  • Track and summarize reviewer redlines per sheet iteration, incorporating DSD staff comments into drawing notation for future plan sets. E.g., “(DSD Redline, 2022-R#16): Note added re: porch calculation, Sheet A-101.”
  • Update data tables for each resubmission to maintain auditorable compliance trail.
  • Use explicit code citations for all ambiguous points: “Detached garage excluded from FAR per clarified definition in LDC 25-2-551 (D)(3).”

Summary

The precision required for drafting in compliance with Austin, TX’s “McMansion” Ordinance (applicable to SF-3-zoned lots) is measured not just in absolute numbers but in clarity, transparency, and consistency across all drawing sheets. The integration of layered hatching, explicit dimension strings, credible tabular data, direct code citations, and careful annotation is key to successful navigation of both Plan Review and Inspection in the City of Austin. Anticipating department review comments, annotating charts and dimensions for cross-verification, and integrating code requirements visually at every drawing phase transforms a code-minimum submittal into a DSD-ready package.

Kingsway Drafting & Design delivers architectural drawing sets that anticipate and resolve compliance challenges with the detail and clarity Austin’s permitting process demands.