Where we observe changes, how often each source refreshes, how much history exists, and where it stops. Every number on this page is counted from the live dataset, not written by hand.
Change detection compares two snapshots of a public record and reports what moved between them. A state with no ongoing ingest cannot produce a new change until someone loads the next snapshot, so the schedule matters as much as the totals.
| State | Ongoing ingest | Changes observed | Latest change |
|---|---|---|---|
| Florida | DailyCorporate filings daily, officer roll from a bulk file by hand | 109,815 | Aug 11, 2026 |
| Virginia | No scheduleLoaded by hand, so no new changes appear between runs | 30,405 | Aug 11, 2026 |
| Texas | No scheduleLoaded by hand, so no new changes appear between runs | 21,651 | Aug 11, 2026 |
| Oregon | WeeklyOfficer roster refreshed every Monday | 11,347 | Aug 17, 2026 |
| Alaska | No scheduleLoaded by hand, so no new changes appear between runs | 1,943 | Aug 5, 2026 |
| Connecticut | WeeklyOfficer roster refreshed every Monday | 1,003 | Aug 24, 2026 |
| Utah | No scheduleLoaded by hand, so no new changes appear between runs | 946 | Aug 11, 2026 |
| Arizona | WeeklyOfficer roster refreshed every Monday, scheduled 2026-08-11 | 623 | Aug 24, 2026 |
| GA | No scheduleLoaded by hand, so no new changes appear between runs | 556 | Aug 11, 2026 |
| MS | No scheduleLoaded by hand, so no new changes appear between runs | 171 | Aug 11, 2026 |
| NY | No scheduleLoaded by hand, so no new changes appear between runs | 161 | Aug 11, 2026 |
| AL | No scheduleLoaded by hand, so no new changes appear between runs | 138 | Aug 11, 2026 |
| TN | No scheduleLoaded by hand, so no new changes appear between runs | 105 | Aug 11, 2026 |
| NC | No scheduleLoaded by hand, so no new changes appear between runs | 103 | Aug 11, 2026 |
| OH | No scheduleLoaded by hand, so no new changes appear between runs | 81 | Aug 11, 2026 |
| MI | No scheduleLoaded by hand, so no new changes appear between runs | 63 | Aug 11, 2026 |
| IL | No scheduleLoaded by hand, so no new changes appear between runs | 58 | Aug 11, 2026 |
| PA | No scheduleLoaded by hand, so no new changes appear between runs | 57 | Aug 11, 2026 |
| SC | No scheduleLoaded by hand, so no new changes appear between runs | 48 | Aug 11, 2026 |
| NJ | No scheduleLoaded by hand, so no new changes appear between runs | 47 | Aug 11, 2026 |
| LA | No scheduleLoaded by hand, so no new changes appear between runs | 41 | Aug 11, 2026 |
| IN | No scheduleLoaded by hand, so no new changes appear between runs | 40 | Aug 11, 2026 |
| MO | No scheduleLoaded by hand, so no new changes appear between runs | 35 | Aug 11, 2026 |
| CA | No scheduleLoaded by hand, so no new changes appear between runs | 35 | Aug 11, 2026 |
| MN | No scheduleLoaded by hand, so no new changes appear between runs | 32 | Aug 11, 2026 |
| KY | No scheduleLoaded by hand, so no new changes appear between runs | 28 | Aug 11, 2026 |
| MA | No scheduleLoaded by hand, so no new changes appear between runs | 25 | Aug 11, 2026 |
| MD | No scheduleLoaded by hand, so no new changes appear between runs | 25 | Aug 11, 2026 |
| WI | No scheduleLoaded by hand, so no new changes appear between runs | 22 | Aug 11, 2026 |
| CO | No scheduleLoaded by hand, so no new changes appear between runs | 22 | Aug 11, 2026 |
| KS | No scheduleLoaded by hand, so no new changes appear between runs | 16 | Aug 11, 2026 |
| WA | No scheduleLoaded by hand, so no new changes appear between runs | 13 | Aug 11, 2026 |
| OK | No scheduleLoaded by hand, so no new changes appear between runs | 10 | Aug 11, 2026 |
| IA | No scheduleLoaded by hand, so no new changes appear between runs | 8 | Aug 11, 2026 |
| NV | No scheduleLoaded by hand, so no new changes appear between runs | 7 | Aug 11, 2026 |
| NH | No scheduleLoaded by hand, so no new changes appear between runs | 7 | Aug 11, 2026 |
| NE | No scheduleLoaded by hand, so no new changes appear between runs | 7 | Aug 11, 2026 |
| WV | No scheduleLoaded by hand, so no new changes appear between runs | 7 | Aug 11, 2026 |
| MT | No scheduleLoaded by hand, so no new changes appear between runs | 7 | Aug 11, 2026 |
| SD | No scheduleLoaded by hand, so no new changes appear between runs | 5 | Aug 11, 2026 |
| DE | No scheduleLoaded by hand, so no new changes appear between runs | 4 | Aug 11, 2026 |
| ID | No scheduleLoaded by hand, so no new changes appear between runs | 4 | Aug 11, 2026 |
| AR | No scheduleLoaded by hand, so no new changes appear between runs | 3 | Aug 11, 2026 |
| RI | No scheduleLoaded by hand, so no new changes appear between runs | 2 | Aug 11, 2026 |
| NM | No scheduleLoaded by hand, so no new changes appear between runs | 2 | Aug 11, 2026 |
| HI | No scheduleLoaded by hand, so no new changes appear between runs | 1 | Aug 11, 2026 |
| ME | No scheduleLoaded by hand, so no new changes appear between runs | 1 | Aug 11, 2026 |
| ND | No scheduleLoaded by hand, so no new changes appear between runs | 1 | Aug 11, 2026 |
Ingest cadence was verified against the scheduler on Aug 11, 2026. Change counts and dates in the same row are read from the dataset on every rebuild of this page.
The change types currently in production, counted across every state. This list grows as new sources are wired up, and it is read from the data rather than maintained by hand.
Everything below is a fact about the dataset, not a disclaimer. A subscriber who reads this and signs up anyway gets what they expected.
A change exists in this dataset only if two snapshots were taken around it. Detection began when we started snapshotting each source, so no plan returns events from before that date. The lookback window on a plan is a ceiling on what that plan may request, never a promise that the history exists yet. Setting a wider date range on the change feed does not return older events.
The newest change in the dataset was observed Aug 24, 2026. Per-state dates are in the table above, and they differ by months.
Virginia, Texas, Alaska, Utah, GA, MS, NY, AL, TN, NC, OH, MI, IL, PA, SC, NJ, LA, IN, MO, CA, MN, KY, MA, MD, WI, CO, KS, WA, OK, IA, NV, NH, NE, WV, MT, SD, DE, ID, AR, RI, NM, HI, ME, ND have changes in the dataset but no scheduled refresh. Those states came from bulk files that are downloaded and applied by hand, some of them several gigabytes, so their records stand still between runs and an alert on them cannot fire in the meantime. Florida, Oregon, Connecticut, Arizona are on a schedule.
Association records come from public sources, and those sources differ enormously by state and county. A state that publishes a corporate registry, a parcel roll and an officer roll produces a deep record. One that publishes only a corporate registry produces a name and an address. The 56 jurisdictions are not comparable to each other and this page does not average them into a single number.
Two bodies of association documents are searchable: files harvested from associations’ own websites, and filings recorded with the county. Without a subscription, a search matches document titles, filenames and the county’s own category labels, across recorded governing documents: declarations, amendments, bylaws, articles, other governing documents and legal descriptions. That answers whether we hold a document and what it is, which is what most people arrive asking.
A paid plan searches the text inside the documents, returns the matched passage, opens every category both bodies hold, including budgets, financials, insurance certificates, capital projects and structural reports, and links to the file itself. The county corpus has no extracted text for anyone, so it is searched by filing name at every plan; which of its categories are visible follows the same line.
Every plan has a monthly allowance of documents and of requests, counted per account rather than per search, so the same allowance applies however a search is sliced. The allowance and how much of it is left are shown on the document search itself.
A personal email address or phone number for an individual never appears here, on any surface, in any export or through the API. That is enforced in the database rather than in this application, so it holds regardless of what any page or API route asks for.
Board members and officers do appear by name, title and term, from the state officer rolls and annual report filings those names are already public in. What does not appear is any way to contact them personally. A management firm, an insurance carrier, an engineering firm or a vendor is a business, and its name and professional details are shown.
Some of what we hold is free text read out of documents an association published: minutes, budgets, inspection reports. Those values are shown only for the fields we have reviewed and classified as carrying no individual's details. Everything else is marked as withheld rather than printed, and a new kind of extracted value stays withheld until somebody classifies it.
The public change statistics break these totals down by state and county. Which association changed, and when, is what the change feed is for.
Subscribers see one row per ingestion source, with the cadence measured from its own run history and per-field coverage scoped to a single state, at sources and freshness.