What is the Common Elements dataset?

A national entity graph of community associations (HOAs and condos), built by resolving records from state corporate registries, DBPR and CAM filings, published appellate opinions, inspection filings, and hazard data into one record per association. Each association carries structured fields for registration status, inspection status, flood and hazard exposure, board turnover, and, where a public record names them, the management firm and any matched appellate cases. Fill rates differ by field and by state; the association data page publishes them.

How is this different from a generic parcel or property database?

A parcel database models land and structures. We model the association itself: the corporate entity, its registration standing, its officers and management company, its statutory obligations, and how all of that connects to the parcels and buildings it covers. That entity-resolution and community-specific layer is what a generic property database does not build.

Is this personal or consumer data?

No. The dataset is aggregated public records about associations, their corporate filings, inspections, and properties. It is not consumer credit data, not a consumer report, and not personal data about individual owners. We do not sell personal information.

Which vertical page should I start with?

If you underwrite or renew habitational risk, start with data for insurance. If you review condo projects for mortgage lending, start with data for lending. If you run a management company, start with data for management companies. All three query the same underlying dataset through the same API.

How current is the data?

Records are refreshed on a recurring cadence from their source registries and feeds. Each record exposes when it was last refreshed, so you can judge freshness before relying on a signal.

Through the Common Elements API: a REST interface plus an MCP server for AI assistants. Browse the dataset one association at a time for free, or start on a paid plan for programmatic access. Bulk export is self-serve from the Growth plan up; scheduled delivery is available under an enterprise data agreement.

Data and API

Know when a board turns over, before you hear it secondhand

Name: Common Elements community association data
Creator: Common Elements

363,000+ HOAs, condos, and co-ops in one place: location, size, type, reserve and inspection exposure, flood risk, and the managers who serve them where a record names one, built from public records. Underneath sits a resolved entity graph that ties every source to the right association. Browse it free, or query it for insurance, lending, or management use cases.

See what it does for your job Explore the API Browse the directory

363,000+: associations in the dataset
Nationwide: coverage varies by source and market
Public records: every field is sourced
REST + MCP: API access

Why Common Elements data

The moat is the entity resolution, not any single source

No single public registry describes a community association completely. We combine the ones that each describe a piece of it, resolve them to the same entity, and attach property-level facts to the right association. That is work a raw data pull does not do on its own.

One record per association, resolved across sources

State corporate registries, DBPR and CAM filings, published appellate opinions, inspection filings, and hazard data all describe the same association under different names, addresses, and IDs. Entity resolution reconciles them into a single, deduplicated association record. That resolution work, not the raw source pulls, is the hard part.

Per-property enrichment, attached to the right building

Flood zone, hazard exposure, and structural-inspection status are area-level and parcel-level facts. We attach them to the specific association and building they describe, so a query returns the right building's exposure, not a nearby parcel's.

Community-specific context, not just a parcel record

Registration standing, board and officer changes, the management firm where a filing names one, matched appellate cases where they exist, and statute reference for the state an association sits in. A generic property or parcel database does not model any of this, because it is not modeling community associations.

What is in the dataset

Sourced fields, resolved to one association record

Every field is aggregated from public records and carries its source and refresh date.

Association registration and standing
Source: State corporate registries
SIRS and milestone-inspection status
Source: FL DBPR and county records
Flood zone and hazard exposure
Source: FEMA NRI and NFIP data
Appellate litigation history
Source: Published appellate opinions, sparse; silence isn't proof of no litigation
Officer changes and management firm on file
Source: State officer filings, condo and HOA registries, CAM licensing records
Statute reference and calculators
Source: State statutory codes
Address, county, and geography
Source: Parcel and cadastral records
Cross-source entity resolution
Source: Reconciled across every source above

Explore by industry

Same dataset, built for how you use it

Each vertical page covers the signals, use cases, and questions specific to that industry, all drawn from the same underlying dataset.

Data for insurance

Underwrite and renew habitational risk with inspection status, flood exposure, and litigation signals for carriers, MGAs, and agencies.

Data for lending

Screen condo project condition and standing for project review and warrantability diligence, built for mortgage lenders and banks.

Data for management companies

