The Grant Agreement is signed. The project is live. And for most consortia, the kick-off meeting is the first moment the full partnership comes together as a working unit not as proposal writers, but as the people responsible for delivering what was promised.
It sounds like a formality. It is not. The decisions, made and not made, in the kick-off meeting shape how the project runs for the next three to five years. Getting it right is significantly cheaper than fixing the consequences of getting it wrong.
This article explains what a kick-off meeting is, what the Grant Agreement requires, what it should cover, and what distinguishes a well-run kick-off from one that leaves the consortium more confused than when it arrived.
What the kick-off meeting is
The kick-off meeting is the first formal meeting of the full consortium after the Grant Agreement enters into force. It marks the operational start of the project — the transition from the legal and administrative phase of Grant Agreement preparation to the practical phase of execution.
The Grant Agreement does not prescribe a specific format, date, or agenda for the kick-off meeting. What it does require is that the project is implemented as described in Annex 1 from the start date — which means the consortium needs to be operationally ready from day one. The kick-off meeting is the primary mechanism for achieving that readiness.
In practice, most consortia hold the kick-off meeting within the first two to three months of the project. Delaying it significantly beyond this creates a gap during which partners are unsure of their responsibilities, governance structures are not in place, and the project is running — in the Commission’s eyes — without having properly started.
What the Grant Agreement requires the consortium to have in place from the start
While the kick-off meeting itself is not a formal GA obligation, several things that it should establish are. Understanding these requirements explains why the meeting matters and what it must actually accomplish.
Governance structures. The GA requires the consortium to have a defined decision-making structure — typically a General Assembly and a Project Management Board or Steering Committee. These bodies must be operational from the project start. The kick-off meeting is where they are formally constituted and their procedures agreed.
The Consortium Agreement. The GA strongly recommends — and in practice requires in almost all cases — that a Consortium Agreement is in place before the project starts. The kick-off meeting is often the point at which the signed CA is confirmed across all partners, outstanding signature issues are resolved, and the internal rules it establishes are communicated to the full team.
Task ownership and work plan alignment. Annex 1 assigns specific tasks to specific partners. Every partner must understand, from the project start, what they are responsible for, what the deliverables and milestones in their work packages are, and what the timeline requires of them. This alignment does not happen automatically — it requires a structured conversation.
Communication and reporting procedures. The GA requires regular reporting to the Commission. But before the consortium can report externally, it needs internal procedures: how progress is tracked, how financial data is collected from partners, how deviations are escalated, and who is responsible for what at reporting time. The kick-off meeting is where these procedures are established.
Who attends
The kick-off meeting brings together the people who will actually run the project — not the full institutions, but the individuals responsible for delivering specific parts of it. In a typical Horizon Europe project, this means:
The coordinator leads the meeting and sets the agenda. This is their first major test as the operational centre of the consortium — how they run the kick-off signals to partners how the project will be managed for the next three to five years.
Work package leaders are the other essential attendees. Each WP leader needs to leave the kick-off with a clear operational picture of their work package: tasks, partners contributing, first deliverables, dependencies on other WPs, and the evidence they will need to maintain throughout execution.
Beyond that, most organisations send one or two representatives — typically whoever will be doing the actual project work, not senior management. The kick-off is an operational meeting, not a ceremonial one.
For a full breakdown of the roles within a Horizon Europe consortium — coordinator, WP leaders, beneficiaries and their respective responsibilities — see our article on how a Horizon Europe consortium works.
The Project Officer. Some coordinators invite the Project Officer assigned by the executive agency to attend. In practice, POs rarely attend — they manage large project portfolios and their presence is neither required nor expected. What is expected is that the coordinator establishes contact with the PO before the kick-off, agrees on expectations for the project’s first months, and informs them of the meeting date. A brief introductory call with the PO before the kick-off is more realistic and often more useful than an invitation to attend.
Financial representatives. Given that financial compliance begins from the first day of the project, having at least one person per organisation who understands cost eligibility, time recording requirements, and financial reporting procedures is important — whether that is a dedicated finance contact or the WP leader themselves.
Communication and dissemination WP leader. The communication work package typically has early deliverables — a project website, a communication plan, initial dissemination activities. Involving the communication WP leader from the outset ensures these activities start on time and are aligned with the consortium’s messaging.
What the kick-off meeting should cover
A well-structured kick-off meeting covers five areas. Each one addresses a specific operational risk that, left unresolved, creates problems over the project lifetime.
1. The Grant Agreement and Annex 1
Every partner needs to understand the legal framework they are operating under. This does not mean reading the GA in its entirety during the meeting — it means ensuring that key obligations are communicated clearly: the project timeline, the reporting periods, the cost eligibility rules, the audit exposure, and the consequences of non-compliance.
Particular attention should be given to Annex 1 — the Description of Action. This is the document that defines what each partner must deliver, by when, and with what outputs. The kick-off meeting is the moment to confirm that every WP leader and every partner understands their specific commitments under Annex 1 — not as proposal text, but as legal obligations.
2. Work package structure and task ownership
The work package structure defined in Annex 1 needs to be translated into operational clarity. Who leads each WP? Who contributes to which tasks? What are the first deliverables due, and when? What are the dependencies between work packages?
This conversation needs to happen in the room, with all relevant partners present. Assumptions that existed during proposal writing — about who would do what, how tasks would be split — need to be confirmed, clarified, or corrected before work begins.
3. Governance and decision-making
How will the consortium make decisions? Who has voting rights in the General Assembly? How are disputes escalated? What happens when a partner falls behind?
The governance structures defined in the Consortium Agreement need to be operationalised — not just documented. The kick-off meeting is where the Steering Committee is formally constituted, its meeting cadence agreed, and the escalation pathway explained to all partners.
4. Financial procedures and time recording
Financial compliance begins from the first day of the project. Partners need to understand, from the kick-off:
- Which costs are eligible and which are not
- How time recording works — the requirement for individual timesheets linked to specific work packages, maintained contemporaneously
- How financial data will be collected for reporting — who submits what, in what format, by what internal deadline
- What documentation must be maintained for audit purposes — and for how long
Partners that leave the kick-off meeting without a clear understanding of these requirements will begin incurring costs in ways that may not be compliant. By the time the first reporting period arrives, correcting months of incorrect time recording or missing documentation is difficult and sometimes impossible.
5. Communication and collaboration tools
How will the consortium communicate day to day? Where will shared documents be stored? How will deliverables be submitted internally for review before being uploaded to the EU Funding and Tenders Portal? How will the coordinator track partner progress between reporting periods?
These decisions seem operational and minor. In practice, a consortium that does not agree on these procedures at the start defaults to email and shared drives — and the fragmentation, version control problems, and documentation gaps that follow are among the most common causes of reporting difficulties.
The kick-off meeting as an evidence document
One aspect of the kick-off meeting that is often overlooked: it generates evidence. The minutes of the kick-off meeting — who attended, what was discussed, what was agreed — are part of the project’s documentary record. In the event of a project review or audit, they demonstrate that the consortium was properly constituted, that governance was established, and that partners were informed of their obligations from the start.
Meeting minutes should be circulated, reviewed, and formally approved by all partners within a defined period after the meeting. They should record not just what was presented, but what was decided — and who is responsible for each action.
The most common kick-off meeting mistakes
Treating it as a presentation, not a working session. A kick-off meeting where the coordinator presents to partners for two days and partners leave without having actively engaged with their specific responsibilities is not a kick-off meeting — it is an orientation session. The meeting must produce decisions and commitments, not just information transfer.
Not contacting the Project Officer beforehand. Before the kick-off, the coordinator should establish contact with the Project Officer, agree on expectations for the project’s first months, and brief them on the consortium’s plans. This working relationship pays dividends throughout the project.
Skipping the financial session. Partners are often reluctant to spend kick-off time on financial procedures. The result is predictable: by month six, time recording is inconsistent, documentation is incomplete, and the coordinator is managing a compliance problem that should have been prevented on day one.
Not confirming Consortium Agreement signatures. The CA governs the internal relationships of the consortium. If it has not been signed by all partners at the time of the kick-off — which is more common than it should be — resolving outstanding signatures must be an explicit agenda item, with a clear deadline.
No follow-up documentation. A kick-off meeting without formal minutes, confirmed action points, and a clear communication plan is a meeting that happened but left no trace. The project’s institutional memory begins here.
How Kronis PMO supports post-kick-off execution
The kick-off meeting establishes the operational foundation. What happens next determines whether that foundation holds.
Kronis PMO provides the shared management layer that takes over from the kick-off meeting — translating the work packages, task assignments, and deliverable commitments agreed in the room into a live operational system that all partners can access. From the day after the kick-off, every partner knows what they are responsible for, what is due when, and what evidence they need to maintain. The coordinator has visibility across the full consortium without relying on email updates.
For coordinators who invest in a well-run kick-off meeting, Kronis PMO ensures that investment is not lost in the weeks that follow.
Final thoughts
The kick-off meeting is the first test of whether a consortium is operationally ready to deliver what it promised. The Grant Agreement does not prescribe its format — but it creates obligations that the kick-off meeting must put in place. Governance, task ownership, financial procedures, communication systems — these are not details to be sorted out later. They are the foundation on which the next three to five years of execution will rest.
The best kick-off meetings are not the most elaborate ones. They are the ones that leave every partner clear about what they are responsible for, how decisions will be made, and what the first three months of the project look like in practice.
What is a Horizon Europe mission and how is it different from a standard call?
Open access in Horizon Europe: what it requires and what happens if you don’t comply
