Freedom Code Compliance
Multi Family

Multi Family Fence

Gate

Last updated: Apr 20, 2026

Section 1

Required Documents

Submit these with your initial project package.

Always required

  • Site Plan
    Site plan showing fence location, height, and relationship to property boundaries
  • Product Specifications
    Product specifications for fence materials and design

Courtesy screen

Courtesy screen on every plan review

Every plan FCC reviews receives a limited courtesy screen for the items below when they are reasonably visible in the submitted documents. If we see an apparent issue that could cause the plans to fail review by another agency, we will identify it as a Courtesy Comment. Courtesy Comments alone do not cause FCC to fail or return the plan set unless the same condition also creates a building-code compliance issue within FCC's review scope. The responsible agency makes the final determination—for example, Planning and Zoning for setbacks, lot coverage, use, and other lot-compliance matters. The absence of a Courtesy Comment is not approval of those separate requirements.

  1. #01Plan and document coordination

    Obvious clerical, title-block, sheet-index, permit-description, or cross-sheet inconsistencies visible in the submitted documents. A Courtesy Comment on these items does not cause FCC to fail or return the plan set unless the same condition also creates a building-code compliance issue within FCC's review scope.

    FBC-B 107.2.1
  2. #02Zoning and site coordination

    Apparent setback, lot-coverage, use, or site-dimension conflicts visible in the submitted plans that could cause the plans to fail Planning and Zoning review. Planning and Zoning makes the zoning and lot-compliance determination. The absence of a Courtesy Comment is not approval of those separate requirements.

  3. #03Floodplain coordination

    Apparent inconsistencies or missing coordination in flood-zone, design-flood-elevation, finished-floor, or flood-opening information shown on the plans that could cause the plans to fail floodplain review. The floodplain administrator makes the determination. The absence of a Courtesy Comment is not approval of those separate requirements.

  4. #04Fire-authority coordination

    Apparent separately reviewed fire alarm, sprinkler, hood-suppression, smoke-control, or similar coordination issues visible on the plans that could cause the plans to fail fire review. The fire marshal makes the determination. The absence of a Courtesy Comment is not approval of those separate requirements.

Section 2

Approval criteria for this project type

These are the building-code criteria FCC uses to determine the plan-review result. An unresolved item may be issued as a Required Correction and cause the plan set to be returned for correction.

BuildingRequired

  1. #01Design wind speed & exposureLife Safety

    Structural drawings must declare design wind speed (Vult) and exposure category matching the jurisdiction's wind speed map.

    FBC-R R301.2.1ASCE 7-22
  2. #02Pool barrier compliance (if applicable)Life Safety

    If fence encloses a pool, must meet ISPSC/FBC-R pool barrier requirements.

    FBC-R R4501.17ISPSC 305
  3. #03Engineer of record sealDocumentation

    Structural drawings must bear a current Florida-licensed engineer's seal and signature.

    Florida Statutes Chapter 471FBC-B 107.3.5

Section 3

Inspection Walkthrough

Inspections are listed in their typical phase order. Your FCC inspector will confirm which apply to your project. Call (772) 222-6679 with questions.

Building

Phase #1

Final Building

RequiredTypical Final
  1. Post installation and depthCritical

    Verify fence posts are set at proper depth and spacing per approved plans

    FBC-R R301.1
  2. Fence height and setbackCritical

    Verify fence height and setback from property line per approved plans

    FBC-R R301.1
  3. Material and constructionCritical

    Verify fence material and construction method match approved plans

    FBC-R R301.1
  4. Gate operation

    Verify gates open, close, and latch properly

    FBC-R R301.1