Here's exactly how a piece of raw data becomes a verified record on our platform.
Every source category carries a weighted reliability score based on historical accuracy.
Local reports are cross-checked against independent sources before a status changes.
Local reports are cross-checked against independent sources before a status changes.
Anyone can flag a record for correction — every flag is tracked and resolved transparently.
Every project record maintains a complete and transparent history of its activity. Status changes, source documents, data additions, corrections, approvals, and other important updates are permanently recorded against the relevant project.
Each activity records what was changed, when the change was made, and the user responsible for the update. This provides authorized users with a clear timeline of every important action taken on a project.
Status changed Planning → Permitting. Source: County Planning API. Reliability: 96/100.
Community correction accepted: operator name updated. Verified against corporate registry.
New source added: satellite imagery confirms site grading. Cross-verified with permit filing.
Record created from early-signal news source. Reliability: 71/100, flagged for human review.
| Source Category | Base Reliability | Verification Path |
|---|---|---|
| Government & Public Records | 95–99 | Direct API, no human review required |
| Global Data Sources (Licensed) | 90–97 | Licensed feed, periodic spot-check |
| Third-Party Data | 80–92 | Cross-referenced against 2+ sources |
| News & Media | 65–85 | Analyst review before status change |
| Community Input | 50–75 | Human verification + corroboration required |