Prospect, onboard, and monitor associations with registration, inspection, board-turnover, and management-firm signals grounded in public records.

HOA and condo association data

Every field we hold, its fill rate nationally and by state, and the ways to get the records.

Common Elements API

REST and MCP access to the dataset. Query a single association or batch-match a portfolio.

Explore the data

Browse association records, compliance signals, and market context before you integrate.

Find the page for your job

Common Elements Data has a page for each job people buy it for: what you get, a sample of the output, and which plan fits.

Free to browse, licensed to build on

The dataset is sourced from public records and is free to browse on the website, one association at a time. Programmatic, at-scale access is a paid product: a paid plan grants a commercial-use license, the right to use the data inside your own product or workflow, plus higher limits and a no-scrape guarantee.

Free tier: personal and evaluation

The free tier is for personal use and for evaluating the API before you commit. It does not grant a commercial-use license. Browsing the website is always free for everyone.

Paid tiers: commercial-use license

A paid plan grants the right to use the data commercially inside your own product or workflow, with higher limits and a no-scrape guarantee so you never have to crawl the site yourself. Bulk export starts at Growth; the written uptime and support SLA comes with Scale and Enterprise.

Public records, source-attributed, no personal data

The dataset is aggregated from public registries, inspection filings, published appellate opinions, and hazard data. It describes associations and properties, not individual consumers. We do not sell personal information, and every field carries its source so your team can defend a decision built on it.

Coverage transparency

Check coverage before you subscribe

Coverage varies by source and market. The live report shows where observations exist, when they were last refreshed, and where our current measurement stops.

Market by market

See the jurisdictions producing observations instead of relying on a national headline.

Freshness included

Scheduled and manual refreshes are labeled so a dated source is never presented as current.

Unknown stays unknown

Missing measurements remain unavailable. They are not converted into zeroes or filled with estimates.

Detailed API coverage is not available on this page yet

We will not substitute cached marketing figures for a missing verified snapshot. The live coverage-and-freshness report remains available below.

Open the live coverage report Review the signed-in layer inventory

The public report contains aggregate counts, dates, and jurisdiction labels only. The signed-in inventory adds layer-by-layer coverage notes without exposing private records.

Questions

What is the Common Elements dataset?: A national entity graph of community associations (HOAs and condos), built by resolving records from state corporate registries, DBPR and CAM filings, published appellate opinions, inspection filings, and hazard data into one record per association. Each association carries structured fields for registration status, inspection status, flood and hazard exposure, board turnover, and, where a public record names them, the management firm and any matched appellate cases. Fill rates differ by field and by state; the association data page publishes them.
How is this different from a generic parcel or property database?: A parcel database models land and structures. We model the association itself: the corporate entity, its registration standing, its officers and management company, its statutory obligations, and how all of that connects to the parcels and buildings it covers. That entity-resolution and community-specific layer is what a generic property database does not build.
Is this personal or consumer data?: No. The dataset is aggregated public records about associations, their corporate filings, inspections, and properties. It is not consumer credit data, not a consumer report, and not personal data about individual owners. We do not sell personal information.
Which vertical page should I start with?: If you underwrite or renew habitational risk, start with data for insurance. If you review condo projects for mortgage lending, start with data for lending. If you run a management company, start with data for management companies. All three query the same underlying dataset through the same API.
How current is the data?: Records are refreshed on a recurring cadence from their source registries and feeds. Each record exposes when it was last refreshed, so you can judge freshness before relying on a signal.
How do I access it?: Through the Common Elements API: a REST interface plus an MCP server for AI assistants. Browse the dataset one association at a time for free, or start on a paid plan for programmatic access. Bulk export is self-serve from the Growth plan up; scheduled delivery is available under an enterprise data agreement.

Put the data to work

Start with the API, explore the data, or talk to us about coverage and an enterprise data agreement for your use case.

Common Elements DataThe change-intelligence console: board and officer turnover and per-association timelines, live.Common Elements APIREST and MCP access to the community association dataset for your stack.Explore the dataBrowse association records, risk signals, and market context before you integrate.Talk to the data teamScope coverage, volume, and an enterprise data agreement for your use case.

Know when a board turns over, before you hear it secondhand.