Procurement Procedure Identifier

The Procurement Procedure Identifier is a key structural element of the eForms framework that enables the linkage of multiple notices belonging to the same underlying procurement into a coherent, traceable lifecycle record on TED. Where the Notice Publication ID identifies a specific publication, the Procurement Procedure Identifier identifies the procedure itself across all its publication events.

What is a Procurement Procedure Identifier?

When a contracting authority launches a procurement procedure, it assigns (or its e-procurement system generates) a Procurement Procedure Identifier. This identifier appears in every eForms notice published for that procedure: the Planning Notice, the Competition Notice, any Change Notices, and the final Result Notice. By including the same procedure identifier in each notice, TED can automatically associate all publications relating to the same procurement into a linked record.

In the eForms SDK, the Procurement Procedure Identifier maps to a specific business term field (BT-22 in the eForms field structure). It is a free-form string that must be unique within the contracting authority's own notice publication history, though not necessarily globally unique. TED uses the combination of the identifier and the contracting authority's identifier to establish uniqueness at the system level.

The introduction of the Procurement Procedure Identifier was a significant improvement over the legacy standard form system. Under legacy forms (Standard Form 1, Standard Form 2, Standard Form 3), the link between related notices was implicit, relying on buyers consistently using the same text references or on users manually searching for associated notices. Under eForms, the link is machine-readable and enforced, enabling automated lifecycle analysis.

For Corrigendum Notices under the legacy system and their eForms equivalents Change Notices, the procedure identifier is supplemented by the Notice Publication ID of the notice being amended, providing a second linkage mechanism.

Why the Procurement Procedure Identifier matters for bidders

The Procurement Procedure Identifier enables procurement platforms to automatically present the full history of a procurement opportunity in a single view. When you look at a contract award for an opportunity you were tracking, you can see the original planning notice, the competition notice, any amendments that were published, and the final award, all linked by the procedure identifier.

This lifecycle view has several practical benefits. It shows you whether the buyer followed a typical procurement path or published multiple amendments (suggesting an unusual or complex procedure). It shows you the elapsed time from planning to award. It shows you whether a planning notice was published in advance of the competition. All of these are signals that inform your understanding of the buyer's procurement practice and your strategy for future competitions.

Example

A Bulgarian road maintenance authority begins a procurement procedure with a Planning Notice published in March. The Planning Notice carries Procurement Procedure Identifier "RDA-2024-0042." In June, the authority publishes a Competition Notice carrying the same identifier. Three weeks later, after receiving clarification questions, it publishes a Change Notice extending the deadline, also carrying "RDA-2024-0042." In September, it publishes a Result Notice with the same identifier. A procurement platform automatically links all four notices and presents the full lifecycle timeline to suppliers monitoring this buyer.

Frequently Asked Questions

Is the Procurement Procedure Identifier assigned by TED or by the contracting authority?

It is assigned by the contracting authority (or generated by its e-procurement system). TED does not assign it centrally. The authority's responsibility is to use the same identifier consistently across all notices for the same procedure.

What happens if a contracting authority uses different identifiers for related notices?

If the identifiers are inconsistent, TED cannot automatically link the notices. The lifecycle chain is broken at the data level, though the notices remain individually searchable. Procurement platforms may use secondary matching techniques (matching buyer, CPV code, and contract description) to infer the link, but this is less reliable than the direct identifier match.

Can I search TED directly by Procurement Procedure Identifier?

TED's standard search interface does not prominently expose procedure identifier as a primary search field, but it is included in TED's open data API and is accessible through advanced search parameters. Procurement platforms that ingest TED data use this field for automatic lifecycle linking.