NEVER Add a Consortium Partner You Cannot Justify to an Evaluator

Here is a hypothetical you may recognise. At a conference, a senior figure from a well-known university says, “Count us in.” The name would look excellent on page one. The coordinator agrees on the spot.

Three weeks later, nobody can say what that university will actually do. A task is invented. Budget is found by trimming everyone else. The proposal now carries a partner it has to explain, rather than one that explains itself.

A recognised name is not a work package

Reputation and relevant delivery capacity are different things. A world-leading department may have no experience of the specific method, setting or user group your project needs.

Evaluators do not award points per partner. In Horizon Europe, the implementation criterion assesses the capacity and role of each participant, and whether the consortium as a whole brings together the necessary expertise. A prestigious partner without a clear job is never neutral. It invites the question of what else in the plan is decorative.

Every extra partner has a cost

Within an indicative budget, each additional partner dilutes everyone’s share. It adds coordination effort: more meetings, more reporting, more approvals. It also raises the risk of overlapping responsibilities.

Overlap is easy to spot. When two partners appear to be doing the same job, an evaluator is entitled to ask whether one is redundant, or whether the work plan was built around the partners rather than the project.

The partner who cannot write may be the one you need most

Some essential partners produce weak proposal text. A municipality, a patient organisation or a network of small businesses may lack a grants office altogether.

Do not mistake that for weak value. If they provide access to the people, data or settings your project depends on, they may be the most important organisation in the consortium. Making their contribution visible, specific and credible on the page is the coordinator’s job, not theirs.

Start from the project’s needs: a five-part partner test

Ask what this project must be able to do, and who is best placed to do each part. The project should create the vacancy. The partner should not create the job.

Before confirming any partner, answer five questions in writing:

1. Expertise: what specific knowledge or skill do they bring that the work plan requires?
2. Access: what users, data, sites or networks can they open that others cannot?
3. Responsibilities: which tasks or deliverables will they lead, and which will they support?
4. Resources: is their budget and effort proportionate to those responsibilities?
5. Evidence of commitment: have they agreed their role, their effort and their budget, and named the people who will deliver?

If a candidate fails on expertise and access, the role is probably artificial. If they fail on commitment, the role may be real but the partner is not yet ready.

How to decline diplomatically

Saying no is easier when the reason is the project’s design rather than the organisation’s quality. Explain that the work plan is fully allocated and that adding a partner would create overlap.

Offer a genuine alternative where one exists. A hypothetical reply might read:

“Our work plan is now fully allocated, and adding a further partner would duplicate work package 4. We would value your expertise on our advisory board, and we would like to talk about the next call on this theme, where your group would be a natural lead.”

Experienced organisations tend to respect a coordinator who protects the proposal’s coherence. Many have been on the other side of that conversation.

The rule. Every partner should have a role you could defend in two sentences to someone who has never heard of them. If you cannot, the partner is a liability, however impressive the logo.

Ask yourself about each partner: if you removed this organisation, what essential capability would the project lose? If the honest answer is “nothing”, you already know what to do.