How an EU research project works: consortium and deliverables
Almost everything a reader can learn about the programmes on this site comes from an EU research project grant record and the documents around it. Knowing what each document is for is most of knowing what it can be trusted to say.
The call, and what it determines
An EU research project begins with a call: the Commission publishes a topic, a budget range, a set of expected outcomes and a deadline. Consortia form to answer it, and the shape of the call largely determines the shape of what gets built — a topic written around unmanned platforms produces proposals about unmanned platforms, whether or not that is the best answer to the underlying problem.
This matters for reading the record. The objectives recorded against a project are the applicants' account of what they intended, written to satisfy a call, at the point of maximum optimism. They are a reliable statement of intention and a poor guide to outcome, and the distance between the two is not evidence of bad faith. It is what proposals are.
The consortium, and why it looks the way it does
A consortium is the set of organisations jointly holding the grant. In the border surveillance programmes profiled in the dossiers the mix is consistent: a research institute coordinating, one or two large industrial partners, several small specialist companies, a university, and — importantly — access to the eventual users, usually as an advisory board rather than as partners.
Three forces shape that composition. The work genuinely needs several disciplines. Calls require participation across member states, so geography enters the design. And a proposal has to demonstrate a route to the people who would use the result, which is why end-user advisory boards appear so consistently. The result is a structure that is partly engineering and partly an artefact of the funding instrument.
What the grant record shows is membership. What it almost never shows is the internal split of the budget, which is why totals can be quoted from these documents and shares cannot.
Work packages and deliverables
The work is divided into numbered work packages, each with a lead partner, and each producing numbered deliverables on a schedule. A deliverable can be a report, a specification, a piece of software, a prototype, a workshop or a website. Each is marked public or confidential.
| It establishes | It does not establish |
|---|---|
| Something was produced and submitted on a date | That it works |
| Which partner led it | That anyone outside the consortium assessed it |
| Its dissemination level as declared | That a "public" one was ever actually posted |
| That the schedule was met, or was not | What was in it, if it is not retrievable |
The third row is the one that repeatedly catches readers, this site included. A deliverable list looks like a library catalogue and is closer to a contractual schedule: it records what was owed, and a proportion of what was owed and marked public cannot be found today. Where a dossier here cites a deliverable, it is one that was actually retrieved.
Reading an EU research project grant record without being misled
- Participants, budget, dates and grant number: authoritative, quote them as they stand
- Objectives: the applicants' intentions at proposal stage, not achievements
- Reported results: written by the consortium about its own work
- Absence of a follow-on: means nothing on its own — procurement is recorded elsewhere, or nowhere
The last point is worth holding onto, because it is where most readers, seeing a programme that ends at a demonstration, supply a conclusion the record does not contain. A framework programme is designed to end there. What happened next is a national decision that leaves its trace in a different system, if it leaves one at all — from prototype to deployment takes that apart.
Two more documents in an EU research project are worth knowing about, because their names sound more conclusive than they are. A periodic report in an EU research project grant record is the consortium's own account of a reporting period, and a review is the assessment of it by experts appointed for the purpose. A positive review means the work was found to be progressing against the grant agreement. It is not a technical validation of the system, not an assessment against anything outside the project's own objectives, and not a recommendation that anybody buy the result. Where a dossier here records that a project was reviewed positively, it means exactly that and nothing more.
Sources for this page
- Model and annotated grant agreements, dissemination levels and reporting obligations: Reference Documents on the EU Funding and Tenders Portal — European Commission
- Grant records, participants, budgets and reported results: CORDIS — European Commission
- The framework programme in force for the current generation of projects: Regulation (EU) 2021/695 establishing Horizon Europe, laying down its rules for participation and dissemination — EUR-Lex
- The framework programme under which the older projects on this site ran: Decision No 1982/2006/EC concerning the Seventh Framework Programme (2007–2013) — EUR-Lex
Where the annotated grant agreement and a project's own account of itself differ, the grant agreement is treated as authoritative: it states what was owed, while the project's account states what the consortium says it did.
Questions about EU research projects
What is an EU research project, formally?
A set of organisations holding one grant agreement with the European Commission, undertaking defined work over a defined period for a defined sum. Everything else — the consortium, the work packages, the deliverables, the reviews — is machinery for managing that single contract.
What does a deliverable actually guarantee?
That the consortium produced something and submitted it. Not that it works, not that it was assessed independently, and not — even when marked public — that it was ever posted anywhere a reader can reach. Treating a deliverable list as a library is the most common error in reading these programmes.
How reliable is a grant record?
Authoritative for what was agreed: participants, budget, dates, objectives. Silent on whether any of it worked. Its objectives are written by the applicants at proposal stage and describe intentions, so quoting them as achievements — which happens constantly — reverses what the document is.
Why does a consortium include so many organisations?
Partly because the work genuinely needs several disciplines, partly because calls require participation across member states, and partly because a consortium is how a proposal demonstrates it can reach end users. The composition is a product of the funding instrument as much as of the engineering.