By Julien Sudre, grant writer and Horizon Europe project manager, founder of Grant360 and Innotrope. Originally published 7 November 2025. Updated: 23 September 2026.
Manage a Horizon Europe project by turning its signed Grant Agreement and Description of Action (DoA) into a workable schedule, clear partner responsibilities, regular decisions and reliable evidence of progress. Track deliverables and milestones, report through the Funding & Tenders Portal, manage costs and risks under the grant's rules, and address material changes before they become reporting problems. The signed agreement governs the particular project; the Commission's Annotated Grant Agreement explains the general rules, and the Funding & Tenders Online Manual describes the main grant management procedures.
This guide draws on the author's experience writing more than a hundred grant applications and managing European projects. It gives coordinators and beneficiaries a practical overview, from kick-off to final reporting. Check your own agreement, funding model, annexes and granting authority's instructions before applying any rule: requirements can differ between actual-cost and lump-sum grants, programmes and individual projects.
What should you do immediately after grant signature?
Translate the DoA into a dated operational plan and verify that every partner can supply the people, facilities, data and access it promised. The DoA, normally Annex 1 to the Grant Agreement, describes the work the consortium undertakes to perform. The European Research Executive Agency (REA) explains that the grant agreement defines the committed work, duration, budget and parties' rights and obligations.
At kick-off, confirm each work package's lead, tasks, deliverables, dependencies and near-term decisions. Agree where authoritative files live, who approves a deliverable, who enters information in the Portal and when unresolved issues are escalated. If a pilot requires access to a hospital dataset, for example, verify the agreement, approvals, responsible personnel and expected date rather than assuming the access promised in the proposal is already available. Put any gap on the risk and action registers immediately.
Our experience of starting new Horizon Europe projects has taught us something: during the kick-off meeting, everybody is enthusiastic and happy to join the initiative, but they also come with many questions, doubts or fears. Most of the participants have not contributed to the grant writing, so the first thing, as a coordinator, is to explain what the project is about, what is expected from everyone, and what the first actions are for the next six months.
Another good practice is to quickly set up your supporting tool, one that can give you quick access to the core information about your project and help you monitor implementation. Check out Grant Planner to learn about such a tool: Grant Planner.
Read next: Key actions in Horizon Europe project management: playbook from Grant Signature to Final Review.
What is the coordinator responsible for?
The coordinator is the consortium's main interface with the granting authority and has specific tasks under the Grant Agreement, including monitoring that the action is implemented properly, collecting information and submitting required reports and deliverables. Each beneficiary still has its own obligations; coordination does not transfer every partner's legal or financial responsibility to one organisation. Check the coordinator and beneficiary provisions in the Annotated Grant Agreement.
In practice, give partners precise requests: which input is needed, in what format, who reviews it and by when. A coordinator might ask a work package leader to confirm whether a pilot milestone has been reached, attach the agreed means of verification and explain a delay's effect on subsequent tasks. This produces a decision-ready update rather than a vague status report. When partners disagree, document the issue, the options, who can decide and whether the grant terms constrain the choice.
Read next: The coordinator in Horizon Europe: leadership, diplomacy and operational mastery.
How should you organise consortium governance?
Use the governance promised in the DoA and the consortium agreement, where applicable, to make timely, traceable decisions. Define who decides scientific changes, budget questions, publication issues, exploitation matters and disputes. A steering committee is useful when its members can resolve issues and commit their organisations; an advisory group helps when its input arrives before the relevant decision.
For a decision to delay a demonstration, record the reason, alternatives considered, effects on deliverables and budget, decision maker and next review date. Work package leaders should then update their task plans and inform affected partners. Meeting minutes need to capture actions and decisions, not a transcript. A shared decision log protects continuity when staff change and helps the coordinator explain the project's evolution at review meetings.
Governance is a practical arrangement shaped by the project and its agreements; no fixed number of committees is required for every Horizon Europe project. If a proposed change affects the Grant Agreement, use the formal amendment procedure described below.
How do you track deliverables, milestones and progress?
Maintain a live schedule of contractual deliverables and milestones, assign an owner and reviewer to each, and collect the evidence needed to show progress. A deliverable is an output listed in the DoA for submission under the grant's terms; a milestone is a defined control point. The Online Manual explains continuous reporting on milestones and deliverables.
For example, if a milestone is "pilot protocol approved," agree in advance whether the means of verification will be an approval letter, meeting decision or final protocol, as specified in the DoA. Check a deliverable's substance against its promised scope before upload. Not every useful internal document is a contractual deliverable, and a milestone is not necessarily a separate public report.
Set an internal review date ahead of the Portal deadline. If work slips, record the cause, revised forecast and effects on later activities; tell the appropriate project contact when required. Continuous reporting should reflect the real state of the project, rather than being completed from memory at the end of a period.
Read next: Continuous reporting: your best ally to avoid last-minute panic.
How do continuous and periodic reporting work together?
Continuous reporting records relevant project information during implementation, while periodic reporting brings together the technical account of progress and the financial information required for a reporting period. The Portal workflows, due dates and payment requests are described in the Online Manual on reports and payment requests. Follow the schedule in your own agreement.
Use the DoA as the reference for the technical report: what was planned, what was achieved, what changed and why, and what follows. Reconcile the narrative with submitted deliverables, milestones, dissemination and exploitation activities and financial information. If a task was delayed, explain its effect on objectives and other tasks, not just that a meeting took place to discuss it.
Maintain an internal reporting calendar with partner deadlines earlier than the Portal's. Each beneficiary should verify its own declarations; the coordinator should check the consortium-level consistency and request clarification where necessary. The Portal is the official submission interface, while internal files provide the supporting working record.
How should you manage the project budget and supporting records?
Start from the project's funding model and signed agreement. For actual-cost grants, beneficiaries must apply the applicable cost eligibility, calculation and record-keeping rules; personnel, purchases, travel, equipment, subcontracting and third-party arrangements can have different conditions. Lump-sum grants follow a different payment logic tied to completed work packages, although beneficiaries still need to perform the work and meet their other grant obligations. Consult the Annotated Grant Agreement and your project's agreement before adopting a cost or evidence procedure.
For an actual-cost purchase, for example, retain the applicable procurement record, invoice and evidence connecting the expense to project work. For personnel, use the calculation and time evidence required by the agreement and the beneficiary's usual practices. Avoid a blanket instruction to collect identical timesheets or depreciate every piece of equipment: the correct treatment depends on the rules and facts of the grant.
Reconcile internal spending forecasts with the tasks being performed. Partners should be able to explain significant variances early, while changes to the grant budget or action must be assessed against the amendment rules. The REA grants and reporting guide points beneficiaries to the governing grant agreement and reporting guidance.
How do you manage risks and changes without losing control of the plan?
Keep a risk and issue register that supports decisions. For a risk, state what might happen, its likely effect, the owner, preventive action and fallback. For an issue, record what has happened, the decision needed and the revised plan. Review major items before milestones and governance meetings, and connect them to the reporting narrative when relevant.
Suppose a pilot site withdraws. The project should assess whether another approved site can deliver comparable evidence, whether the timetable and partner resources must change, and whether the change affects the DoA. It is unsafe to assume that every budget movement needs an amendment, or that a small movement never does: what matters is whether the planned change alters the agreement or falls under flexibility allowed by it. The Online Manual on amendments explains the formal route. Discuss a potential amendment with the responsible project contact in time to avoid implementing an unauthorised change.
An amendment request should state the reason, proposed revised text or figures and consequences for objectives, schedule, partners and budget. Internal minutes document the consortium's decision but do not replace an amendment when the agreement requires one.
How do you keep the project ready for checks and audits?
Retain records that support the action and the information reported under the applicable agreement. Define file ownership, naming conventions, access rights and a handover process so that evidence remains retrievable when staff change. For actual-cost claims, connect declarations to the relevant financial and activity records; for scientific progress, retain evidence of work, deliverable review and decisions. The Annotated Grant Agreement explains record-keeping and checks, audits and reviews, including applicable retention periods.
For example, a beneficiary should be able to retrieve the basis for a declared personnel cost and show how the relevant work relates to the action. A consortium should also be able to locate a dated decision approving a changed pilot schedule. The exact evidence required depends on the grant and the point under review; do not treat one universal folder checklist as a substitute for the agreement.
If an audit or review is announced, read its notice and scope, coordinate the relevant finance, research and legal teams, provide the requested records and examine draft findings within the stated response period. Funding & Tenders Online Manual: checks, audits and reviews.
Read next: Mastering Horizon Europe audits: a complete integrated guide for beneficiaries and coordinators.
How do you handle ethics, data and other project commitments?
Turn the project's approved ethics and security commitments into dated tasks with responsible people and evidence. Where the work involves human participants or personal data, verify approvals, consent arrangements, access controls and any relevant data protection assessment before the activity begins. Consult the ethics requirements and any conditions recorded for your project, alongside the relevant provisions of the Horizon Europe Programme Guide and Grant Agreement.
Distinguish organisational eligibility conditions, such as a Gender Equality Plan (GEP) where applicable, from the integration of a gender dimension into the project's research and innovation content. Other open science, dissemination, intellectual property, communication and visibility obligations should likewise have owners and a place in the schedule. Their application depends on the project and grant terms; a generic assurance in a meeting minute is not evidence of implementation.
For a health study, for instance, check who has authority to begin recruitment, who can access identifiable data and how any publication will protect participants. Record when those decisions are made and update the plan if conditions change.
How should you use the Funding & Tenders Portal during the project?
Use the Portal for the official grant management actions required of the project, including submission of deliverables, continuous and periodic reporting and amendments. Assign the appropriate roles, know who can submit or sign, and reconcile Portal entries with internal records. The Funding & Tenders Online Manual groups the relevant workflows.
An internal task list can show a deliverable as "finished" while the Portal still shows it as unsubmitted. Make both statuses visible to the responsible team, with a final owner for submission. Schedule periodic checks instead of waiting for a reporting deadline. For a more focused walkthrough, read Navigating the Participant Portal without getting lost.
Conclusion: What does effective Horizon Europe project management look like?
It connects contractual commitments to everyday decisions and verifiable progress. The coordinator and beneficiaries know what is due, who is responsible, which risks need a decision, what has changed, and which evidence supports their reports. Establish those routines at kick-off, adjust them to the project's scale and funding model, and use the signed Grant Agreement and official guidance whenever an obligation is uncertain.
If you need a place to organise consortium tasks and responsibilities, see Grant Planner for its current features. Use the project's official agreement and Portal as the authoritative sources for grant obligations and submissions.