How to write an intermediate or final funding report that lands well? Let’s start with the bigger picture.
EU project reporting exists for one reason: To prove to the funder that the money was spent as agreed and that it produced what was promised. Everything else, meaning: The tone, the structure, the vocabulary flows from that. The report writer’s job is to build a credible, evidence-based narrative that connects what happened to what was supposed to happen. And while doing that, adhering to a structure which is easily recognised and followed by the report reader. Most SMEs involved in funded projects aren’t professional report writers though – their reporting load usually falls on whoever has a moment to spare. With predictable consequences for quality and timing.
Here is what you need to know about EU project funding reports in 2026 – and where I can help. My operational background in several industries has prepared me well to spot not only inconsistencies in delivered inputs, but also upcoming bottlenecks in terms of timing.
The EU project landscape is a vast one – Horizon 2020, Interreg, COSME, to name but a few.
My following two sample reports are a fictional case for the Interreg programme (2021–2027). As the term Interreg suggests, this programme is meant to foster cross-border and transnational cooperation between regions. And it is especially relevant, among others, to sustainable tourism projects spanning multiple European countries. Reporting is sent to a Managing Authority (MA), not directly to the Commission. It is a partnership-heavy programme which means, multiple organisations are supposed to be reporting together. With one of the involved organisations acting as main point of contact (aka project lead) and coordinator.
That said, there are some recent developments likely to facilitate the reporting process, too: The Commission has been pushing simplification. The 2025–2027 Horizon work programme for instance explicitly aims to cut administrative burden by 25–35% for SMEs. In practice this means that we can probably expect slightly leaner templates and more proportional reporting for smaller grants. Yet at the same time, there also is growing emphasis on evidence of real-world uptake: Report readers will screen a report for details not just like “we published a guide”, but for more specifics, like “Here’s who used our guide and what they did differently after reading it.” See below the definitions output vs. outcome vs. Impact.
A quick and simple glossary of the main recurrent terms:
- Grant Agreement (GA)
This is the contract between the funder and the lead partner. The reporting period, deliverables, budget and everything else is defined here. The report is always written against the GA. If something changed, you explain why. - Description of Action (DoA)
The approved project plan. What the project said it would do. The narrative report is essentially a structured account of how reality compared to the DoA. - Work Package (WP)
EU projects are divided into thematic chunks called work packages. Each WP has its own objectives, activities, outputs and responsible partners. A typical project might have 4–7 WPs. One is almost always “Project Management”, one “Communication and Dissemination” while the rest covers the actual content work. - Deliverable
A tangible output submitted to the funding entity: A report, a toolkit, a training module, a website. Deliverables have due dates and are tracked. - Milestone
A control point marking that a key stage has been reached. Unlike a deliverable, one does not submit a document. Instead, one simply confirms the deliverable took place; Examples: “The kick-off meeting was held”, “the pilot was completed”. Think of milestones as a synonym for signposts. And see deliverables as “products”.
An important distinction worth to keep in mind here: Outputs vs Outcomes vs Impacts. Not the same thing:
Output: What the project produced (“A training was held”, “a guide was published”)
Outcome: What changed as a result (“10 SMEs adopted sustainable practices”)
Impact: The longer-term effect of the project (“Regional tourism carbon footprint was reduced”)
Funders are increasingly asking for outcomes and impacts to be specified, not just “outputs”. So a common mistake would be writing a report full of outputs and calling it done.
- Periodic Report
An interim report submitted at defined intervals (often every 12–18 months). Covers progress to the respective date. - Final Report
Submitted at project close. Covers the whole project, summarises results and often feeds into a dissemination or legacy document. - Lead Partner / Coordinator
The organisation responsible for consolidating all partners’ contributions and submitting the report
(aka the project “babysitter” since that party has the job to chase after all the other’s input).
The general structure of a narrative funding report
Regardless of the type of programme, the narrative part of an EU project report follows a recognisable logic:
- Executive summary
Brief overview of the period, key achievements, any significant issues - Progress per Work Package
For each WP: What was planned, what was done, what was delivered, any deviations and why these deviations happened - Deliverables and milestones
Status of each (completed / on track / delayed, with explanation) - Impact and dissemination
What has been communicated externally, who was reached, early signs of uptake - Issues and risks
What went wrong or might go wrong and what the project partners are doing about it - Next steps
What is planned for the next period
Also, keep in mind that a project evaluator has to read through many reports. Reason why they will appreciate the golden combination of clarity, specificity and honest acknowledgement of problems (with solutions) – far more than vague positivity or hazy general statements about the achievements of the project. So instead of writing, for example, “we raised awareness”, much better be specific like “The training reached 47 SME representatives across three countries, 82% of whom reported increased confidence in sustainability reporting”.
Based on all this, I have prepared two fictive sample reports: And briefly commented each section in blue font. An interim narrative project report and a final project report. Both documents should give you a clear idea about what would be expected in terms of contents and structure, for this type of EU project.
The financial report runs in parallel but separately – that would be the accountant’s domain.
Download both reports here:
And if your team needs support collecting input, structuring the narrative or writing the report itself — that’s exactly what I do. Get in touch.