How EU tender evaluation works: what evaluators look for and score

The legal framework: Financial Regulation, PRAG, and procurement directives

EU procurement for service contracts runs on two separate legal tracks, and the distinction determines which evaluation rules apply to any given tender. The first track covers contracts placed by EU institutions and member state public authorities using domestic public funds. It is governed by Directive 2014/24/EU (standard public sector) and Directive 2014/25/EU (utilities sectors). The second track covers EU External Action procurement: contracts placed by the European Commission and EU Delegations to implement development, neighbourhood, and enlargement programmes. This track is governed by the EU Financial Regulation (Regulation (EU, Euratom) 2018/1046, as amended) and operationalised through the PRAG.

Most consultancy, technical assistance, and programme management contracts funded through INTPA (International Partnerships), DG NEAR (Neighbourhood and Enlargement), and related EU external financing instruments are procured under the PRAG. The PRAG is updated periodically. The current version is PRAG 2025, which incorporates changes following the 2024 revision of the Financial Regulation. Bidders should work from the current PRAG, not older guidance documents circulating in the market.

The Financial Regulation sets the principles: economy, efficiency, effectiveness, transparency, and equal treatment. The PRAG translates these into specific procedural steps, evaluation rules, standard contract forms, and templates. Where a tender dossier is silent on a procedural point, the PRAG provides the default. Familiarity with both documents is a basic competency for EU procurement advisory work and for organisations running their own bids.

For EU internal procurement under Directive 2014/24/EU, the evaluation structure is broadly similar but contracting authorities have more discretion on award criteria design. The best price-quality ratio (BPQR) framework is explicitly codified in the Directive, and the quality/price weighting can vary considerably across contracting authorities and contract types.

The two-envelope system

Under PRAG procedures, technical assistance and service contract tenders use the two-envelope system. Tenderers submit one package containing two sealed components: a technical offer and a financial offer. Both envelopes are submitted simultaneously by the tender deadline. The financial envelope is not opened until technical evaluation is complete.

The sequence runs as follows:

1. The evaluation committee opens all technical envelopes and scores them independently against the evaluation grid.
2. Bids that do not reach the minimum technical score are eliminated. Their financial envelopes are returned or destroyed unopened.
3. Financial envelopes for technically qualified bids are opened in a formal session.
4. Financial scores are calculated and combined with technical scores to produce the final ranking.
5. The bid with the highest combined score is recommended for award.

The separation of technical and financial scoring is a structural safeguard built into the PRAG. It prevents price from anchoring technical judgments, and it prevents technically weak bids from winning on cost alone. For bidders, the practical consequence is that the technical offer must stand entirely on its own merits: evaluators scoring your methodology do not know whether your bid is the cheapest, the most expensive, or in the middle of the field.

Technical evaluation criteria and the scoring grid

The evaluation grid is published as part of every tender dossier. It sets out each criterion, its sub-criteria, the maximum points available per sub-criterion, and any minimum score required to pass a sub-criterion. Evaluators are bound by the published grid; they cannot introduce new criteria or shift weightings after publication.

For INTPA and NEAR technical assistance contracts, the technical component is scored out of 100 points. The structure below is representative of a standard service contract evaluation under PRAG procedures, though the precise weights vary by contract size, sector, and contracting authority:

These allocations are indicative. Methodology typically carries the highest weight in technical assistance contracts. For large, complex assignments, the methodology criterion alone may account for 40 to 60 points out of 100. Read the specific evaluation grid in the tender dossier before structuring the technical offer.

Minimum sub-criterion thresholds

Many evaluation grids set minimum scores at sub-criterion level, not just at the total. A common rule is that each sub-criterion must reach at least 50% of its maximum. A bid that scores 35/40 on methodology but 4/20 on team organisation may still be eliminated if the evaluation grid sets a minimum of 10 points on that criterion.

Before writing, identify every sub-criterion that carries a minimum threshold. Ensure each section of the technical offer addresses those criteria directly, by name, and in enough depth to comfortably clear the floor. A strong methodology section does not rescue a near-zero score on risk management if the grid sets a minimum there.

Key expert CVs and the team criterion

For contracts that specify key expert positions, the team criterion is partly formula-driven. The tender dossier sets minimum qualification and experience requirements for each position, plus preferred criteria that earn additional points. An expert who meets all minimum requirements but none of the preferred criteria will score at the floor; an expert who meets several preferred criteria will score higher.

Evaluators cross-reference CVs against the evaluation grid line by line. CVs that rely on generic language without specific contract references, dates, client names, and deliverable descriptions will consistently score below their potential. The CV is an evidence document, not a career summary. Every claim the expert makes about their experience should be traceable to a named assignment.

The evaluation committee: individual scoring and consensus

Evaluation committees for EU external action contracts typically include three to five voting members. All members sign declarations of impartiality and confidentiality before evaluation begins. Any member who identifies a potential conflict of interest with a tenderer is recused and replaced.

