We All are Europe - AESAEC

However, at the same time you need to describe and explain a complex topic, involving
several partners and using a multi-level project process. This does all require a certain
amount of space – so do not be too brief either! Such catch 22 situations are not unusual
when writing a project application!
Do not be afraid to use technical / professional terms as they underline your expertise,
which is quite important too. However, do not overdo it and make sure the reader knows
what is meant by them.
For the same reason also try to structure your text properly, e.g. you can make your key
messages clear by underlining, -) listing or writing in bold.
Also redundancies are recommended but you will be in trouble if you push too hard. It is
fine to remind the evaluator from time to time what the main ideas and outputs of your
project are but he / she must not get the impression that you have run out of ideas and are
simply repeating things previously stated in the application.
The application must be of the highest possible linguistic quality (grammar, orthography,
expression etc.); regardless of fairness, it gives a poor impression if you are not able to
write your application properly. Of course, an evaluator should not judge this aspect; however
he / she may unknowingly become negatively influenced if it is poorly written.
Further to what was said before, it makes sense for somebody with a high level of language
skills and who has not yet been involved in the proposal writing to check through the application
and improve the linguistic level – thus you have quality control over the linguistic
quality as well as over the content and structure.
Try to entertain the evaluator as best you can, meaning to make him / her interested in
reading the proposal, to feel the spirit of the project group and to connect with your undertaking.
After going through your proposal, the evaluator should have the feeling of having
heard something new or even having learnt something new, and that your proposal is worth
spending money on. This is a very important point for your project’s summary, which is usually
on one of the first few pages of a proposal.
Try to be definite about your planned activities, and do not put them into questions, e.g.
we will do…, we will organise … and not: we might do …, very likely it will be organised …).
If you are not convinced of what will happen in your project how should the evaluator be
However, do also try to be as objective as possible when explaining your project and the
problems / circumstances relating to why the project is necessary. The evaluator must not
think that you are the only person who thinks positively about your project but that there is
a general need for it. Therefore, persuade with expressions like As commonly known … or
With regards to recent studies … instead of I am strongly convinced that … or We think it
would be the best that … Of course your opinion and expertise also count in the evaluator’s
eyes, but do try to underline them by using publications, bulletins, studies, media releases
etc.
Make sure you always indicate the most relevant information concerning your proposal (particularly
in the summary); usually you simply need to follow the most important question
words (also called W words), which are:
What
Why
Who
Where
When
90