Author: Julien Sudre, Horizon Europe Grant Writing and Project Management Specialist, founder of Grant360 and Innotrope
Managing a Horizon Europe project requires more than delivering research and innovation activities. Coordinators and beneficiaries must establish effective governance, monitor progress, manage financial and contractual obligations, document results, and prepare for European Commission reviews throughout the project lifecycle.
The most effective approach is to treat project management as a continuous process rather than a series of administrative tasks triggered by reporting deadlines. This guide provides a practical roadmap from Grant Agreement signature to the final review, combining the Horizon Europe contractual framework with operational recommendations.
What should coordinators do immediately after signing the Grant Agreement?
The first priority is to translate the Grant Agreement (GA) into an operational management plan. Review contractual commitments, confirm each beneficiary's responsibilities, establish the reporting calendar, and prepare internal procedures before project activities accelerate.
The GA establishes the legal framework. Annex 1, the Description of Action (DoA), defines the work to be implemented, while Annex 2 sets out the estimated budget. Both should become everyday management references.
How do you turn contractual commitments into a management checklist?
Extract project dates, reporting periods, deliverable deadlines, milestones, Work Package (WP) responsibilities, task dependencies, budget allocations, payment arrangements, communication and dissemination commitments, and ethics, security, data protection and open-science obligations. Assign an owner, deadline, expected evidence and validation process to each commitment.
For example, if a prototype must be validated by month 18, the plan should identify when testing begins, which partners supply inputs, who validates the results and when the deliverable must be ready for internal review.
How do you establish the project calendar?
Create one calendar covering scientific activities, contractual obligations and consortium meetings. Distinguish official deadlines from earlier internal deadlines: a deliverable due in month 12 might have an internal draft deadline in month 11 to allow for review. Such internal deadlines are management recommendations, not additional Commission requirements.
How should you organise the kick-off meeting and consortium governance?
The kick-off meeting should establish a shared understanding of objectives, responsibilities, decision-making procedures and working methods. It should produce concrete decisions rather than simply repeat the proposal.
What should the kick-off meeting cover?
Discuss objectives and expected results, the implementation calendar, WP responsibilities, governance, financial management, reporting, and communication and dissemination. Agree on document exchange, progress monitoring and deliverable validation procedures. End with an action list identifying owners and deadlines.
How should governance responsibilities be distributed?
Typical governance responsibilities include:
- General Assembly: consortium-level decisions under the agreed governance rules.
- Steering Committee: operational monitoring and coordination of major activities.
- Project Coordinator: overall coordination, contractual interface and formal submissions.
- Work Package Leaders: monitoring activities, deliverables, risks and partner contributions.
- Advisory Board, where relevant: external scientific or strategic advice.
The exact structure depends on the project and should be reflected in the Consortium Agreement (CA). Establish escalation procedures: a technical disagreement might first go to the WP leader and then, if unresolved, to the Steering Committee.
For further guidance, see The Coordinator in Horizon Europe: Leadership, Diplomacy and Operational Mastery.
How can you monitor project progress and risks throughout implementation?
Monitor activities, deliverables, milestones, resources and risks regularly against the DoA. The purpose is to identify deviations early enough for corrective action, not merely to report delays.
What monitoring cycle should you establish?
A practical approach might combine monthly WP meetings, quarterly Steering Committee reviews and consortium-wide meetings every six months. Adapt these intervals to the project's size and complexity. Each meeting should identify achievements, delays, decisions, action owners and deadlines; record decisions in written minutes.
Which indicators should you track?
Useful internal indicators include:
- Deliverables submitted on time: implementation-calendar compliance.
- Milestones achieved: progress towards objectives.
- Overdue corrective actions: follow-through on management decisions.
- Budget consumption against planned activities: alignment between spending and implementation.
- Risks requiring intervention: technical, financial and organisational exposure.
These are suggested internal indicators, not a mandatory Commission dashboard. A project may submit every deliverable on time while experimental work is delayed; combine contractual indicators with operational evidence.
How should you maintain the risk register?
For each risk, record likelihood, consequences, responsible partner, mitigation, status and corrective actions. If equipment delivery is delayed, assess affected activities, alternative facilities and implications for contractual milestones. Update reporting information as appropriate and assess whether the Project Officer should be informed.
How should you manage continuous reporting in Horizon Europe?
Update continuous reporting throughout implementation as activities take place and results become available. The European Commission's Funding & Tenders Portal provides the electronic environment for deliverables and project information.
What information should be updated regularly?
Depending on the action and grant requirements, maintain information on deliverables, milestones, risks, publications, datasets, communication and dissemination, exploitable results, intellectual property and progress towards relevant objectives and indicators. Verify the reporting fields applicable to your grant.
How can you avoid reporting backlogs?
Assign each category to an owner and establish an internal update schedule. For example, WP leaders can provide monthly progress updates while the communication team maintains an activity log with dates, audiences and supporting evidence. Review consistency periodically rather than reconstructing a year of activity before the reporting deadline.
Read our dedicated guide: Continuous Reporting: Your Best Ally to Avoid Last-Minute Panic.
How should you prepare and submit periodic reports?
Periodic reporting demonstrates achievements during the reporting period, explains deviations and provides the required financial information. Use the reporting periods and deadlines specified in your own GA.
What should the technical report contain?
Part A draws on structured Portal information. Part B explains work performed, progress towards objectives, achievements, deviations and corrective measures. Answer three questions: what was promised, what was achieved with evidence, and what deviations occurred and how were they addressed?
For example, describe a prototype's demonstrated performance, validation conditions and remaining limitations rather than simply claiming it was developed. Distinguish completed achievements from work still in progress.
How should financial reporting be organised?
Each beneficiary prepares its financial statement under the applicable funding model and grant eligibility rules. For actual-cost grants, maintain accounting records and supporting evidence and explain resource use where required. Set internal deadlines for preparation and validation. Compare spending with technical progress: rapid personnel-budget consumption alongside limited task completion merits investigation but does not automatically indicate ineligible expenditure.
When is a Certificate on the Financial Statements required?
A Certificate on the Financial Statements (CFS) is required when the applicable threshold and other conditions in the GA are met. For standard Horizon Europe actual-cost grants, the usual threshold is €430,000 in requested EU contribution based on actual costs and, where applicable, average personnel costs, subject to the specific grant rules. It is not simply a threshold based on total project expenditure. The certificate is generally submitted with the final financial report when required. Verify the signed GA and applicable guidance.
How should you manage project finances and payments?
Connect the contractual budget, actual expenditure, technical progress and cash-flow needs throughout implementation. Monitor consortium-level finances and beneficiary information.
How are payments organised?
Under standard arrangements, the Commission provides pre-financing, interim payments where applicable and a final payment following the relevant reporting and assessment procedures. Amounts, schedule and limits depend on the GA. The coordinator receives payments on behalf of the consortium and distributes funds in accordance with applicable contractual arrangements.
How can you maintain financial control?
Compare each beneficiary's budget, reported expenditure, forecast expenditure and progress. Monitor subcontracting, procurement, personnel costs and other relevant categories. Low spending early on may be consistent with an expensive final-year experiment; rapid spending without matching technical progress may call for corrective action. The aim is alignment, not a constant spending rate.
When does a Horizon Europe project require a Grant Agreement amendment?
A formal amendment is required when a proposed change affects contractual elements that cannot be modified within the flexibility permitted by the GA. Not every operational adjustment requires an amendment.
Which changes may require an amendment?
Examples include extending the contractual duration, adding or removing a beneficiary, changing contractual activities, deliverables or milestones, and budget or implementation changes outside permitted flexibility. Certain budget transfers may be possible without amendment; minor internal meeting changes would not normally require one unless they affect a contractual obligation.
What should you do before requesting an amendment?
Assess the change, justification and effects on objectives, budget, timeline and beneficiaries. Discuss the approach with the Project Officer and follow consortium decision-making procedures. Where required, initiate the formal amendment through the Funding & Tenders Portal and follow the review and electronic signature process. Submission of a request does not itself authorise the change.
How should you prepare for project reviews?
Consolidate evidence of technical progress, assess deviations and show how implementation challenges are being addressed. The timing and format of reviews depend on the project and applicable monitoring arrangements.
What evidence should be available?
Prepare deliverables, milestone evidence, technical results, demonstrations, risk-management information and updated plans. Explain objectives, achievements, remaining challenges and next steps. A diagnostic-technology project, for example, could present validation results, prototype demonstrations and remaining deployment steps, clearly distinguishing demonstrated results from expected outcomes.
How should you address delays or deviations?
Explain causes, consequences and corrective measures transparently. If clinical validation is delayed by recruitment difficulties, describe the original plan, actual recruitment, knock-on effects and specific remedies rather than presenting a revised timeline without a feasible plan.
How should you prepare for the final review and project closure?
Demonstrate completion of contractual activities, submit required final reports and deliverables, and clarify how results will be managed after EU funding ends. Start closure preparation early enough to resolve outstanding obligations.
What should be completed before the project ends?
Verify all deliverables and milestones, technical and financial information, and outstanding commitments. Consolidate research results, publications, datasets, intellectual property, communication and dissemination records. Where applicable, update the Data Management Plan (DMP) and the Plan for Exploitation and Dissemination of Results (PEDR) to reflect final results and continued use.
How can project results remain useful after funding ends?
Assign responsibility for exploiting, maintaining, disseminating or otherwise using results. An open-source platform may need an owner for maintenance, hosting, documentation and support; a commercial technology may need agreed intellectual-property arrangements and market-deployment steps. Align these with the CA and GA.
Does the final review end all project obligations?
No. Record retention, checks, audits, confidentiality and certain results-related obligations may continue after implementation and final payment. Retain supporting documentation for the contractual period and assign responsibility for responding to subsequent requests. See Mastering Horizon Europe Audits: A Complete Integrated Guide for Beneficiaries and Coordinators.
Conclusion: What are the key actions for successful Horizon Europe project management?
Successful management depends on clear responsibilities, continuous oversight and alignment between scientific progress and contractual and financial obligations. From grant signature to final review, coordinators should translate commitments into an operational plan, establish effective governance, monitor progress and risks, maintain reliable reporting and prepare the exploitation and sustainability of results.
The central principle is anticipation: regular monitoring, documented decisions, internal quality checks and continuous reporting help the consortium address problems before they threaten project objectives. For the broader framework, see our Horizon Europe Project Management guide.
About the author
Julien Sudre — Horizon Europe Grant Writing and Project Management Specialist
Julien Sudre specialises in Horizon Europe proposal development, project management and communication. Through his professional activities and the development of Grant 360, he helps research and innovation organisations manage the lifecycle of European collaborative projects, from proposal preparation to implementation and reporting.