EU Contract Award Notices 2026: How to Read TED Award Data for Competitor Intelligence

What Is a Contract Award Notice?

A Contract Award Notice (CAN) is the official public announcement — published in the EU's Official Journal Supplement (OJS), accessible via TED, Tenders Electronic Daily — that a public contract has been awarded to a specific supplier or group of suppliers. It's the final notice in the public procurement lifecycle, following the Contract Notice (the original tender advertisement) and the award decision communicated to bidders during the standstill period.

Many suppliers confuse the award decision with the CAN. They're different things. The award decision is an internal administrative act communicated to all bidders — including unsuccessful ones — during the standstill period before contract signature. The CAN is the public notice required by EU Directive, published after the contract is actually signed. The CAN is what the whole world can see. And here's the thing: most suppliers never systematically read them, which means those who do have a significant information advantage.

The volume is enormous. TED publishes approximately 500,000–600,000 notices per year across all notice types, and CANs constitute a significant slice of that. The EU's implementation of the eForms standard (Commission Implementing Regulation (EU) 2022/2303) has progressively standardised CAN data structure from October 2023, improving machine-readability and enabling more sophisticated automated intelligence extraction. That's good news if you're building systematic monitoring — the data is better structured than it used to be.

Legal Publication Requirements

Article 50 of Directive 2014/24/EU requires contracting authorities to send a contract award notice to the Publications Office of the EU within 30 days of concluding — signing — the contract. Not the award decision. Not the expiry of the standstill period. The moment of formal contract signature is what starts the 30-day clock.

For framework agreements under Article 33, a CAN must be published within 30 days of concluding the framework. Individual call-offs under a framework don't require separate CANs unless the framework was established as a closed, single-supplier arrangement. For Dynamic Purchasing Systems under Article 34, CANs for individual call-offs may be grouped and published quarterly — this is a specific DPS exemption from the 30-day rule.

Utilities sector contracting entities under Directive 2014/25/EU must publish equivalent CANs under Article 70, same 30-day timeline. Defence procurement under Directive 2009/81/EC has equivalent requirements under Article 30, with some exemptions for classified contracts.

Non-publication or late publication is a formal infringement of EU procurement law. The Commission's monitoring has tightened since 2020, and member states with systematic under-publication face infringement proceedings. That said, in practice many contracting authorities routinely publish late — delays of 60–90 days are not uncommon for complex contracts where finalisation takes time after the award decision. This is worth knowing when you're tracking CAN publication for specific buyers: the absence of a CAN doesn't necessarily mean a contract hasn't been awarded.

CAN Structure: What Information It Contains

Under the eForms standard (applicable from October 2023 for above-threshold notices), a CAN follows a standardised structure. Here's what each section actually contains and why it matters:

Section I — Buyer: Contracting authority name, official address, type of authority (central government, regional/local authority, body governed by public law, utilities entity), main activity, and contact information for the procurement office. This section is the key for building a buyer profile — name, type, and sector all feed into understanding the buyer's broader procurement patterns.

