You have signed the Grant Agreement. The project is live. And somewhere on the other side of the table sits the European Commission — represented not by a single contact, but by a team of specialists, each with a distinct role, distinct responsibilities, and a distinct relationship with your consortium.
Most coordinators discover this gradually, through experience. This article explains it upfront: who the Commission-side roles are, what each one does, when they appear in the project lifecycle, and how to work with them effectively.
The agencies behind Horizon Europe
Before understanding the individual roles, it helps to understand the institutional structure. The European Commission does not manage all Horizon Europe projects directly. Most are managed by dedicated executive agencies that act on the Commission’s behalf:
- REA — Research Executive Agency: manages the majority of collaborative research projects under Pillar II
- ERCEA — European Research Council Executive Agency: manages ERC grants
- EISMEA — European Innovation Council and SMEs Executive Agency: manages EIC instruments
- CINEA — European Climate, Infrastructure and Environment Executive Agency: manages projects in climate, energy, and transport
- HaDEA — European Health and Digital Executive Agency: manages health and digital projects
- EACEA — European Education and Culture Executive Agency: manages education and culture programmes
The agency managing your project is specified in the Grant Agreement. All formal communications — report submissions, amendment requests, audit notifications — pass through your assigned agency, not through the Commission’s central departments.
The Project Officer
The Project Officer (PO) is the primary point of contact between the consortium and the Commission throughout the project lifetime. Every funded project is assigned one.
What they do:
The PO monitors the project’s scientific and technical progress. Their core responsibilities include:
- Reviewing and approving technical progress reports submitted at each reporting period
- Assessing whether deliverables and milestones have been achieved as defined in Annex 1
- Raising questions and requesting clarifications when reports are incomplete, inconsistent, or unconvincing
- Authorising the release of payments once reports are approved
- Managing formal communications with the coordinator on operational matters
- Reviewing and processing amendment requests to the Grant Agreement
- Conducting project reviews — either desk-based or on-site — when the project warrants closer scrutiny
What they are not:
The PO is not a project manager. They do not advise the consortium on how to run the project. They do not resolve internal consortium disputes. And they are not an obstacle to be managed — they are a counterpart to be worked with professionally.
How to work with them effectively:
The quality of the relationship with the Project Officer has a tangible effect on how smoothly a project runs. POs manage portfolios of multiple projects simultaneously — they are busy, and they appreciate coordinators who communicate clearly, submit on time, and flag problems proactively rather than hoping they go unnoticed.
The single most important principle is transparency. A coordinator who informs the PO of a significant deviation from the work plan before the reporting deadline — with a clear explanation and a corrective action — is in a fundamentally stronger position than one who tries to present the same deviation as a success in the technical report. POs are experienced at reading between the lines.
The Financial Officer
The Financial Officer is the Commission-side specialist responsible for reviewing the financial dimension of the project. In some agencies and projects, the financial review is conducted by the same person as the PO; in others, it is a distinct role. The Grant Agreement and your agency’s internal structure determine which applies to your project.
What they do:
- Review the financial statements submitted by each beneficiary at each reporting period
- Assess the eligibility of claimed costs against the Grant Agreement rules
- Flag cost items that require clarification, additional documentation, or rejection
- Process the financial aspects of amendments — budget reallocations, changes to the financial structure
- Manage the calculation and release of payments following report approval
- Coordinate with auditors when a financial audit is initiated
What they focus on:
The Financial Officer is looking for costs that are actually incurred, within the project period, necessary for the project, documented, and consistent with the beneficiary’s accounting practices. Any cost that cannot be clearly evidenced against these criteria will be questioned.
In practice, most interactions with the Financial Officer happen at reporting time — when financial statements are submitted and reviewed — and during audits, when the Financial Officer coordinates between the audit team and the consortium. For well-managed projects with clean financial records, the Financial Officer interaction is largely administrative. For projects with documentation gaps or eligibility problems, it becomes more intensive.
The key difference from the PO:
The PO evaluates what the project has done. The Financial Officer evaluates what the project has spent. These are parallel reviews that happen simultaneously — and a project can receive technical approval from the PO while still having financial issues under review by the Financial Officer. Payment is only released when both reviews are complete.
The Legal Officer
The Legal Officer handles the contractual and legal dimension of the project — everything that involves changes to or interpretations of the Grant Agreement itself.
What they do:
- Process formal amendments to the Grant Agreement — changes to the work plan, budget structure, consortium composition, project duration, or specific conditions
- Review requests to add or remove consortium partners
- Manage the formal process when a beneficiary needs to be replaced or terminated
- Handle legal interpretations of GA clauses when the coordinator or a partner raises a question about what the agreement requires or permits
- Process force majeure notifications and related contractual adjustments
- Manage the legal aspects of IP ownership changes or licensing arrangements that affect the GA
When they appear:
The Legal Officer is not involved in day-to-day project management. They appear when something about the contractual structure of the project needs to change. In a well-run project that stays close to its original work plan and consortium, the Legal Officer interaction may be minimal — limited to routine amendments and minor adjustments.
In a project that experiences significant changes — a partner leaving, a major work plan revision, a dispute over IP — the Legal Officer becomes a critical interlocutor, and the quality of the legal documentation prepared by the coordinator directly affects how quickly and smoothly those processes are resolved.
What coordinators frequently misunderstand:
The Legal Officer manages the formal amendment process — they do not advise on whether an amendment is advisable, or on the legal implications of a decision the consortium has already made. Coordinators who approach the Legal Officer for strategic guidance on how to handle a contractual problem typically need to seek that guidance elsewhere — from their institution’s legal team, their National Contact Point, or specialist legal counsel.
How the three roles interact
In practice, these three roles function as a team within the agency, even if the coordinator interacts with them separately. A technical report submitted by the coordinator triggers a review process that involves all three: the PO assesses the technical content, the Financial Officer assesses the costs, and the Legal Officer is engaged if anything about the contractual structure needs adjustment.
For the coordinator, the practical implication is clear: communication with the Commission side is not a single channel. Different questions go to different people, and conflating their roles — asking the PO about a financial eligibility question, or copying the Legal Officer on routine progress communications — creates confusion and delays.
The coordinator who understands this structure, communicates through the right channels, and prepares submissions that address the concerns of all three roles simultaneously runs a smoother project than one who treats the Commission as a single, undifferentiated counterpart.
How Kronis supports Commission-side communication
Every interaction with the Project Officer, Financial Officer, and Legal Officer ultimately depends on the quality and completeness of what the consortium submits. Technical reports that accurately reflect Annex 1, financial statements that are clean and well-documented, and amendment requests that are formally complete — these are what determine how smooth or difficult those interactions are.
Kronis PMO structures day-to-day project execution around the Grant Agreement, so that when reporting time arrives, the evidence base for the PO’s technical review is already in place. Kronis Finance ensures that the financial records submitted to the Financial Officer are accurate, traceable, and audit-ready from day one.
Final thoughts
The Commission side of a Horizon Europe project is not a monolith. It is a structured team of specialists, each with a defined scope and a defined relationship with the consortium. Understanding who they are, what they do, and when they are involved is not just useful knowledge — it is the foundation of professional project management at the EU level.
The coordinators who work most effectively with the Commission are those who understand this structure clearly enough to communicate through the right channels, prepare submissions that address the right concerns, and build a relationship with their Project Officer based on transparency and reliability rather than on managing information flow.
EIC Advanced Innovation Challenges: the EIC’s newest funding instrument explained
RIA, IA and CSA: what are the different types of Horizon Europe actions?
