Procurement dataset

Government Tenders Dataset

Define a public procurement dataset by country, buyer, sector and deadline. Scope notices, amendments and award records with traceable official sources.

Jurisdictions on requestAvailability on inquiry14 proposed fields
Coverage, pricing and delivery confirmed individually. Requests open your email app.
Built around your research

Keep notices, amendments and awards distinct

A public tenders dataset should preserve the procurement stage and the authority responsible for each notice. An advance notice, an open solicitation, an amendment and a contract award are different records with different uses. Specify countries, sectors, classification codes and publication windows before choosing the sources. Extracto will need to confirm the collection scope and available fields; this page does not provide an existing tender feed or submit bids.

01

Find opportunities matching a supplier scope

Select relevant procurement categories, locations and notice stages. Keep the official notice link and deadline so a supplier can review eligibility and requirements at the source.

02

Research public-sector buyers

Group notices by contracting authority and sector. Budgets and estimated values can be absent or revised, so published amounts should retain their currency and source context.

03

Follow amendments and award outcomes

Request a relationship between an original notice and later updates where the source supports it. An award can be useful research evidence without representing an opportunity still accepting bids.

Choose jurisdictions and procurement stages

Identify the countries or procurement portals, notice types and sector codes that matter to your business. Publication dates, response deadlines and contract performance locations should remain distinct. If an opportunity has several lots, decide whether each lot should have a separate record. Preserve the official notice identifier so corrections and amendments can be related to the original rather than counted as unrelated tenders.

Keep documents and deadlines traceable

Store deadline time zones and the source URL for full tender documents. An estimated value, maximum framework value and awarded amount have different meanings and should not share an unexplained price field. A recurring feed requires a confirmed source and update process. Qualification, bid preparation and submission remain separate activities; a dataset listing alone does not establish supplier eligibility or guarantee that a deadline has not changed.

Define your structure

Data fields to discuss

Use this field guide to plan your request. Coverage and completeness will be confirmed individually. The CSV template contains column headers for planning.

Proposed fields for Government Tenders Dataset
FieldColumn nameDescription
Notice IDnotice_idOfficial procurement notice identifier.
Notice typenotice_typePlanning, solicitation, amendment, award or another source stage.
Notice titletitleProcurement title as published by the authority.
Contracting authoritybuyer_namePublic buyer responsible for the notice.
JurisdictioncountryCountry or jurisdiction associated with the procurement source.
Sector codesclassification_codesSource-provided CPV, NAICS or other classification identifiers.
Publication datepublished_atDate the particular notice was published.
Submission deadlinesubmission_deadlinePublished response deadline with time zone when available.
Estimated valueestimated_valuePublished estimate, kept separate from award or framework amounts.
CurrencycurrencyCurrency associated with the stated procurement value.
Lot IDlot_idLot identifier when procurement is split into separate lots.
Related noticesrelated_notice_idsSource-supported references to amendments, originals or awards.
Official notice URLofficial_urlTraceable page containing the authoritative procurement information.
Collected atcollected_atTime the notice or amendment was observed.
Start a conversation

From requirements to a clear scope

01

Share your requirements

Send your target sources, locations, essential fields, dates and expected volume. Mention the Government Tenders Dataset so the team has context.

02

Confirm the details

Discuss availability, source coverage, sample requirements, pricing and delivery timing before deciding.

03

Agree on the output

Confirm the final fields, file format and delivery method for the agreed dataset.

Before you request

Frequently asked questions

Is this a ready-made download?

This page defines a dataset specification. Contact Extracto to confirm source coverage, available records, price and delivery timing for your requirements. A displayed sample is a saved example with its own location and collection date.

Does this include only tenders accepting bids?

Specify the required stages in your request. Planning notices, open solicitations, amendments and awards should be distinguishable. A listing’s current deadline and status must be reviewed at the official source before taking action.

Can I filter by industry codes and contract value?

Those are useful requirements when the selected source exposes the relevant codes and amount definitions. Currency, missing estimates, multi-lot notices and framework ceilings need clear handling rules before filters are applied.

Is an automated procurement feed already available?

A procurement source and collection workflow have not been established for this specification. Availability, country coverage, refresh frequency and delivery terms need to be confirmed with the team before ordering.

Keep exploring

Related datasets

View category →
Your market. Your requirements.

Discuss your dataset requirements

Have a narrower location, a specific field list or a target volume in mind? Send your requirements to the Extracto team.