About
Methodology
Every rule on this site comes from a document you can open yourself. Here is how we find those documents, check them and keep them current.
What counts as a primary source
We state a rule only when we have read it in one of these:
- Statutes and rules published by the state legislature or agency, such as the Florida Statutes.
- Adopted codes and standards, such as the fire code edition a state or county has adopted, read in the code text itself.
- Fire marshal (AHJ) documents: guidelines, permit checklists, ordinances and official web pages from the fire department or building department that enforces the rule.
- Federal sources, such as FCC rules on signal boosters.
News stories, vendor blogs and forum posts can point us to a document, but we never state a rule on their word alone.
How we verify a rule
- Open the document at its official address and read the section that sets the rule.
- Record it: address, title, publisher, type of source and the date we read it. That date is the "verified" date you see on the page.
- Cite the exact section next to the rule, for example F.S. 633.202(18)(h)2, so you can find it in seconds.
- Write it plainly without changing what it means. Conditions stay attached to the number they belong to.
An example of why conditions matter: Florida's statute mentions 12,000 square feet as part of an exemption for buildings under that size with no underground areas (F.S. 633.202(18)(h)2). It is not a statewide rule that every building over 12,000 square feet needs a system, and we do not present it as one.
When a rule is not published
If we cannot find a published threshold, signal level, test interval or deadline for a jurisdiction, the page says "Not published; confirm with the fire marshal". We do not fill gaps with a neighboring county's rule, a model code default or an installer's rule of thumb.
Confidence levels
| Level | What it means |
|---|---|
| High | We read the rule in a current primary document from the state or the local fire marshal. |
| Medium | We read a primary document, but it is old, unclear or partly contradicted by another source. The page explains which part is uncertain. |
| Low | We have only a pointer, such as a fire marshal's statement that a local rule exists, without the rule text. Treat the page as a starting point. |
How checker verdicts work
The building checker compares your answers with the published rules for your jurisdiction, starting with the state and then the county or city. Exemptions are checked first. An answer you leave as "not sure" never counts as yes or no; it becomes an open question in the result. Every verdict names the rule and section it relied on and ends with the same advice: confirm with your fire marshal (AHJ). The checker gives guidance, not engineering advice.
Two rules about how the checker reads Florida law:
- Low-confidence local pages. Where we could not read a city's or county's own documents (confidence "low"), an answer that would say "required" becomes "a radio signal test is the way to know". A statewide exemption in the statute still settles it: those buildings need no signal assessment (F.S. 633.202(18)(h)), and a local fire marshal may not require more than the state (F.S. 633.202(18)(i)).
- Condominiums. The statute's exemptions for low-rise and wood-frame buildings say "apartments". Condominium buildings are normally classed as apartment occupancies, so the checker applies those exemptions to condos too. Confirm with your fire marshal.
- Height left blank. The wood-frame exemption is for buildings 75 feet or less (F.S. 633.202(18)(a)). If you leave height blank but give the number of stories, the checker counts at least 7 feet per story, so a building of 11 or more stories cannot match it. The story count is never used to make a rule apply.
How often we re-check
- Every source is re-checked at least every 180 days, and sooner when a reader reports a change or a jurisdiction adopts a new code edition.
- Every re-check is logged in the changelog, including re-checks that found no change, and the page's verified date moves forward.
- Pages not re-checked within 365 days are marked as out of date until we check them again.
Independence
ERRCSCheck is funded by installers who pay WhenLeads for alerts and quote requests (see how we make money). They have no say over what the reference pages say. There are no paid listings, rankings or "recommended installer" badges.
Corrections
Found something wrong or out of date? Tell us through the contact form with the page address. We check it against the source, fix it if needed, and log it in the changelog.
Questions people ask
Why do some pages say "Not published"?
Because the jurisdiction has not published that rule in a document we could find and read. We would rather tell you to ask the fire marshal than give you a number we cannot source.
Do installers who pay WhenLeads review or approve pages?
No. Installers do not write, review or approve requirement pages, and paying for alerts or quote requests does not change what a page says.
How do I know a page is current?
Each page shows when it was last verified, and every change or re-check is listed with a date in the changelog.
Sources
Primary documents we read for this page. Rules change; confirm with your fire marshal (AHJ).
- Florida Statutes 2026, section 633.202, subsection (18), The Florida Senate
Related
Sources
Every primary document ERRCSCheck relies on for ERRCS and BDA rules, with the publisher, type of source, where we use it and the date we last verified it.
Changelog
Every change to ERRCSCheck in one place: new requirements pages, re-verified sources, corrected rules and new guides, newest first.
Guidance, not engineering advice
ERRCSCheck explains published ERRCS and BDA rules. It is not engineering, legal or code-official advice. Your fire marshal (AHJ) makes the final decision.