All articles
compliance · HVHZ

How to verify a NOA or Florida Product Approval is still valid

The window series that cleared plan review on your last job can be ineligible on the next one without anyone issuing a bulletin about it. The two approval systems that cover South Florida go stale in two completely different ways, and only one of them gives you a date.

A submittal PDF reused because the NOA number looked familiar, and a supplier’s word that the FL number is current, both survive a bid package and fail at plan review. Verifying either takes about five minutes, and the check is different for each.

Stylized 3D render of two translucent glass approval documents on a deep navy background, scanned by glowing lime-green beams with a checkmark ring and a fading calendar ring

The short version

  • A Miami-Dade NOA expires on a date. The cover page states an expiration date, and the document says outright that it “shall not be valid after the expiration date stated below.” Typical cycle is five years.
  • A Florida Product Approval has no expiration date. Under Fla. Stat. § 553.842(1)(f), state and local approvals are valid until the requirements of the code they are based on change, the product changes in a manner affecting its performance, or the approval is revoked.
  • So the FPA clock is a code edition, not a calendar. The FBC 9th Edition takes effect December 31, 2026 — exactly the trigger the statute describes.
  • Look up the NOA in the Miami-Dade Product Control Search and the FL number on the state’s BCIS search. Neither requires a login or a fee, and neither substitutes for reading the document you get back.
  • Renewal of an NOA is not automatic, and a lapsed NOA is the most common reason an envelope submittal comes back on the first pass.

Two approval systems, two validity clocks

A Miami-Dade NOA is a document issued by the county’s Product Control Section for one tested configuration of one product line. It carries an issue date and an expiration date on the cover page, and it terminates at that date unless the manufacturer files for renewal.

A Florida Product Approval is a statewide record on the Building Codes Information System (BCIS) at floridabuilding.org, identified by an FL number. It stays valid until the code it is based on changes, the product changes in a performance-affecting way, or the Commission revokes or suspends it — grounds set out in Rule 61G20-3.013, F.A.C.

That asymmetry is the whole problem. An NOA that runs out is obvious the moment you read the cover page. An FPA that quietly stopped matching the code looks fine on the supplier’s spec sheet.

See NOA vs. Florida Product Approval for which of the two a given jurisdiction actually requires.

Checking a Miami-Dade NOA: three fields

Go to the Product Control Search at miamidade.gov/building/pc-search_app.asp, the county’s database of approved products, certificates and listings. Enter the file number exactly as written on the quote — the format is YY-MMDD.NN, so 21-1108.05 is the fifth NOA issued on November 8, 2021 — or search by manufacturer and category if you do not have it.

Then read three fields:

  1. The current version of the number. NOAs get revised and renewed, and each version supersedes the last. A number you recognize from an older bid package may be a superseded revision. The field-by-field walkthrough covers the rest of the document.
  2. The expiration date. If it has passed, the acceptance is lapsed. A product installed against a lapsed approval was not an approved product at the time of inspection — a worse problem than a returned submittal.
  3. The governing code edition. NOAs are backed by an approval document signed and sealed by an engineer of record, and manufacturers submit a letter of conformance naming the FBC edition the product was evaluated against. An NOA built on an earlier edition is worth checking before it goes in a package.

Why an NOA renewal is not automatic

The renewal language on the NOA itself is narrow. Renewal “shall be considered” after a renewal application has been filed and there has been no change in the applicable building code negatively affecting the product’s performance. Termination occurs at the expiration date, or earlier if the materials, use or manufacture of the product changed.

Three consequences for an estimator:

  • The county files renewals, not you. It is normal to find a product line still sold and currently unapproved.
  • A renewal is a filing with its own fee, and the same county application form covers three separate actions: new NOA, revision, and renewal.
  • A revision is not a renewal. A revision is valid only up to the expiration date of the original NOA. If you are relying on a revision, the original expiration date still governs.

RER can also revoke, modify or suspend an acceptance if the product fails to perform as accepted or to meet the requirements of the applicable code. Approval status is live, not a one-time grade.

Checking a Florida Product Approval: status, not a date

The state search lives in the BCIS product approval module. It takes an FL number plus the code version, or a manufacturer and code version if you are hunting for the number yourself.

Two things about that interface matter more than the search:

  • There is a code-version dropdown, and it defaults to the current edition — the 8th Edition (2023), as of this writing. Search under the wrong version and a perfectly good product returns nothing. That false negative is the most common mistake in the whole exercise; if a product comes up empty, re-run it under the previous edition before you conclude anything.
  • The record reports a status, and only one status clears plan review. Approved, Revoked, Suspended, Validated, Pending, Applied For, Denied. Anything other than Approved is not usable for new installations, regardless of what the product still does in the field. The same record states whether it is approved for use in the HVHZ or outside it, which answers the HVHZ question for a statewide approval.

Rule 61G20-3.013, F.A.C. lists the revocation and suspension grounds, and two show up in real projects: failure to maintain the quality assurance program for the manufacturing of the approved product, and advertising or selling a product for uses inconsistent with the conditions and limitations of its approval. The Commission must post approvals, denials and suspensions on BCIS — which is why the status column is there.

The edition change that resets every approval

The FBC 9th Edition takes effect December 31, 2026. The statute’s first validity trigger — the requirements of the code on which the approval is based changing — is precisely what an edition flip is.

Florida opened the 9th Edition product approval process on July 1, 2026. The Commission’s guidance gives manufacturers three routes, all visible on the state record you are checking:

  • Self-affirmation, for products whose standards and restrictions did not change, including a statement from an approved evaluation or validation entity where the underlying evaluation report refers to the previous edition.
  • Application revision, where the standards or restrictions affecting the product did change and new evidence — a test report or evaluation report — has to be submitted. Editorial-only revisions are not accepted for a code update, and self-affirmation is not available once the standards move.
  • A new product application, for products that fit neither path.

Applications are accepted with fees waived from July 1 through December 31, 2026, including submissions still made under the 8th Edition. That waiver window is a signal about expected re-filing volume. We covered the rest of the transition — wind loads and the expanded 160 mph zone — in what changes on December 31.

What “still valid” should mean in your bid file

A verification that lives in someone’s memory is not a verification. The check has to leave an artifact, and it has to happen at pricing time rather than permit time. In order:

  1. Identify the approval path. HVHZ work needs a Miami-Dade NOA or a statewide approval specifically evaluated for HVHZ use.
  2. Pull the record from the issuing body, not from the supplier’s submittal packet — the Product Control Search for an NOA, BCIS for an FL number.
  3. Check expiration on the NOA, status on the FPA. No date on the FPA does not mean no expiry; it means the code edition is the expiry.
  4. Confirm the edition the approval is based on will still be the governing edition when the permit is issued, not when you bid.
  5. Print the evidence and date it, and flag anything expiring inside the construction window.

The cost of skipping this is not the returned submittal. It is a window line that loses its approval between bid and permit — a re-price, a revised shop drawing, and a conversation with a general contractor who is counting days.

This is the mechanical part of envelope compliance — pulling the records, reading them against the project, keeping the evidence — and it scales badly out of a folder of PDFs. It is also the part we run for general contractors and envelope subcontractors across Miami-Dade and Broward: estimation and compliance support with verification built into the package rather than bolted on after a rejection.

Approval is a status with a shelf life, not a sticker. Treat it that way and the submittal stops being a gamble.