All articles
compliance · HVHZ

Miami-Dade vs. Broward: where the submittal actually differs

Miami-Dade and Broward are both in the High-Velocity Hurricane Zone. That shared fact makes people assume the two submittals are identical. They are not.

The wind loads are different, the product-approval document each department leans on is different, and the web portal you verify a number in is different. If you price a storefront expecting one package to fit both counties, the second job stalls.

Stylized 3D render of two storefront window panels facing each other across a dark void, connected by a jagged neon lime-green energy bolt with glowing gauges and directional arrows, on a deep navy background

The short version

The wind load is higher in Miami-Dade. Florida Building Code (FBC) Section 1620.2 sets the design wind speed for each HVHZ county. Miami-Dade runs higher in every risk category: 165 mph (Risk Category I), 175 (II), 186 (III), 195 (IV). Broward is 156, 170, 180, 185. The same opening can need a higher design pressure on the Miami-Dade side of the county line.

The product-approval document differs. Miami-Dade issues and administers its own Notice of Acceptance (NOA) through the county Product Control program. Broward operates on the statewide Florida Product Approval system (the FL number). Florida Statute 553.842 governs both paths, and the Florida Building Commission accepts approval by the State or by Miami-Dade County for use within the HVHZ — but which document a department wants you to submit is a per-project call.

So you verify in a different place. Miami-Dade numbers go through the county Product Control search. Florida numbers go through the FL product-approval portal.

The two wind loads behind the same “HVHZ”

“HVHZ” names the zone, not a single number. Section 1620.2 assigns a distinct 3-second-gust design wind speed to each county, by risk category:

Risk Category Miami-Dade Broward
I (limited-occupancy) 165 mph 156 mph
II (standard occupancy) 175 mph 170 mph
III (essential facilities) 186 mph 180 mph
IV (high-occupancy / hazardous) 195 mph 185 mph

The gaps are 9, 5, 6, and 10 mph. Translated into design pressure, they are not small — design pressure scales with the square of wind speed, so the Miami-Dade requirement at Category II is roughly six percent higher on the load side before you account for exposure.

This is why you read design pressure off the structural drawings, not off the county name. A product approved at a pressure that covers a Broward opening may not cover the identical opening twenty miles east in Miami-Dade. Check the pressure the approval carries against the pressure the opening needs — that is the step that decides the submittal.

The product-approval document is not the same

Here is where people get hurt. Both counties are HVHZ, so the instinct is to treat one approval as good for both. The approval systems are not one thing.

Miami-Dade runs its own product-control program and issues NOAs. That county NOA is what Miami-Dade departments expect to see, and it is verified in the Miami-Dade Product Control search.

Broward does not run its own NOA program. It relies on the statewide Florida Product Approval list. An FL number is valid there — but only if that specific listing explicitly covers HVHZ use. A statewide approval that does not state HVHZ coverage does not cover a Broward job, and it never covers Miami-Dade. This is the exact gap the NOA vs. Florida Product Approval distinction turns on: the number is real, the product is fine, and the coverage simply does not extend to the HVHZ.

Two practical consequences:

  • Miami-Dade project: expect an NOA, and confirm it is current in the county Product Control search.
  • Broward project: expect an FL number, and confirm that listing is approved for HVHZ use — not just “Florida.”

And in both counties, confirm the document is current. An expired or superseded approval is the most common reason a submittal comes back, and it is entirely preventable.

Same rules that do not change

For all the county-to-county variance, the substantive envelope rules are shared. Both counties apply the same HVHZ testing protocols — the TAS series for impact and wind loading. Both expect the anchorage, substrate, and opening size to match what the approval actually specifies. The differences are in the magnitude of the load and the document trail — not in the underlying test regime.

That is the practical takeaway for an estimating team: keep the engineering the same, but build the compliance step per county. Same testing standard, different target number, different paper to prove it.

Build the county check into your process

A package that sails through one county line can stall at the next purely because nobody checked which wind speed applied or which approval document was asked for. Fold three checks into every submittal before it ships:

  1. County + risk category first — that fixes the design wind speed off Section 1620.2.
  2. Approval covers that pressure — the document must list a design pressure at least equal to what the opening needs.
  3. Approval is valid for that county — Miami-Dade NOA coverage or an FL listing with explicit HVHZ coverage, whichever the department wants.

This is compliance work that looks like a lookup but is really a per-opening reconciliation — exactly the kind of deliverable the EnergyCheck compliance team carries so your people are not chasing numbers across two county systems on deadline.

The county line changes the number. Knowing which number belongs to which county is what keeps the submittal from bouncing.