The application form trap: why starting there ruins the proposal

The scene repeats itself. The call opens, someone forwards it around, the team gets excited, they open the guide PDF, download the official form and start filling it in. Box by box. General objective, specific objectives, target group, work packages, indicators. By the time they reach the impact section, they are exhausted, and that explains why it gets written like a hurried dessert at the end of a long dinner.

The error is not in filling out the form. It is in starting there.

The form is not a design tool

An Erasmus+, Horizon Europe or Global Gateway form is built around a clear logic: to allow an external evaluator, who does not know your organisation or the territory where you work, to compare your proposal against five hundred others using the same criteria. The boxes are uniform. The word limits are rigid. The structure is what it is because the institution needs comparability, not because it is the best way to think a project through.

If you open the form first, what you are actually doing is adopting the evaluator’s logic before having thought as an organisation. You start trimming your idea so it fits the boxes. You start using the call’s vocabulary without having decided first whether that vocabulary describes anything real your team can deliver.

Three things that get lost when you start with the form

What is distinctive. Every organisation has a history, a network of relationships, a way of working that makes it different from the others. When the first step is completing standard boxes, that texture flattens. Proposals submitted in the same round tend to look alike because they were all written staring at the same form. The evaluator, who reads twenty proposals in a row, remembers the ones with their own voice. The others blur together.

The connection with what we already do. A project that does not connect with what the organisation is already doing is hard to sustain after the grant ends. But the form does not ask that explicitly. It asks for activities, deliverables, indicators. And so it is easy to end up designing a project that closes neatly on paper, but that lives inside the organisation as a foreign body nobody wants to maintain when the money runs out.

Room to think about what is realistic. Filling boxes has a curious psychological effect: it invites you to put in big numbers and broad promises, because empty space looks better when filled. The question “what can we actually sustain with the team and resources we have?” does not appear on the form. It has to appear before.

Three questions to answer before touching the form

When we support an organisation through an application, the first thing is not to open the Word document. It is to sit down and answer three questions, honestly, in a team session.

What realistic impact can we generate, given what we already know how to do? Not the impact we would like to declare so it sounds good. The one we can actually defend in front of a panel of evaluators who ask for evidence. If the answer is modest, even better. A modest, deliverable promise is worth more than a grandiose, suspect one.

How does this project connect with what we are already doing, or are we forcing a connection? This question separates projects that strengthen an organisation from projects that disrupt it. If the project extends, deepens or expands something already in motion, there is a base for it to survive past the funding. If it is an opportunistic move to win the grant, it most likely ends up as an orphan annex inside the organisation.

What is original or irreplaceable about how we approach this, that another organisation could not copy? This is the most uncomfortable question and the most useful one. It forces you to articulate the real value proposition, not the generic version that any competent team could write. If we cannot find an answer, the problem is not in the writing. It is in the design.

The form comes after

When those three questions have answers, opening the form is a technical act, not a creative one. The form becomes a container where you pour in a proposal that already exists outside of it. The boxes fill quickly because the proposal is already thought through. And, most importantly, the boxes do not distort the thinking, because the thinking is already finished.

When those questions have no answers and the form comes first, the opposite happens: the proposal ends up looking like the form. Generic, flat, voiceless. Indistinguishable from the other five hundred the evaluator is going to read.

Why it matters for LAC applicants

For Latin American and Caribbean organisations applying to European funds, this is doubly critical. Cultural, linguistic and administrative distance already creates a barrier. If on top of that the proposal is written directly on the form, what reaches the evaluator is an impoverished version of what the organisation can actually contribute.

Institutional originality, connection to territory, the specific way a team understands a problem from its context, are precisely the assets that can make a proposal from Chile, Colombia or Mexico stand out among European ones. But those assets do not fit in a box. They have to be articulated first, and only then decide how they enter the form.

At 2811, when an organisation comes to us with the form already started, the first thing we do is close it. We go back to the three questions. Most of the time, the proposal changes. And it improves.

---

This post is part of a series on designing proposals for European funding. Related reading: Theory of Change, defining impact before application.