Global construction project intelligence

The project chain, verified. Everywhere.

Projects are tracked from first planning submission to completion, with the full chain of parties resolved on each one. One canonical schema, every jurisdiction carried as a first-class object.

Request a demonstration Request a Project Fit Review Explore coverage

0 jurisdictions · 0 countries · 0 live

Live Partial Mapped

0 matching project records

No records match that query.

…

Records tracked

…

Jurisdictions live

…

Countries with records

…

Jurisdictions in registry

…

Last sync

The chain

One project, every party, resolved

A project is not a record, it is a chain. Veritrace holds each link and the parties attached to it. The schema is canonical; the labels are local. Switch the example to see the same chain render in a different jurisdiction.

City of Gold Coast · local term for a planning submission: Development Application

Select a stage to see what we hold

Planning submission

Development Application

DA-2025/0873

What we hold at this stage

Local reference: DA-2025/0873
Lodged: 2025-11-04
Canonical stage: under_assessment
Site area: 4,120 m2

Verification

A switchboard number is not a contact record

Category incumbents publish company details. Veritrace publishes named roles, direct lines and the date each record was last verified, so you can judge the age of what you are acting on.

Typical incumbent record

CompanyKinnear Constructions

ContactNot held

RoleNot held

Phone+61 7 5555 0100 (switchboard)

Emailinfo@ company address

VerifiedNo date published

Veritrace record

CompanyKinnear Constructions

Entity IDVT-C-40218832

ContactKate Donnelly

RoleContracts Manager, Queensland

Direct line+61 7 3128 4471

VerifiedVerified 6 days ago

Verification is a dated event on the record, not a claim about the record. Where a contact has not been re-checked inside 30 days, the interface says so.

Illustrative records. Field names match the public data dictionary, entity VT-C-40218832.

Solutions

Six families, one reference source

35 roles use the same verified project chain, each reading it for a different decision.

Tier 1 contractors

Track pipeline before tender documents are released, across every country you bid in

Mid-market builders

Find approved projects in a defined radius with developer and certifier already resolved

Subcontractors

See which main contractors are appointed on projects in your trade, before the package goes out

Independent trades

One jurisdiction, one trade, an alert each morning with a name and a direct line

Product manufacturers

Size demand by product category and territory, and reach the specifier while specification is open

Distributors and wholesalers

Branch-level territory pipeline and account targeting

Equipment hire

Structure and slab dates drive crane, scaffold and formwork demand

Labour hire

Forecast crew requirements by trade, region and start date

Site services

Waste, traffic management, fencing and amenities, triggered at construction start

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.

0 carrying records0 countriesNo sync recorded

Country	Jurisdictions	Live	Partial	Records	Region

View full coverage registry

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.

Public data dictionary

Compliance and governance

Programme posture, stated plainly

Veritrace publishes the state of its control programme rather than badges. Where a certification is not yet held, the page says so.

Information security programme aligned to ISO 27001

Controls, access management and incident response are documented against the standard and reviewed on a fixed cycle.

SOC 2 readiness

A readiness assessment governs control design across security, availability and confidentiality ahead of formal examination.

GDPR and Australian Privacy Act compliant processing

Lawful basis is recorded per processing activity, with data subject request handling inside statutory timeframes.

Source licensing documented per jurisdiction

Every feed carries a recorded licence in the coverage registry, and redistribution rights follow that licence.

Trust centre

Data governance

What a procurement team needs to see

Provenance

Records originate from primary planning and building control registers, national and state interfaces, and licensed portal feeds. The source is named on the jurisdiction object.

Licensing

Each feed is ingested under a stated licence: open government, open data, licensed or negotiated. Redistribution rights follow the licence recorded for that jurisdiction.

Retention

Project records are retained for the life of the registry. Contact records are retained while the role remains current and are removed once superseded.

Removal rights

Data subjects may request access, correction or removal of personal data held against a role. Requests are handled inside statutory timeframes and logged.

Insights and research

Published research

Index

Global Construction Pipeline Index, Q2 2026

2026-07-14 · 42 pages

Review

Planning Data Availability: A 50-Country Review

2026-06-02 · 68 pages

Analysis

Contractor Appointment Lead Times by Market

2026-04-21 · 31 pages

Standard

Entity Resolution Across Borders: Method Note

2026-03-09 · 24 pages

All research

Pricing

Additional seat

One extra login for a colleague, on the plan you already hold.

A$97per month

One additional user on your existing plan
Same regions, same data as the plan owner
Buy as many as you need
Cancel individual seats at the end of the term

How many seats

A$97 per month in total

Enterprise

Every region, unlimited seats, delivery by API, webhook or bulk CSV.

A$3,000per month

All current and future regions
Unlimited seats
REST API, webhooks and bulk CSV delta
Contractual service levels
Warehouse delivery on request, on the roadmap

Contact sales

Enterprise

API access, bulk feed, warehouse delivery, multi-country licensing and contractual service levels. Priced on volume and jurisdictions, quoted in your currency.

Contact sales

Prices listed in AUD, converted at FX date 2026-08-03. All plans run on a 12-month minimum term and renew automatically; cancel from workspace settings to stop the renewal at the end of your term. No free trial. Add a region (VIC, QLD, UK) for +A$399/mo when live.

Data delivery

Built as infrastructure

Read the registry the way it suits your stack: REST API, webhooks, bulk export, or direct warehouse delivery.

REST API

Projects, parties, companies and jurisdictions. Cursor pagination, ETag caching, ISO 8601 timestamps, one Veritrace ID per object.

GET /v1/projects?jurisdiction=au-nsw&stage=tender

Webhooks

Stage changes, tender notices and value revisions posted to your endpoint as they land, with an HMAC-signed payload, a timestamp for your replay window, and retries.

POST /your-endpoint  event=project.stage_change

Bulk export

Daily deltas or a full snapshot, in CSV, filtered to the jurisdictions on your plan. Pull the delta on a schedule instead of re-reading the registry.

GET /api/export/snapshot?kind=delta&table=projects

Warehouse delivery

Parquet snapshots and managed shares into Snowflake, BigQuery and Databricks are on the roadmap. Today the same data reaches a warehouse through the API or a scheduled CSV delta.

On the roadmap

API documentation

Global presence

Gold Coast, AustraliaPrimary entity
Sydney, Australia
London, United Kingdom
Singapore, Singapore

Benchmarks

Measured, not asserted

Three measures decide whether a project database is usable: how quickly a record arrives, how much of the world it covers, and how much of the chain it resolves.

Median hours from source publication to record availability

Veritrace

4 hours

Weekly batch providers

82 hours

Research-cycle providers

318 hours

In a market where the value of a project record decays from the moment it is published, latency is the product.

Full methodology, sample definitions and measurement periods.