Outdated · success
Broward broward_bsip
Oldest import among current source files: Jul 29, 2026
1,800 rows across the latest source files; rows may overlap
Provenance
Check which source datasets have recorded imports, when they were collected, and what their coverage can establish. Association records may also include reviewed document submissions.
Sources
Names, links, dates, and import status below come from recorded source snapshots. Each date is the oldest import among that source’s current files. Row counts total those files and may overlap; they do not establish complete statewide coverage.
Outdated · success
Oldest import among current source files: Jul 29, 2026
1,800 rows across the latest source files; rows may overlap
Outdated · success
Oldest import among current source files: Jul 29, 2026
1,992 rows across the latest source files; rows may overlap
Outdated · success
Oldest import among current source files: Jul 29, 2026
932 rows across the latest source files; rows may overlap
Outdated · success
Oldest import among current source files: Jul 29, 2026
27,949 rows across the latest source files; rows may overlap
Outdated · success
Oldest import among current source files: Jul 29, 2026
140,979 rows across the latest source files; rows may overlap
Outdated · success
Oldest import among current source files: Jul 29, 2026
5,648 rows across the latest source files; rows may overlap
Outdated · success
Oldest import among current source files: Jul 29, 2026
830 rows across the latest source files; rows may overlap
Outdated · success
Oldest import among current source files: Jul 29, 2026
1,818 rows across the latest source files; rows may overlap
Outdated · success
Oldest import among current source files: Jul 29, 2026
1,825 rows across the latest source files; rows may overlap
Outdated · success
Oldest import among current source files: Jul 29, 2026
1,384 rows across the latest source files; rows may overlap
Outdated · success
Oldest import among current source files: Jul 29, 2026
1,105 rows across the latest source files; rows may overlap
Outdated · success
Oldest import among current source files: Jul 29, 2026
350 rows across the latest source files; rows may overlap
Outdated · success
Oldest import among current source files: Jul 29, 2026
812 rows across the latest source files; rows may overlap
Freshness is calculated from the oldest successful import among a source’s current files: Fresh within 2 days, Stale after 2 days, and Outdated after 7 days. Failed imports or missing dates are Unknown. These dates do not prove that every association field has been updated, and no automatic refresh schedule is promised.
No Sunbiz source snapshot is recorded. Corporate data availability and dates need verification.
No statewide parcel source snapshot is recorded. Parcel data availability and dates need verification.
SIRS coverage
Our copy contains 10,410 SIRS report rows, with filings matched to 4,279 of 15,057 associations in our 25+ unit registry. Imported rows may include duplicates. This coverage is not a statewide completion count or a compliance rate. No matched filing does not establish that a study was not completed or reported.
SIRS applies to buildings with 3+ habitable stories. Registry unit counts do not establish building height; applicability must be verified with the association and relevant agency.
How to read it
Record indicators (filing recency, corporate standing, DBPR annual fees due, milestone-age exposure) are derived from the public records above using documented rules. They are informational signals for further inquiry — they are not legal conclusions, determinations of wrongdoing, or statements about any association's safety or solvency. Entity matching across sources is probabilistic; each match carries a confidence score, and we surface provenance so you can verify against the underlying public record.
FL Condo Data is not affiliated with DBPR, the Division of Corporations, or any government agency. Nothing here is legal, financial, or engineering advice. Verify time-sensitive facts against the primary source before acting.
Corrections
If you represent an association and believe a record is inaccurate or stale, email data@flcondodata.com with the association name, the field in question, and supporting documentation. We review correction requests against the primary sources and update or annotate records accordingly.