What EU procurement evaluators actually read — and in what order

Who evaluates EU proposals: committee structure

Under PRAG procedures, evaluation is carried out by an evaluation committee. For open competitive procedures, the committee must include an odd number of voting members — minimum three — to allow majority decisions where consensus cannot be reached. A non-voting chairperson manages the process: recording scores, managing timekeeping, and ensuring procedural compliance. The chairperson does not score.

Evaluators are typically subject-matter experts, though they are not always specialists in the precise sector of the contract. They may be Commission or Delegation staff, independent experts contracted for the evaluation, or in some cases academic or technical reviewers. Their task is to apply the evaluation grid to the proposal, not to judge whether the proposed approach is optimal by their own professional standards. A technically excellent approach that is poorly evidenced in the proposal will score lower than a more conventional approach that is clearly and fully documented against the grid criteria.

Some evaluations also include a non-voting observer, typically from an oversight or anti-fraud function within the contracting authority. The observer monitors procedural compliance and can flag concerns but does not influence scores.

For grant applications managed through the EU Funding and Tenders Portal (Horizon Europe and similar), the evaluation structure is similar but may include external experts drawn from a published database, with names disclosed post-evaluation. For INTPA and NEAR service contracts, evaluator identities are not disclosed.

How evaluators are briefed

Before the evaluation begins, each evaluator receives a briefing pack that includes the evaluation grid with all sub-criteria and their assigned maximum scores, the terms of reference, a reading guide or marking guide explaining the indicators for each score band, and a declaration of absence of conflict of interest relative to the bidders. Evaluators sign the declaration before they can proceed; any evaluator with a conflict is replaced.

The evaluation grid is the evaluator's primary tool throughout the reading. It defines exactly what must be demonstrated in each section, what evidence counts as sufficient, and how the score bands are calibrated. Good proposals are written to the grid. Proposals that do not follow the grid's logic — presenting information in a different structure, omitting required evidence, or placing relevant content in sections where the evaluator is not scoring for it — create unnecessary difficulty that costs points.

The marking guide typically defines score bands in terms of whether the proposal is absent, insufficient, partially satisfactory, satisfactory, or excellent on each element. The language varies by procedure, but the principle is consistent: scores are awarded for demonstrated evidence, not for claimed capability. "Our team has extensive experience in X" scores poorly against "Our team managed X in context Y, delivering Z, as evidenced by contract reference [name, client, value, dates]."

What evaluators read first

Evaluators are instructed to read proposals individually and completely before scoring. In practice, the reading follows a consistent pattern shaped by the evaluation structure.

First: table of contents and proposal structure

Before reading the body, evaluators review the table of contents to understand how the proposal is organised. A table of contents that maps directly to the evaluation sub-criteria allows the evaluator to locate the relevant section for each scoring element without searching through the document. A proposal whose sections are labelled to match the evaluation criteria exactly makes the evaluator's job easier from the first page — and that ease translates into fewer missed scoring points.

Second: executive summary

The executive summary is read before the main body. It is typically not a separately scored section, but it sets the frame through which the evaluator reads everything that follows. An executive summary that accurately signals the methodological approach, the key team, and the understanding of context gives the evaluator a reference point for confirming detail in the scored sections. A generic summary — describing the firm's credentials rather than the specific assignment — gives no such reference and leaves the evaluator to form their own first impression from the scored sections without guidance.

Third: key expert CVs

CVs are often read early, even before the methodology, because they directly determine whether the proposal passes minimum qualification checks. Evaluators identify the key expert requirements in the terms of reference and cross-reference them against each CV before moving further. A proposal that does not clearly evidence the minimum qualifications for a key expert can be excluded at this stage, regardless of methodology quality.

Then: the scored sections in order

Evaluators work through the scored methodology, organisation, and work plan sections in sequence, applying the evaluation grid to each. They annotate directly against the sub-criteria, noting what evidence is present, what is absent, and a provisional score. These individual scores are recorded before the consensus meeting.

How scoring works: individual, consensus, moderation

PRAG evaluation follows a three-stage process: individual scoring, consensus, and where necessary, moderation by the contracting authority.

Individual scoring

Each evaluator scores the proposal independently, recording a score for each sub-criterion with a written justification. Individual scores are completed without discussion with other committee members. The independence requirement is strict: evaluators cannot compare notes or discuss proposals before their individual scores are finalised.

Consensus phase

After individual scoring, the committee meets to compare scores. Where scores diverge significantly, evaluators discuss the relevant section and arrive at a consensus score. The consensus score is the official recorded score for that sub-criterion and may differ from all of the individual scores. The consensus meeting is where a strong individual score can be pulled down if another evaluator's concerns are substantive enough to shift the group position.

The consensus discussion focuses on what the proposal actually says, not on what the firm's general reputation is. Evaluators cannot award marks for work or experience not evidenced in the proposal itself. If the consensus meeting surfaces an ambiguity in the proposal — a section that can be interpreted in two ways — the committee will typically score conservatively.

Moderation

Where the committee cannot reach consensus on a score, a moderator from the contracting authority may facilitate. The moderator can propose a resolution but cannot impose a score. If the committee remains unable to agree, the lower score typically prevails as a risk-conservative default. Moderation situations are more common where the evaluation grid is ambiguous or where the proposal is at the boundary of the scoring band definitions.

The evaluation report

