Under Austin’s Small Lot Amnesty Program (SLAP), development opportunities arise on substandard parcels-many created before 1946-provided documentation and drawings meet the letter of city, state, and ICC code. Sheet-level compliance is not incidental; it is achieved through deliberate drafting strategies, plan-sheet callouts, and specification of every property constraint and condition. SLAP submittals in Austin’s SF-3 and SF-4A zoning districts require documentation, calculation, and graphical conventions tailored to the demands of city reviewers and the unique limitations of legacy lots. Satisfying Development Services Department (DSD) reviewers-especially when reconciling legal non-conformities, meeting strict area thresholds, and supporting field implementation-demands precision and fluency with local standards.

Documenting Precise Lot Area, Impervious Cover, and Floor Area Ratio (FAR) Calculations for Austin DSD SLAP Review: Detailing on Site Plans for SF-3/SF-4A Zoning

Calculations for lot area, impervious cover, and floor area ratio (FAR) are fundamental to Austin permit plans. Errors or omissions here trigger delays and redesigns-especially when DSD is reviewing drawings for SLAP eligibility on small, irregular tracts.

Lot Area Documentation and Drawing Standards

Lot area, defined by Austin LDC § 25-2-492 as “the total horizontal area within the lot boundaries,” is the basis for all other development constraints. Sheet A1-the Site Plan-must present boundaries dimensioned to legal descriptions, certified survey data, or platted records. Each side of the lot must have its length labeled; the drawing must incorporate a north arrow and scale (minimum 1”=20’-0” for urban lots; 1”=10’-0” is preferred for very small tracts). The total lot area shall be calculated and indexed on the sheet, positioned in a dedicated “Site Data Table.” This table should read as follows:

  • Lot Area: [xxxx] sq. ft. (per plat or survey [doc/date])

Example:

  • Lot Area: 3,750 sq. ft. (per Plat 1946-0023A, recorded 08/12/46)

DSD plan reviewers expect visible, dimensioned property lines-not implied boundaries. Redlines are common: “Property boundaries are not clearly defined; provide accurate dimensions.” - i.e., missing end-points, ambiguous callouts, or absence of total area figure can stall review.

Impervious Cover: Calculation Methods and Graphics

Austin’s SF-3 and SF-4A zones prescribe strict limits on impervious cover, enforced to protect urban watersheds. Per LDC § 25-2-492, for SF-3, maximum impervious cover is 45% of lot area; for SF-4A, it is 65%. All surfaces preventing natural infiltration-foundations, driveways, porches, decks, and even certain compacted gravel-must be included.

  • Impervious Cover Calculation Table (on Site Plan):
    • Building Footprint(s): [xxxx] sq. ft.
    • Driveway(s): [xxxx] sq. ft.
    • Patios/Walks: [xxxx] sq. ft.
    • Other (specify): [xxxx] sq. ft.
    • Total Impervious Cover: [xxxx] sq. ft. ([xx]% of lot area; max allowed: 45% [SF-3] / 65% [SF-4A])

The covered surfaces should receive clear hatch or shading legends. Each area is labeled with dimensions on plan: “25’-0” x 10’-0” = 250 SF DRIVEWAY IMPERVIOUS.” Hatching must be consistent across sheets; ambiguous or inconsistent shading is a red-flag for plan reviewers.

Typical redline: “Impervious cover calculations exceed the allowable percentage for the zoning district.” If this appears, a drafter must surface a full breakdown, and either reduce coverage (move/resize walkways, convert to pervious pavers) or document pervious status of disputed surfaces (“flagstone set in sand, not counted as impervious”).

Floor Area Ratio (FAR) Documentation and Conventions

In SF-3 zones, FAR is not a base limit, but Subchapter F (the “McMansion Ordinance”) governs most urban neighborhoods, capping FAR for single-family homes at 0.4 or 2,300 sq. ft. (whichever is greater). For SF-4A, FAR is commonly capped at 0.55. Sheet A1 must show total gross floor area (GFA)-sum of all stories’ enclosed, conditioned floor area. This is listed in a table:

  • Floor Area Calculation Table:
    • First Floor (conditioned only): [xxxx] sq. ft.
    • Second Floor: [xxxx] sq. ft.
    • Other Stories/Attics: [xxxx] sq. ft.
    • Total Gross Floor Area: [xxxx] sq. ft.
    • FAR: [GFA] / [Lot Area] = [xx]
    • Max allowed: 0.4, or 2,300 sq. ft., whichever is greater [SF-3, Subchapter F]; 0.55 [SF-4A]

