Methodology
How a project record is sourced, resolved and verified.
Sources, licensing, entity resolution, verification cadence, normalisation and known limitations, documented in full.
Methodology
How the data is produced
Sources, licensing, cadence, verification, entity resolution and known limitations, documented in full.
Sources
Primary planning and building-control registers, national and state APIs, open data releases and licensed portal feeds. Each jurisdiction record names its source type and update frequency.
Licensing
Every feed is ingested under a stated licence: open government, open data, licensed or negotiated. The licence is carried on the jurisdiction object and governs redistribution rights.
Entity resolution
Companies are resolved across borders into one entity with multiple jurisdiction footprints, using registry identifiers, address history and party co-occurrence on projects. A contractor working in three countries is one Veritrace ID.
Verification
Contact records carry the date they were last checked. Automated checks propose changes; the record only moves when a check passes. The interface shows verification age rather than implying permanent accuracy.
Normalisation
Local stage names map onto one canonical ladder, values are stored in native currency with the FX date published, areas are stored in square metres, and trades map onto one global taxonomy with local naming preserved.
Known limitations
Dark jurisdictions publish nothing machine-readable. Partial jurisdictions omit some stages or party types. Both are labelled in the registry rather than smoothed over.
Coverage
Every jurisdiction, with its status published
Every jurisdiction on earth is an object in the data model from day one. Most start as mapped or dark. We publish that, because a coverage claim you cannot check is not a coverage claim.
| Country | Jurisdictions | Live | Partial | Records | Region |
|---|