Section II — Scope of Procurement: Contract title, CPV code(s), value estimate from the original notice (not the final awarded value — that's in Section V), contract description, place of performance (NUTS code), and contract duration. Note that the value here is the original estimate. Whether the awarded value in Section V is above or below this estimate is itself an intelligence signal.

Section IV — Procedure: Type of procedure used (open, restricted, competitive procedure with negotiation, competitive dialogue, innovation partnership, negotiated without prior publication). Award criteria — whether MEAT or lowest price, with weightings if applicable. Date of dispatch of the original contract notice, which links back to the original tender advertisement for traceability.

Section V — Award of Contract: This is where the intelligence lives. Date of contract conclusion; number of tenders received; number from SMEs (where reported); number from tenderers from other EU member states; name and address of the contractor — a mandatory disclosure for above-threshold contracts; whether awarded to a consortium; and total value of the contract (the final awarded value, not the estimate). For multi-lot contracts, Section V repeats for each lot, giving you lot-level data on winners, values, and competitive intensity separately.

Not all authorities complete every optional field. Winner name and contract value are mandatory. The number of bids received and SME status of the winner may be omitted. When they are included, though, that bid count data is some of the most actionable intelligence you'll find anywhere.

Finding CANs on TED

TED (ted.europa.eu) is the primary public interface for EU CANs. A few search strategies that actually work in practice:

Filter by notice type first. Without this filter, search results mix contract notices, prior information notices, and every other notice type with the award notices. It's noise. Filter by "Contract award notice (CAN)" and you see only what was awarded.

CPV code searches are your primary sector filter. Search at the division level (CPV 72 for IT services, CPV 45 for construction) to get broad sector coverage, then refine to specific groups if you're getting too many irrelevant results. Remember that contracting authorities often use parent codes for complex procurements covering multiple categories — you may need to monitor at least three levels of the hierarchy to capture everything relevant to your product area.

Searching competitor names in the keyword field is an efficient method for building a competitor's EU contract win history. TED's keyword search applies to notice text — a company named as winner in a CAN will show up when you search for that company name. Run this search for your top three competitors. You'll find things that surprise you.

Search all CANs from a specific contracting authority to understand their procurement volumes, supplier pool, and contract patterns over time. Reviewing their last 3–5 years of CANs gives a comprehensive picture of procurement patterns, incumbent suppliers, and contract cycle timing. If you're targeting a specific buyer, this is table stakes — you should know who they've been buying from before you put effort into a bid.

For systematic intelligence extraction at scale, the TED Open Data API at open.ted.europa.eu provides structured access to all historical notice data. If you're building a competitive intelligence system or procurement analytics function, the API is the right route — not manual searching.

Using CAN Data for Competitor Intelligence

This is where most suppliers leave significant value on the table. CAN data enables several distinct intelligence use cases that are genuinely actionable — not just interesting to know, but useful for bid decisions.

Mapping who is winning in your sector: Search TED for CANs by CPV code in your service area over the last 3–5 years. Aggregate the Section V winner names across multiple CANs. You'll identify which companies are winning the largest proportion of EU public contracts in your sector, their geographic spread, and their preferred buyer relationships. This takes a few hours the first time you do it properly. Most companies never do it at all.

Understanding competitive intensity from bid count data: Section V records the number of tenders received per lot. A lot that received 12 tenders is intensely competitive; a lot that received 2 tenders has very limited competition. Tracking this data systematically across your target sector identifies which CPV categories, geographies, and buyer types attract fewer competitors — and therefore where your bid effort has higher probability-adjusted return. The honest answer is that not all markets are equally competitive, and bid count data is the clearest signal of where you'll face a crowded field versus where you might be one of three serious bidders.

Identifying entrenched buyer-supplier relationships: When the same supplier wins from the same contracting authority three consecutive times in the same category, that's a pattern worth understanding. Either the incumbent is genuinely exceptional — in which case you need to understand why — or the buyer has become comfortable with a supplier in a way that may warrant scrutiny. For a challenger supplier, identifying this pattern enables a targeted approach: engage the buyer earlier through pre-tender market engagement, understand what the incumbent offers that has repeatedly differentiated their bid, and position to disrupt the next cycle before the tender appears.

Framework participation mapping: CANs for framework agreements disclose which companies have been admitted (all lots where they're named as winners, or in multi-supplier frameworks, the fact of their participation). This directly maps which competitors have access to specific framework markets — a real indicator of their competitive reach in that buyer's procurement over the framework period. If a competitor is on a framework you're not on, they have a structural advantage in that buyer's call-offs for the next four years.

Price Benchmarking from Award Data

The contract values disclosed in Section V are the most reliable publicly available pricing benchmark for EU public procurement. Unlike commercial market pricing databases — which may be based on list prices or survey data — CAN values represent actual contracted prices paid by public bodies in competitive procurement processes. That's a meaningful difference.

But CAN contract values need careful interpretation. The disclosed value is typically the total contract value including all options and renewals — not the base year annual value. A 4-year framework with a 2-year extension option at an annual value of €500,000 may be disclosed with a total estimated value of €3 million. You need to understand the contract structure to derive meaningful unit pricing benchmarks. Reading just the headline number without looking at the contract duration, lot structure, and option provisions gives you a misleading picture.

For service contracts, the contract value divided by duration and scope gives an implicit day-rate or unit-rate benchmark. For construction works, value per scope measurement — floor area, road kilometre, volume of material — gives unit cost benchmarks. These are indicative rather than precise; scope differences between contracts limit direct comparability. But they're the most systematic pricing intelligence available without access to bid submissions themselves, which are typically confidential.

The comparison between estimated value (original contract notice) and awarded value (CAN) is itself a signal. Contracts awarded significantly below the original estimate indicate either market-competitive pricing — more competition than expected — or scope reduction. Contracts awarded above estimate indicate scope additions, market pricing above expectation, or competitive dynamics that favoured suppliers. When you see a pattern of awards consistently above or below estimate for a specific buyer, that tells you something about how accurately they estimate and how competitive their market actually is.

Related Notice Types: VEAT, PIN, Corrigendum

VEAT (Voluntary Ex Ante Transparency Notice): Where a contracting authority intends to award a contract without prior publication of a contract notice — using a negotiated procedure without prior publication under Article 32 of Directive 2014/24/EU — it may voluntarily publish a VEAT notice in the OJEU before signing. This gives a 10-day window during which any interested supplier may challenge the intended direct award. VEATs are visible on TED and provide intelligence about procurement that would otherwise be entirely invisible — including which supplier an authority intends to award to for a sole-source procurement and on what grounds. If a competitor keeps winning directly awarded contracts from a buyer you're targeting, VEATs are where you'll find the paper trail.

Prior Information Notices (PINs): Published before a contract notice, PINs announce upcoming procurement in advance. For CAN research, PINs from 12–24 months before a CAN provide context about the original procurement intent and how the actual award compared to what was announced. Useful for understanding how a buyer's scope evolved through the process.

Corrigendum notices: Published to correct errors in previously published notices — including CANs. Where a CAN contains an error in the winner name, value, or other fields, a corrigendum corrects the record. When researching CAN data systematically, always check for corrigenda that may supersede the original — particularly for high-value contracts where the detail matters.

DPS and Framework Agreement Award Notices

For framework agreements, the CAN published at framework conclusion discloses who has been appointed. In large multi-supplier frameworks, this is strategically significant information: knowing which competitors are on the framework — and which lots they hold — directly maps their access to that buyer's procurement over the next four years. You can identify whether you're facing them across all lots or only specific ones, and whether the framework has vacant lots where additional suppliers could potentially be admitted mid-term.

For Dynamic Purchasing Systems, CANs are published quarterly for all call-offs under the DPS rather than individually. The quarterly CAN groups multiple awards — disclosing the total awarded value and cumulative winner information for the period. Individual call-off winner details may be less granular than single-contract CANs, but they still provide market share intelligence at the category level over time. If a competitor is consistently winning DPS call-offs in a category you want, you need to understand why — and the quarterly CANs give you the pattern even if not the individual transaction detail.

Spotting Retender Windows

One of the most actionable uses of CAN data is identifying upcoming retender windows — when incumbent contracts are due to expire and will be re-tendered competitively. This is where the investment in systematic CAN monitoring pays off most directly.

By tracking CANs in your target CPV categories and buyer organisations, you can identify contracts with specific start dates and durations and calculate the expected retender window. A contract awarded on 1 January 2023 for a 4-year term will expire on 31 December 2026. Given that EU procurement processes for above-threshold contracts take approximately 4–6 months from contract notice publication to award, the retender process would typically commence with a contract notice around June–September 2026 to ensure service continuity. Identifying this window 12–18 months in advance allows a challenger supplier to do something meaningful: research the incumbent's performance and any reported issues, engage the contracting authority through pre-tender market engagement events, ensure qualifications and references are updated to meet the likely selection criteria, and prepare a bid strategy before the contract notice appears.

This approach — using CAN duration data to forecast retender windows — is standard practice among sophisticated EU market participants. The difference between suppliers who do this and suppliers who don't is the difference between reactive bidding (responding to whatever appears on TED this week) and strategic pipeline management (knowing twelve months ahead which contracts will come to market and being positioned to win them). Most suppliers are reactive. You don't have to be.

Frequently Asked Questions

Where can I find EU Contract Award Notices?

EU CANs for above-threshold procurement are on TED (ted.europa.eu) — filter by notice type "Contract award notice". Below-threshold CANs appear on national portals (eTenders Ireland, BOAMP France, DTVP Germany). Filter TED by CPV code, country, and contracting authority for targeted searches. The TED Open Data API provides bulk access for systematic intelligence extraction. TenderMetric aggregates CANs with filtering by sector and country for procurement intelligence without manual TED searches.

What information is contained in a EU Contract Award Notice?

A CAN contains: contracting authority details (Section I); contract scope, CPV codes, and estimated value (Section II); procedure type and award criteria (Section IV); and — most valuably — the winner name and address, total awarded contract value, number of tenders received, number from SMEs, and number from other EU states (Section V). For multi-lot contracts, Section V repeats per lot. Winner name and contract value are mandatory for above-threshold CANs; some authorities omit optional fields like bid count and SME status.

How long does a contracting authority have to publish a Contract Award Notice?

Article 50 of Directive 2014/24/EU requires publication within 30 days of contract conclusion (contract signature). For DPS call-offs, a quarterly grouping exemption applies. Framework agreement CANs must be published within 30 days of the framework conclusion. In practice, 60–90 day delays are not uncommon for complex contracts — the absence of a CAN doesn't mean a contract hasn't been awarded. The eForms regulation (2022/2303) is improving CAN timeliness through standardisation, but compliance varies by member state.