AI plan review built for Florida’s hardest reviewing environment
HVHZ wind requirements, Miami-Dade NOAs, Florida Building Code editions, milestone inspections. If a review engine handles South Florida, your county is easy. Flikt is built and run in Miami.
Why Florida is the stress test
Florida layers requirements most states never see. The High-Velocity Hurricane Zone provisions of the Florida Building Code govern Miami-Dade and Broward. County-level product-approval regimes decide what may actually be installed. The state code runs its own edition cycle rather than tracking the model I-codes one-to-one. And since 2022, aging residential towers carry milestone-inspection and structural-reserve obligations that reach back into the documents.
A plan set that reviews clean here has survived the toughest gauntlet in the country. That is why we built the engine here first.
Code edition change ahead: the 8th Edition of the Florida Building Code has governed since December 31, 2023. The 9th Edition takes effect December 31, 2026. Sets drawn against the outgoing edition, and permits landing near the changeover, are exactly where edition mismatches turn into review comments.
What Flikt checks on a Florida set
HVHZ wind speed, against the actual FBC threshold
Flikt reads the design wind speed off your structural and architectural sheets and compares it to the Florida threshold for the zone the drawings place you in — 175 mph in the HVHZ, 160 mph in the coastal Wind-Borne Debris Region, 150 mph inland. A set drawn to the IBC base speed passes a generic review and fails here. The finding cites FBC Section 1609.3 by name.
Florida amendments, layered on the model codes
Flikt grounds findings in the model codes every AHJ starts from — IBC, NEC, IECC — then layers Florida amendments on top once the drawings establish the jurisdiction. That ordering matters: it is why a Texas set never gets reviewed against Florida requirements, and why a Florida amendment finding names the FBC edition and section your reviewer will recognize.
Jurisdiction read from the documents
The engine determines the governing jurisdiction from the set itself — title-block addresses, AHJ notes, code callouts, product-approval references — rather than asking you to declare it. Miami-Dade, Broward, and the HVHZ sub-zones are distinguished, so a Broward set is not reviewed against inland thresholds.
Everything in a standard review
Cross-discipline coordination conflicts, code issues, and scope gaps across 16 disciplines. 2D PDFs only — no BIM model required.
None of that is specific to Florida — the code editions and the wind requirements are, but the finding types are the same everywhere. See what the review checks on any set, or read where it is the wrong tool for the job.
What a Florida set actually costs when it goes unreviewed
The failure mode in South Florida is rarely a dramatic collision. It is a wind speed carried forward from an earlier project, an approval that lapsed between design and installation, or a specification section that contradicts the drawings on an assembly nobody re-checked after the last revision. None of those stop a permit. All of them surface in the field, after the material is bought.
On one South Florida commercial retail set, Flikt surfaced a range of coordination exposure that had cleared every prior review — the arithmetic is in the case study, and you can run your own numbers with the ROI calculator.
Built by a Miami developer, not a software company
Flikt was built by Greg Baumann, a licensed general contractor and multifamily developer who has delivered more than 2,600 units. It exists because a missed cross-discipline conflict became a six-figure change order on one of his own projects. Every finding the engine produces is shaped by what actually costs money in the field, which is a perspective no venture-funded drawing-analysis tool can copy.
Who we work with in Florida
- Multifamily and condo developers — where HVHZ requirements and product-approval exposure quietly become change orders
- Condominium boards and their engineers — getting ahead of the document side of milestone inspections and reserve studies
- General contractors bidding hard-bid, lump-sum work — pricing a set someone else drew, with no model to check it against
- Architects and engineers of record — a tireless second pair of eyes before the set is issued
- Se habla español — reports and support in Spanish, disponible en español
If it handles Miami-Dade, it can handle your county
Same-day review. Severity-ranked, sheet-cited findings. No BIM required.
Flikt.AI is available nationwide. Florida is where the engine was built and hardened, not a limit on where it works. Reports are recommended as a supplement to professional review, not a replacement; the engineer or architect of record remains responsible for the documents.
The pre-IFC coordination checklist
50 checks before you issue for construction, ordered by what actually goes wrong — built from 1,516 findings across 34 real plan sets. Comes as an assignable tracker (Excel) with status, owner and due date, plus a printable PDF. No call, no card.