oSIST prEN 17014-1:2026

SLOVENSKI STANDARD
01-marec-2026
Elektronska javna naročila - Faza pred oddajo naročila - 1. del: Koreografije
Electronic public procurement - Pre-award - Part 1: Choreographies
Elektronisches öffentliches Beschaffungswesen - Ausschreibungsverfahren - Teil 1:
Choreographien
Marchés publics électroniques - Avant attribution - Partie 1: Chorégraphies
Ta slovenski standard je istoveten z: prEN 17014-1
ICS:
03.100.10 Nabava. Dobava. Logistika Purchasing. Procurement.
Logistics
35.240.20 Uporabniške rešitve IT pri IT applications in office work
pisarniškem delu
35.240.63 Uporabniške rešitve IT v IT applications in trade
trgovini
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

DRAFT
EUROPEAN STANDARD
NORME EUROPÉENNE
EUROPÄISCHE NORM
January 2026
ICS 35.240.63
English Version
Electronic public procurement - Pre-award - Part 1:
Choreographies
Marchés publics électroniques - Avant attribution - Elektronisches öffentliches Beschaffungswesen -
Partie 1: Chorégraphies Ausschreibungsverfahren - Teil 1: Choreographien
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/TC 440.
If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations
which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.

This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.

Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.

EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2026 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 17014-1:2026 E
worldwide for CEN national Members.

