Self-Reporting Registry Map
Turn scattered local reports into a visible, vetted pattern
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 96%
Brockovich starts with a cluster signal: many people from the same town independently raising the same concern. She then returns to the source by collecting firsthand submissions in a self-reporting registry. Each submission is read, its location is vetted, and incomplete entries or projects that do not yet exist are held back. The accepted reports are pinned to a map so communities can see that an apparently isolated problem may be widespread. Recurring observations can then be categorized and counted over time. The mechanism converts dispersed experience into a visible lead-generating dataset; it does not by itself establish scientific causation, but it identifies patterns worth testing, gives investigators places to look, and lets affected communities find one another.
Origin
Extracted from The Shawn Ryan Show, where Erin Brockovich describes building a data-center reporting map after receiving 30 emails from one town.
Core principles
- 01Treat repeated reports from one place as an investigation signal
- 02Go back to the source rather than relying on summaries
- 03Make isolated experiences visible as a shared pattern
- 04Vet submissions before presenting them as mapped evidence
How to run it
- 1
Detect a cluster
Treat multiple independent reports from the same place as a signal that warrants investigation.
Pro tip Set a practical trigger for reviewing a location, such as a sudden cluster of similar reports.
Watch out A cluster is a lead, not proof of causation.
- 2
Collect source reports
Let affected people submit what they directly observe, including a usable location and concrete details.
Pro tip Ask for photos, videos, bills, notices, or other records when available.
Watch out Do not default the report to claims the submitter did not make.
- 3
Vet each entry
Read every submission and verify its location before including it in the public pattern.
Pro tip Hold entries with missing location data until they can be resolved.
Watch out Do not map a proposed facility as operating if construction has not begun.
- 4
Visualize the whole
Pin vetted reports on a map so isolated communities can see the geographic pattern.
Pro tip Keep the underlying report tied to each pin for auditability.
Watch out Dense mapping can imply certainty that the evidence does not support; label the data as self-reported.
- 5
Classify and update
Group recurring observations, calculate descriptive statistics, and publish updates as evidence accumulates.
Pro tip Separate proposal, construction, and operating-stage reports.
Watch out Do not turn descriptive counts into causal conclusions without further evidence.
In the wild
After receiving 30 emails from one town, Brockovich created a self-reporting registry. Her small team read submissions, verified locations, withheld entries that could not be located or described projects not yet present, and pinned thousands of usable reports across the country.
→ A local concern became a visible national and international pattern that communities could inspect.
Common mistakes
Publishing unvetted pins
Mapping every submission immediately sacrifices credibility and can misstate where a facility exists.
Claiming causation from reports
Self-reported patterns can direct investigation, but they do not independently prove what caused an observed health or environmental effect.
Is it for you?
Best for
It is best for geographically distributed issues where residents possess firsthand evidence but no shared view.
Not ideal for
It is not ideal for proving causation without independent testing, records, and expert analysis.
From the episode
#322 Erin Brockovich - Will AI Data Centers Secretly Drain America’s Water Supply?
Erin Brockovich