Each floor plan sheet (A2, A3...) must indicate the exact area for that level (“1ST FLOOR = 1,135 SF (PERIMETER SHOWN) [INCLUDES CONDITIONED SPACE ONLY]”). Spaces counted towards FAR are called out using shading or perimeter lines-the legend must unambiguously distinguish between conditioned and non-conditioned area.

Improper or missing FAR documentation remains a top source of DSD reviewer comment. Unless calculations and diagrams itemize every portion of habitable area (“Attic storage excluded per §25-2-772”; “Unfinished garage not counted”), the plan risks a redline: “FAR calculations are missing or incorrect; ensure compliance with Subchapter F standards.”

Setbacks and Building Height-Code Prescriptions at a Glance

SF-3 and SF-4A setbacks apply regardless of lot size under SLAP. As per LDC § 25-2-492 and plan reviewer convention:

  • SF-3: Front 25’, Side 5’, Rear 10’
  • SF-4A: Front 15’, Side 3’, Rear 5’

Building height is capped at 35’, with Subchapter F imposing 32’ maximum in designated neighborhoods (unless within the 100-year floodplain). These numerical constraints must appear-with code references (e.g., “35’-0” MAX HT PER §25-2-492”)-on both the data table and building elevations.

All materials, whether for slabs or cladding, must reference current IRC standards as locally amended; Austin has adopted the 2015 IRC and IBC, documented in LDC 25-12. Omission of code references or conflicting material specs is a frequent reviewer comment: “All assemblies must comply with 2015 IRC as locally amended; provide material callouts.”

Strategies for Graphic Representation and Notation of Existing Non-Conforming and Proposed Setbacks on Austin Permit Plans for SLAP Compliance

Existing non-conforming conditions are routine on SLAP-eligible lots. Plan sheets must visibly distinguish existing setbacks from those now required, and use rigorous notation to document pre-code encroachments or discrepancies per LDC Chapter 25-2 and local amendments (LDC §25-12-3).

Code Basis: Zoning Setbacks and Local Amendments

All setback dimensions derive from LDC §25-2-492 (for urban single-family zones), enforced per plat and site survey. Within Austin’s adopted 2015 IBC/IRC (see LDC §25-12-3), local amendment may affect particular neighborhoods or historic overlays, altering mandatory distances or allowable encroachments.

  • SF-2 baseline: Front 25’, Side 5’ (or 15’ for a side street on corner lots), Rear 10’
  • Key data must be rooted in current zoning: “SF-3-NP”, “SF-4A-CO”, with overlays listed in title block and site data table.

Drawing Conventions for Setbacks and Non-Conforming Conditions

On the primary site plan, property lines must be solid, setback lines dashed, differentiated by lineweight from utility or easement boundaries. The legend should specify:

  • Thick dashed line = required (current code) setback
  • Thin double-dash or dotted = existing non-conforming setback
  • Double hatching = area of existing encroachment (with clear text, e.g., “NON-CONFORMING FRONT YARD-EX. HOUSE @ 17’ SETBACK; CODE = 25’”)

Every building element’s distance from the property line must be dimensioned-“5.3’ FROM N PROP LINE”; “10.1’ TO REAR PROPERTY LINE”-including both corners and projections. Enclosed spaces, open porches, and steps are differentiated by annotation in accordance with the degree such elements impact setback calculation (see LDC and DSD interpretations).

For non-conforming structures, notation must include a reference, e.g., “See Note 2: Existing non-conforming structure (erected 1947); legal status per City Archival Permit #2114-A. Any expansion triggers compliance per LDC §25-12-3.”

Reviewer Comments and Typical Redlines

The most common DSD comments on setbacks:

  • “Incorrect setback depictions-property lines and required setbacks must be shown in plan and dimensioned.” Redline: Add/correct dashed linework and clearly dimension each building face.
  • “Non-conforming structures not identified-provide explicit callout and note documenting status.” Redline: Place note and graphic reference on plan.
  • “Proposed element (e.g., porch addition) encroaches required setback; revise plan for compliance or note applicable code exception.”