Contents Page
European foreword . 5
Introduction . 6
0.1 Derivative use pilot . 6
0.2 Intended use of this publication . 6
0.3 Parts of the document to which derivative use apply . 6
1 Scope . 7
2 Normative references . 7
3 Terms and definitions . 7
4 Business environment and high level business requirements . 8
4.1 Introduction . 8
4.2 Business goals . 9
5 Business environment . 10
5.1 General . 10
5.2 Business context . 10
5.3 Positioning in EIRA . 11
5.4 Organization and business partners involved . 12
5.5 High level business process requirements . 13
6 Processes . 15
6.1 General . 15
6.2 Business process variants . 15
6.2.1 Introduction . 15
6.2.2 Claiming compliance . 16
6.3 Business process variant A - Open Procedure . 16
6.3.1 Introduction . 16
6.3.2 Open Procedure legal framework . 16
6.3.3 Open Procedure requirements . 17
6.3.4 Open Procedure definition . 17
6.3.5 Open Procedure scenarios . 17
6.3.6 Open Procedure business rules . 18
6.3.7 Open Procedure key examples . 18
6.4 Business process variant B - Restricted procedure . 22
6.4.1 Introduction . 22
6.4.2 Restricted procedure legal framework . 22
6.4.3 Restricted procedure requirements . 23
6.4.4 Restricted procedure definition . 24
6.4.5 Restricted procedure business rules . 24
6.4.6 Restricted procedure key examples . 24
6.5 Business process variant C - Dynamic purchasing system . 26
6.5.1 Introduction . 26
6.5.2 Dynamic purchasing system legal framework . 27
6.5.3 Qualification and role of ESPD . 28
6.5.4 Use of eCatalogues . 28
6.5.5 Dynamic purchasing system requirements . 29
6.5.6 Dynamic purchasing system definition . 30
6.5.7 Dynamic purchasing system business rules . 31
6.5.8 Dynamic purchasing system key examples . 31
6.6 Business process variant D - Competitive Dialogue . 32
6.6.1 Introduction . 32
6.6.2 Competitive Dialogue legal framework . 32
6.6.3 Competitive Dialogue requirements . 33
6.6.4 Competitive Dialogue definition . 34
6.6.5 Competitive Dialogue business rules . 35
6.6.6 Competitive Dialogue key examples . 35
6.7 Business process variant E - Competitive procedure with negotiation . 37
6.7.1 Introduction . 37
6.7.2 Competitive procedure legal framework . 37
6.7.3 Competitive procedure requirements . 38
6.7.4 Competitive procedure definition . 39
6.7.5 Competitive procedure business rules . 40
6.7.6 Competitive procedure key examples . 40
6.8 Business process variant F - Innovation partnership . 42
6.8.1 Introduction . 42
6.8.2 Innovation partnership legal framework . 42
6.8.3 Innovation partnership requirements . 43
6.8.4 Innovation partnership definition . 44
6.8.5 Innovation partnership business rules . 45
6.8.6 Innovation partnership key examples . 45
7 Sub processes . 47
7.1 Introduction . 47
7.2 Notification . 47
7.2.1 Introduction . 47
7.2.2 Notification requirements . 48
7.2.3 Notification definition . 49
7.2.4 Notification business rules . 49
7.2.5 Notification key examples . 50
7.3 Procurement procedure subscription and access . 51
7.3.1 Introduction . 51
7.3.2 Procurement procedure subscription and access requirements . 51
7.3.3 Procurement procedure subscription and access definition . 52
7.3.4 Procurement procedure subscription and access business rules . 53
7.3.5 Procurement procedure subscription and access key examples . 53
7.4 Tenderer qualification . 54
7.4.1 Introduction . 54
7.4.2 Tenderer qualification requirements . 55
7.4.3 Tenderer qualification definition . 55
7.4.4 Tenderer qualification business rules . 56
7.4.5 Tenderer qualification key examples . 56
7.5 Invitation to tender . 57
7.5.1 Introduction . 57
7.5.2 Invitation to tender requirements . 58
7.5.3 Invitation to tender definition . 59
7.5.4 Invitation to tender business rules . 59
7.5.5 Invitation to tender key examples . 60
7.6 Tender submission . 61
7.6.1 Introduction . 61
7.6.2 Tender submission requirements . 61
7.6.3 Tender submission definition . 62
7.6.4 Tender submission business rules . 62
7.6.5 Tender submission key examples . 63
7.7 Awarding . 64
7.7.1 Introduction . 64
7.7.2 Awarding requirements . 64
7.7.3 Awarding definition . 65
7.7.4 Awarding business rules . 66
7.7.5 Awarding key examples . 66
8 Tendering message response . 67
8.1 General . 67
8.2 Tendering message response requirements . 68
8.3 Tendering message response definition . 69
8.4 Tendering message response business rules . 70
8.5 Tendering message response key examples . 70
9 Collaborations and transactions . 71
9.1 Summary . 71
Annex A (normative) Overview of the clauses and subclauses which fall under derivative use 74
Bibliography . 75
European foreword
This document (prEN 17014-1:2026) has been prepared by Technical Committee CEN/TC 440
"Electronic Public Procurement", the secretariat of which is held by DIN.
This document is currently submitted to the CEN Enquiry.
This document is part of a series of multi-part documents prepared, or under preparation, by CEN/TC
440:
— EN 17011 series [1]: e-Procurement Architecture, providing a set of spécifications outlining
different aspects of the e-Procurement architecture for Business Interoperability Spécifications.
— EN 17014 series [2]: Pre-award Business Interoperability Spécifications, providing a set of
spécifications outlining business choreography, transaction, syntax binding spécifications and
guidelines required to support the pre-award processes.
— EN 17015 series [3]: e-Catalogue Business Interoperability Spécifications, providing a set of
spécifications outlining business choreography, transaction, syntax binding spécifications and
guidelines required to support the e-Catalogue processes.
— EN 17016 series [4]: e-Orderin Business Interoperability Spécifications, providing a set of
spécifications outlining business choreography, transaction, syntax binding spécifications and
guidelines required to support the e-Ordering processes.
— EN 17017 series [5]: é-Fulfilmént Business Interoperability Spécifications, providing a set of
spécifications outlining business choreography, transaction, syntax binding spécifications and
guidelines required to support the e-Delivery processes.
Introduction
0.1 Derivative use pilot
This document falls under a CEN-CENELEC pilot on derivative use (as approved by the CEN/CA
(Administrative Board) through Decision 38/2019).
CEN has the copyright to all CEN publications, including their entire content and associated metadata,
as spécifiéd in CEN-CENELEC Guide10 "Policy on dissemination, sales and copyright of CEN-CENELEC
Publications". However, through the derivative use pilot, CEN gives permission to the copying,
replication and translation of content from CEN/TC 440 deliverables in spécific circumstances.
Under the derivative use pilot, spécific sections of CEN/TC 440 publications may be copied, replicated
and translated in cases where this is a necessary condition for the meaningful implementation of the
publication. The sections which fall under derivative use will typically be elements such as semantic
définitions and rules related to the use of information elements, and the name, définition and description
of processes and transactions, which are needed in software solutions, whether intended for sale in the
private market or for use in the public sector, and documents guiding the implementation and use in
spécific countries and/or business sectors.
Under derivative use, any use of content which has been copied, replicated, or translated from a
CEN/TC 440 publication must comply with the intended use of the publication. Derivative use cannot
be applied in use cases other than those the publication is intended to support. The intended use of this
publication is set out below.
0.2 Intended use of this publication
This document has been developed for any organization looking for guidance on the implementation
and use of electronic procurement deliverables as well as for organizations developing or implementing
software applications related to electronic procurement, such as software providers, business entities
and national entities. These software applications shall be in conformance with this publication.
0.3 Parts of the document to which derivative use apply
Each subclause which falls under derivative use will be clearly marked with a note. The degree to which
the spécific content can be modifiéd is définéd in CEN/TS 17011-3 [6].
Annex A provides an overview of the line number references to all subclauses of the publication which
fall under derivative use.
1 Scope
This choreographies document spécifiés pre-award processes between Contracting Entities (Buyer)
and Economic Operators (Seller) where the Contracting Entity wants to contract an Economic Operator.
It spécifiés a series of activities that govern communication between the parties and refers to the
spécifications where information and rules that apply are spécifiéd.
The various possible behaviours of the Seller and Buyer subsequent to the communication are conveyed
by variants of this choreography that are spécifiéd in Clause 6.
This document is linked to the directives on public procurement [7] and on procurement by entities
operating in the water, energy, transport and postal services sectors [8] and on the award of concession
contracts [9] and on the coordination of procedures for the award of contracts in the fiélds of defence
and security [10]. Implementing Regulation (EU) 2019/1780 establishing standard forms for the
publication of notices [eForms] [11] and Implementing Regulation (EU) 2016/7 establishing the
standard form for the European Single Procurement Document [ESPD] [12] are supplementary
regulations that are relevant to this document.
The idéntifiér of this choreographies document is EN 17014-1:2026.
The corresponding transactions are described in prEN 17014-2:2025 [13].
How to claim conformance to this choreography is spécifiéd in 6.2.2.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and définitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— IEC Electropedia: available at http://www.electropedia.org/
— ISO Online browsing platform: available at http://www.iso.org/obp
3.1
agent
person, organization, or system that acts in procurement or has the power to act in procurement
3.2
business process
sequence or network of activities and collaborations between two or more agents
3.3
business process variant
spécification of a business process belonging to a choreography
Note 1 to entry: Different variants may support different electronic information exchange or collaborations. Agents
may publicly advertise their capability to support one or more variants in an automated fashion.
3.4
choreography
set of business processes having the same goals
3.5
collaboration
interaction between two or more agents that result in the exchange of data between the agents involved
as part of a business process
3.6
role
part played by an agent in a particular business process, including its responsibilities (options and
obligations) to perform certain activities and collaborations in that business process
Note 1 to entry: The role is used to show the division of labour and responsibility amongst the agents involved in
the process or within the organization of an agent.
3.7
state
set of options and obligations of the participating agents at a définéd step in a business process to
perform spécific activities and collaborations
Note 1 to entry: An activity of an agent or a collaboration may cause the transition of one state to another in a
prédéfinéd set of next steps.
3.8
transaction
content of data exchanged or shared between the agents in a collaboration
Note 1 to entry: A transaction is the atomic unit that leads to a synchronized state in the information systems of
collaborating agents. It is the basic building block to définé the choreography between agents. When an agent
recognizes an event that changes the state of a business object within a business process, it uses a transaction to
synchronize with the collaborating agent. A transaction therefore changes the state of a business process. It carries
the intention of the initiating agent and is represented by a data structure that is définéd by a data model. The
exchange of a transaction may alter legal obligations between business partners.
4 Business environment and high level business requirements
4.1 Introduction
eTendering can be put in place using different procedures, depending on the value and the type of the
contract to be awarded, on the legal nature of the contracting entity and on spécific member state
national legislation. Different tendering procedures that can be used by contracting entities are for
example described by European procurement directives [7] [8] [9] [10].
In open procedures, any economic operator can access the tender documents (including the call for
tenders) and submit a tender before the time expires, without any previous assessment of their
capabilities. In restricted and negotiated procedures and in a competitive dialogue the interested
economic operators have to submit a request to participate in order to be invited in the tendering
process by the contracting entity. When the contracting entity has published a notice, for example using
the standard forms for the publication of notices (eForms) définéd by the Commission Implementing
Regulation (EU) 2019/1780 [11], interested economic operators may subscribe (unscubsribe) to obtain
(not obtain) tendering information using sub process subscribe to procedure. Restricted and negotiated
procedures require sending the invitation to tender to the idéntifiéd candidates.
Once the interested economic operator has subscribed to an open procedure, the contracting entity
provides the procurement documents. This can be repeated at any time until the tender submission
deadline to receive the latest version of the procurement documents has been reached. Additionally,
contracting entities need to push updates to the economic operators that subscribed to a procedure.
Within the call for tenders, contracting entities inform economic operators how to qualify for the
procedure. This may be done by an European Single Procurement Document (ESPD) définéd by the
Commission Implementing Regulation (EU) 2016/7 [12]. Additionally, call for tenders may include pre-
award catalogue information to describe products and services in a common format allowing economic
operators to send offers in a structured way and contracting entities to evaluate products and services
automatically through their tendering tools.
Restricted and negotiated procedures require a previous qualification before submitting a tender. In
restricted and negotiated procedures the contracting entity will send an invitation to tender to the
idéntifiéd candidates which have been selected to submit a tender. In contrast, those economic operators
whose qualifications are being rejected are informed.
Once the economic operator has received the call for tenders or invitation to tender, it can use the sub
process of raising questions about procurement documents. This sub process supports economic
operators asking questions about call for tenders. Answers of the contracting entity are to be sent to all
economic operators that subscribed to the procedure and additionally the call for tenders are updated
and pushed to the subscribers of the procedure.
In case the economic operator decides to submit a tender, he can use the tender submission sub process.
After the submission of a tender, the contracting entity notifiés the economic operator of having received
the tender. Economic operators can also decide to withdraw a tender that was previously submitted.
The contracting entity notifiés the economic operator of having received the tender withdrawal. After
the tender withdrawal, an economic operator may submit a new offer at any time before the tender
submission deadline.
On the opening date, the contracting entity gathers and opens all received tenders. The opening board
members can now evaluate the received tenders. If questions about spécific offers arise during the
course of the evaluation, they can be answered using the tender clarification sub process. This sub
process supports the contracting entity to clarify questions on a tender which has been submitted.
At the end of the evaluation process, the contracting entity needs to inform the participating economic
operators upon the results of the tender evaluation. For this purpose, contracting entities can use the
awarding sub process which provides electronic messaging support to inform the bidders that a contract
has been awarded to a particular economic operator. The contracting entity can use the sub process to
inform the winner(s) at the same time as they inform the unsuccessful tenderers and they has to
individually declare the reasons why they failed. The standstill period also begins with the notification
of the imitated award decision. After the stand still period, the contracting entity can finalizé the contract
with the winning supplier and also send a contract award notice.
4.2 Business goals
The business goals supported by implementing this choreography are spécifiéd in Table 1 .
Table 1 — Business goals
ID Description
G-17014-1:2025-1 No previous bi-lateral setup or agreements required - Parties (economic
operators and contracting entities) should communicate without a previous bi-
lateral setup or agreements.
G-17014-1:2025-2 Transparency - The contracting entity wants to obtain the best value-for-money
by maximising the transparency of its tender procedures in order for economic
operators to easily find this business opportunity.
G-17014-1:2025-3 Equal treatment - The contracting entity has the obligation to treat all economic
operators equally during the whole tender procedure.
G-17014-1:2025-4 Competition - The contracting entity wants to obtain the best value-for-money
by maximising the competition among bidders.
G-17014-1:2025-5 Insurance bid - The economic operator wants insurance that his bid is valid and
has been received by the contracting entity within the time limit set out in the
tender documents.
G-17014-1:2025-6 Interoperability - The Member State policymakers want interoperability
between all tendering solutions in order to facilitate one single European Market
because the better interoperability the more bids.
ID Description
G-17014-1:2025-7 Equal access - economic operators want equal access to all public procurement
business opportunities.
G-17014-1:2025-8 Authentication - The contracting entity wants insurance that it is dealing with
real economic operators during the tender procedure.
G-17014-1:2025-9 Legal valid bid - The contracting entity wants insurance that the bid is signed by
persons mandated by the economic operators therefore being a legally valid bid.
The main business bénéfits to be gained by implementing this choreography are spécifiéd in Table 2.
Table 2 — Business benefits
ID Description
G-1714-1:2025-10 Reduce human errors and resources - Automated matching of the Tender with
the Call for Tender document should eliminate human keying errors and
facilitates redeployment of resources.
G-1714-1:2025-11 Facilitate Automated Tender Preparation - e-Tendering/e-Submission solutions
should allow Economic Operators (semi)automatically to generate a tender
based on the information définéd in procurement documents
G-1714-1:2025-12 Efficiéncy - The contracting entity wants to increase éfficiéncy in the business
process, e.g. when evaluating the received bids, in order to save time and costs.
G-1714-1:2025-13 Integrity of the bid - The contracting entity and the economic operator want
insurance that the integrity of the bid is secured, i.e. insurance of accuracy and
consistency when storing and retrieving data.
G-1714-1:2025-14 Administrative burdens - The Member state policymakers want to lower the
administrative burden in public procurement for economic operators and
contracting entities.
G-1714-1:2025-15 Re-use of information - The economic operator re-uses as much information and
documents as possible when preparing a bid in order to save time and costs.
G-1714-1:2025-16 Standards - The economic operator wants to receive as much as possible
standardized tender documents, in order to easily understand the content and
to easily respond by creating a tender and to respond with standardized evidence
and product information that are requested.
G-1714-1:2025-17 Accountability - The contracting entity - being accountable for the procedure -
doesn't want to make mistakes during the whole tender procedure.
5 Business environment
5.1 General
The intended scope for this choreography is focused on public procurement.
This choreography is intended to support use of electronic documents for processing in
(semi-)automated processes. The legal requirements that were taken into account are requirements
from European legislation, particularly the EU Directives, as mentioned in the Bibliography of this
document.
The list of the transactions that are part of this choreography is définéd in Clause 8.
5.2 Business context
This choreography belongs to the procurement business area that is spécifiéd in Figure 1.
Figure 1 — Pre award context
5.3 Positioning in EIRA
EIRA (European Interoperability Reference Architecture) provides a reference model that enables
architects to position the IOP (InterOPerability) spécifications. This document provides a domain-
spécific IOP spécification to which any SBB (Solution Building Block) implementing the ABB
(Architecture Building Block) should be compliant to. The positioning of this document in the EIRA
context is spécifiéd in Table 3.
IoP spécifications provide a valuable source of information to formulate requirements during
architecture development and solution development. By identifying architectural building blocks
through a common terminology, it
—  helps reuse of cross domain building blocks such for instance e-Signature Vérification and Validation
Service, and e-Timestamp Creation Service;
—    helps synchronization with European solutions such as CEF eDelivery;
—  and will provide guidance in using them to provide the prescribed capability enabling, thus managing
and rationalizing IT portfolios.
Table 3 — Positioning in EIRA
EIRA-ID Title Domain Interface Scope Modality
EN1714-1:2 Electronic Public Procurement Machine/ • eProcurement extension Endorsing
025 Procurement - Pre- Contracting of ABB176 Organizational
award -Choreography Entity Interoperability
Spécification
Machine/
Economic • eProcurement extension
Operator of ABB12 Business
Capability
Machine/
Publication body • eProcurement extension
of ABB170 Exchange of
Business Information
• eProcurement extension
of ABB16 Business Rule
5.4 Organization and business partners involved
The following business partners participate in this choreography, acting in the roles as définéd in Table
4 and Figure 2 below.
Table 4 — Roles
Key role Description
Contracting entity The authority or body that is buying supplies, services, or tendering works and is
contracting one or more suppliers. In many cases, the contracting entity is acting in
the role of a buyer.
Economic operator Party participating with a bid in a procurement process to sell goods, services or
works. In many cases, the economic operator is acting in the role of a seller.
Publication body A Pan-European, national, or regional organization that publishes procurement
notices of a contracting entity. While the basic role of the publisher may apply to any
newspaper, other roles and functions are often restricted to official gazettes. These
gazettes are also often responsible to ensure a formal vérification of the notices in
respect of legislative or other requirements in vigour. Official gazettes may also have
the role to receive information exempted from publication (e.g. due to confidéntial
content) used for notification to a supervising authority.
Figure 2 — Roles
5.5 High level business process requirements
Based on the goals and scope of this choreography the following set of high-level requirements is
idéntifiéd. Each requirement is connected to a goal.
Additionally, requirements of major business processes within pre-award are listed.
These requirements are relevant for all variants depicted within this choreography and spécifiéd in
Table 5.
Table 5 — High level requirements
Req. ID Requirement statement Ref. To goal
HLR-17014-1:2025 All procurement activities and decisions shall be transparent and G-1714-1:2025-17
-1 documented.
HLR-17014-1:2025 The process shall ensure clear communication and visibility at each G-1714-1:2025-17
-2 stage, from publication to contract award.
HLR-17014-1:2025 All potential suppliers shall be given equal access to information and G-1714-1:2025-3
-3 opportunities.
HLR-17014-1:2025 No supplier should be given preferential treatment during the G-1714-1:2025-3
-4 process.
HLR-17014-1:2025 Suppliers should not be discriminated against based on nationality or G-1714-1:2025-3
-5 other non-relevant factors.
HLR-17014-1:2025 The process shall comply with anti-discrimination laws and G-1714-1:2025-3
-6 regulations.
HLR-17014-1:2025 A contract notice shall be published in the Official Journal of the G-1714-1:2025-3
-7 European Union (OJEU) and on national procurement portals.
Req. ID Requirement statement Ref. To goal
HLR-17014-1:2025 The contracting authority shall ensure the confidéntiality of suppliers’ G-1714-1:2025-13
-8 proprietary information.
HLR-17014-1:2025 Measures shall be in place to protect sensitive information throughout G-1714-1:2025-13
-9 the process.
HLR-17014-1:2025 All stages of the procurement process, including decisions and G-1714-1:2025-17
-10 communications, shall be documented.
HLR-17014-1:2025 Documentation shall be retained for auditing and transparency G-1714-1:2025-17
-11 purposes.
HLR-17014-1:2025 An award notice shall be published in the OJEU and on the national G-1714-1:2025-3
-12 procurement portal after the contract is awarded.
HLR-17014-1:2025 The notice should include the name of the winning supplier and key G-1714-1:2025-3
-13 details of the contract.
HLR-17014-1:2025 The procurement process shall comply with relevant laws, G-17014-1:2025-9
-14 regulations, and directives.
HLR-17014-1:2025 Legal requirements regarding public procurement, data protection, G-17014-1:2025-9
-15 and anti-corruption shall be strictly followed.
HLR-17014-1:2025 Potential risks associated with the procurement shall be idéntifiéd G-17014-1:2025-5
-16 and mitigated.
HLR-17014-1:2025 The awarded contract shall be managed to ensure compliance with G-17014-1:2025-4
-17 terms and conditions.
HLR-17014-1:2025 Performance monitoring and regular reviews should be conducted to G-17014-1:2025-4
-18 ensure the supplier meets their obligations.
HLR-17014-1:2025 A process shall be established for handling queries and clarifications G-17014-1:2025-7
-19 from potential suppliers.
HLR-17014-1:2025 Responses to queries shall be provided promptly and shared with all G-17014-1:2025-7
-20 interested suppliers to maintain transparency.
HLR-17014-1:2025 All transactions in the procurement procedure, such as subscribe to G-17014-1:2025-2
-21 procedure or status inquiry, and documents, such as call for tenders
or catalogues, should be based on common standards.
HLR-17014-1:2025 The value of digitization lies in the implementation of all transactions G-17014-1:2025-2
-22 in a procedure. A contracting entity may therefore enforce a business
process (tendering procedure), consisting of multiple transactions,
on economic operators. Both contracting entities and economic
operators may state conformance of their system to the entire
process.
HLR-17014-1:2025 Code lists shall be consistent for all transactions in a complete G-17014-1:2025-1
-23 procedure. 6
HLR-17014-1:2025 For contracting entities and economic operators to be able to process G-17014-1:2025-2
-24 individual transactions, they (or their systems) need to know to what 0
business process the transaction belongs to. The process type and the
process instance need to be idéntifiéd at two levels: the level of the
...