Contract notices
The opportunity itself, structured.
- Title, scope and description
- Estimated value and duration
- Procedure type and framework indication
- Lot structure and lot-level detail
- Publication date and deadlines
Notices and awards, deduplicated across portals with incumbents identified.
The same contract notice appears on a national portal, a regional portal, an EU-level aggregator and the authority's own website, with different reference numbers and sometimes different deadlines. Deduplication and deadline reconciliation are the work.
Free pilot on your own sources, returned in 48 hours. No card, no trial clock — and you keep the sample data either way.
Last verified 5 August 2026 by the Actowiz Solutions Data Engineering team.
Government tender data scraping is the automated collection of public procurement information: contract notices with scope, value and deadlines, prior information notices, classification codes, contracting authority details, tender documents where publicly downloadable, and award notices showing outcomes.
Public procurement is published deliberately — transparency is the point — which makes this one of the more comfortable collection categories. The difficulty is not access. It is that the same notice is published many times.
Our observed ratio is around 2.7 raw notices per real opportunity. Uncorrected, a bid pipeline appears nearly three times larger than it is, and bid teams waste effort triaging duplicates.
When portals disagree on a deadline, we do not pick one silently. We record all observed deadlines with their sources, flag deadline_conflict, and identify which source is the authority's own where identifiable. A missed deadline because a vendor chose the wrong date is not a risk we will take on your behalf.
Competitor bid pricing beyond published award values, evaluation scores where not published, and any pre-tender intelligence. Award notices disclose what a market publishes; the rest is not public.
Notice monitoring is the largest use case. Award notices and incumbent detection are where strategic value sits.
The opportunity itself, structured.
Who is buying, resolved.
So sector monitoring actually works.
The detail bid teams need.
What actually happened.
The strategic layer.
A managed engagement, not a tool licence. We own the pipeline and everything that breaks in it.
Every engagement delivers a documented schema. These are the core fields; the full dictionary runs to 120+ and is agreed during scoping.
| Field | Type | What it captures | Refresh |
|---|---|---|---|
notice_key |
string | Canonical notice identity after cross-portal deduplication | Every run |
notice_type |
enum | Contract notice, prior information, award notice, correction or cancellation | Every run |
authority / authority_id |
string | Contracting authority as published and normalised identity for history joins | Every run |
cpv_codes / sector |
array / string | Classification codes as published plus normalised sector mapping | Every run |
value_estimate / currency / duration_months |
decimal / string / int | Estimated contract value, currency and duration where published | Every run |
published_at / deadline / deadline_source |
date / timestamp / enum | Publication date, deadline and which source that deadline came from | Daily |
deadline_conflict / deadlines_observed |
boolean / array | Whether sources disagree, and every deadline observed with its source | Daily |
sources_seen |
int | How many portals carried the notice, retained as a signal of prominence | Daily |
lots / documents |
int | Lot count and document count, with lot-level detail available | Daily |
winner / award_value / bidders_count |
string / decimal / int | Award outcome fields where an award notice is published | Per award |
incumbent_probable |
object | Probable incumbent with the basis for the inference and a confidence score | Per notice |
Incumbent detection is always delivered with its basis and a confidence score, never as a bare assertion. A wrongly identified incumbent can send a bid team down an entirely wrong strategy, so the reasoning must be inspectable.
Procurement portals differ enormously in structure and language. Coverage is built jurisdiction by jurisdiction.
Some portals require registration to download documents. We collect notice metadata publicly and flag where document access requires registration rather than creating accounts to obtain them. Request a source we don't list →
We deliver into 40+ countries. These are the markets where this particular service is requested most, and the reason demand concentrates there.
| Market | Why demand concentrates here |
|---|---|
| European Union | Layered EU, national and regional publication makes deduplication essential; TED plus national portals is the standard scope. |
| United Kingdom | Find a Tender and Contracts Finder alongside devolved portals, with strong award transparency supporting incumbent detection. |
| United States | Federal SAM.gov plus a large fragmented state and municipal landscape, where regional portal coverage drives most of the value. |
| India, GCC & multilateral banks | Fast-growing public procurement with large infrastructure programmes and improving publication discipline. |
We run production collection across 40+ countries. Coverage depth varies by market and by source, so we confirm what is actually available for your specific markets during scoping rather than claiming uniform global coverage. Ask about a market we don't list →
Bid teams at public sector suppliers dominate, with consultancies and analysts following.
Opportunity pipelines are inflated by duplicate notices and full of irrelevant sectors, so triage consumes bid team capacity.
Deduplicated notices filtered to your sector and value thresholds, with deadlines reconciled and conflicts flagged.
Bid win rate
Winning requires knowing the incumbent and the authority's award history before the notice publishes.
Probable incumbent with basis and confidence, plus authority award history by sector and contract end dates for recompete timing.
Capture rate
Public sector market sizing needs award data across jurisdictions on a consistent classification basis.
Harmonised award notices with normalised classification and authority identity, enabling category spend analysis.
Analysis coverage
You cannot monitor dozens of regional and municipal portals manually, and that is where SME-suitable contracts sit.
Regional and municipal portal coverage with deduplication and value-threshold filtering to surface accessible opportunities.
Opportunities identified
Finding teaming partners requires knowing who wins what, where, and with whom.
Supplier win history by authority, sector and value band, with consortium participation where published.
Teaming success
Procurement transparency research needs harmonised, deduplicated data across jurisdictions.
Documented, deduplicated notice and award datasets with classification harmonised and methodology stated.
Reproducibility
Four patterns, with the outcome each is judged on.
Notices are deduplicated across portals to canonical opportunities, filtered by classification, value threshold and geography, with deadlines reconciled and conflicts flagged.
Outcome: Bid pipeline roughly a third the raw volume, with triage effort spent on real opportunities.
Probable incumbents are inferred from prior awards to the same authority in the same classification, delivered with the basis and a confidence score.
Outcome: Capture strategy informed by likely incumbency rather than developed blind.
Award notices with contract durations are used to project when contracts come up for renewal, building a forward pipeline months or years ahead of publication.
Outcome: Business development engaged with authorities before the notice publishes.
Award notices are harmonised across jurisdictions with classification and authority identity normalised, producing category spend and supplier share analysis.
Outcome: Market sizing and competitor share grounded in published award data.
Clients rarely permit naming. These are real engagement shapes with identifying detail removed, so you can judge whether the work resembles your situation.
Notices were ingested from several portals without deduplication, so the same opportunity appeared repeatedly and bid triage consumed most of the team's capacity.
Cross-portal deduplication to canonical opportunities with classification filtering, value thresholds and deadlines reconciled with conflicts flagged.
Pipeline volume fell to roughly a third, with triage effort redirected to genuine opportunities.
Business development engaged only once notices appeared, by which point incumbents had months of relationship advantage.
Award notice history with contract durations used to project recompete windows, plus probable incumbent inference with basis and confidence.
Engagement began well before publication on projected recompetes, with likely incumbency known.
Examples are anonymised at client request. Named references are available on request under NDA. See published case studies →
Before you commit to anything, we run this service against your own sources and send you the output. If the coverage isn't there, the sample will show you that too — which is the point. We would rather lose the deal at the pilot than at month three.
Same collection pipeline and same QA underneath. The difference is who holds the schedule and how the data reaches you.
We own the collection, the QA and the delivery. You receive clean data on a schedule and never touch a scraper.
Best fit: Teams who need the data, not the infrastructure.
The same collection pipeline exposed as an authenticated REST endpoint your systems query directly.
Best fit: Product and engineering teams building on live data.
A defined pull for a specific question — market sizing, diligence, a pitch, a one-off audit.
Best fit: Research, strategy and diligence work with a deadline.
Every engagement is quoted individually, because the honest answer depends on your scope: how many sources, how many records, how often, and how the data reaches you. We scope it with you, run a free pilot on your own sources, and then quote a fixed monthly figure — no per-request metering and no overage billing when volumes move. Request a quote and you will have a number after one call.
Portal count and multilingual deduplication are the burden, and portals change structure frequently.
| Consideration | In-house scraping team | Generic proxy / DIY tool | Actowiz managed feed |
|---|---|---|---|
| Time to first usable data | 6–12 weeks of engineering before anything is trustworthy | Days, but output needs manual cleanup before use | Free pilot in 48 hours, production in 5–10 business days |
| Who fixes it when a source changes | Your engineers, at the cost of their roadmap | You do — tools report failures, they don't resolve them | We do, same business day, inside the retainer |
| Data quality assurance | Whatever your team has time to build | None beyond HTTP success | Schema validation plus sampled human QA on every run |
| Compliance documentation | Rarely produced, then requested urgently by legal | Not provided; terms risk sits with you | Sources, method and lawful basis documented for review |
| Accountability | Distributed across a team with other priorities | A support ticket queue | A named engineer and an account owner |
| True annual cost | Engineer salaries, proxies, hosting, ongoing maintenance | Low licence fee plus significant hidden analyst time | One fixed monthly retainer, quoted after scoping |
Knowing who currently holds a contract is often the single most valuable piece of pre-bid intelligence. It is also an inference rather than a published fact in most cases, and how a vendor handles that distinction matters.
A wrongly identified incumbent sends a capture team down an entirely wrong strategy: wrong differentiators, wrong pricing assumptions, wrong relationship approach. That is expensive in a way a missing field is not.
So every incumbent inference carries basis naming the specific reasoning and confidence as a score. High confidence means a prior award with matching authority, classification and plausible end date. Low confidence means weaker signals, and we would rather deliver a low-confidence flag you can investigate than a clean-looking assertion you might trust.
Where there is no reasonable basis, the field is absent rather than populated with a guess. Some contracts are genuinely new, and inventing an incumbent for them is worse than useless.
This is a small design decision with disproportionate consequences, and it is worth explaining because most vendors handle it the other way.
Every observed deadline is retained with its source in deadlines_observed, deadline_conflict is set when they disagree, and deadline_source identifies which source the primary deadline came from — with the authority's own publication preferred where identifiable.
We do not silently pick a date. If a bid team misses a deadline because a vendor chose the wrong one, that is a lost contract, and it is not a decision we will make on your behalf without showing you the disagreement. A flagged conflict costs a minute of checking; a wrong date costs the bid.
This is the same principle applied in our real estate and local business services, where ambiguous evidence is surfaced rather than resolved by the pipeline.
Jurisdictions, classification scope and value thresholds are scoped first, since portal count drives cost and multilingual coverage adds work.
You send us target sites, regions, SKUs or keywords. We return a field-level schema proposal, coverage estimate and refresh recommendation — usually within two working days.
We extract a real sample from your actual targets so you can inspect field fill rates, edge cases and match quality before any commitment.
Our engineers build extractors, then wire validation rules: type checks, range checks, duplicate detection and golden-record comparison against a manually verified subset.
Feeds run at your chosen cadence and land in the warehouse or bucket you already use. Schema changes are versioned and announced before they ship.
We watch coverage drift, fill rates and source changes daily. A named engineer owns your account, and layout breaks are fixed by us — not queued for you.
JSON, JSONL, CSV, Parquet or XLSX, delivered to Amazon S3, Google Cloud Storage, Azure Blob, SFTP, Snowflake, BigQuery, Databricks or a REST/GraphQL endpoint. Webhooks fire on completion, and every batch ships with a manifest containing row counts, schema version and QA results so your pipeline can fail loudly instead of silently ingesting a bad file.
We collect publicly published procurement notices, award notices and publicly downloadable tender documents. Where document access requires portal registration we flag it rather than creating accounts. Named individual contact details in notices are not part of the deliverable; authority and role-based contact information is.
These are contractual, not marketing copy. They appear in the engagement document.
| Commitment | What we hold ourselves to |
|---|---|
| Pilot turnaround | A real sample from your own sources within 48 hours of scoping, at no cost. |
| Go-live | Production collection running within 5–10 business days of sign-off. |
| Delivery punctuality | 99.5% on-schedule delivery, measured monthly and reported to you. |
| Breakage response | Source layout changes triaged same business day; critical sources inside 4 hours. |
| Data quality | Schema validation on every run plus sampled human QA before any delivery leaves us. |
| Escalation | A named engineer and an account owner, not a shared ticket queue. |
| Change requests | Field additions and source changes handled inside the retainer, not re-quoted. |
| Exit | Your historical data exported in full on request. No lock-in, no export fee. |
Plain definitions of the terms used on this page, so procurement and legal reviewers are working from the same vocabulary as your data team.
What bid, capture and analysis teams ask during evaluation.
About 2.7 raw notices per real opportunity in our coverage, and higher in jurisdictions with layered national, regional and supranational publication. Uncorrected, a pipeline looks nearly three times larger than it is.
We deduplicate to canonical opportunities using content matching rather than reference numbers, since every portal issues its own reference. sources_seen is retained because notice prominence is itself mildly informative.
Often, as an inference with its reasoning shown. We look for prior awards to the same authority in the same classification with plausible end dates, framework participation, and notice language referencing existing arrangements or transition obligations.
Every inference carries basis and confidence. Where there is no reasonable basis, the field is absent rather than guessed — because a wrongly identified incumbent sends a capture team down an entirely wrong strategy, which costs more than a missing field.
We flag it and show you all of them. Every observed deadline is retained with its source, deadline_conflict is set, and the authority's own publication is preferred as primary where identifiable.
We deliberately do not pick a date silently. A missed deadline because a vendor chose wrong is a lost contract, and that is not a decision we will make on your behalf. A flagged conflict costs you a minute; a wrong date costs the bid.
Where they are publicly downloadable without registration, yes — specifications, ITTs, clarifications and Q&A publications, with revision detection.
Many portals require registration to download documents. We do not create accounts to obtain them; we flag that document access requires registration and provide the notice metadata and document list so your team knows what to request. Creating accounts under our identity to obtain documents for you would be a terms problem for both of us.
Award value and, where published, the number of bidders. Individual competitor bid prices, evaluation scores and scoring breakdowns are generally not published, and where they are not, no vendor can supply them.
Jurisdictions differ: some publish more outcome detail than others. We tell you per jurisdiction what award transparency actually looks like rather than implying uniform detail.
Yes, from award notices with contract durations — projecting likely recompete windows months or years ahead of publication. This is one of the more valuable outputs, since it lets business development engage before a notice appears.
The projection is inferential: extensions, early terminations and scope changes are common and often unpublished. We deliver the projected window with its basis rather than as a date, and clients treat it as a targeting signal rather than a schedule.
Notices are collected in their published language with the original retained, and classification codes provide language-independent filtering — which is why CPV mapping matters so much here. Titles and scope descriptions are translated for search and filtering while the original text remains authoritative.
Translation is for triage, not for bid preparation. Bid teams should always work from the original document, and we keep the original precisely so that is possible.
Procurement notices are published specifically for public access — transparency is the legislative purpose — which makes this one of the more comfortable collection categories. Several portals also offer bulk access or APIs, which we use in preference to page collection where available.
We respect stated rate limits and access conditions, document methodology per portal, and make a DPA available before signature. Named individual contact details in notices are excluded from the deliverable; role-based authority contacts are included.
We quote individually. The drivers are jurisdiction and portal count, whether municipal and regional portals are included alongside national ones, classification scope, multilingual coverage, and refresh frequency.
National portals in one or two jurisdictions filtered to your sectors sits at the lighter end. Multi-jurisdiction coverage including regional and municipal portals with award history and incumbent detection sits higher. One scoping call, a free pilot on your own sectors within 48 hours, then a fixed monthly quote. Request a quote.
Send us your classification codes and jurisdictions. We return deduplicated notices with deadlines reconciled and incumbents flagged within 48 hours.
Free pilot, no card, no obligation. We'll show you the raw-to-canonical ratio in your own sectors.Our web scraping expertise is relied on by 4,000+ global enterprises including Zomato, Tata Consumer, Subway, and Expedia — helping them turn web data into growth.
Watch how businesses like yours are using Actowiz data to drive growth.
From Zomato to Expedia — see why global leaders trust us with their data.
Backed by automation, data volume, and enterprise-grade scale — we help businesses from startups to Fortune 500s extract competitive insights across the USA, UK, UAE, and beyond.
We partner with agencies, system integrators, and technology platforms to deliver end-to-end solutions across the retail and digital shelf ecosystem.
The EU AI Act impact on web scraping & AI training data GPAI transparency, copyright reservations, prohibited practices & a compliance checklist from Actowiz.
How a B2B supplier replaced manual tender-portal checking with an automated, filtered feed of relevant government tenders from GeM and CPP/eProcure never missing a bid deadline again.
Actowiz Solutions tracks post–World Cup 2026 travel pricing — hotel ADR & airfare normalization across host cities, event-premium decay data & lessons for travel teams.
Whether you're a startup or a Fortune 500 — we have the right plan for your data needs.