Data & methods

Methodology

Data updated August 31, 2026 · Florida DBPR

HOA Census is compiled from public records published by state agencies — a different registry in each state, with different fields and different registration regimes. This page documents exactly where each state’s data comes from, how it is processed and verified, and what it does not cover.

Sources, by state

Florida — DBPR, Division of Condominiums, Timeshares, and Mobile Homes
The Department of Business & Professional Regulation publishes extracts of every condominium and cooperative association it regulates: association name, county, unit count, recorded date, filing status, and the managing entity of record. Cross-referenced against the Florida Division of Corporations (Sunbiz) corporate registry.
Colorado — Division of Real Estate (DORA) HOA registration roster
Colorado HOAs must register annually under CCIOA (C.R.S. 38-33.3-401); a lapsed registration suspends the association’s lien rights. The public roster includes designated agent, address, units, management company, self-managed vs professionally managed status, and the HB22-1137 self-reported figures each HOA files at renewal (delinquencies, judgments, payment plans, average assessments). DORA notes it cannot verify the self-reported figures; they are shown as filed.
Texas — TREC HOA management certificates (SB 1588)
Since December 2021, Texas Property Code §209.004 requires property owners’ associations to record a management certificate and file it with the Texas Real Estate Commission. The filings index (association name, county, city, ZIP, filing type, link to the recorded certificate PDF) is published on the Texas Open Data Portal and refreshed daily. Amended certificates are de-duplicated to one record per association and county.
Nevada — Real Estate Division (NRED) active common-interest community list
Nevada CICs register annually under NRS 116.31158; NRED publishes the active list monthly with association type (standard, master, sub-association), declared unit count, county, and the association’s Secretary of State corporate ID.
Virginia — DPOR Common Interest Community Board regulant list
Virginia associations register annually with the CIC Board (Va. Code 54.1-2349). The public regulant list (license type 0550) records name, certificate number, mailing address, and certification/expiration dates. It does not record unit counts or the community’s own location, so Virginia is presented as a statewide roll without county pages.

Collection & update cadence

Processing & verification

  1. Staging. Source files are loaded as-is into typed staging tables. Nothing is edited by hand; every run is replayable from the original artifacts.
  2. Classification. Records are classified (condominium, cooperative, HOA, master association, and so on) using each source’s own program or type field. Where a registry does not distinguish types (Virginia), records are labeled generically rather than guessed.
  3. County assignment. Where the source names a valid county, it is used as filed. Where it is blank or invalid (most of the Colorado roster, a minority of Texas filings), the county is assigned from the association’s in-state mailing ZIP code using the Census Bureau’s ZCTA-to-county relationship file; out-of-state mailing addresses are left unassigned. A professionally managed association that receives mail at its manager’s office may be attributed to the manager’s county.
  4. Resolution. Managing-entity names are normalized so management companies can be counted across associations; in Florida and Nevada, records are matched to the state corporate registry.
  5. History. Records are never hard-deleted. When a record leaves a source extract, it is marked expired with the date; changes are versioned so past states remain queryable.

Record counts

The current build contains 60,785 associations across 5 states:

Known limitations

Corrections

If you represent an association or management company and find an error, write to us via the contact address with the record link; we verify against the primary source and correct in the next release, and corrections are noted in the run log. This methodology and the data releases are maintained by John Riddle.