The standard process under PRAG is:

1. Individual reading and scoring: each evaluator reads and scores each technical offer independently, recording scores and written justification on their individual score sheets. This phase happens before any group discussion.
2. Comparison: the committee meets and compares individual scores. The range of scores per sub-criterion is noted for each bid.
3. Consensus discussion: where scores diverge beyond a defined tolerance, evaluators explain their reasoning. The committee then agrees a consensus position based on what is actually written in the offer. Consensus is not averaging; it requires a justifiable, evidence-based position.
4. Finalisation: consensus scores are recorded in the evaluation report with written justifications. All committee members sign the report before it is submitted to the contracting authority for approval.

The evaluation report is an auditable document. Contracting authorities keep it on file and may be required to disclose score breakdowns to unsuccessful tenderers on request. The written justifications matter: they form the basis of debriefs and, if a challenge is lodged, they must withstand scrutiny.

Quality/price weighting and how financial scores are calculated

For technical assistance contracts under PRAG procedures, the standard award weighting is 80 points for technical quality and 20 points for financial offer. This split reflects the EU's consistent position that quality of delivery is the primary driver of value for money in service contracts, and that marginal price differences matter less than the capacity of the team to deliver.

The financial score is calculated by formula, stated in the tender dossier's instructions to tenderers. The most common approach gives the maximum financial points (20) to the lowest compliant financial offer. Other bids receive financial points proportional to their premium above that lowest offer. A bid priced 10% above the lowest compliant tender would receive approximately 18 of the 20 available financial points, not zero. The formula is specified per tender and should be read before finalising the financial offer, particularly for contracts where multiple lots are possible.

Financial points alone cannot rescue a weak technical offer. A bid that scores 69 out of 80 technical points fails the 70/100 overall minimum and is eliminated regardless of its price. Conversely, a bid that scores 82 technical points but is priced substantially above the indicative budget envelope will receive few financial points and is unlikely to win even with a strong technical score.

For EU internal procurement under Directive 2014/24/EU, the quality/price split varies more widely. For routine service contracts where technical differentiation is limited, price may account for 40% to 50% of the award score. For specialist advisory or implementation contracts, the quality weighting is typically higher. The contracting authority's chosen weighting must be stated in the contract notice or tender documents and cannot be changed after publication.

The minimum technical threshold

Under standard PRAG procedures, the minimum technical score to advance to financial evaluation is 70 out of 100 points. Bids scoring 69 or below are eliminated, and their financial envelopes are not opened.

Some tender dossiers set a higher threshold. Complex, high-value technical assistance contracts may require 75 or 80. The threshold is stated explicitly in the instructions to tenderers and is binding on the evaluation committee. Check it before allocating writing effort across the technical offer.

In competitive markets, the 70-point threshold functions as a floor, not a target. When ten experienced organisations are bidding, several will score in the 70 to 79 range, a few in the 80s, and differentiation happens at the margin. Bids that win consistently tend to score in the upper 70s to mid-80s on technical, with a competitive but not necessarily lowest financial offer.

A bid that scores 85 or above on technical is in a strong position almost regardless of reasonable price variation. Reaching that band reliably requires a well-structured methodology, CVs matched precisely to the evaluation grid's preferred criteria, and a quality assurance narrative that addresses the contracting authority's specific concerns. These are not arbitrary stylistic choices; they are directly linked to the score.

Standstill period and debriefing rights

Under PRAG procedures, the contracting authority notifies all tenderers of the award decision simultaneously. The notification states the name of the recommended contractor, the scores of all technically qualified bids broken down by criterion, and the reasons for the decision. The standstill period then begins: a minimum of 10 calendar days from the award notification during which no contract may be signed.

The standstill period exists to allow unsuccessful tenderers to challenge the award before the contract becomes legally binding. Challenges are submitted to the contracting authority or, in appropriate cases, to the competent administrative review body. Grounds for challenge are typically: procedural breach, non-compliance with the published evaluation criteria, or manifest error in the evaluation. A challenge that simply disputes the score without identifying a procedural or legal basis will not succeed.

Separately from any challenge, unsuccessful tenderers have the right to request a debrief. A debrief should provide:

• Your bid's score against each criterion and sub-criterion.
• The winning bid's scores against each criterion.
• Written observations from the evaluation committee on the strengths and weaknesses of your offer.

Request a debrief on every unsuccessful bid, regardless of how close or how far the result was. The feedback provides direct evidence of where the next bid needs to improve. Systematic debrief analysis is one of the simplest ways to improve scores over successive submissions. If the contracting authority does not provide observations automatically, request them explicitly. Under the Financial Regulation and PRAG, you are entitled to them.

For EU procurement advisory purposes, tracking debrief feedback across multiple bids against the same contracting authority also reveals scoring patterns: which criteria the authority consistently values, what level of specificity they expect in the methodology, and whether their preferred criteria for key experts are materially different from their stated minimums. That information has direct value when writing the next offer.

Frequently asked questions