Horizon consortia: prove every partner's role, resource and authority

Horizon Europe consortia can look impressive in a logo slide and remain operationally weak. The problem appears when a partner's reputation is not connected to a necessary task, the task is not matched by person-months, or the organisation lacks authority to deliver the decision attributed to it.

The current application forms collect structured participant information, including roles in the project and examples of relevant publications, datasets, software, products, services or other achievements. The technical proposal then asks evaluators to assess the capacity and role of the consortium as a whole.

PRINCEPS recommends four linked tests for every participant. The necessity test asks what would fail or weaken if the partner were removed. The capability test asks what dated evidence proves the organisation and named team can deliver. The resource test asks whether staff, facilities, data, equipment and person-months are sufficient. The authority test asks whether the partner can make, approve or implement the decision assigned to it.

A role should be expressed as an accountable contribution, not a broad label. 'Supports dissemination' is weak. 'Leads engagement with municipal procurement authorities, validates the adoption requirements and owns milestone M6 acceptance evidence' is testable.

Capability evidence should be selective and relevant. A long institutional profile can consume space without proving the exact role. Use recent projects, methods, facilities, datasets, operating mandates, user access or implementation records that directly support the assigned tasks.

Resource coherence requires a partner-level check across the narrative, task descriptions, person-month table, other-cost tables, subcontracting, equipment and travel. A partner cannot be central to field implementation while receiving token effort and no realistic operating cost.

Authority is often the missing dimension. A ministry unit may contribute policy knowledge but not hold approval authority. A university may conduct research but not own the infrastructure needed for deployment. A private partner may reach customers but not control a sector-wide standard. State the real mandate and avoid assigning powers the organisation does not possess.

African participation should be tested on the same basis. If the project depends on African users, data, sites, regulation or uptake, African partners should normally hold corresponding design, evidence, implementation and acceptance roles. Treating them only as recruitment channels or dissemination audiences weakens both credibility and fairness.

The role map should also expose overlaps and gaps. Two partners claiming the same leadership may create conflict, while an unowned function such as data stewardship, exploitation, ethics, standards or post-project maintenance can create a silent failure point.

Before freezing the consortium, run a red-team interview with each work-package leader. Ask for the exact input expected from every partner, the evidence that input is feasible, the named decision owner, the resource basis and the fallback if delivery fails.

Benefits should remain proportionate and transparent. Partners need a credible reason to commit staff and assets, but the proposal should not imply procurement, market access, intellectual-property ownership or future revenue that has not been agreed or supported by the grant framework.

This analysis is strategic and editorial. It does not determine participant eligibility, operational capacity, legal mandate or grant rights. Verify the live topic, General Annexes, Participant Register information, application form, budget rules, Model Grant Agreement and consortium advice before submission.

Editorial note: This is PRINCEPS analysis for general information. It does not replace the official work programme, topic conditions, submission system, grant rules or professional advice specific to an application.