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.
Define a public procurement dataset by country, buyer, sector and deadline. Scope notices, amendments and award records with traceable official sources.
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.
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.
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.
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.
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.
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.
Use this field guide to plan your request. Coverage and completeness will be confirmed individually. The CSV template contains column headers for planning.
| Field | Column name | Description |
|---|---|---|
| Notice ID | notice_id | Official procurement notice identifier. |
| Notice type | notice_type | Planning, solicitation, amendment, award or another source stage. |
| Notice title | title | Procurement title as published by the authority. |
| Contracting authority | buyer_name | Public buyer responsible for the notice. |
| Jurisdiction | country | Country or jurisdiction associated with the procurement source. |
| Sector codes | classification_codes | Source-provided CPV, NAICS or other classification identifiers. |
| Publication date | published_at | Date the particular notice was published. |
| Submission deadline | submission_deadline | Published response deadline with time zone when available. |
| Estimated value | estimated_value | Published estimate, kept separate from award or framework amounts. |
| Currency | currency | Currency associated with the stated procurement value. |
| Lot ID | lot_id | Lot identifier when procurement is split into separate lots. |
| Related notices | related_notice_ids | Source-supported references to amendments, originals or awards. |
| Official notice URL | official_url | Traceable page containing the authoritative procurement information. |
| Collected at | collected_at | Time the notice or amendment was observed. |
Send your target sources, locations, essential fields, dates and expected volume. Mention the Government Tenders Dataset so the team has context.
Discuss availability, source coverage, sample requirements, pricing and delivery timing before deciding.
Confirm the final fields, file format and delivery method for the agreed dataset.
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.
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.
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.
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.
Define a company-level dataset from published job postings. Scope roles, locations, posting dates and source evidence, with a saved U.S. data-engineering sample.
Plan a newly opened business list with explicit opening or registration evidence. Define dates, categories, locations and public business contact requirements.
Scope a roofing company contact list by location, roofing system and customer type. Discuss public emails, branch coverage and source-backed service filters.
Have a narrower location, a specific field list or a target volume in mind? Send your requirements to the Extracto team.