All articles
compliance · HVHZ

NOA vs. Florida Product Approval: which one does your submittal actually need?

If you build in South Florida, you have run into both acronyms. A supplier sends a Florida Product Approval number, the plans examiner asks for a Notice of Acceptance, and the submittal stalls for two weeks while somebody figures out which document was actually required.

They are not the same thing, and the difference is jurisdictional rather than technical.

Stylized 3D of two approval documents linked by a neon lime-green line to a storefront window, on a deep navy background

The short version

Miami-Dade Notice of Acceptance (NOA) is issued by the Miami-Dade County Department of Regulatory and Economic Resources. It certifies that a product has passed the county’s own testing protocols — the TAS series — and is accepted for use within Miami-Dade County.

Florida Product Approval is the statewide system administered under the Florida Building Commission. A product approved there carries an FL# and is valid across Florida, including in High-Velocity Hurricane Zone counties, provided the approval explicitly covers HVHZ use.

The trap is that last clause. A statewide FL# does not automatically mean HVHZ-approved. The approval document has to say so.

Where projects actually get stuck

In practice, three things account for most rejected building-envelope submittals we see:

  1. An FL# submitted for an HVHZ project without HVHZ coverage. The number is real, the product is legitimate, and the approval simply does not extend to Miami-Dade or Broward. The reviewer is right to bounce it.
  2. An expired or superseded NOA. NOAs carry expiration dates and get revised. Contractors pull a PDF from a folder used on a job two years ago, and the version has since been replaced.
  3. Installation conditions that do not match the approval. The approval covers a specific substrate, anchor pattern, and design pressure range. A window approved for a concrete opening is not approved for the wood-framed condition someone detailed on sheet A-501.

The third is the expensive one, because it usually surfaces at inspection rather than at plan review.

How to check before you order

Work in this order and most of the pain disappears:

  • Establish the jurisdiction first. Miami-Dade and Broward are HVHZ. That single fact determines which documents are even eligible.
  • Pull the design pressures off the structural drawings, not off the product data sheet. The approval has to cover the pressures your project requires at that specific opening.
  • Verify the approval is current on the issuing authority’s own portal, not from a supplier’s PDF.
  • Read the installation detail in the approval and compare it to the detail on the architectural drawings. If they disagree, that gets resolved now, not in the field.

An approval document is not a product endorsement. It is a statement that a specific assembly, installed a specific way, meets a specific pressure — and every one of those words matters at inspection.

Why this is worth systematizing

Any one of these checks takes a few minutes. The problem is that a mid-size envelope package might have forty distinct product configurations across six openings types, and the checks have to be repeated for every one of them, every time a supplier substitutes a product.

That is the kind of work that rewards a process rather than diligence. Keeping a live register of approvals by product, with expiration dates and covered pressure ranges, turns a two-week submittal stall into a lookup.

Once you know which document your project needs, reading a Miami-Dade NOA field by field is the next step. And to see whether a product’s approval covers the pressure at a specific opening, run the numbers in our free wind-load calculator. If you are handling approvals out of a folder of PDFs and institutional memory, a structured compliance workflow is worth a look.