Grant Agreement Preparation (GAP) often starts with a sense of relief.
The proposal has passed evaluation, the invitation has arrived, and the project feels secure. This is also the point where projects begin to lose time and room to manoeuvre. GAP compresses legal, financial, and technical decisions into a short window. During this phase, the evaluated proposal is converted into a legally binding Grant Agreement (GA). Once signed, its articles and annexes govern reporting, payments, amendments, and audits for the entire project duration. Assumptions that remain unclear at this stage are rarely neutral. They become obligations.
The patterns below come directly from EC Horizon Europe implementation trainings and agency guidance. They reflect recurring points where consortia run into avoidable friction during GAP, often without realising the long-term impact until implementation has started.
Why GAP changes the balance of control
Before signature, the project exists only in theory. During GAP, that theory turns into a contract.
Annex 1 (Description of Action) and Annex 2 (Estimated Budget) are not administrative attachments. They define what the consortium commits to deliver, how resources are allocated, and how performance will be assessed. Once signed, correcting inconsistencies or unclear commitments requires formal amendments. From the side of the EC, GAP is used to confirm that the project can be implemented as written. From the consortium side, it is often treated as structured data entry. That difference in perspective explains many of the issues that surface later. Below we detail 6 common risks consortia face during GA preparation.
Risk 1: Treating GAP as administration rather than contract finalisation
GAP work is frequently concentrated with a single coordinator or project manager. Partners send inputs independently, assuming that technical and operational questions were settled during proposal writing. During GAP, the focus shifts. Decisions no longer affect evaluation outcomes; they define contractual precision. If deliverables, responsibilities, or effort allocations are accepted without full internal alignment, they become binding commitments. These issues rarely disappear. They tend to reappear months later as reporting clarifications, amendment requests, or audit findings.
A simple check helps here. If no one has reviewed the full Grant Agreement package end to end, including annexes, GAP is being handled as a clerical task rather than a contractual one.
Risk 2: Inconsistencies between Part A and Part B of Annex 1
EC project implementation trainings repeatedly warn against duplicated or misaligned information between Part A, entered in the IT system, and Part B, submitted as the narrative Description of Action. Part A is designed to be updated during the project lifecycle. Part B often is not. When the same information appears in both places and later diverges, the Grant Agreement may contain conflicting obligations. This is common with partner lists, work packages, deliverables, milestones, and effort distribution.
These inconsistencies usually remain unnoticed until an amendment, review, or audit forces a close reading of the contract. At that point, correcting them becomes procedurally heavy.
If information appears in both Part A and Part B and alignment is postponed, the exposure already exists.
Risk 3: Ethics, security, and eligibility checks during GAP
Ethics assessments, security scrutiny, and eligibility checks continue during GAP. They do not stop at evaluation. When issues are identified at this stage, requirements may need to be fulfilled before signature, delaying the Grant Agreement. Other requirements may be added directly to the contract, sometimes generating additional work packages or deliverables through the system. Eligibility conditions, including Gender Equality Plan requirements where applicable, must be met by the time of signature. Proceeding without them is not possible.
When these obligations are introduced during GAP, they shape implementation from day one. They often resurface later as reporting requirements or mandatory deliverables, with limited scope for reinterpretation.
Risk 4: Legal and financial validation for newcomers and coordinators
Legal entity validation, ownership control checks, and financial capacity assessments are often triggered late in GAP. This usually happens because thresholds or preparation steps were underestimated. Agency guidance is clear on the consequences. Financial validation is mandatory above defined grant thresholds. Beneficiaries that are not validated cannot accede to the Grant Agreement. In some cases, the Grant Agreement may be signed without a partner, with accession handled later through an amendment if permitted.
These situations delay pre-financing and complicate early project coordination. When a partner’s validation status remains unresolved close to GAP submission deadlines, signature timing is already under pressure.
Risk 5: Assumptions about deliverables and resource flexibility
Requests for additional deliverables during GAP often come as a surprise. So does the clarification that certain cost eligibility options cannot be changed. Some deliverables, such as data management plans or dissemination and exploitation plans, are standard Horizon Europe obligations. Ethics or security reviews may add further deliverables or even additional Work Packages. Cost options are defined in call conditions and selected at proposal stage; they generally cannot be altered during GAP.
Misunderstandings at this point tend to surface later as amendment requests rather than discussions. By then, flexibility is limited.
Risk 6: Coordination and responsiveness during GAP
Delays that can be prevented by the consortium, frequently stem from missed Declarations of Honour, late accession forms, unclear division of responsibilities, or slow responses to Project Officer requests. GAP tasks run in parallel across beneficiaries. One missing action can block the entire consortium and delay signature. Official guidance frames GAP as a cooperative process that relies on timely, coordinated input across partners.
How experienced consortia approach GAP
Consortia with repeated Horizon Europe experience approach Grant Agreement Preparation with a clear sense of prioritisation.
Some issues determine whether the Grant Agreement can be signed at all: unresolved validations, missing eligibility requirements, or inconsistencies that prevent contractual alignment. Other issues do not block signature but tend to surface later, during reporting periods, amendments, or audits, when correcting them becomes slower and more resource-intensive.
Experienced coordinators account for both.
They begin GAP with a consolidated internal review of Annex 1 and the budget, focusing first on elements that affect signature readiness. Clear and frequent communication with partners is a must. Ownership for technical, legal, and financial inputs is assigned explicitly. Questions are raised early with the Project Officer to confirm constraints while there is still room to clarify them. Decisions taken during GAP are treated as long-term commitments, not short-term formalities.
The difference is rarely knowledge of the rules. It is timing.
Before signature, alignment mainly costs time and coordination. After signature, the same issues often require amendments, delayed payments, or corrective action across the consortium. GAP is the last phase where clarity can be established with relatively low administrative cost.
This is why many consortia choose to involve dedicated project management support during Grant Agreement Preparation, particularly when coordinating multiple beneficiaries or entering Horizon Europe for the first time. Further details on how Future Needs supports coordinators during GAP and early implementation can be found here.
About the authors
Anna Palaiologk, the founder of Future Needs, is a Research & Innovation Consultant with 18 years of experience in proposal writing and project management. She has worked as a project Coordinator and Work Package leader in 30+ EU projects and has authored 50+ successful proposals. Her research background is in economics, business development and policy-making. Email Anna at anna@futureneeds.eu.
Chariton Palaiologk, the Head of the EU Project Management Team, is currently leading the project management of 10+ EU-funded projects. He has a background in data analysis and resource optimisation, having worked at the Greek Foundation for Research and Technology. Email Chariton at chariton@futureneeds.eu.
Thanos Arvanitidis is a Researcher & Innovation Project Manager, with a background in physics and biomedical engineering. He manages EU-funded research projects from initial conception through to implementation, working across key Horizon Europe clusters, including Cluster 1: Health; Cluster 4: Digital, Industry & Space. His expertise spans AI, healthcare, cybersecurity, and digital education. Email Thanos at thanos@futureneeds.eu.
