{"id":50241,"date":"2026-11-13T06:28:11","date_gmt":"2026-11-13T04:28:11","guid":{"rendered":"https:\/\/nexuswelt.com\/?p=50241"},"modified":"2026-11-04T20:20:41","modified_gmt":"2026-11-04T18:20:41","slug":"horizon-europe-consortium-gap-review","status":"publish","type":"post","link":"https:\/\/nexuswelt.com\/de\/horizon-europe-consortium-gap-review\/","title":{"rendered":"Consortium Gap Review: What Evaluators Will Miss Before You Submit"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Evaluators will not tell you what your consortium is missing before you submit. They assess proposals as submitted and are instructed not to recommend changes such as a different consortium composition, so any gap in capability, ownership or evidence simply shows up as a lower score. The deadline is the last point at which the consortium can still close it.<\/p>

This article is for coordinators and grant offices with a consortium core and a selected topic, typically some weeks before the deadline. It does not cover finding partners, which is the subject of our article on consortium strategy and partner search<\/a><\/u><\/span>. It covers testing whether the partners you already have can credibly deliver the proposed work.<\/p>

Eligible is not the same as capable<\/h2>

Formal eligibility<\/b> is a fixed check. Unless the topic says otherwise, a collaborative action needs at least three independent legal entities as beneficiaries: at least one in an EU Member State and at least two others, each in a different Member State or Associated Country. Topics can add conditions. A consortium either meets them or it does not.<\/p>

Implementation quality<\/b> is an expert judgement under the criterion “Quality and efficiency of the implementation”. It covers the work plan, risk assessment, the effort assigned to work packages and the resources overall, and the capacity and role of each participant and whether the consortium as a whole brings together the necessary expertise. Operational capacity is assessed within this criterion, based on the competence, experience and resources of each participant.<\/p>

Passing the first test says nothing about the second. Partner names and countries are not evidence that the work can be delivered, and a particular geographical spread does not by itself raise a score. Where a topic sets conditions on participant types, countries or widening participation, they apply to that topic only.<\/p>

Start from expected outcomes and planned work<\/h2>

Run the review in one direction, from what the project must deliver to who delivers it and how that is shown:<\/p>

  1. List the topic’s expected outcomes and specific conditions, such as participant types, TRL, pilots, end-user involvement or access to data and infrastructure. These vary between calls, so check the topic text.<\/li>
  2. List the work packages with their main tasks, deliverables and milestones.<\/li>
  3. Name the capability each item requires.<\/li>
  4. Only then look at the partners: who is assigned, and what in the proposal shows they can do it.<\/li><\/ol>

    The evidence has fixed places in the proposal. Section 3.1 holds the work plan, including deliverables, milestones, critical risks and staff effort, which must match the budget. Section 3.2 asks how the members complement one another and requires each participant to have “a valid role, and adequate resources in the project to fulfil that role”, including any affiliated entities and associated partners. Part A carries each participant’s researchers, relevant publications or achievements, previous projects and infrastructure.<\/p>

    Five potential consortium gaps<\/h2>

    These categories organise a review. None is an automatic evaluation failure; whether a gap matters depends on the topic and the proposed work.<\/p>

    1. Missing technical or interdisciplinary expertise.<\/b> A task requires a method or discipline no partner can evidence, or depends on one person with no backup.<\/li>
    2. Weak work package ownership and dependencies.<\/b> A work package has no lead with the capacity to run it, effort is spread too thinly, or a critical dependency has no owner and no risk measure.<\/li>
    3. Insufficient end-user, pilot-site or validation capacity, where needed.<\/b> The project claims validation in a relevant or operational environment, but no partner controls the site, data or users. Check first whether the topic calls for this at all.<\/li>
    4. Missing exploitation, stakeholder engagement or uptake capability.<\/b> The Impact section describes routes to users or markets that no partner has the role, relationships or resources to pursue.<\/li>
    5. Commitments that are not convincingly supported.<\/b> Effort, budget, equipment or access are claimed but do not appear in the effort table, the budget or the partner descriptions, or a partner has not confirmed its contribution internally.<\/li><\/ol>

      A consortium capability matrix<\/h2>

      The rows below are illustrative<\/b>, for a fictional project. They show the format, not real evaluation findings.<\/p>

      \"\"<\/p>

      Expected outcome or task<\/span><\/span><\/p><\/td>

      WP<\/span><\/span><\/p><\/td>

      Required capability<\/span><\/span><\/p><\/td>

      Assigned partner<\/span><\/span><\/p><\/td>

      Evidence<\/span><\/span><\/p><\/td>

      Gap or risk<\/span><\/span><\/p><\/td>

      Corrective action<\/span><\/span><\/p><\/td>

      Owner, deadline<\/span><\/span><\/p><\/td><\/tr><\/thead>

      Illustrative:<\/i> validate prototype on an industrial line<\/span><\/span><\/p><\/td>

      WP4<\/span><\/span><\/p><\/td>

      Access to a production line and operators<\/span><\/span><\/p><\/td>

      Partner C (research institute)<\/span><\/span><\/p><\/td>

      Lab facilities only<\/span><\/span><\/p><\/td>

      No partner controls an industrial site<\/span><\/span><\/p><\/td>

      Check whether an industrial beneficiary can host; otherwise recruit a host or reduce the validation claim<\/span><\/span><\/p><\/td>

      Coordinator, week 2<\/span><\/span><\/p><\/td><\/tr>

      Illustrative:<\/i> data pipeline for sensor fusion<\/span><\/span><\/p><\/td>

      WP2<\/span><\/span><\/p><\/td>

      Data engineering at scale<\/span><\/span><\/p><\/td>

      Partner A<\/span><\/span><\/p><\/td>

      Two relevant projects in Part A<\/span><\/span><\/p><\/td>

      Single named expert<\/span><\/span><\/p><\/td>

      Name a second team member and add effort<\/span><\/span><\/p><\/td>

      Partner A lead, week 1<\/span><\/span><\/p><\/td><\/tr>

      Illustrative:<\/i> exploitation plan for key results<\/span><\/span><\/p><\/td>

      WP6<\/span><\/span><\/p><\/td>

      Market analysis and route to users<\/span><\/span><\/p><\/td>

      Not assigned<\/span><\/span><\/p><\/td>

      None<\/span><\/span><\/p><\/td>

      No owner<\/span><\/span><\/p><\/td>

      Assign to the industrial partner with D&C support; add tasks and effort<\/span><\/span><\/p><\/td>

      WP6 lead, week 2<\/span><\/span><\/p><\/td><\/tr>

      Illustrative:<\/i> regulatory compliance check<\/span><\/span><\/p><\/td>

      WP5<\/span><\/span><\/p><\/td>

      Sector-specific regulatory expertise<\/span><\/span><\/p><\/td>

      Partner B<\/span><\/span><\/p><\/td>

      General legal office<\/span><\/span><\/p><\/td>

      Expertise not sector-specific<\/span><\/span><\/p><\/td>

      Clarify scope; consider a justified subcontract for a bounded task<\/span><\/span><\/p><\/td>

      Partner B, week 3<\/span><\/span><\/p><\/td><\/tr><\/tbody><\/table><\/div>

      Use one row per expected outcome or major task. An empty evidence cell is the most useful finding the matrix can produce.<\/p>

      What to do when a gap is found<\/h2>

      Each option is subject to the applicable rules, and none automatically fixes an eligibility or implementation weakness.<\/p>

      Option<\/span><\/span><\/p><\/td>

      When it can help<\/span><\/span><\/p><\/td>

      Constraints<\/span><\/span><\/p><\/td><\/tr><\/thead>

      Strengthen an existing beneficiary’s role<\/span><\/span><\/p><\/td>

      The capability exists but was under-described or under-resourced<\/span><\/span><\/p><\/td>

      Effort and budget must match; evidence must be real<\/span><\/span><\/p><\/td><\/tr>

      Recruit a new beneficiary<\/span><\/span><\/p><\/td>

      A capability central to the work is genuinely missing<\/span><\/span><\/p><\/td>

      Eligibility, validation, budget redistribution and time to agree roles<\/span><\/span><\/p><\/td><\/tr>

      Involve an associated partner<\/span><\/span><\/p><\/td>

      An organisation can contribute tasks, sites or access without funding<\/span><\/span><\/p><\/td>

      Cannot charge costs; key Grant Agreement obligations must apply to it; describe it in section 3.2<\/span><\/span><\/p><\/td><\/tr>

      Subcontract<\/span><\/span><\/p><\/td>

      A bounded, non-core task can be bought from a third party<\/span><\/span><\/p><\/td>

      Core tasks should not be subcontracted; justify per participant; best value for money and no conflict of interest<\/span><\/span><\/p><\/td><\/tr>

      Redesign the task<\/span><\/span><\/p><\/td>

      The gap cannot be closed in time<\/span><\/span><\/p><\/td>

      The work must still address the topic’s expected outcomes<\/span><\/span><\/p><\/td><\/tr><\/tbody><\/table><\/div>

      The rules also allow operational capacity to be shown, exceptionally, through concrete measures to obtain the competence by the time the tasks start, such as planned recruitment. That does not replace capability the project needs from day one.<\/p>

      Prioritising gaps<\/h2>

      Use explicit criteria, not a score:<\/p>