{"id":47505,"date":"2026-09-28T09:00:52","date_gmt":"2026-09-28T07:00:52","guid":{"rendered":"https:\/\/nexuswelt.com\/?p=47505"},"modified":"2026-09-20T12:13:50","modified_gmt":"2026-09-20T10:13:50","slug":"eu-project-reporting-deliverables-milestones","status":"publish","type":"post","link":"https:\/\/nexuswelt.com\/de\/eu-project-reporting-deliverables-milestones\/","title":{"rendered":"EU Project Deliverables and Reporting: What You Actually Have to Produce"},"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

Munich, 28 September 2026 \u00b7 Nexuswelt Group<\/span><\/span><\/span><\/p>

Almost everything written about EU funding stops at the moment of award. What happens afterwards – what you have to produce, when, in what system, and who submits it – is learned by most partners in the week before the first deadline.<\/span><\/span><\/p>

It is not complicated, but it has specific mechanics that are easy to get wrong and awkward to fix retrospectively. This is the practical account: the two reporting systems, the difference between deliverables and milestones, how deadlines are counted, and the choices made at proposal stage that you live with for the project’s duration.<\/span><\/span><\/p>

\"Comparison<\/b><\/p>

The relationship between the two is the thing to understand. Continuous reporting is not a preliminary to periodic reporting – it becomes part of it. A consortium that neglects the continuous module all period then faces a periodic report whose Part A is empty and whose evidence has to be reconstructed.<\/i><\/span><\/span><\/p>

Deliverables and milestones are not the same thing<\/b><\/span><\/span><\/span><\/h2>
\u00a0<\/td>Deliverable<\/b><\/span><\/span><\/span><\/td>Milestone<\/b><\/span><\/span><\/span><\/td><\/tr><\/thead>
What it is<\/b><\/span><\/span><\/td>An output of the work – a report, a dataset, software, a prototype description. Tangible or intangible<\/span><\/span><\/td>A control point marking that a defined stage has been reached<\/span><\/span><\/td><\/tr>
What it carries<\/b><\/span><\/span><\/td>A dissemination level<\/span><\/span><\/td>A means of verification<\/span><\/span><\/td><\/tr>
Submitted?<\/b><\/span><\/span><\/td>Yes, uploaded to the Portal<\/span><\/span><\/td>Reported as achieved, not uploaded as a document<\/span><\/span><\/td><\/tr>
Purpose<\/b><\/span><\/span><\/td>Evidence of what was produced<\/span><\/span><\/td>Evidence of progress toward an output<\/span><\/span><\/td><\/tr><\/tbody><\/table>

A useful way to hold it: the milestone is the checkpoint, the deliverable is the thing that passes through it. Both are contractual obligations set out in Annex 1 to the grant agreement – the Description of Action –\u00a0 with the dates you proposed and the Commission accepted.<\/span><\/span><\/p>

Dissemination levels: a proposal-stage choice you live with<\/b><\/span><\/span><\/span><\/h2>

Every deliverable carries a dissemination level, set per deliverable rather than for the project as a whole:<\/span><\/span><\/p>