Government Contract Awards& Winning Suppliers

Download one normalized daily edition of public award-stage notices from TED, Find a Tender and Contracts Finder. Analyze buyers, named suppliers, lifecycle stages, values and classifications—with every row linked back to its official source.

Refresh

Daily publication window

Formats

CSV · JSON · JSONL

Lifecycle

Intended · Contracted · Awarded

Privacy

Contact fields excluded

Latest daily edition

Pick the format that fits your workflow.

All three files contain the same normalized rows. The manifest documents the row grain, aggregation warning, source coverage, run outcome, byte size and checksum.

Official sources

Three procurement systems.One transparent edition.

Source systems publish different stages and structures. Every record keeps its original URL and licensing reference; the live status below comes from the latest manifest.

European Union and other TED-participating jurisdictions

Completed

3,143

source items processed

TED

Result notices from Tenders Electronic Daily that name a selected winner. The current edition uses a conservative notice-to-winner row when award relationships cannot be aligned safely.

Window: result notices published on target_date; latest notice versions only

United Kingdom (Find a Tender coverage)

Completed

168

source items processed

Find a Tender

Award-stage OCDS releases from the UK's central procurement platform. UK6 notices are marked intended; UK7 or a signed-date relationship is marked contracted.

Window: award releases updated in the target_date and previous-day overlap

United Kingdom (Contracts Finder coverage)

Completed

284

source items processed

Contracts Finder

OCDS award releases from Contracts Finder, including awards connected to procurements begun under the earlier UK regime.

Window: award releases published in the target_date and previous-day overlap

Reading UK award stages

A Find a Tender UK6 notice follows the award decision but precedes contract signature; UK7 confirms that the contract was entered into. The normalized award_stage preserves that distinction. Read the official award-notice guidance ↗.

Reading TED rows

TED's result notices can contain several winners, awards and values. Until those XML relationships are aligned safely, this dataset emits a conservative notice-winner row, uses the notice identifier as its stable result namespace and leaves uncertain dates, values, currencies and supplier details blank rather than guessing. See the official competition-results model ↗.

UK source attribution: Contains public sector information licensed under the Open Government Licence v3.0.

Normalized schema

Award and supplier fields,with lifecycle context.

One award × supplier where the source exposes that relationship; TED is conservatively one result notice × named winner. Dates use ISO 8601 strings, monetary values stay paired with their currency, and classification codes retain their source scheme.

Stable identity

01
idsourcesource_award_idsource_supplier_idsource_notice_idsource_release_id

Award lifecycle

02
notice_typetitleaward_statusaward_stageaward_datecontract_signed_atpublished_atcontract_start_atcontract_end_at

Buyer & supplier

03
buyer_namebuyer_countrybuyer_regionsupplier_countsupplier_namesupplier_identifiersupplier_country

Value, method & place

04
award_valueaward_currencyprocurement_methodcategoryclassification_schemeclassification_codesplace_countryplace_region

Traceability & changes

05
source_urlsource_licensefirst_seen_atlast_seen_atcontent_hashchange_type

How it is prepared

A cautious, auditable daily pipeline.

The pipeline keeps source semantics visible and leaves uncertain relationships blank instead of manufacturing a cleaner-looking record.

  1. 01

    Collect

    Request each official publication or update window and retain the source identifiers needed for traceability.

  2. 02

    Select

    Keep explicit award or result releases and named suppliers; exclude source records without a usable award outcome.

  3. 03

    Normalize

    Map lifecycle, buyer, supplier, value, classification and place fields without collapsing intended and contracted stages.

  4. 04

    Publish

    Write CSV, JSON and JSONL atomically, then publish source status, row-grain notes and SHA-256 checksums in the manifest.

What you can do with it

See who buys, who winsand where awards cluster.

01

Map suppliers

Group named suppliers by buyer, category, place or classification to explore a public-sector supplier landscape.

02

Track buyers

Follow contracting authorities over time and compare the categories, procedures and suppliers they report.

03

Build alerts

