Coordinating a Horizon Europe proposal, the part that is not writing

Ask anyone who has coordinated a Horizon Europe proposal what the hardest part was, and very few will say the writing. There are guides, templates and courses for the writing. What almost nobody prepares you for is the job a coordinator actually does, which is not writing at all: it is pulling one coherent proposal out of ten or more partners, each with different priorities, different writing styles and different native languages, before a hard deadline. A consortium of that size, without strong central coordination, drifts into a fragmented document. This page is about that job, the recurring pains that come with it, and what actually reduces them. It is part of our guide on how to write a winning Horizon Europe proposal.

We have interviewed coordinators, grants officers and freelance grant writers about how consortium proposals actually get built. The same five pains came up again and again. If you have coordinated even one proposal, you will recognise most of them.

1. Getting partners to commit and contribute at all

Before a single section is written, the coordinator is already selling the project internally. Coordinators told us the first battle is simply to attract and involve partners, and to secure enough budget share for each of them to keep them motivated. Others described partners who "need more convincing" and want support just to be onboarded.

This is invisible work. It does not appear in any proposal template, yet it decides everything that follows: a partner who was never really convinced will be the partner whose contribution arrives late, thin, or not at all. The coordinator spends the first weeks of the proposal not writing, but negotiating attention.

2. Contributions that arrive late, verbose, or off-spec

When contributions do arrive, they are often not what was asked for. One coordinator told us their single most time-consuming problem was partners producing low-context, verbose text: a partner team that spent two hours on paragraphs that should have taken five minutes, because they did not know what shape the contribution needed to have.

The other recurring complaint is length. Partners do not respect the word and length guidelines, so the coordinator has to cut everything back to fit the page limit. And the limit is real: Part B is capped at 40 pages for a RIA or IA, 45 for lump-sum calls (see the Part B template for how those pages are structured). Every partner writes as if their section were the only one, and the coordinator does the trimming nobody else will do.

3. Tool resistance and scattered work

Coordinators repeatedly told us the hardest thing is that partners will not adopt a shared tool. Whatever platform the coordinator proposes, half the consortium keeps working the way they always have. So the work falls back to the lowest common denominator: a shared spreadsheet used as a task list, a shared drive full of versions, and a group chat where decisions sink out of sight.

The result, in the words of the coordinators who live it, is getting "lost in all the documents" on the drive. There is no single source of truth. There is no reliable view of who has done what. The coordinator becomes the only person who holds the state of the proposal in their head, and holds it imperfectly, because the state is spread across three tools and forty files.

4. Merging a dozen hands into one voice

This is the heaviest load, and the least visible from outside. Ten partners produce ten sections in ten styles. Some write in long academic paragraphs, some in bullet points, some in English that needs reworking. The coordinator has to make all of it read as one document, written by one team, with one argument running through it.

An experienced freelance grant writer we spoke to called the intelligent merging of partner contributions the single biggest structural problem in a consortium proposal. Not the science, not the budget: the merging. Because a patchwork reads as a patchwork, and no evaluator has ever mistaken one for a coherent plan.

5. Propagating one change everywhere

The last pain arrives late, which is exactly when there is no time for it. One partner changes an objective, a KPI, a work package or a budget line, and the change does not stay where it was made. The coordinator has to carry it through every section that depends on it, so that the objectives, the tables and the impact story still agree with each other.

Under deadline pressure, this coherence tax is where consistency quietly breaks. A number is updated in one table and not in the other. An objective is renamed in section one and keeps its old name in the work plan. Nobody decided to let the proposal contradict itself; it happened because one change had six homes and only three of them were found.

Why this is a proposal-quality problem, not just admin

It would be a mistake to file all of this under project administration. A fragmented document does not just cost the coordinator sleep, it costs points. Evaluators read a proposal written by twelve hands and feel the seams: objectives that do not match the tables, an impact story that does not line up with the work plan, the same term used three different ways in three sections. Coordination is not clerical, it is part of how the proposal scores, because coherence is part of what is being judged. The recurring, visible-to-evaluators version of this problem is catalogued in typical mistakes in Horizon Europe proposals.

What actually reduces these pains

None of this is solved by working harder. Coordinators already work hard. What changes the shape of the job is changing where and how the work happens.

• One shared workspace instead of a drive, an inbox and a group chat. The proposal, the partners and the work live in one place, so nothing is "lost in the documents" and the coordinator stops being the only holder of the current state.
• Structured elements and clear assignments. Each partner knows exactly what to produce and in what shape: this objective, this work package description, this length. Knowing the shape in advance is what turns a two-hour paragraph back into a five-minute one.
• Inline guidance while a partner writes. The Grant Coach sits next to the text as the partner works, so a contribution arrives usable rather than as raw material the coordinator has to rewrite from scratch.
• Comments and discussions anchored to the text. Feedback to a partner lives next to the sentence it is about, not buried in an email thread that half the consortium never opens.
• A collaboration hub that shows who has done what and what is still missing, so the coordinator can see status at a glance instead of chasing partners one by one.

To be honest about what this does and does not do: it does not remove the coordinator's judgement. Someone still decides what the proposal argues, which contribution stays and which is cut, and how the pieces fit. What it removes is the chasing, the scattered files, and the rewriting-from-scratch, which is to say most of the part of the job that was never really the job.

Coordinate your next proposal in one shared workspace, and spend the last week before the deadline on the argument, not on chasing contributions.

Part of our guide on how to write a winning Horizon Europe proposal. See also the Part B template, section by section.