The consensus scores are compiled into an evaluation report, signed by all committee members, and submitted to the contracting authority for the award decision. The contracting authority reviews the report for procedural compliance and may query the committee on specific scoring decisions, but it cannot change scores. The award decision follows the ranking produced by the evaluation report.

Common reasons proposals get low scores

The failure patterns in EU technical proposals are consistent across procedures and sectors. Most are avoidable.

Generic methodology not anchored to the specific terms of reference

Evaluators score proposals against the specific sub-criteria in the grid for this call, not against abstract consulting methodology standards. A methodology section that describes the firm's standard approach to similar work without demonstrating how that approach addresses the specific challenges, context, and deliverables in the ToR will score in the middle of the band at best. The highest scores go to proposals that engage with the ToR directly: acknowledging the specific challenges identified, referencing the stated outputs and indicators, and explaining why the proposed approach is appropriate for this context specifically.

CVs that claim experience without evidencing it

Evaluators apply the minimum qualification thresholds exactly as stated. A CV that states "15 years of experience in governance and public sector reform" without providing dated project references that account for those 15 years will not receive credit for the full period. Evaluators count verifiable years from the project references provided. A CV that lists roles without dates, or project references without scope or client information, is unscoreable on the experience sub-criterion.

The standard for EU technical proposals: for every year of relevant experience claimed, there should be a verifiable reference in the CV that accounts for it. The reference should include client name, assignment title, dates (start and end), and a brief description of the evaluator's personal role and the outputs delivered.

Work plans without a critical path or risk register

EU service contract ToRs almost always require a work plan covering the implementation timeline, phase structure, resource allocation, and identification of key risks with mitigation measures. Work plans that present a list of activities with indicative dates but no dependency logic, no identification of which activities are on the critical path, and no risk assessment score poorly on the organisation and planning sub-criteria. These sections are explicitly scored in most evaluation grids, and a weak or absent response is a direct score loss regardless of the methodology quality.

Logical framework disconnected from the methodology

Many EU external action ToRs require a logical framework (logframe) or results framework as part of the technical proposal. A logframe that lists outputs and outcomes not traceable to the proposed activities, or that copies the logframe from the ToR without adapting it to the specific approach, signals that the team has not integrated the results framework into their thinking. Evaluators compare the logframe to the work plan and methodology; inconsistencies are noted and scored down.

Budget narrative inconsistent with the technical proposal

The financial proposal is evaluated separately from the technical, but evaluators who note a significant inconsistency between a very lean budget and a methodology that proposes extensive field work, multi-country presence, or large key expert input can flag this in the evaluation report. Consistency between technical and financial components matters, particularly for complex assignments where the budget envelope is a plausibility signal.

The minimum threshold rule

Every EU service contract evaluation has a minimum technical score threshold. Proposals that score below this threshold are excluded from further evaluation. Their financial envelopes are not opened. The contracting authority does not negotiate with technically failing proposals; exclusion is automatic.

The threshold is stated in the procurement documents. For INTPA and NEAR service contracts, it is commonly 70 points out of 100, though calls with highly selective quality requirements sometimes set it at 75 or 80. Some calls also set sub-thresholds: a minimum score for individual sub-criteria, meaning that a proposal can fail even if its total score is above the overall threshold if it falls below the sub-criterion floor.

The practical implication is significant. A proposal that scores 69 out of 100 technical points is excluded entirely from the financial comparison, regardless of how competitive its price might be. The financial proposal is treated as unsubmitted. No ranking, no feedback on price position, no award consideration. This is why proposals that are structurally sound but under-evidenced on one or two sub-criteria are commercially high-risk: the aggregate score may fail the threshold even where most sections score well.

What debriefing reveals about evaluator priorities

Unsuccessful tenderers under PRAG procedures can request a debrief. The request must be made within 15 days of receiving the notification of rejection. The contracting authority will provide your scores per sub-criterion and the successful tenderer's scores for comparison, allowing a direct gap analysis by section.

Debrief data is the most reliable source of information about what the evaluation committee actually scored and where points were lost. Common patterns revealed by debriefs:

• Methodology gaps: proposals frequently score lower than expected on methodology sub-criteria because evaluators found the approach generic or insufficiently tailored to the ToR. High total score on key experts but low score on methodology is the single most common gap pattern in mid-range proposals.
• Key expert sub-criterion failures: where the ToR specified a minimum experience threshold (e.g. "lead expert must have a minimum of ten years in public finance management"), proposals that submitted a candidate with nine years of evidenced experience failed that sub-criterion entirely and could not recover the score elsewhere.
• Work plan and risk: consistently underscored when the work plan is presented as a timeline chart without accompanying narrative on dependencies, resource intensity at each phase, and specific risks tied to the context of the assignment.
• Cross-proposal score gaps: the difference between the winning proposal's score and the next-ranked is often smaller than expected — commonly 5 to 10 points out of 100. Proposals that lose by a narrow margin on one or two sub-criteria represent avoidable losses. Debrief identifies exactly which sub-criteria closed the gap.

Use debrief feedback systematically. Record the scores, identify which sub-criteria underperformed, trace them back to the specific passages in the proposal, and update your templates and guidance accordingly before the next submission. For support in reviewing debrief feedback and restructuring proposal templates, see our EU bid writing services or get in touch.

For a structured approach to deciding which tenders to bid on in the first place, see our guide on when to walk away from an EU tender.

Frequently asked questions