Detail and Enlargement Drawings

Complex boundary conditions-such as irregular property shapes, flag lots, or substantial grade change-require enlarged plan insets. These “bubble callouts” tie to full-size details (e.g., “SEE DETAIL 2/A1.2 FOR SETBACK CONDITION AT NW CORNER”). Elevations and sections must reinforce plan information by showing property lines projected in “ghost” lines behind architectural elements, including explicit vertical and horizontal distances.

Every legend symbol, line style, and callout must be included in the standard site plan legend and general notes. Sheet title blocks reference the zone (e.g., “SF-3-NP”-Single Family Neighborhood Plan), current edition of code adopted (Austin's amendments to 2015 IRC/IBC per LDC §25-12-3), and special overlays if relevant.

Drafter's Guide to Illustrating and Dimensioning Building Height and Stories on Sections/Elevations for Austin SLAP Projects

Few redlines cause as much redesign pain as a “building exceeds permitted height” comment: the root is often failure to correctly interpret LDC’s unique measurement protocol for height and story-especially for SLAP lots where a small tally error can push a structure out of conformance.

Official Definitions and Measurement Standards

Per LDC §25-1-21(50), Austin measures building height “from the average of the highest and lowest grades adjacent to the building” to the appropriate point:

  • Flat roofs: top of coping
  • Mansard roofs: deck line
  • Pitched/hip roofs: average height of highest gable
  • Other roofs: highest point of building

Story, per IBC §202 and LDC, is segment “between the upper surface of a floor and the upper surface of floor or roof next above.” Basements are counted as stories if finished floor above is >6’ above grade at any point (or for more than 50% of perimeter).

Subchapter F (McMansion standards) further restricts most Central Austin single-family projects: max height is 32’ (except 35’ in 100-year floodplain).

Elevation and Section Drawings: Dimension Callouts and Planes

Main elevation sheets must display both “natural grade” and “finished grade” adjacent to each façade. This requires either:

  • Spot elevation callouts (“+512.4’ NGVD29 @ NE CORNER; +511.8’ @ SW CORNER”)
  • Dashed grade line, labeled as “NATURAL GRADE-AVERAGE ELEV = +512.1’” and “FINISHED GRADE-AVERAGE ELEV = +511.5’”

Dimension lines, vertically, must be drawn from average grade-not from finish floor-up to “top of roof per LDC 25-1-21.” A sample notation: “32’-0” MAX HEIGHT (MEASURED FROM AVG ADJ. GRADE PER 25-1-21(50)).”

All roof types require graphic label of the measuring point (e.g., gable mid-point, coping, deck line) with leader note per code. All stories, including qualifying basements and habitable attics, must be demarcated-“STORY 1: FIN FLOOR EL 0’-0”; STORY 2: FIN FLR EL +10’-2”…”-with a schedule or callout box showing area per story (ties to FAR table).

Setback Planes (Subchapter F) in Drawing Practice

Within Subchapter F, side and front “setback planes” control upper volume:

  • Side setback plane: Starts at 15’ above side property line, slopes in at 45°
  • Front setback plane: Starts at 20’ above front property line, slopes in at 45°

On elevation and section sheets, these planes are shown as dashed lines angling inward. Annotate with text: “15’-0” HEIGHT LIMIT/45° SLOPE PLANE PER SUBCH F §2.6.A”. Any proposed roof/dormer crossing the plane is another major review redline.

Common DSD Reviewer Comments

  • “Height not measured from average of highest and lowest adjacent grades-recalculate and revise.”
  • “Design exceeds 32’ height per McMansion standards (§25-2 Subch F). Adjust roof or finish floor elevation to comply.”
  • “Building element (e.g., dormer) violates setback plane.” Plan must be adjusted so all portions respect planes as projected from property lines.
  • “Basement not counted as a story-review if finish floor above triggers full story per elevation.”

Dimension, Fire-Rating, and Material Specs

  • Max Heights: 32’ (Subchapter F zone), 35’ (otherwise)
  • Setback Planes: 15’/45° (side), 20’/45° (front) measured from property line
  • Fire-Rated Walls: 1-hour walls required within specific setback distances per IRC/IBC-must be labeled on plan and wall sections with UL assembly number and “PROVIDE 1-HR RATED ASSEMBLY PER 2015 IRC/IBC CH7”
  • Roof/Wall Materials: Call out by trade and performance: “ASPHALT SHINGLES W/ 30# FELT (MIN 110 MPH RATED)”; “FIBER-CEMENT LAP SIDING OVER ZIP SYSTEM SHEATHING”

Integrating Austin DSD Plan Review Comments and Jobsite Call-Outs for SLAP-Specific Conditions

No project survives first submission without at least a handful of DSD reviewer comments. The permit department’s workflow can include zoning, engineering, environmental, and fire review-often each responding to different aspects of SLAP-involved sites. Drafters must document all response actions and current status with a disciplined, revision-scheduled approach tailored to legal non-conformities and SLAP-specific permitting hurdles.

Legal Non-Conforming Elements: Recognition and Direction

Existing elements that were lawful when built but are now non-conforming enjoy certain protections-but cannot be expanded or materially altered to increase non-conformity (LDC §25-12-3, Section G102.3). The permit set must document such features both graphically and textually.

  • Notation Example: “EXISTING NON-CONFORMING WALL-ERECTED 1948 PER ARCHIVE REVIEW. NO EXPANSION OR ALTERATION INCREASES NON-CONFORMITY PER LDC §25-12-3”

Sheets must further describe the scope of “work to remain,” “work to be removed,” and “proposed alteration.” For partial demolitions, shading and crosshatches on plan differentiate removed (diagonal hatch) versus protected (solid color or bold outline) work. Any planned demolition of 50%+ market value requires compliance upgrade for entire structure.

DSD Plan Review Workflow and Revision Management

All plan review cases are logged in Austin’s online portal. Revision management within sets uses “clouding” (rev bubbles), keyed revision numbers/letters in the title block, and a “Revision Schedule” table on each affected sheet (per AIA convention):

  • Rev: B / Date: 2024-01-15 / Description: “FAR calculation update per DSD comment B6-FAR revised to 0.38”

All reviewer requests or directives-“Adjust impervious cover tabulation; clarify setback at NE property corner per survey”-must tie to specific drawing changes, reflected in clouds and revision notes. An unresolved DSD comment is a guarantee of bottleneck at subsequent submittal.

Cross-discipline coordination is vital: structural, MEP, and civil sheets must all reflect the updated geometry and code responses. For example, moving a fire-rated wall to accommodate a non-conforming element on architectural sheet A2 triggers corresponding structural and code analysis detail updates.

Call-Outs and Detail Standards for Field Direction

All site and code compliance features addressed by reviewer comment (e.g., “Heritage tree root protection-3’ minimum soil protection per City Arborist Memo dated 2024-02-01”) appear not only in general site notes but as bold callouts on plan and details. For on-site execution, each drawing must allow the field team to quickly discern whether a feature is to be altered, protected, preserved, or demolished.

Revision clouds and their associated “delta” reference must be kept clear and not obscure vital dimensions-especially on SLAP lots where buildable space is at a premium. Sheet index must record the latest submitted version (“ISSUED FOR PERMIT-REV C; DSD RESPONSE-2024-02-21”) with a summary of all prior significant city comments responded to in the set.

Dimensions, Ratings, Accessibility, and Materials at Revision

Dimensional changes (e.g., after a required reduction in driveway size to meet impervious cover) must be called out in both data tables and direct dimensions on revised sheets. Any fire rating or material change mandated by a code correction must reference detail numbers, code sections, and updated manufacturer specs (e.g., “NEW GARAGE EAST WALL: 1-HR RATED GYPSUM ASSEMBLY PER UL U419, 2015 IRC CH7, REVISED FROM 1/2” NON-RATED DEMISING WALL”).

Addressing Accessibility (IRC Chapter 11) and Fire Apparatus Access (Austin Fire Code) on Constrained SLAP Lots: Site Plan Requirements and Detailing

Small, pre-code tracts eligible under the Small Lot Amnesty Program frequently challenge standard approaches to accessibility and fire apparatus access. Achieving compliance on-site-and on paper-requires granular site detailing, explicit grading notes, and close referencing of code backup.

Accessibility (IRC Chapter 11): Drawing and Notation on Small Lots

Where new construction on a SLAP parcel triggers accessibility provisions (notably for attached dwelling units or qualifying multifamily under current code), requirements include:

  • Accessible route: minimum 36” clear width
  • Doorways: minimum 32” clear opening @ 90° open, with maximum threshold 1/2” height
  • Ramps: 1:12 (8.33%) maximum slope, landings at least 60” long
  • Accessible parking: at least one 96” stall with 60” adjacent aisle-firm, stable, slip-resistant surface

On the site plan, these routes, landings, and parking stalls are annotated as “ACCESSIBLE ROUTE-MIN 36” CLEAR-SLOPE 1:12 MAX PER IRC CH11,” “ACCESSIBLE PARKING-96” STALL W/ 60” AISLE (STRIPED OR CURBED).” Cross slopes, where present, must be called in plan and section, and grading/slope percentages labeled (e.g., “PROPOSED WALKWAY SLOPE = 5.0%”).

Failure to maintain the 1:12 ramp slope, insufficient door widths, or missing parking dimensions are all rapid paths to a redline: “Accessible route from parking to entrance exceeds maximum slope of 1:12. Adjust grading to comply with IRC Chapter 11 requirements.”

Fire Apparatus Access: Austin Fire Code Detailing for Constrained Sites

Austin’s 2024 Fire Code, as locally amended per LDC §25-12-173, requires:

  • Fire lane width: minimum 25’ unobstructed
  • Vertical clearance: 14’ minimum (for wires, limbs, overhangs)
  • Turning radii: 25’ inside, 50’ outside minimum; must be supported by dimensioned “turning diagram” on site plan
  • Surface: all-weather, supporting imposed loads (reference AASHTO spec for bridges/elevated surfaces)

On sheets, fire lanes are identified with a bold “FIRE LANE-NO PARKING” callout, width dimension string (“25’-0” MIN WIDTH PER AFC §503.2.1”) and directional arrows. Turning diagrams use a dashed, double-headed curve shaped to code radius, labeled “FIRE APPARATUS TURNING RADIUS-25’ INSIDE, 50’ OUTSIDE MIN.”

On SLAP lots, tight access often means applying local exceptions: for city-maintained streets, widths as low as 20’ may suffice if fire department approval is documented, with this notation: “FIRE ACCESS AS APPROVED, SEE AFD VARIANCE LETTER DATED [2024-02-28],” and clouded boundary lines indicating the specific area of relief.

Plan reviewers frequently comment on insufficient fire lane dimensions, poor turning radii, or poorly signed fire protection features. Required fixes include “reorient driveway,” “reduce fence post encroachment,” or “add Knox Box at entry gate per AFC §506.”

Specific Plan-Sheet Details and Specs for Small, Non-Conforming Sites

  • Fire Lane: 25’ min width; 14’ min vertical clearance
  • Turning Radius: 25’ inside, 50’ outside (dimensioned and diagrammatically indicated)
  • Accessible Parking: 96” stall, 60” aisle (dimension lines and hatching callout)
  • Ramps: 1:12 maximum slope (callout: “RAMP: 1:12 MAX; RAILING PER CH32”)
  • Materials: All-weather aggregate, stamped with design load (AASHTO)-callout “COMPACTED GRAVEL, 95% PROCTOR MIN, LOAD TESTED TO 75,000#”

Reviewer Comments and Redline Triggers

  • “Fire lane width does not meet 25’ minimum; revise site plan to comply with AFC §503.2.1.”
  • “Proposed turning radius is insufficient for fire apparatus; ensure 25’ inside and 50’ outside radius per AFC §503.2.4.”
  • “Accessible route from parking to entrance exceeds max allowed slope; revise grading.”

All required specs, dimensions, and code citations are not merely placed in a general notes section but directly annotated in plan, section, and detail drawings-supporting both reviewer analysis and field layout.

Conclusion

From site plan through elevation, detail, and revision schedule, SLAP-compliant submission sets demand not only mastery of Austin’s layers of code but the rigorous application of graphic standards, dimensioning conventions, and sheet-level cross-references tied to the unique constraints of urban infill work. Clear notation, explicit calculation, precise representation of all zoning and code restrictions, and disciplined revision management distinguish construction intelligence at the drawing board. Every tabulation, callout, and code reference on Austin SLAP permit plans is a proactive foundation for streamlined review, confident field construction, and successful project delivery-qualities at the core of Kingsway Drafting & Design’s service principles.