Use stable row IDs, publication dates, change types and source links as inputs to a focused award-monitoring workflow.

04

Prototype intelligence

Test supplier enrichment, procurement search or market-analysis ideas before commissioning broader history or coverage.

Coverage & responsible use

Analyze the rows.Keep the source context.

01

Publication window, not award date

A daily edition captures notices published or updated in the source window. award_date or contract_signed_at can be earlier than the edition date.

02

Award decision is not always signature

Use award_stage before treating a row as a signed contract. In particular, UK6 is intended and UK7 is contracted.

03

Deduplicate before summing

award_value is an award-level value repeated on every supplier row. Do not sum it across supplier rows; deduplicate using source, source_notice_id, and source_award_id. supplier_count reports the number of source suppliers for that award or TED notice.

04

TED relationships are conservative

TED rows name a selected winner and use the notice ID as a stable result namespace. Award dates, values, currencies and public supplier identifiers stay blank until the source XML relationships can be parsed safely.

05

Defined sources, not global coverage

The first edition uses TED, Find a Tender and Contracts Finder. It is not a comprehensive ledger of all European, worldwide or United States government contract awards.

06

Reported value is not paid spend

award_value preserves the value reported by the notice, whose meaning can vary by source and notice stage. It should not be treated as invoiced or paid government spending.

07

Expect thresholds and revisions

Official publication duties vary by procurement regime, threshold and exemption. Notices can also be delayed, corrected, replaced or cancelled, so revisit source_url for decisions that matter.

08

Verify and respect source terms

The public schema does not map contact-person names, email addresses, telephone numbers, or street addresses. Supplier organization names and public organization identifiers are retained as the subject of each award. Publisher-supplied title and organization-name text can still contain unexpected details and should be reviewed for privacy-sensitive uses.

FAQ

Before you download.

Practical details about lifecycle stages, row grain, aggregation, verification and reuse of the daily award edition.

Is the government contract awards dataset free?

Yes. The latest daily CSV, JSON and JSONL files can be downloaded without an account, email address or payment details.

Which procurement sources and regions are included?

The initial dataset uses result or award-stage releases from TED, Find a Tender and Contracts Finder. It covers those European and UK source systems; it does not claim comprehensive worldwide or United States contract-award coverage.

Does every record represent a signed contract?

No. Some official notices report an intended award before contract signature. Use award_stage: intended means a reported award decision, contracted means the source reports a signed or entered contract, awarded means an explicit award without enough evidence to classify it as contracted, and unknown means the source was inconclusive.

What does one row represent?

Where the source exposes an award-to-supplier relationship, one row represents one award and one named supplier. TED is currently more conservative: one row represents one result notice and one named winner when flattened source fields cannot be safely aligned to a specific award.

Can I sum award_value across all rows?

Not directly. A multi-supplier award can repeat its award-level value on each supplier row. Deduplicate with source, source_notice_id and source_award_id before summing award values, and review supplier_count. TED award values may be blank when the source relationship cannot be aligned safely.

How often is the dataset refreshed?

The pipeline runs daily. The edition records notices published or updated in each source window; the award decision or contract signature itself may have happened earlier. The manifest reports the exact edition date, source status, coverage notes and checksums.

Can I use the data commercially?

Each source retains its own reuse terms. Records include the source URL and source-license URL, and the manifest lists source licenses. Review those terms for your use case; WebTruffle does not place one blanket license over the combined source data.

How should I verify an award or supplier?

Open source_url and rely on the official notice for the authoritative lifecycle stage, supplier, value, amendments and contract details. The normalized file is for discovery and analysis, not a substitute for the source record.

Can WebTruffle provide history, an API or more countries?

Yes. WebTruffle can scope historical archives, additional award systems, company enrichment, custom filters and managed API or file delivery around a defined procurement market.

Need more than the free edition?

Build contract-award data around your market.

Add jurisdictions, history, company enrichment, custom qualification rules, alerts or an API. WebTruffle can manage the collection and delivery while your team works with the data.